Page 18 - Microsoft Word - Extended_Course_MLIS_Ref_Mgt.docx

Referencing and Bibliography Management Tools

 Complex configuration: Requires server access details (hostname, port,
database name).
 Outdated UI models: Newer web-based APIs (e.g., SRU/SRW, RESTful APIs)
are more user-friendly.
 Declining adoption: Superseded in some systems by web-based alternatives
like OAI-PMH and REST APIs.

4. Integrating COinS, DOIs, and Z39.50 into Scholarly Workflows

These technologies, while serving distinct purposes, can be combined to enhance metadata
interoperability, citation accuracy, and access to scholarly resources.

4.1 In Digital Libraries

COinS metadata can be embedded in the HTML output of a digital repository (e.g., DSpace or
Omeka), making the metadata harvestable by Zotero. If the resource has a DOI, the repository
can link it in the COinS metadata, enabling enriched citation data.

4.2 In Reference Managers

Zotero can detect COinS metadata from a webpage and automatically extract it. Mendeley can
resolve a DOI and populate the record with complete citation details. EndNote allows users
to connect to Z39.50 servers to search and import MARC records. EndNote, being a
proprietary tool, offers sophisticated features tailored for researchers working with
extensive datasets. Its custom field creation and advanced filtering mechanisms support
nuanced literature reviews, especially in medical and engineering fields. By investing in
EndNote, institutions facilitate a structured and scalable research environment.

4.3 In OPAC and Discovery Systems

Library OPACs often offer COinS spans and Z39.50 endpoints. WorldCat and union catalogs
support both Z39.50 querying and DOI linking, enabling global resource sharing.

5. Emerging Trends and Alternatives

While COinS, DOIs, and Z39.50 continue to be valuable, newer protocols and models are
evolving.

5.1 Linked Data and RDF

Libraries are increasingly using BIBFRAME and schema.org to represent bibliographic data
in a linked data format. DOIs are increasingly linked with ORCID iDs, author authority files,
and CrossRef APIs.

5.2 RESTful APIs and OAI-PMH