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

[UXPROD-4592] Feature: Data Rules BF2 | BF Cataloging Created: 10/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: bf-alpha, bf-beta, emwg
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Cloners
clones UXPROD-4286 Feature: MARC validation rules | BF C... Open
Relates
relates to UXPROD-4451 Feature: Clone resource description |... Open
Release: Ramsons (R2 2024)
Epic Link: EPIC: cataloging in BIBFRAME / Linked Data
Front End Estimate: Small < 3 days
Front-End Confidence factor: 80%
Back End Estimate: Large < 10 days
Back-End Confidence factor: 80%
Development Team: Citation
PO Rank: 0

 Description   

Current situation or problem:

The FOLIO BIBFRAME module will allow catalogers to create / edit resource descriptions in BIBFRAME, as well as derive MARC records from BIBFRAME resource descriptions. We will need to enforce validation rules within the Marva application to ensure that the BIBFRAME resources and MARC records derived from these resources adhere to quality standards.

In scope

  • All resource descriptions must have FOLIO identifiers
  • Error codes and messages specific to BIBFRAME 2
  • Admin data, including
    • Generation Process - e.g. DLC marc2bibframe2 v1.7.0-SNAPSHOT
    • Status - e.g. corrected or revised
    • Encoding Level - e.g. full
    • Description Conventions - e.g. AACR
    • Identified By - e.g. bf:Local, <identifier>
    • Change Date
    • Creation Date
    • Description Modifier - e.g. United States, Library of Congress
    • Non-rendered Predicates - e.g. lclocal:d906

Out of scope

  •  

Use case(s)

Proposed solution/stories

Links to additional info

 

Questions

  1. For MARC, Khalilah Gambrell will provide a list of validation rules and principles used in FOLIO currently. She has held more requirement gathering sessions with LC staff and will be writing up Jiras for additional validation rules, which she'll share with Citation.
  2. For BIBFRAME 2.0, we'll engage with the NetDev team to flesh out use cases and corresponding Jira tickets. 

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