Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

FEATURE: Provenance & admin data | Reporting

Description

As a cataloger, I need the ability to access the provenance of a resource description, in order to can understand the context for decisions made about the resource (the 'who / what / why') so that I can effectively collaborate.

The administrative data elements should be consistent with those supported for the MARC-based cataloging workflows. 

The UX considerations for how the administrative data is accessible and incorporated into the cataloging workflows will need to be tested with pilot libraries. 

 

In scope

  • All resource descriptions must have FOLIO identifiers

  • Linked data admin data - per Library of Congress documentation - includes

    • Resource creation (e.g. date resource first created; institution that created it; corresponding status flag)

    • Updating a resource (e.g. date resource last updated; institution that updated it; corresponding status flag)

    • Converting a MARC record into a resource (e.g. software used to perform conversion, date converted)

    • General (other) metadata (e.g. encoding level, local system number)

  • MARC admin data includes

    • All 9xx fields from incoming MARC records

Q: Need to determine whether there are any validation rules tied to admin data; and if so, what rules would prevent a bibliographic resource from being saved vs. rules for prompting a cataloger to follow best practices.

Priority

Labels

Fix versions

Development Team

Citation

Assignee

Solution Architect

Parent

Parent Field Value

None

Parent Status

None

blocks

defines

Checklist

hide

TestRail: Results

Activity

Show:

Doug Loynes January 6, 2025 at 3:19 PM

For the Sunflower release, minimum support is the ability to preserve metadata from an incoming MARC record for fields that have not yet been mapped to resource description components, so that the data can be ‘appended’ to the MARC derived record.

Until the MARC fields are fully mapped to resource description components, catalogers will not be able to edit the fields in the Linked Data Editor. However, this feature ensures that the original data will be preserved as part of the record in the interim.

Khalilah Gambrell September 11, 2024 at 5:36 PM

Will provide a mini-MARC editor with the applicable admin fields.

Details

Reporter

PO Rank

0

Release

Sunflower (R1 2025)

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created May 9, 2023 at 2:23 PM
Updated January 30, 2025 at 4:18 PM
TestRail: Cases
TestRail: Runs