BIBFRAME Thin Thread Epic (UXPROD-4318)

[UXPROD-4367] Feature: Cataloging logistics | BF Thin Thread Created: 22/Jun/23  Updated: 30/Nov/23

Status: In Progress
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: BIBFRAME Thin Thread Epic

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

Issue links:
Defines
defines MODLD-72 Story: Publish Functionality Open
defines UILD-12 Story: Publish resource description Open
defines UILD-16 Story: Publish Functionality Open
defines MODLD-64 Story: Save, Close, Delete | BF Thin ... Closed
defines UILD-10 Story: Save Work | BF Thin Thread Closed
defines UILD-11 Story: Close Work | BF Thin Thread Closed
defines UILD-13 Story: Delete resource description | ... Closed
Epic Link: BIBFRAME Thin Thread Epic
Development Team: Citation
PO Rank: 0

 Description   

Current situation or problem:

For the Thin Thread effort, this feature focuses on the cataloging workflow logistics when a cataloging technician has completed work on a resource description.

In scope

  • Save / Work in Progress - a cataloging technician must be able to save work completed on a resource description before it is shared or published
  • Delete - where the cataloging technician decides to remove/delete work previously completed (e.g. to avoid adding duplicate records to the catalog)

Out of scope

  • Publish - where a cataloging technician completes work on a resource description that doesn't require further review or editing of the description, the technician must have the ability to publish the description.  NOTE: This was functionality was originally included within scope of the Thin Thread, but moved out of scope to manage timeline for releasing the Thin Thread.
  • Roles/responsibilities - for the Thin Thread, assume anyone working on a resource description in Marva / BIBFRAME is a cataloging technician. That is, additional role-based work required for completing a resource description will not be supported in Marva / BIBFRAME. Additionally, Marva / BIBFRAME will not enforce rules for determining if or when the technician's work on a resource description is complete
  • Notification - the Thin Thread will not need to create a specific queue for work that needs to be passed to senior catalogers. This functionality may be required for Day 1, but not for the Thin Thread
  • Authority lookup - the technician will be required to inspect and verify certain authority entries in a resource description. That work is outside the scope of this feature. 

Use case(s)

Work in Progress - Success

  • Library technician completes work on a resource description
  • The technician is not authorized to publish the description
  • Technician selects some type of 'complete' option to save work 
  • Resource description saved in BIBFRAME
  • Resource description updated in FOLIO

Proposed solution/stories

Links to additional info

Questions

  • When a senior cataloger must review / update work started by a library technician, the senior cataloger will do so within FOLIO. What kind of 'hooks' - if any - must be included in the resource description, so that the catalogers can continue work in FOLIO?
  •  

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