explore potential to build search index in Pigeon Optics as a view

[Bluebie]

Pigeon Optics, the new database project I'm building to make auslan datasets more easily available and accessible, has a map reduce view system, a little bit similar to couchdb.

PO can input and output CBOR. It feels plausible that search index could be a PO view in the future, eliminating the need for cron jobs to rebuild find-sign's index.

It could also hotlink videos right out of PO's attachment store.

Upsides:

• sign-search becomes much simpler in implementation. It's only job is to query, rank, and display results. All server side work moves to PO's responsibility.
• Easier to fork, mess with the ranking, play and experiment, without needing to wrestle with large amounts of data to get things working.

Downsides:

• find-sign would lose it's tenuous compatibility with dweb distribution, becoming dependant on an application server. Possibly the data could be cached to disk and deployed to dweb, but it becomes more complex than mirroring a filesystem. None of the dweb stuff works properly today, so this shouldn't be a high priority.
• It would be more involved and difficult to mirror find-sign, to make a fully functioning interactive local backup.
• How stable is Pigeon Optics anyway?
• Is this just more of a Rube Goldberg machine, yet more things in the pipeline that can fail and crash and bring the whole site down?