Skip to:

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

MARC Authority Validation: Update a Non-local MARC authority field validation rule

Description

Background: Cataloging staff wants FOLIO to check that a MARC authority record complies with MARC authority standards (https://www.loc.gov/marc/authority) and/or their own standards. 

Requirement 1: The user assigned the permission to create/edit a MARC authority field validation rule, can update Non-Local MARC fields validation rules See Non-local MARC field definition -  

Requirement 2: For Non-Local MARC fields, a user can configure the following validation rules: .

  • The user can add/append to the valid list of First and Second Indicator codes and descriptions

    • The user cannot edit any MARC documented codes and descriptions

  • The user can add/append to the valid list of subfield codes and descriptions

    • The user cannot edit any MARC documented codes and descriptions, repeatable/non-repeatable

    • The user can set the subfield code required/optional for all subfield codes (whether MARC documented or created by user)

    • For the additional subfield codes, the user can specify required/optional, repeatable/non-repeatable

Scenario 1 > No change to Default validation rules list

IF the library/tenant has made no change to default MARC authority validation rules

THEN Non-local MARC fields validation rules for the following will be based on MARC authority specifications will be based on MARC authority specifications - https://www.loc.gov/marc/authority/ecadlist.html

  • Field description and repeatable/non-repeatable designation

  • First indicator description, indicator codes, and indicator code descriptions

  • First indicator description, indicator codes, and indicator code descriptions

  • Second indicator description, indicator codes, and indicator code description

  • Subfield codes, description, repeatable/non-repeatable designation

Scenario 2 > Changed a MARC validation rule

MARC validation rule

Expected outcome

Change Field to required

The field is required to save record

Change Field description

The library can add more information (up to 350 characters) to help catalogers

Change Help URL

The library can link to a page that has more details about their catalog practices for a specific field.

Append First indicator codes + code descriptions

The library may include additional indicator codes and code descriptions to valid list.

Append Second indicator codes + code descriptions

The library may include additional indicator codes and code descriptions to valid list.

Set any subfield code to required

The library may set any subfield code as required IF the field has been added to the record.

Append subfield codes + descriptions and set repeatable/non-repeatable

The library may include additional subfield codes, code descriptions and repeatable/non-repeatable designations to valid list.

Scenario 3 > Enter an invalid rule

See

Environment

None

Potential Workaround

None

Checklist

hide

Activity

Show:
Duplicate

Details

Assignee

Reporter

Labels

Priority

Development Team

Spitfire

Release

Ramsons (R2 2024)

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created April 14, 2024 at 2:34 PM
Updated July 5, 2024 at 12:24 PM
Resolved June 3, 2024 at 3:01 PM
TestRail: Cases
TestRail: Runs