-
Notifications
You must be signed in to change notification settings - Fork 1
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
Version manifest should recreate missing versions #907
Comments
@justinlittman can you say more about why we need to write these versions? Why not just have the actual versions in the manifest? |
Otherwise PURL would not to understand that these versions were implicitly withdrawn. This avoids PURL having to be aware of such logic. |
@justinlittman Where in purl does it care about missing versions? |
When an object is public then dark then public, it's earlier user versions are deleted from stacks. When it is made public, there is a requirement to indicate that earlier user versions existed, but were withdrawn. @andrewjbtw Is this a correct understanding of the requirement? |
@justinlittman Sorry, I missed the question in the ticket here. Yes, that's the correct understanding. |
When writing a new object and the version > 1, entries should be made in the version manifest for previous versions. Those previous versions should be marked as permanently_withdrawn and have no date. The head version should be set to the version.
The text was updated successfully, but these errors were encountered: