There should be added validation to the mod-inventory on the Handlers level. The main goal is to finish the data import process with errors (fail it) in cases when some UUID-type fields are not UUID one(it can be the case when the value from specific field, ex: “949$n” can’t match the accepted values on the env). It will avoid us from unknown errors on the next processing of newly created/updated entities with valid fields.

Feel free to look into this ticket, this was already implemented for “natureOfContentTermIds“: [MODINV-1012] [RRT] Invalid values (as it is) created in JSON when value is not matching accepted options provided in Instance field mapping for Nature of Content term - FOLIO Jira (atlassian.net)

Also, there is a code base for the different fields on the branch named “MODINV-1012-extended”. Feel free just to extend it with different entites/fields.

This validation should be added for Create and Update actions.

It should be added for these fields:

1. Instance:
   - statisticalCodeIds
   - alternativeTitles.alternativeTitleTypeId
   - identifiers.identifierTypeId
   - contributors.contributorNameTypeId; contributors.contributorTypeId
   - instanceTypeId
   - natureOfContentTermIds
   - instanceFormatIds
   - notes.instanceNoteTypeId
   - classifications.classificationTypeId

2. Holdings:
   - statisticalCodeIds
   - permanentLocationId
   - temporaryLocationId
   - callNumberTypeId
   - illPolicyId
   - notes.holdingsNoteTypeId

3. Item
   - statisticalCodeIds
   - materialType
   - itemLevelCallNumberTypeId
   - itemDamagedStatusId
   - permanentLoanType.id
   - temporaryLoanType.id
   - permanentLocation.id
   - temporaryLocation.id
   - electronicAccess.relationshipId