Definitions

Here we will define terms that we need to use in our discussion. If terms have been defined sufficiently elsewhere, please point or cite source.

Definitions (cooked)

• MARC21
  • 1. The Z39.2/ISO 2709 record structure
  • 2. MARC 21's implementation of the Z39.2/ISO 2709
  • 3. MARC 21's family of formats (bib, authority, etc.)
  • 4. MARC 21's set of data elements for each of the formats
  • 5. MARC 21's instructions for punctuation or other included coding in the data values.

• OPAC
• Z39.2/ISO 2709

Definitions (raw)

• The Next Generation "Entity" (not using the term catalog) is comprised of:
  • A list of items owned by the library. This list is at a macro level (e.g. serial titles but not the articles in the serial). Often that level is determined by the purchase unit, since this list interacts with the library's acquisitions function.
  • Serial issues received. This is usually found in a separate module called a serials check-in system (which replaced the old Kardex)
  • Licenced resources. These may be listed in the catalog, but they may either/also be found in a database used by an OpenURL resolver or in an ERM system (which is not accessible to users). In some cases, these are listed on a web site managed by the library.
  • Journal article indexes. These used to be hard-copy reference books. They are now often electronic databases. User interface to these varies.
  • Items available via ILL. This could be a union catalog of libraries in a borrowing unit. It also is a function that interacts with OCLC's ILL system. This latter usually isn't visible in the user view of the library.
  • Links and connections from information systems not hosted by the library, such as the ability to link from an article in a licensed database to the full text of the article from another source; or a link from an Internet search engine to library-managed resources through a browser plug-in or a web service.
  • Location and circulation status information, plus the ability for users to place holds on items or to request delivery of items.
  • Interaction with institutional services such as courseware.
  • One or more user interfaces. Many of these services above will have a separate interface just for that service, but there are also meta-interfaces that will combine services.