This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
access_coordination [2019/06/24 15:27] jmulvaney [Access Systems Coordination] |
access_coordination [2024/08/30 19:45] (current) myoungberg [Database A-Z List] |
||
---|---|---|---|
Line 95: | Line 95: | ||
==== Database A-Z List ==== | ==== Database A-Z List ==== | ||
- | Research Services manages the A-Z list in Springshare. Jennifer Friedman gets email notifications when her workflow step becomes active so that she can add, edit, or delete springshare records. She leaves a Springshare ID note in the cataloging tab with the ID for the database record. She is also on the Platform changes worksheet to catch those resources and make changes as needed. | + | **updated as of 30 August 2024** |
+ | |||
+ | Academic Engagement manages the A-Z list in Springshare. Once Camille or Margaret reach this part of a CORAL workflow, the following happens: | ||
+ | |||
+ | To add new resources: | ||
+ | * DRMS fills out a row in the [[https://docs.google.com/spreadsheets/d/1NnyMfEIgwJqeEkAvHTmQY2BwkUpDJEJ8Xix1ZHz71tQ/edit?gid=140890334#gid=140890334|A-Z To add tab]] of the spreadsheet | ||
+ | * Academic Engagement reviews resources, decides whether to include them, and documents this decision in the row | ||
+ | * DRMS documents the decision in the appropriate Agreement in FOLIO | ||
+ | |||
+ | |||
+ | To update or remove existing resources: | ||
+ | * DRMS fills out a row in the [[https://docs.google.com/spreadsheets/d/1NnyMfEIgwJqeEkAvHTmQY2BwkUpDJEJ8Xix1ZHz71tQ/edit?gid=0#gid=0|A-Z Updates to existing tab]]A-Z Updates to existing tab of the spreadsheet | ||
+ | * Academic Engagement reviews, makes changes as appropriate, and documents any additional information | ||
+ | * DRMS confirms FOLIO is updated to match. | ||
==== Ejournal Transfers ==== | ==== Ejournal Transfers ==== | ||
Line 112: | Line 125: | ||
==== Platform Changes ==== | ==== Platform Changes ==== | ||
- | Whenever someone sees a platform change (either from HTTP-HTTPS or between companies like Atypon or Ingenta) they should put it on the [[https://docs.google.com/spreadsheets/d/1Fchqgk9b_yanTktkw7-r0bcUC3K3Akban0n9UJ185p4/edit#gid=0|Platform Changes Sheet]]. Basic information like the name, change type, availability, and shut down should be recorded immediately. | + | Whenever someone sees a platform change (either from HTTP-HTTPS or between companies like Atypon or Ingenta) they should email Jack. |
- | * Jack takes care of making changes to the CORAL record, as well as creating new admin accounts if need be. | + | * Jack will take care of things in the discovery systems and alert the UMBLT or Research Services. |
- | * Anyone can change the holdings record URL. | + | |
- | * Nancy or Judy make changes to information surrounding usage reports if need be. | + | |
- | * Scott makes changes to the EXProxy Stanzas. | + | |
- | * Jack makes changes in SFX, EDS, and/or HLM. | + | |
- | * The BLT makes changes if the resource is batch loaded into Aleph. | + | |
- | * Jennifer Friedman (Research Services) makes changes to the Database A-Z List. | + | |