...
Tom said that he got an initial response from Jeannie at Atlas Systems to his inquiry about improving the staff interface by enhancing the Z39.50 search interface. Jeannie initially said she would discuss this with the development team and get back to Tom, but hasn't done so yet.
...
Tom presented options we discussed in previous meetings to Access Services. His summary of the feedback he received:
As a side note, and something for everyone to chew one.. I ran some of the ideas past the Ares focus group and they liked them all.. the one thing that was emphasized was that they really need the full functionality of the Voyager catalog. This was demonstrated by Cyannea (sorry if that is spelled wrong) from Music. They like the idea of possibly having a search button on the submission form but where afraid that a system using the XML services would be to limiting.
Based on this, Tom started experimenting with an Ares update, that he demo'd for us at today's meeting. Tom added a link within the Ares interface that opens the Voyager Web interface in a jQuery grey box. The obstacle this uncovered is that interaction between Ares and either the Voyager patron Web interface or Web Services are in HTML and XML respectively and can't be accessed across domains. There is a plain text print/save version of the records, but this may not be easy to manipulate with jQuery. The Voyager Web Services do not produce JSON output that we could access across domains with JSONP.
...
We have test systems for both Atlas and Voyager, so we can fully evaluate both options.
Action Items:
| Excerpt |
|---|
Tom will email Jennifer to see if anyone else is using a proxy server, or some kind of pass through script for this type of specific purpose, how did they do it, what were issues encountered, etc. Tom will get URLs to Rick that need to be proxied. (DONE):
Rick will send Tom URL to Voyager Web Services documentation. Adam will set up meeting for late next week to assess progress on these scenarios. |
...