-
Notifications
You must be signed in to change notification settings - Fork 2
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
import jade-lta data into FC #221
Comments
Sounds like this involves appending to the FC data schema. Can this be reflected in https://github.com/WIPACrepo/file_catalog/blob/master/file_catalog/schema/types.py#L163? |
I'm not sure if it does or not. Depends exactly how much is optional, and how much info @blinkdog has in the jade-lta DB. |
Optional fields included, it's nice to have a centralized reference of what all could possibly be in an FC record. Even though the schema is not prescriptive / records aren't fully validated (as of now). |
BTW, some checksums are NULL. Not a huge number, but that's another corner case for us. |
What's an instance of this? |
A checksum with a sha512 subfield is mandatory in the validation step (https://github.com/WIPACrepo/file_catalog/blob/master/file_catalog/schema/validation.py#L47). NULL/None values will fail to POST |
Of course the file isn't there right now, but |
Looks like a regular tar, would it be difficult to get checksums for these? |
We can
|
There should be checksums for those files in the regular JADE database too. As for the files at NERSC, there's no help for it. We'll need to bring the bundle back in order to check that the file in there matches our checksum (regardless if we get it from pole disk or a JADE database). |
If we need to bring all the files back, that sounds like a great thing to do next year for running pass3. |
Import old archive data from jade-lta into the FC, in the proper format to be retrieved.
The text was updated successfully, but these errors were encountered: