AIP, DIP, SIP generation

[Alex Kent]

We have been getting questions recently about automatic generation of AIP, DIP, and SIP packages

AIP - Archival Information Packet

DIP - Dissemination Information Packet

SIP - Submission Information Packet

How would you answer the question, does Islandora have these? I have said that we don't officially have these all packaged together, but that there are automatic processes that create derivatives, etc.  I just want to make sure I am not missing anything, and to see what others have done here.  

Thanks in advance, hopefully my question is clear...

[dp...@metro.org]

Hi Alex,

All those are formats (input/transport/storage) that Archivematica manages and Islandora does not have them natively. But many of our own (fedora) representations look similar to pieces/version of those.

Mark Jordan and I had a meeting last week with Justin Simpson about this: how to get from Archivematica to Islandora and what native/inter-format and workflow would be the best to do so. 

I started to sketch an idea around that and some workflow, basically working on existing code and using the various API's that archivematica exposes to fetch the resources and build back an Islandora Object.

It will take me some time (probably months) but it is something I always wanted to do and Mark Jordan (with his knowledge and wisdom on this and many other matters) is a great support on accomplishing this.

Best

Diego Pino N

Metro.org

[Companjen, B.A.]

Hi Alex,

 

SIP, AIP and DIP are conceptual terms for – roughly – "what you ingest", "what you store" and "what you offer by default". Islandora does not explicitly mention the terms, as Islandora doesn't come from the digital preservation realm, and moreover, because the terms don't map to Islandora concepts directly.

 

A SIP could be a single file or a ZIP that becomes a single or multiple objects that form one or more AIPs and DIPs. It depends on where you draw the line around AIP and DIP. Archivematica, mentioned by Diego Pino, makes a more direct mapping of *IP to a directory in the storage system. I think that is a design decision that relates to the software being targeted at digital preservation people.

 

If one Islandora object is the result of a SIP, I would probably consider the MODS, RELS-EXT, RELS-INT and OBJ datastreams as part of the AIP and MODS, RELS-EXT and derivative datastreams part of the DIP, since that is what you want to preserve and disseminate, respectively.

 

I hope this helps a little; there is a lot to talk about when it comes to digital preservation.

 

Regards,

 

Ben

--
For more information about using this group, please read our Listserv Guidelines: http://islandora.ca/content/welcome-islandora-listserv
---
You received this message because you are subscribed to the Google Groups "islandora" group.
To unsubscribe from this group and stop receiving emails from it, send an email to islandora+...@googlegroups.com.
Visit this group at https://groups.google.com/group/islandora.
To view this discussion on the web visit https://groups.google.com/d/msgid/islandora/da8fa41a-1ba8-4594-8ace-567ba857d07e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mark Jordan]

Hi Alex,

I agree with what Ben says, and also want to point to the excellent work Nick has done at York around documenting how Islandora fits into their digital preservation action plans. Brad Spry has also done a lot of super work in this area.

But, I'd be very cautious about ticking the "digital preservation" box just because you can lay the SIP/AIP/DIP language over Islandora. Digital preservation is more about process than it is about formats or packages. If you don't have an explicit, proactive plan for ensuring your AIPs remain accessible into the future, you're probably not going to be able to access them in the future. To help Islandora sites create actionable digital preservation processes, Islandora can:

• Enable checksums on datastreams, via the Checksum module
  
• Perform periodic integrity checks on datastreams, via the Checksum Checker module
  
• Document and manage the results of those integrity checks over time, via the PREMIS module
  
• Export objects in a preservation-friendly package, via the BagIt module
  

For sites that don't want to implement a full-stack digital preservation platform, these tools are the basis for . If a site also implements Archivematica, it's currently possible to push Islandora objects to Archivematica via the Archidora module (in which case, Islandora objects are the Archivematica SIP; Archivematica then manages the AIP and DIP according to its policies and workflows). The work that Diego mentioned turns this worfklow around, so that the Islandora object is the DIP; the SIP and the AIP are managed by Archivematica.

My advice is to not focus on whether Islandora has SIPs, AIPs, and DIPs, but to develop a digital preservation policy/framework/action plans defining what your institution wants to achieve with "digital preservation", and stemming from those goals develop processes that you can then apply to your digital assets. The *IPs are only relevant to the extent that they provide a common vocabulary for documenting digital preservation processes and workflows. You're correct in saying that Islandora has some automated digital preservation processes but they need to be configured to support local policies/action plans.

Mark

To view this discussion on the web visit https://groups.google.com/d/msgid/islandora/B6AD91D7-F815-4ABD-861C-564038B1B446%40library.leidenuniv.nl.

[Alex Kent]

Thanks for the replies! They are certainly helpful.  I wanted to be sure I described these correctly.   What would be use cases for having the SIP, AIP, DIPS generate automatically? I need to research these more, but thought I would ask here as well.  

Thanks again!