Hi Antranig,

You could use the exhibit id from the McCord feed as a domain-specific stable key.

Cheers,
Hugues

Antranig Basman wrote:
I might have broken this myself by recent changes... but my best impression is that a few (one?) of the Couch views are not functioning correctly, perhaps as a result of the "always output strings" changes of this evening.

The following URL is one of those issued to Couch - intermittently I managed to get a version of it issued by the system that was actually encoded in ISO-8859 but this seems to have now passed.

http://142.150.154.59:5984/mccord_exhibitions/_design/exhibitions/_view/view?key={"title":"Simply%2BMontr%25C3%25A9al%253A%2BGlimpses%2Bof%2Ba%2BUnique%2BCity","lang":"en"}

The return value from Couch is
{"total_rows":10,"offset":8,"rows":[]}

I should mention that this is an entirely unsatisfactory kind of URL but I guess we have known this for a while - I have tried to make the barest beginnings this evening to a more reasonable way of mapping state onto a URL space but it will have to wait till post-pilot to see more work.

Could I suggest in the meantime that instead of issuing titles in URLs we instead use document UUIDs, which will head off risks of encoding issues of this kind? Titles are not a stable element of the data domain. In truth, we should be deriving a proper domain-specific stable key, but I don't know enough about the McCord set to find this right now.

Also, that this URL should be redesigned to read
http://142.150.154.59:5984/mccord_exhibitions/_design/exhibitions/_view/view?key=docID&lang=en

Apologies if I broke this view myself, I scratched my head a while about it :P

Cheers,
Antranig.
_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work
.


_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work

Reply via email to