FEATURE: Cataloging logistics | Thin Thread

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?

Priority

Fix versions

None

Development Team

Citation

Assignee

Solution Architect

Parent Field Value

None

Parent Status

None

Checklist

hide

TestRail: Results

Activity

Show:

Anuar Nurmakanov October 9, 2024 at 11:12 AM

Architecture Review is Required

Doug Loynes August 6, 2024 at 8:12 PM

Scope of this feature includes saving work to the back end.

Deleting a resource description will not be supported.

Done

Details

Reporter

PO Rank

0

Release

Sunflower (R1 2025)

Tech Design Ready

Yes

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created June 22, 2023 at 10:24 AM
Updated October 31, 2024 at 8:56 AM
Resolved August 6, 2024 at 8:12 PM
Loading...