search

LD4 / ld4-community-recon

LD4 Community Working Group on Reconciliation - ARCHIVED
11 stars 6 forks source link

Matching e-resource content across multiple vendor knowledge bases #80

Closed eightBitter closed 6 years ago

eightBitter commented 7 years ago

Primary Actor (Required if possible)

e-resource employee

Scope (Optional)

e-resource employees, e-resource workflow

Story (Required)

The ability to match e-resource content across multiple vendor knowledge bases. Employee does work in one knowledge base, and then sends the holdings to another knowledge base.

Note that matching on ISSN is problematic.

vcharles89 commented 7 years ago

84, #82, #81 and #80 provide good general motivations for reconciliation

cmharlow commented 7 years ago

What is the differentiation between knowledge base and other metadata persistence layers (like ILS databases) here?

eightBitter commented 7 years ago

I'll try my best to clarify (still a serials noob). We use two knowledge bases for managing serials content: Serials Solutions and a homegrown system called E-Matrix. Serials Solutions is where we manage access to e-resource content, including turning on/off access to journals/databases and managing link resolvers. We also receive 360 MARC records through Serials Solutions that we ingest into our ILS.

E-Matrix serves as an additional knowledge base where we have finer-grained serials management, such as the ability to manage both print and electronic journals/databases.

I'm attaching a serials system diagram that might explain it better than me!

Hope this helps.

NCSU Libraries Serials System Diagram