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

[UXPROD-4587] Feature: LCCN 'Structure A' Created: 04/Dec/23  Updated: 08/Dec/23

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: back-end, front-end
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Epic Link: EPIC: cataloging in BIBFRAME / Linked Data
Development Team: Citation
PO Rank: 0
RCA Group: TBD

 Description   

Current situation or problem:

For the BIBFRAME Thin Thread proof of concept, the module supports discovery and display of LCCN identifiers that adhere to the library's 'Structure B' format --> essentially items acquired by the Library of Congress since 2001. 

Resources acquired prior to 2001 fall into the 'Structure A' category, as explained here: https://www.loc.gov/marc/lccn_structure.html

For the production release of BIBFRAME, LCCN use cases must cover both 'Structure A' and 'Structure B' scenarios, so that catalogers have more complete access to the library's collections through the BIBFRAME editor. 

In scope

  • LCCNs the fall into the 'Structure A' bucket
  • Initially, LCCNs for monographs only
  • Creating / applying normalization rules for 'Structure A' resources on the back end
  • Enforcing normalization rules for 'Structure A' resources on the front end

Out of scope

  • LCCNs the fall into the 'Structure B' bucket
  • Initially, LCCNs for non-monograph resources

Use case(s)

Proposed solution/stories

Links to additional info

Questions


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