You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 24, 2020. It is now read-only.
In addition to the PUT method to start a manual validity check it might be worthwhile to take a hint from cijoe and have a uri for last full validity check, independent of specific job. So it would return:
200 - OK (last check was successful)
412 - PRECONDITION FAILED (like cijoe) or 500 error??
Could include last modified headers for when job was completed.
A payload could be retrieved with specific errors.
The text was updated successfully, but these errors were encountered:
Should this information be added to the metadata returned when listing bags, rather than calling the validation url for each bag. It would also give 3rd parties a quick way to know which bags have been 'finished'
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In addition to the PUT method to start a manual validity check it might be worthwhile to take a hint from cijoe and have a uri for last full validity check, independent of specific job. So it would return:
Could include last modified headers for when job was completed.
A payload could be retrieved with specific errors.
The text was updated successfully, but these errors were encountered: