EPIC: cataloging in BIBFRAME / Linked Data (UXPROD-4215)

[UXPROD-4606] BIBFRAME Fingerprinting - MARC transformation Created: 22/Dec/23  Updated: 04/Feb/24

Status: Open
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: EPIC: cataloging in BIBFRAME / Linked Data

Type: New Feature Priority: TBD
Reporter: Doug Loynes Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Release: Ramsons (R2 2024)
Epic Link: EPIC: cataloging in BIBFRAME / Linked Data
Back End Estimate: XXL < 30 days
Back End Estimator: Pavel Bobylev
Back-End Confidence factor: 100%
Development Team: Citation
PO Rank: 0
RCA Group: TBD

 Description   

Current situation or problem:

BIBFRAME Resources are identified with IDs that provide unique fingerprints for each thing. Fingerprints uniquely identify a particular resource in a data graph. 

Fingerprinting is a crucial / essential feature of the service by: (1) unambiguously identifying resource, so that (2) libraries can build out their own data graphs with integrity, and so that (3) libraries can work collaboratively to definitely determine what is common between collections and what is different between collections. 

Fingerprinting of resources occurs when resources are added to a data graph - via ETL, via microservices, via cataloging performed in the Marva interface.  So it is critical that the fingerprinting logic applies across these services. Otherwise the library's data graph is susceptible to duplicate entries that are identical save for the fingerprint identifier. 

In scope

The scope of this card is limited to fingerprinting applied to transformation of MARC records into BIBFRAME resource descriptions via ETL or via data import. 

Currently, if the same MARC record were processed separately through ETL and again through data import, it would result in duplicate entries - with separate fingerprint ids - in the BIBFRAME Linked Data database. 

Data transformation with respect to fingerprinting needs to be aligned across ETL and the BIBFRAME microservice so that it guards against duplication.

Out of scope

There are important questions about how fingerprinting rules apply when a cataloger is creating new works and/or instances within the Marva application. 

We agreed in Refinement on 24 Jan to address these concerns separately as its own feature card. 

Use case(s)

Proposed solution/stories

Links to additional info

Questions


Generated at Fri Feb 09 00:41:11 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.