Skip to:

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

MARCXML authority import fails when an 024 (other standard identifier) does not have a $a even though this can be valid

Description

I believe it is possible to have an 024 with only a $0 or a $1. Currently an 024 with only a $1 leads to this error (and failure) on an attempted import:

The following errors were found:
agent_record_identifiers/1/record_identifier : Property is required but was missing

To see this in action, try importing the LCNAF record for Kamala Harris (https://id.loc.gov/authorities/names/n2009045056.marcxml.xml).

It would be great to get confirmation from the Metadata Standards sub-team that this should be allowed.

Environment

None

Bug Report Description

None

Activity

Show:

Rachel SearcyMarch 24, 2022 at 7:52 PM

Tested and working as expected. Kamala Harris authority record can be imported without error.

Don RichardsMarch 7, 2022 at 10:16 PM

Angela WhiteNovember 22, 2021 at 4:35 PM

I ran Metadata Standard’s recommendations through Dev-Pri, and we agreed to pass this along for development.

Kevin SchlottmannOctober 20, 2021 at 5:20 PM

Metadata Standards reviewed this ticket. The writer is correct, per the spec this is technically true:

In AS 3.0, record identifier is a required field (correctly), but only 024$a maps there (AS code).

If we were to recommend a change, the importer logic should be:

Import 024$a. If no 024$a, then use 024$0 as identifier; if no 024$0 either, then use 024$1. If 024 exists but none of ${a,1,2} are present, reject the import.

This likely a relatively easy fix, but it probably only applies to very few records.

Tagging for DevPri to prioritize.

Valerie AddonizioSeptember 16, 2021 at 4:51 PM

Review of this ticket has been assigned within Metadata Standards; review will be forthcoming.

Done

Details

Assignee

Reporter

Labels

Time tracking

2d logged

Fix versions

Priority

Harvest Time Tracking

Open Harvest Time Tracking

Created August 19, 2021 at 8:00 PM
Updated September 8, 2022 at 1:31 PM
Resolved September 8, 2022 at 1:31 PM
Harvest Time Tracking