Skip to content
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

Closed
5 tasks
scollazo opened this issue Feb 2, 2022 · 3 comments
Closed
5 tasks
Milestone

Comments

@scollazo
Copy link

scollazo commented Feb 2, 2022

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

  • Retrieve such info from elasticsearch (not an option if not using the index)
  • Parse archivematica logs to identify the date of transfers

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:

  • All pull requests related to this issue are properly linked
  • All pull requests related to this issue have been merged
  • A testing plan for this issue has been implemented and passed (testing plan information should be included in the issue body or comments)
  • Documentation regarding this issue has been written and merged
  • Details about this issue have been added to the release notes
@scollazo 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 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
@tw4l
Copy link

tw4l commented Aug 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

@tw4l tw4l added this to the 1.14.0 milestone Aug 19, 2022
@tw4l tw4l self-assigned this Aug 19, 2022
@tw4l tw4l added the Status: in progress Issue that is currently being worked on. label Aug 19, 2022
@tw4l
Copy link

tw4l commented Aug 19, 2022

Milestoned for 1.14 after discussing with @sromkey

@replaceafill
Copy link
Member

Verified this by creating a compressed AIP and an uncompressed AIP and checking their stored_date column in the Storage Service database being populated correctly.

@replaceafill 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
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants