Hi, On Mon, Aug 24, 2009 at 4:10 PM, Melissa Belvadi<[email protected]> wrote: > Sorry for a dumb question, but is it appropriate to ask a federated search > vendor to create a target connector for our EG 1.4 catalogue using OpenSRF > instead of Z39.50? > Or is OpenSRF only good for passing information about known items?
It would be possible in principle for a federated search vendor to write an OpenSRF connector - as far as I know, all of Evergreen's search functionality can be accessed via OpenSRF calls - but for basic bib searching and guaranteed compatibility with future versions of Evergreen, they're almost certainly better off using Z39.50. If they're looking for a lighter-weight protocol, they could go through Evergreen's OpenSearch interface. Is there something specific that the federated search vendor is trying to do that would not be handled by Evergreen's default Z39.50 service? Regards Galen Charlton Equinox
