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

Consider updates to schemas when selecting records to evaluate for publication #14

Open
marksparkza opened this issue Oct 27, 2023 · 1 comment

Comments

@marksparkza
Copy link
Member

The static data initialization script, which runs on deployment, updates schema timestamps if schema content has changed since the last deployment.

When publishing, a record should be selected for evaluation if its metadata schema - or any of its tags' schemas - has been updated since it was last evaluated.

@marksparkza
Copy link
Member Author

This is only needed for records belonging to harvested collections, since only curator QC (and not metadata validity) applies to the publishing of non-harvested records.

There should still, however, be some means of invalidating previously validated records - though that should be captured as a separate issue.

There is also not really any point in checking tag schema timestamps. Tag instances must be valid when they are set on a record. If a tag schema changes subsequently, then a larger migration is probably needed.

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

No branches or pull requests

1 participant