comet: allow ARK creation (but not modification) from Bulkrax ingest
When creating or updating resources via Bulkrax, it should be possible to populate (but not edit) the ARK field. This will be a common need for import from other systems which will have created the ARK. Bulkrax should not explicitly call out to the EZID api when updating these ARKs; this should be handled by workflow or other comet infrastructure.
Acceptance Criteria:
-
When creating or updating resource via batch import and data is in an ARK field in the import document (eg CSV), the data is added to the ARK field on the object if and only if: -
the data can be cast to a valid ARK URI; -
the resource does not already have an ARK.
-
-
if the above criteria are not met, fail validation before creating/updating other data on resources.
related to: ucsb-library/comet-local#19 (closed)
Edited by Gabriela Montoya