Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enrichment attributes are being saved to the wrong record #69

Merged
merged 11 commits into from
Jun 12, 2024

Conversation

richardmatthewsdev
Copy link
Contributor

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.

…of a fragment when the enrichment URL is full in the fragment
Allow the key and source id for an enrichment to be specified in an extraction definition.
…e pages refer to the correct document

The filesystem order cannot be relied on as different filesystems order files differently. We are essentially treating the file system as an array of pages and needing the index to be the same as the page number, so doing something like @documents[10] needs to give page the 10th page. Without sorting them this is not necessarily the case and you can get back a different page than what you are expecting.
@richardmatthewsdev richardmatthewsdev merged commit 3019f1b into DigitalNZ:main Jun 12, 2024
6 of 8 checks passed
@richardmatthewsdev richardmatthewsdev deleted the rm/enrichment-attribute-issue branch June 14, 2024 01:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants