Comments on: Standards Cage Match http://maisonbisson.com/blog/post/11171/standards-cage-match/ A bunch of stuff I would have emailed you about. Wed, 04 Nov 2009 23:52:48 -0800 http://wordpress.org/?v=2.8.4 hourly 1 By: Caveat Lector » Blog Archive » Things I can’t ask Lorcan Dempsey http://maisonbisson.com/blog/post/11171/standards-cage-match/comment-page-1/#comment-349722 Caveat Lector » Blog Archive » Things I can’t ask Lorcan Dempsey Sat, 27 Jun 2009 05:13:04 +0000 http://maisonbisson.com/blog/?p=11171#comment-349722 [...] Bisson’s point about library standards hemming us in? I’m really, really feeling it right now. We can’t even translate our own standards to [...] [...] Bisson’s point about library standards hemming us in? I’m really, really feeling it right now. We can’t even translate our own standards to [...]

]]> By: The ILS Brick Wall « MaisonBisson.com http://maisonbisson.com/blog/post/11171/standards-cage-match/comment-page-1/#comment-44948 The ILS Brick Wall « MaisonBisson.com Tue, 13 Jun 2006 18:14:42 +0000 http://maisonbisson.com/blog/?p=11171#comment-44948 [...] Coincidentally, I’ll be at AALL next month. My presentation will focus on the things we can do once we overcome the problems Nicole describes, but my concordance with her point should be clear (see previous posts one, two, three). [...] [...] Coincidentally, I’ll be at AALL next month. My presentation will focus on the things we can do once we overcome the problems Nicole describes, but my concordance with her point should be clear (see previous posts one, two, three). [...]

]]> By: Native To Web & The Future Of Web Apps « MaisonBisson.com http://maisonbisson.com/blog/post/11171/standards-cage-match/comment-page-1/#comment-33498 Native To Web & The Future Of Web Apps « MaisonBisson.com Thu, 16 Mar 2006 22:23:45 +0000 http://maisonbisson.com/blog/?p=11171#comment-33498 [...] Don’t re-invent the wheel [link added –Casey]. [...] [...] Don’t re-invent the wheel [link added –Casey]. [...]

]]> By: Michael Fagan http://maisonbisson.com/blog/post/11171/standards-cage-match/comment-page-1/#comment-32140 Michael Fagan Fri, 24 Feb 2006 19:52:45 +0000 http://maisonbisson.com/blog/?p=11171#comment-32140 Oh, one thing I forgot to mention, since we're discussing conversions. This XSLT http://opensearch.a9.com/xslt/generic.xsl provides a nice template for converting any XML into OpenSearch. Oh, one thing I forgot to mention, since we’re discussing conversions. This XSLT http://opensearch.a9.com/xslt/generic.xsl provides a nice template for converting any XML into OpenSearch.

]]> By: Davey P http://maisonbisson.com/blog/post/11171/standards-cage-match/comment-page-1/#comment-32105 Davey P Thu, 23 Feb 2006 22:15:45 +0000 http://maisonbisson.com/blog/?p=11171#comment-32105 Excellent post Casey! For me, one of the advantages in going for a REST style interface was that I can litter the XML with things like copy specific information, circulation stats, and borrowing suggestions (based on previous circulation history) - e.g.: http://161.112.232.203:4128/rest/record/id/258223 Hopefully one day soon we'll also have user supplied tags and comments in the output too! :-) The challenge (for me at least) is more about getting the information from the ILS in the first place -- once you can do that, you can squeeze it into whatever output format/standard you want. Excellent post Casey!

For me, one of the advantages in going for a REST style interface was that I can litter the XML with things like copy specific information, circulation stats, and borrowing suggestions (based on previous circulation history) – e.g.:

http://161.112.232.203:4128/rest/record/id/258223

Hopefully one day soon we’ll also have user supplied tags and comments in the output too! :-)

The challenge (for me at least) is more about getting the information from the ILS in the first place — once you can do that, you can squeeze it into whatever output format/standard you want.

]]> By: Michael Fagan http://maisonbisson.com/blog/post/11171/standards-cage-match/comment-page-1/#comment-32091 Michael Fagan Thu, 23 Feb 2006 18:14:02 +0000 http://maisonbisson.com/blog/?p=11171#comment-32091 I definitely agree with your main point. The library community needs to start taking more advantage of the wider community. This isn't to be saying that they haven't been doing great work, of course. > get a detailed record for each result (not possible with OpenSearch) sure it is. the whole point of OpenSearch is that it is XML and all aspects are extensible. Go ahead and stick any namespaced elements in anywhere. A big part of moving from 1.0 to 1.1 was to not just make extensions possible, but to make them simpler to make use of (eg with the Query element - and thanks for the compliment). I'm not saying anything against SRU or anything else here, just making a point about OS ;-) Heck, since it's XML you could go ahead and use an opensearch:Query element inside SRU if you wanted to. That's what XML is all about. OpenSearch is clearly a read-API tool. So you could use it (ignoring privacy issues for the moment) to request what books a user has taken out ( example.com/opac/books-taken-out?user={lib:username} ). I think a big misconception about OpenSearch is that it's some sort of API. I think of it more as a container/framework for any read-based-API. Anything that can be queried (ie. at least one variable in the request) can have an OpenSearch Description, and anything that returns a list can have an OpenSearch Response. Add in OpenSearch Query and autodiscovery, and things start getting very neat :-) I definitely agree with your main point. The library community needs to start taking more advantage of the wider community. This isn’t to be saying that they haven’t been doing great work, of course.

> get a detailed record for each result (not possible with OpenSearch)

sure it is. the whole point of OpenSearch is that it is XML and all aspects are extensible. Go ahead and stick any namespaced elements in anywhere. A big part of moving from 1.0 to 1.1 was to not just make extensions possible, but to make them simpler to make use of (eg with the Query element – and thanks for the compliment).

I’m not saying anything against SRU or anything else here, just making a point about OS ;-)

Heck, since it’s XML you could go ahead and use an opensearch:Query element inside SRU if you wanted to. That’s what XML is all about.

OpenSearch is clearly a read-API tool. So you could use it (ignoring privacy issues for the moment) to request what books a user has taken out ( example.com/opac/books-taken-out?user={lib:username} ).

I think a big misconception about OpenSearch is that it’s some sort of API. I think of it more as a container/framework for any read-based-API. Anything that can be queried (ie. at least one variable in the request) can have an OpenSearch Description, and anything that returns a list can have an OpenSearch Response. Add in OpenSearch Query and autodiscovery, and things start getting very neat :-)

]]>