Enrichment attributes are being saved to the wrong record #69
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Acceptance Criteria
All enrichment data is applied to the record that it is intended for.
Notes
During our investigation of the Gazette harvest we discovered that some records were having an incorrect administering agency or title being applied to them. We can verify this because the title / administering agency on the actual landing page of the record is different to what is being written to the record. This is similar to an issue that Tim Hannah has found with enrichments on DNZ.
This also includes some quality of life changes that have been added to PCO around how to specify enrichments.