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

[UXPROD-4672] Feature: Executing Work entity components / Instance entity components Created: 23/Jan/24  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
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Cloners
clones UXPROD-4609 Feature: Mapping Work entity componen... Open
Release: Ramsons (R2 2024)
Epic Link: EPIC: cataloging in BIBFRAME / Linked Data
Front End Estimate: XXXL: 30-45 days
Front-End Confidence factor: 90%
Back End Estimate: XXXL: 30-45 days
Back-End Confidence factor: 100%
Development Team: Citation
PO Rank: 0
RCA Group: TBD

 Description   

In scope

Related to UXPROD-4609 Open

The scope of this feature is to execute BFLITE to BF2 for components that make up the Work and Instance entities 

BF2 Monograph profile only

  • Complete support for all components that make up Work entity
  • Complete support for all components that make up Instance entity
  • Indexing rules and routines for components in the Work and Instance entities

Out of scope

  • BIBFRAME 2 Hub entity
  • BIBFRAME 2 Item entity

Use case(s)

All components that make up LC's BIBFRAME 2 Monograph profile must be displayed in production in Marva, inclusive of

  • literals fields
  • lookup fields

Indexing rules and routines

  • keyword for selected indexes (starting with ISBN, LCCN, Title, Contributor)
  • phrase for supported full text fields (TBD)
  • exact phrase for supported full text fields (TBD)

NOTE: will need to determine if the module will support a general keyword index against all (or defined subset of) entity components

Components treated consistently between BIBFRAME LITE and BIBFRAME 2

Components treated differently between BIBFRAME LITE and BIBFRAME 2 --> resulting in increased complexity of mapping

Proposed solution/stories

Links to additional info

Questions

 


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