Points of Harmony

  • Similar process/procedures
  • Common systems - Serials Solutions (360 Link, Summon, MARC updates service), Voyager (almost same version), EZ-Proxy.

Points of Discord

  • How reports come in.  Source of reports.  Similar kinds of reports, but different sources and different information gathered from user.
  • Content of typical initial reports - Columbia gets permissions, Cornell does not. 
  • Access to information: permits/permissions, EZ Proxy updates,
  • Different systems - III-ERM/Serials Solutions Resource Manager, 
  • What information is recorded where? - Payments? One-line vs. Package? What titles?  License information? User permissions?

Possible solutions

  • Incident tracking system
  • EZ-Proxy and permission tools for in-house configuration and updating.
  • Bring together workflows: Similar documentation organization - Cornell will try to emulate
    Columbia's troubleshooting dashboard pages - Get Sally Lockwood access to Columbia wiki.
    • Next step - combine into single wiki page
  • No labels