-
Notifications
You must be signed in to change notification settings - Fork 3
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
Deployment of new PMPY #196
Comments
This was blocked until Jupiter 2.1.0. Currently it's blocked by a change in architecture which requires a shared file system for era_assets with Jupiter |
Thanks all for the work on the AIPs. Reviewing in progress (still to look at AIP for a collection and an AIP for modified item), but minor observations thus far (notes here:
|
It looks like information on modification date and the agent that made the modification are not being captured; notes here. |
Currently AIPs are not being created for collections. There is important information about collections that we should be capturing in the preservation metadata in one way or another. This discussion can pick up again following on conversations about our preservation path going forward. |
Reviewed details on what is currently being collected in the database for communities and collections (database schema: https://github.com/ualbertalib/jupiter/blob/b6961f5a3b9fd20fd552469d5872eca425f7d6bf/db/schema.rb#L91-L123 samples: https://gist.github.com/pgwillia/eed7dd858e17a9a67f9d90cb1d703adb#file-atmire_collection_data-csv and https://gist.github.com/pgwillia/eed7dd858e17a9a67f9d90cb1d703adb#file-atmire_community_data-csv). Properties for inclusion in AIPs for collections: rdf:type (i.e., is a pcdm:Collection) Properties for inclusion in AIPs for communities: rdf:type (is a pcdm:Object, is a ual:Community) |
The text was updated successfully, but these errors were encountered: