[UXPROD-4423] Add additional fields to FOLIO record format for search Created: 28/Jul/23  Updated: 24/Jan/24  Resolved: 24/Jan/24

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: None

Type: New Feature Priority: P2
Reporter: Christine Schultz-Richert Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: loc, metadatamanagement
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Front End Estimate: Large < 10 days
Front End Estimator: Khalilah Gambrell
Front-End Confidence factor: 70%
Back End Estimate: XL < 15 days
Back End Estimator: Khalilah Gambrell
Back-End Confidence factor: 70%
Development Team: Spitfire
PO Rank: 0

 Description   

Current situation or problem: This feature is intended to encompass user stories for adding search/filtering options for fields that are not currently mapped in MARC-Instance mapping and are not available in the search index.

In scope

  • Authority scope notes (260 - see refs, and 360 - see also refs)
  • Fixed field values
    • Bib level
    • Type of control
  • Additional dates - for example:
    • Date information may be represented in multiple MARC fields (including 008, 033, 046, 245$f$g, 260/264$c, 6XX$y) 
    • publication and/or production information, chronological and/or topical information about item subject content, bulk and span dates of archival collections, holdings information, expected publication dates (for CIP and ISSN Centre records)
  • Authority narrower/broader terms: $w from 4XX and 5XX fields
  • Record provenance; examples (need exhaustive list) :
    • Bibs: 906|c, 040, 923, and other 9XX
    • Authorities: 040

Out of scope

Use case(s)

Proposed solution/stories

Links to additional info

Questions



 Comments   
Comment by Khalilah Gambrell [ 03/Sep/23 ]

Hey Christine Schultz-Richert  is this feature still needed?

Comment by Christine Schultz-Richert [ 24/Jan/24 ]

Will be replaced with specific, more granular data mapping/search changes

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