Overview:

On UI we have validation for cases when:

• linkable (but not linked yet field) has $9

• linked field has additional $9 added by user

See attached screenshots for example:

Requirement:

Add validation for ‘/records-editor/records’ endpoint for following case:

• user tries to add “$9” subfield in linkable field (but not linked yet) of MARC bibliographic record via API request (POST, PUT to ‘/records-editor/records’)

No changes for linking or $9 handling.

Steps to reproduce:

1. Send POST/PUT with $9 subfield in linkable (but not linked) field:

2. Check status of started job:

Actual result: Error is returned with following message:

Expected result: Return sensible error message on for POST, PUT request, ex.: “$9 is an invalid subfield for linkable bibliographic fields.”

Approach

1. Create ticket to add UUID format validation for $9 subfield in record specification. Possible options:

   1. Update Subfield entity definition to include valueFormatType(uuid, regex) enum and valueFormat fields

   2. Use invalidSubfieldValue rule for $9

2. Check that all fields required for linking present if $9 present. If only $9 present - return expected error