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: uncompressed AIPs need pointer files #324

Open
jrwdunham opened this issue Feb 9, 2018 · 3 comments
Open

Problem: uncompressed AIPs need pointer files #324

jrwdunham opened this issue Feb 9, 2018 · 3 comments
Assignees
Labels
Picturae 📍 Pointer-files Request: discussion The path towards resolving the issue is unclear and opinion is sought from other community members. Status: refining The issue needs additional details to ensure that requirements are clear. Waffle label.

Comments

@jrwdunham
Copy link
Contributor

jrwdunham commented Feb 9, 2018

Pointer files are needed to describe uncompressed AIPs. (They are already created for compressed AIPs.) Motivations:

  1. Encrypted uncompressed AIPs (which are tarred) need pointer files so we can know which GPG key is needed to decrypt them.
  2. Replica uncompressed AIPs need pointer files so we can know what original AIP is their source.
    • Relatedly, uncompressed AIPs cannot currently be replicated. AIP replication requires a pointer file.
  3. Improving the performance of fixity checking requires pointer files for uncompressed AIPs so that bag-based fixity checking of the entire AIP can be documented in the pointer files of all kinds of AIPs. See Problem: checksum verification happens twice archivematica#918.

The scope of fixing this issue should include introduction of METS/PREMIS validation using the validation already implemented in mets-reader-writer.

TODO: provide an estimate of what resolving this issue would entail.

@jrwdunham jrwdunham added the Request: discussion The path towards resolving the issue is unclear and opinion is sought from other community members. label Feb 9, 2018
@jrwdunham jrwdunham self-assigned this Feb 9, 2018
@joel-simpson
Copy link

Adding some context and additional detail following a brief discussion with @sromkey.... one of the reasons uncompressed AIPS did not have pointer files was due to a limitation in earlier versions of PREMIS, where you could only describe a bitstream, but not an intellectual entity. PREMIS 3 now allows for description of intellectual entity.

I would add a further motivation for this fix... simple consistency. It would simply make more sense to have a pointer file for every AIP (one less 'exception' or special case for users to have to understand). Alternatively, the UI should explain why there isn't a pointer file, or at least not provide a button to view the pointer file when one doesn't exist (currently if you press that button for an uncompressed AIP you get a 404 message from the storage service which is not very user-friendly).

@sallain
Copy link
Member

sallain commented Dec 19, 2019

@ross-spencer Assigning this to you for the future - it's for 1.12, but probably needs some analysis!

@jens-st
Copy link

jens-st commented Aug 18, 2021

I agree with @joel-simpson, more consistency for AIPs and less confusion for dashboard users.
Clicking on Pointer file --> "View" on a previous selected AIP still results in a 404 (not found) error for the user in Archivematica 1.13.0.

{"success": false, "message": "Storage service returned 404; check logs?"}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Picturae 📍 Pointer-files Request: discussion The path towards resolving the issue is unclear and opinion is sought from other community members. Status: refining The issue needs additional details to ensure that requirements are clear. Waffle label.
Projects
None yet
Development

No branches or pull requests

6 participants