Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
access_coordination [2019/04/23 10:19]
jmulvaney [EDS/HLM]
access_coordination [2019/06/24 11:27] (current)
jmulvaney [Access Systems Coordination]
Line 9: Line 9:
  
   * __SFX__: Officially, only eJournals and databases with full text content are activated in SFX. Some eBooks (like the autoload targets) are activated but we do not use the SFX eBook search interface. Some databases (like the aggregators) have their own targets for the content contained within them, while some are individual OPs in the Misc. eJournal target for the search page only. Some resources are not available in SFX and have to be found elsewhere, as we try not to create LCL items.   * __SFX__: Officially, only eJournals and databases with full text content are activated in SFX. Some eBooks (like the autoload targets) are activated but we do not use the SFX eBook search interface. Some databases (like the aggregators) have their own targets for the content contained within them, while some are individual OPs in the Misc. eJournal target for the search page only. Some resources are not available in SFX and have to be found elsewhere, as we try not to create LCL items.
-  * __EDS__: Officially, everything we pay for is enabled in EDS. This is an overgeneralization. Content published by EBSCO is enabled and uses SmartLinks to connect to full text. Content purchased from EBSCO is enabled ​and uses SmartLinks Plus to connect to full text at the publisher platform. ​Content from EBSCO partner databases is enabled and custom links are created for full text linking at the publisher platform. Some resources are not available in EDS and have to be found elsewhere. +  * __EDS__: Officially, everything we pay for is enabled in EDS. This is an overgeneralization. Metadata from EBSCO partner databases is enabled and custom links are created for full text linking at the publisher platform. Content published by EBSCO is automatically ​enabled and uses SmartLinks to connect to full text. Content purchased from EBSCO is selected in HLM through Order Integration ​and uses SmartLinks Plus to connect to full text at the publisher platform. ​HLM also pushes ​the things we select outside order integration to facilitate SmartLinks where our holdings match metadata. Some resources are not available in EDS and have to be found elsewhere. ​(ex. ProQuest.) ​ 
-  * __HLM__: Officially, all journal content we pay for is enabled ​in HLM. Anything paid to EBSCO is enabled and managed by them. Everything else has to be manually ​enabled ​and tracked. ​Elsevier holdings ​are FTP'd with the autoload data from SFX. +  * __HLM__: Officially, all journal content we pay for is selected ​in HLM. Anything paid to EBSCO is enabled and managed by them through Order Integration. Everything else has to be manually ​selected ​and tracked. ​Some resources ​are not found in HLM, but title lists can be sent to support to create a new package or SFX data can be uploaded to do this locally
-  * __Aleph__: ​Officially, only bibs we pay on are loaded into Aleph. This includes ​individual eJournals, eJournal ​packagesand databases. ​Individual eJournal records from subscription databases ​are not loaded into ALEPH. Database and eJournal Package cover records are suppressed so they are not discoverable in ALEPH. Some databases and individual eJournals are left unsuppressed and are discoverable in the catalog. When resources are not available in SFX or EDS/HLM we batch load records for them into Aleph.+  * __Aleph__: ​Bibs are the top level record in Aleph and anything ​we pay on requires a Bib. This includes ​cover records and title level records. All records are suppressed at time of purchase until we get access. Anything we want to be discoverable in the OPAC or EDS is unsupressed (//Database Cover RecordsIndividual eBooks, Physical Materials//​) while the rest stay suppressed (//eJournal/Book Packages, Individual ​eJournals, memberships,​ softwares, tools, etc.//​). ​eJournal records from package subscriptions ​are not loaded into Aleph as a matter of course. When resources are not available in SFX or EDS/HLM we batch load records for them into Aleph by making a request to the [[batch_loading_team|BLT]] who look for a collection in OCLCThey will automatically load records into Aleph when they are provided by the vendor and if they are good enough quality. (//eBook packages//)
   * __DB List__: The A-Z database list is managed by RS now. Jennifer Friedman is in charge of additions and edits at the moment. All paid content that arrives in a database model is included, with reference to the Springshare ID made in CORAL'​s cataloging tab. The A-Z list is the place of last resort when something cannot be found in SFX, EDS, or Aleph.   * __DB List__: The A-Z database list is managed by RS now. Jennifer Friedman is in charge of additions and edits at the moment. All paid content that arrives in a database model is included, with reference to the Springshare ID made in CORAL'​s cataloging tab. The A-Z list is the place of last resort when something cannot be found in SFX, EDS, or Aleph.
  
access_coordination.txt · Last modified: 2019/06/24 11:27 by jmulvaney
[unknown link type]Back to top
www.chimeric.de Creative Commons License Valid CSS Driven by DokuWiki do yourself a favour and use a real browser - get firefox!! Recent changes RSS feed Valid XHTML 1.0