Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
eds_admin_management [2022/06/06 15:37] jmulvaney [Catalog Customizations] |
eds_admin_management [2022/08/16 15:05] (current) jmulvaney |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ===== EDS Admin Management ===== | ===== EDS Admin Management ===== | ||
| + | |||
| + | This page is now deprecated. Please see the Confluence page in the Five College space: https://fc-library.atlassian.net/wiki/spaces/FOLIO/pages/789020673/Discovery+EDS+Administration | ||
| 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. | 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. | ||
| Line 10: | Line 12: | ||
| "We run a job on ALEPH every day (except Sundays) at about noon which finds any bibs or holdings that have been added, deleted or edited within the past 3 days. The reason we wait till the next day is we wait for the union view process in ALEPH to run its overnight process. The process collects a union-view bib for those records, the preferred full bib with holdings location/url data attached (852/856) and send them to EBSCO via FTP. EBSCO gets these records by early afternoon and they are generally loaded in EDS by late afternoon." | "We run a job on ALEPH every day (except Sundays) at about noon which finds any bibs or holdings that have been added, deleted or edited within the past 3 days. The reason we wait till the next day is we wait for the union view process in ALEPH to run its overnight process. The process collects a union-view bib for those records, the preferred full bib with holdings location/url data attached (852/856) and send them to EBSCO via FTP. EBSCO gets these records by early afternoon and they are generally loaded in EDS by late afternoon." | ||
| + | |||
| + | **FOLIO-EDS** Testing Profile w/ OA SSO: https://search.ebscohost.com/login.aspx?custid=umaah&groupid=main&profid=umfolio21&authtype=sso | ||
| + | |||
| + | xmlonly=Y& | ||
| + | For XML view, insert after https://eds.a.ebscohost.com/eds/detail/detail? | ||
| + | |||
| + | &debug=true | ||
| + | https://search.ebscohost.com/login.aspx?custid=umaah&groupid=main&profid=eds&authtype=sso&debug=true | ||
| ==== EDS Profile Overview ==== | ==== EDS Profile Overview ==== | ||
| Line 351: | Line 361: | ||
| * Link Language Stanzas | * Link Language Stanzas | ||
| * Managed as part of Five College Discovery. Documentation is stored in the FCDC shared Google Drive. Our stanza is based on certain language in the 856 of the holdings record which will allow the URL to display (UMass: Link to Resource) | * Managed as part of Five College Discovery. Documentation is stored in the FCDC shared Google Drive. Our stanza is based on certain language in the 856 of the holdings record which will allow the URL to display (UMass: Link to Resource) | ||
| + | |||
| + | **Additional customizations will arrive with the FOLIO catalogs.** | ||
| ==== Widgets ==== | ==== Widgets ==== | ||
| * | * | ||
| Line 365: | Line 377: | ||
| * Continue Search in WorldCat | * Continue Search in WorldCat | ||
| * Database Placard | * Database Placard | ||
| - | |||
| - | ===== EDS & eJournal Content ===== | ||
| - | eJournal content is managed through the connection to [[hlm_admin_maintenance|HLM]]. Titles with specific material types enabled in HLM appear in the exact match eJournal placard in EDS. | ||
| - | * SFX file to EDS for Library Collection Limiter: There is a cron job set up to transfer SFX holdings to EDS for the Library Collection Limiter. The cron runs at 4:01 am every Tuesday to be processed by EBSCO on Wednesdays at 11:00 am. The cron sends an Advanced Export serials file by ftp to EBSCO. Ask Steve Bischof for more information. | ||
| - | * Once we migrate to FTF this will change as the connection will be 1:1 at all times. | ||
| - | * This is only for the SFX CL available in EDS. There are two in use for EHOST which are set to always display and do not rely on a curated local collection. | ||
| --- //[[jmulvaney@library.umass.edu|Primary contact: Jack Mulvaney]]// | --- //[[jmulvaney@library.umass.edu|Primary contact: Jack Mulvaney]]// | ||
