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 · 1 comment

Comments

Projects
None yet
2 participants
@jrwdunham
Copy link
Contributor

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 artefactual/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.

@joel-simpson

This comment has been minimized.

Copy link

commented Aug 8, 2018

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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.