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

[UXPROD-4451] Feature: Clone resource description | BF Thin Thread Created: 06/Sep/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, front-end, loc
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to UXPROD-4286 Feature: MARC validation rules | BF C... Open
relates to UXPROD-4592 Feature: Data Rules BF2 | BF Cataloging Open
relates to UXPROD-4594 Feature: BF integration with SRS --> ... Open
Release: Ramsons (R2 2024)
Epic Link: EPIC: cataloging in BIBFRAME / Linked Data
Front End Estimate: Medium < 5 days
Front-End Confidence factor: 90%
Development Team: Citation
PO Rank: 0

 Description   

Current situation or problem:

As a cataloger, I need the ability to clone (or copy) an existing resource description that serves as the basis for a new resource description in order to save time on keying. 

Currently, the BIBFRAME environment allows catalogers to create a new resource description from scratch or to update an existing resource description. 

This card extends BIBFRAME functionality to create a new resource description by deriving it from an existing resource description.

In scope

  • Ability to clone an existing resource description for a Work and retain component values from the original Work
  • Ability to clone an existing resource description for an Instance and retain component values from the original Instance
  • Dependent on / subject to
    • rules for saving a new resource description
    • synching a new resource description with FOLIO SRS

Out of scope

Use case(s)

 

Proposed solution/stories

Links to additional info

Questions

  • Differentiate with overlay use cases (e.g. overlaying with a record retrieved from OCLC)
  • Differentiate with use cases where cataloger wants to copy values from Instance entity to Work entity and vice versa
  • Main use case: deriving a new instance (e.g. new edition) from an existing instance

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