Pros Cons
RM
- 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, keepy Voyager and the ERM in closer sync.
- License, resource, contacts information already in knowledgebase 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.
COUNTER
- 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 more complicated issues and updating the system, considerable effort is recovered.
- Selectors will be able to access the system and make custom consolidated reports. This is possible, but complicated in the current "system"
RM-CE
- Platform changes and other resource maintenance - One person/process can make the changes for both institutions when both CULs have content in the same collections.
- Alerts monitoring
- Comparison of e-collections will be considerably easier. This will help with collection development decisions, shared workflow.
Make a specific recommendation on whether to implement the Consortial Version of Serials Solutions at both institutions or hold off on integrating e-resource management and data migration until we have a shared LMS;
...
I am so sorry about this delay (Joyce – got your vm today). I was on vacation for two weeks and am just returning. I checked with Ashley on your notes below and her comments are below. If this makes sense to you, we can set up the pilot project. To do that, we would want Cornell to subscribe to RM with the pricing that I sent Jesse earlier and then we would ask for an "upcharge" “upcharge” for the consortial version. 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.
...
how does this help Cornell?
Questions from ERNIE:
360 COUNTER -
- How migratable is data and admin info to another system?
- flaws of COUNTER - title changes, ceased publication, others - Does 360 COUNTER help?
1/14/2014 Call with Kate Howe and Ashley Bass
Roadmap:
Plan to move existing customers to Intota platform later this year - this seems to be happening regardless of suite of services used - September? Perhaps later? Consortial would delay this to possibly December
- Data will move
- Changes will be in the user (staff) interface
- Consortial functionality will carry over
Intota with all functionality?
Timeline for us: Implement exsisting system, some time months to year after, change over to Intota platform (target goal for first live INTOTA customer = May 15 / June)
- Consortial decision determines when we would move. If we want consortial immediately, we would wait. If we can wait for consortial, we could move sooner
- Does consortial help us migrate and/or get up and running sooner? I.E can Columbia helps us populate things more easily under consortial?
- Work for consortial - What does "parent" look like? Is one of us the parent or do we make a 2CUL parent?
- scenarios: Clone Columbia account to be parent account of both Cornell and Columbia - pros/cons?
- fresh parent account?
- What do we load/enter from III ERM, what do we populate from "parent"
- License uploader
- Contacts uploader
- Can provide them a spreadsheet of admin login info.
Upcharge to Intota Assessment once migrated to platform? Stop paying for COUNTER start with Assessment - Net change (~$10,000-18,000) each?
10:30 Sunday - ALA Meeting - Bob/Joyce, ask Xin.
Migration
- We can export data from III ERM into spreadsheets or text files. Can these be migrated? How successfully? Any customers that have done this that we might be able to speak to?
Resource Manager:
- We believe there used to be a "Custom Proxy URL" field that could be used at the provider, database and/or title level. This doesn't seem to be there now. Cornell currently uses a few different proxy URL prefixes to sort out different levels of access between our main campus and medical campus.
- Consortial -
Meeting at ALA? - Can we come up with a few times then see if we can get Bob Wolven and Xin Li