Versions Compared

Old Version 53

changes.mady.by.user Jesse T. Koennecke

Saved on

compared with

New Version 54

changes.mady.by.user Jesse T. Koennecke

Saved on

Key

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

...

  • Cornell -
    • Annual: $11,693 (RM) + $10,450 (360 COUNTER)  - ~$10,000 (Innovative ERM cost recovery) = ~$12,000
    • One-time: $1969 + $3,990 (RM set-up) + $688 (360 COUNTER set-up) = $6,647
  • Columbia - No change beyond 2CUL costs summarized below.
  • 2CUL - Our team assumes these fees would be split evenly, but felt it was useful to single them out.
    • Annual:  $8,000 first year pilot, $20,000 future years (RM-CE)
    • One-time: $2,000 + $3,995 (RM-CE Implementation) = $5,995

RM at for Cornell

License fees - $11,693/year plus one time set up $1969 (includes data population services) and a onetime consultation fee of $3990

...

  • Record loads into III - requires considerable attention for week every month. wear and tear on body and soul. Impact on patrons (updated holdings, public display inaccurate and slow), staff (stress and ability to focus on other work) 10-20 hours per month.  Some of the time saved could be spent handling more frequent Serials Solutions MARC updates loads, keeping Voyager and the ERM in closer sync.  This will reduce delays between purchasing content and having that content appear in discovery tools such as Blacklight and Summon.
  • License, resource information already in knowledge base for many resources - III system is all hand entry for resource and license records.
  • Selectors will be able to access the system with relatively little training to view title lists, license terms, contact information.  As a web based tool, this will be possible remotely (during a conference).  III system has limited simultaneous connections and requires considerable training to get new users up to speed.
  • Reducing the number of systems involved in e-resource management without loss of functionality or access to information.  This has significant impact on training time, procedure retention, and ease of use.
  • Cleaner matching of resources between management and discovery systems.  This has significant impact on our ability to effectively troubleshoot resource access issues.
  • Knowledgebase Notifications alert us to changes in platforms, database titles, and other important maintenance issues.  This will allow for more pro-active work to reduce access problems.

360 COUNTER for 360 COUNTER at Cornell

License fees $10,450/year plus onetime set up $688

...

  • Annual harvesting of usage statistics - This will be mostly automated - SUSHI compliant resources each month, Non-SUSHI resources 2x yearly. System alerts us when changes are coming, usage harvesting data is out of date, - Sally Lockwood currently spends 12 weeks at about 75% of her time to harvest.  If we can recover 50-70% of this time to handle only the non-COUNTER resources, more complicated issues and updating the system, considerable effort is recovered.
  • Selectors will be able to access the system and make custom customized consolidated reports.  This is possible, but complicated and labor intensive in the current "system"our current wiki-based environment.
  • There is potential for 2CUL collaboration regarding how to handle non-COUNTER compliant resources, uploading cost data, and troubleshooting SUSHI problems.

RM-CE for 2CUL

License fees - $14,000 total, split between CULs for first year.  $20,000 total years 2+.

  • Standard pricing is about 20k for you all but since this is a pilot (and you all are good PQ customers), we can cut that to 8K for the year of the pilot and see how it goes.  There is also an implementation fee of $2,000 and a consulting fee of $3995.  We can create a statement of work to be sure we are aware of what the implementation looks like.  This will allow you to take time to work on the project without limitations and see how it works for you. - Kate Howe, Serials Solutions

Benefits and potential savings:

  • Platform changes and other resource maintenance  - One person/process maintenance can often be time intensive projects. We can handle these tasks collaboratively and can make the changes for both institutions when both CULs have content in the same collections. 
  • Alerts monitoringCollaborative monitoring of Knowledgebase Notifications will be possible, thereby reducing duplicate effort.
  • Comparison of e-collections will be considerably easier.  This will set us up to engage in  cooperative collection development decisions, shared workflow.

...