Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Last revision Both sides next revision
glossary [2019/01/07 12:20]
127.0.0.1 external edit
glossary [2019/05/03 09:02]
jmulvaney
Line 139: Line 139:
  
 Intended to be published in a specific number of volumes, like an ordinary continuation. ​ However, each volume focuses on a specific topic and has individual author/​title entry in the OPAC.  The volumes are assigned their own call numbers. Intended to be published in a specific number of volumes, like an ordinary continuation. ​ However, each volume focuses on a specific topic and has individual author/​title entry in the OPAC.  The volumes are assigned their own call numbers.
 +
 +===== CORAL =====
 +
 +CORAL is an acronym meaning Centralized Online Resource Acquisitions and Licensing. The title doesn'​t mean much, but CORAL is our electronic resource management (ERM) system. ERM systems are usually third party applications used to supplement the ILS (Aleph) since most were not designed to handle electronic resources or rights management. CORAL is where we track access, pricing, and licensing data about eResources.
  
 ===== Corporate body ===== ===== Corporate body =====
Line 165: Line 169:
 ===== Dublin Core ===== ===== Dublin Core =====
 Managed by the [[http://​dublincore.org/​|Dublin Core Metadata Initiative]],​ this is a metadata standard of simple and generic resource description properties. The original 15 elements of core metadata include contributor,​ creator, coverage, format, language, title, type, etc. The DCMI has recommendations for interoperability,​ semantics, user guidelines, model-related specifications and syntax guidelines. Managed by the [[http://​dublincore.org/​|Dublin Core Metadata Initiative]],​ this is a metadata standard of simple and generic resource description properties. The original 15 elements of core metadata include contributor,​ creator, coverage, format, language, title, type, etc. The DCMI has recommendations for interoperability,​ semantics, user guidelines, model-related specifications and syntax guidelines.
 +
 +===== EDS/​Discovery Layer =====
 +
 +EBSCO Discovery Search/​Service (EDS) is the libraries Discovery layer. Discovery layers are the library-worlds solution to Google-esque search habits. It allows users to perform a federated search, or a search in one location that spans multiple sources. This means that a user can search for the word "​cat"​ across many of our physical and digital databases of resources at once, instead of performing the search multiple times in multiple locations and interfaces. EDS does not however search everything that the library owns or buys, so it is supplemented by other knowledge bases or catalogs like the Five College Catalog, EDS, the Database A-Z page, Credo, etc.
  
 ===== EZProxy ===== ===== EZProxy =====
Line 184: Line 192:
  
 ===== Gobi ===== ===== Gobi =====
 +
 +===== HLM =====
 +
 +HLM (possibly Holdings and Link Management or just Holdings Management) is a system that lives in the EBSCOAdmin and powers our eJournal placard. It takes information that we give it (our eJournal holdings) and facilitates direct title matching. So when a user searches a journal title that HLM recognizes (Journal of Fish Biology) it will display the exact match eJournal placard at the top of the results and allow users to search directly within the full text of that particular publication or be launched to the platform that holds that publication.
  
 ===== Holdings record ===== ===== Holdings record =====
  
-Holdings records provide copy-specific information on a library resource (call number, shelf location, volumes held, and so forth).+Holdings records provide copy-specific information on a library resource (call number, shelf location, volumes held, URL, and so forth).
  
  
Line 202: Line 214:
 ===== MARC - Machine readable cataloging ===== ===== MARC - Machine readable cataloging =====
  
 +MARC is an encoding language for bibliographic records created in the 1960s to replace paper card catalogs. The many fields are encoded so that they can be converted from data files to readable text, meaning both computers and people can read the information contained within.
  
 ===== MARCit ===== ===== MARCit =====
Line 267: Line 280:
 ===== SFX ===== ===== SFX =====
  
 +SFX is an ExLibris product (a ProQuest company) which is our link resolver. It allows full text access to our eJournal content, and plugs into EDS and other databases so that when searching users can call out to SFX and check for all the places full text access for titles exists. SFX is an Open URL Link Resolver (the original one actually) which ingests metadata from a source (wherever a patron happens to be searching) puts the metadata against an SFX object (a journal title, article, etc.) and provides a list of targets (everywhere where we have told the knowledgebase that we have access to that object) that link to an external platform with full text content to the article.
  
 ===== Shelf ready ===== ===== Shelf ready =====
glossary.txt · Last modified: 2019/05/03 09:03 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