Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
eds_admin_management [2021/03/25 16:01] jmulvaney [UMass SCUA Digital Collections (ir01012a)] |
eds_admin_management [2022/06/06 15:18] jmulvaney [EDS Admin Management] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ===== EDS Admin Management ===== | ===== EDS Admin Management ===== | ||
| - | Management of content in EDS means balancing the combination of EBSCO published (EBSCOHost) and non-EBSCO published metadata. EBSCO "manages" metadata and access issues in the same way that ExLibris maintains the back end, but we still have to activate targets to create access. Enabling metadata in EDS follows a three step process that must all be completed for something to be correctly searchable. Once something appears in your CORAL queue then you can start the process of enabling metadata. | + | Management of content in EDS means balancing the combination of EBSCO published (EBSCOHost) and non-EBSCO published metadata. EBSCO partners with publishes for eResource metadata and we provide a file of our FOLIO records as well as several institutional repositories to create the search experience in EDS. Linking to content through CustomLinks is possible in EDS but has no benefit outside of EDS, meaning FTF handles a large portion of eResource linking. Enabling metadata and linking in EDS follows a three step process that must all be completed for something to be correctly searchable. Once something appears in your CORAL queue then you can start the process of enabling metadata. |
| **Also See** | **Also See** | ||
| * [[hlm_admin_maintenance|HLM Admin Maintenance]] | * [[hlm_admin_maintenance|HLM Admin Maintenance]] | ||
| + | * [[ebscohost_maintenance|EBSCOhost Database Maintenance]] | ||
| Per Steve, here’s how records get from Aleph to EDS: | Per Steve, here’s how records get from Aleph to EDS: | ||
| Line 118: | Line 119: | ||
| * Test the URL to make sure it is what you expect. | * Test the URL to make sure it is what you expect. | ||
| * Test in Opera with the Silk Prefix. If it does not work it means the resource is not correctly configured in EZPRoxy. | * Test in Opera with the Silk Prefix. If it does not work it means the resource is not correctly configured in EZPRoxy. | ||
| + | |||
| + | ==== EBSCO Outage Procedures ==== | ||
| + | |||
| + | Please see this [[https://docs.google.com/document/d/1H59fZ2ukJnZa32YsgQupNndeyTEUhdmDSK7NRkwTW2c/edit?usp=sharing | Google Doc]] for instructions on how to handle outages in the EBSCO environment. | ||
| ===== Enabling a New Resource ===== | ===== Enabling a New Resource ===== | ||
| Line 277: | Line 282: | ||
| * Go to the URL Aaron created to access the OAI endpoint. (It is stored in JGMs calendar invite.) | * Go to the URL Aaron created to access the OAI endpoint. (It is stored in JGMs calendar invite.) | ||
| * Scroll to the bottom of the XML Tree | * Scroll to the bottom of the XML Tree | ||
| - | * Compare the final collection to the most recent file sent to EBSCO (As of 20210201 it is Silvio O. Conte) | + | * Compare the final collection to the most recent file sent to EBSCO (As of 20211201 it is Silvio O. Conte) |
| * Check DRMS Drive or EBSCO Connect | * Check DRMS Drive or EBSCO Connect | ||
| * If they match, no new collections have been added | * If they match, no new collections have been added | ||
