Research VIAF as authoritative data source for agents and geographic locations

[andrewmarconi]

Overview

Research the Virtual International Authority File (VIAF) at viaf.org as a viable authoritative data source for linking agents (people and organizations) and geographic locations to other authoritative sources.

Background

VIAF is an international service that combines multiple national authority files into a single name authority service. It is operated by OCLC and includes records from over 50 national and international libraries.

Why VIAF?

• Authority control: Provides unique identifiers for persons, organizations, and geographic entities
• Cross-referencing: Links to other authority files (Library of Congress, Deutsche Nationalbibliothek, BnF, etc.)
• Disambiguation: Helps distinguish between entities with similar names
• Linked data ready: Provides URIs and supports RDF/JSON-LD formats
• Widely adopted: Used by libraries, archives, and cultural heritage institutions worldwide

Relevance to ZineCore2

AgentCore2 (People & Organizations)

• Could provide authoritative identifiers for zine creators, publishers, and contributors
• Enable linking to biographical data from multiple national libraries
• Support disambiguation of common names

Geographic Locations

• Authority control for place names (cities, countries, regions)
• Useful for `dcterms:spatial` fields in ZineCore2 and related profiles
• Links to geographic authority files (GeoNames, LC Subject Headings, etc.)

Research Questions

1. API Access

   • What APIs does VIAF provide? (REST, OAI-PMH, SRU/SRW?)
   • Are there rate limits or authentication requirements?
   • What data formats are available? (RDF/XML, JSON-LD, MARC21?)

2. Data Coverage

   • How comprehensive is coverage for individuals vs. organizations?
   • What geographic regions have better coverage?
   • Are there gaps relevant to zine culture (small publishers, DIY communities)?

3. Integration Approach

   • Should VIAF IDs be stored as a controlled vocabulary term or as a URI field in AgentCore2?
   • How to handle entities not in VIAF?
   • Should we support lookup/autocomplete during agent creation?

4. Alternative Sources

   • How does VIAF compare to alternatives (Wikidata, ISNI, ORCID)?
   • Could we use VIAF as a hub to link to multiple sources?
   • Should we support multiple authority identifiers per agent?

5. Schema Impact

   • Does this require changes to the AgentCore2 profile in `spec/`?
   • New field? (e.g., `authority_id`, `viaf_uri`)
   • Vocabulary additions to `spec/vocabularies/canonical/`?

Deliverables

• Document VIAF API capabilities and limitations
• Evaluate data coverage relevant to zine culture
• Propose schema changes to AgentCore2 if needed
• Create proof-of-concept integration (API query, data retrieval)
• Compare with alternative authority sources (Wikidata, ISNI, etc.)
• Recommend implementation approach with pros/cons

Resources

• VIAF Homepage: https://viaf.org
• VIAF API Documentation: https://www.oclc.org/developer/api/oclc-apis/viaf.en.html
• Linked Data Service: https://viaf.org/viaf/data/
• SRU API: https://www.oclc.org/developer/api/oclc-apis/viaf/authority-cluster.en.html

Related

This research may impact:

• `spec/` repository (profile and vocabulary updates)
• AgentCore2 schema definition
• Geographic location vocabularies
• Server API endpoints for agent creation/editing