...
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?
...