Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

November 19, 2010

Tom met with Bill Klinko: we can add Ares server to DNS database: reserves.library.cornell.edu so he is then able to pull in JSON from Voyager into Ares without cross domain security issues.

Tom will arrange this with Bill Klinko.

Tom will ask Todd in meeting about creating BlackBoard building blocks and about changing BlackBoard Building Block settings for DNS change.

We may have to make changes in our sites and services too (probably not on CUL site). May affect John's services, Tom will discuss with John. Vanilla registrar services works well for Tom's current needs.

Do at end of classes, early-mid December, because it is a server wide change, potentially large impact.

Tom can continue developing with local data in the meantime.

On Z 39.50 question, still no response from Ares. Michael with others to email Atlas with ultimatum on support items, or contract will be pulled next year. Will reference Z 39.50 issue.

Action Items:

Tom:

  • Tom will arrange DNS change for reserves.library.cornell.edu with Bill Klinko.
  • Tom will ask Todd in meeting about creating BlackBoard building blocks and about changing BlackBoard Building Block settings for DNS change.
  • Continue developing interface with local data.

November 9, 2010

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.

...

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):

The current domain for all the Ares urls is:
https://cornell.ares.atlas-sys.com

The pdfs are transported using the following URL:
https://cornell.ares.atlas-sys.com/ares/ares.dll?SessionID=C102120752F&Action=10&Type=10&Value=23388

It does look like all the PDF's are renamed to ares.pdf

As a side note it does appear that you can link directly to an item's PDF using the following URL format:
https://cornell.ares.atlas-sys.com/ares/ares.dll?Action=10&Type=10&Value=23388

where the Value = the item's ID number. I am not sure what happens for new users to the system, but for existing users you are passed the PDF.

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.


October 27, 2010

(Much of the discussion of the meeting is reflected on the main page for this project, specifically, in the Goals, Scenarios to evaluate->Evolving recommendation, Aspects sections.

...