-
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
Problem: aip ingest date is not easy to find when using indexless mode #1529
Milestone
Comments
scollazo
changed the title
Problem: aip size is not easy to find
Problem: aip size is not easy to find when using indexless mode
Feb 2, 2022
scollazo
changed the title
Problem: aip size is not easy to find when using indexless mode
Problem: aip ingest date is not easy to find when using indexless mode
Feb 3, 2022
Related to #731 - if we add accurate stored dates in the Storage Service, we could use those in the Archival Storage tab whether or not there's a date in Elasticsearch |
Milestoned for 1.14 after discussing with @sromkey |
tw4l
added
Status: review
The issue's code has been merged and is ready for testing/review.
and removed
Status: in progress
Issue that is currently being worked on.
labels
Aug 24, 2022
Verified this by creating a compressed AIP and an uncompressed AIP and checking their |
replaceafill
removed
the
Status: review
The issue's code has been merged and is ready for testing/review.
label
May 24, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please describe the problem you'd like to be solved
I want to be able to know the size of an AIP, or the aggregate size of a list of AIPs (let's say, the ones ingested between two dates)
Describe the solution you'd like to see implemented
Add a new field to storage service locations_package that stores the AIP ingest date
Describe alternatives you've considered
Additional context
This feature would be useful for creating reports showing how many aips/gigabytes have been ingested in a period of time
For Artefactual use:
Before you close this issue, you must check off the following:
The text was updated successfully, but these errors were encountered: