LogoLogo
  • What is LABDRIVE
  • Concepts
    • Architecture and overview
    • Organize your content
    • OAIS and ISO 16363
      • Understanding OAIS and ISO 16363
      • LABDRIVE support for OAIS Conformance
      • Benefits of preserving research data
      • Planning for preservation
      • ISO 16363 certification guide
      • LABDRIVE support for FAIRness
  • Get started
    • Create a data container
    • Upload content
    • Download content
    • Introduction to metadata
    • Search
    • File versioning and recovery
    • Work with data containers
    • Functions
    • Storage mode transitions
    • Jupyter Notebooks
  • Configuration
    • Archive organization
    • Container templates
    • Configure metadata
    • Users and Permissions
    • Running on premises
  • DATA CURATION AND PRESERVATION
    • Introduction
    • Information Lifecycles
    • Collecting Information needed for Re-Use and Preservation
    • Planning and Using Additional Information in LABDRIVE
    • How to deal with Additional Information
      • Representation Information
      • Provenance Information
      • Context Information
      • Reference Information
      • Descriptive Information
      • Packaging Information
      • Definition of the Designated Community(ies)
      • Preservation Objectives
      • Transformational Information Properties
    • Preservation Activities
      • Adding Representation Information
        • Semantic Representation Information
        • Structural Representation Information
        • Other Representation Information
          • Software as part of the RIN
            • Preserving simple software
              • Jupyter Notebooks as Other RepInfo
            • Preserving complex software
              • Emulation/Virtualisation
                • Virtual machines as Other RepInfo
                • Docker and other containers as Other RepInfo
              • Use of ReproZip
      • Transforming the Digital Object
      • Handing over to another archive
    • Reproducing research
    • Exploiting preserved information
  • DEVELOPER'S GUIDE
    • Introduction
    • Functions
    • Scripting
    • API Extended documentation
  • COOKBOOK
    • LABDRIVE Functions gallery
    • AWS CLI with LABDRIVE
    • Using S3 Browser
    • Using FileZilla Pro
    • Getting your S3 bucket name
    • Getting your S3 storage credentials
    • Advanced API File Search
    • Tips for faster uploads
    • File naming recommendations
    • Configuring Azure SAML-based authentication
    • Exporting OAIS AIP Packages
  • File Browser
    • Supported formats for preview
    • Known issues and limitations
  • Changelog and Release Notes
Powered by GitBook
On this page

Was this helpful?

  1. DATA CURATION AND PRESERVATION
  2. How to deal with Additional Information

Packaging Information

This is the information that describes how the components of an Information Package are logically or physically bound together and how to identify and extract the components.

PreviousDescriptive InformationNextDefinition of the Designated Community(ies)

Last updated 3 years ago

Was this helpful?

An information Package is quite a general object and the Packaging Information describes how the various components are arranged and how they can be extracted.

OAIS does not provide any details for the SIP or DIP.

On the other hand OAIS provides a great deal of requirements for the Archival Information Package (AIP), and so the bulk of the following is about the AIP.

Only the packaging format maps directly to the OAIS Archival Information Package.

An OAIS AIP may be as simple as a collection of pointers to the various components required by OAIS, namely

  • Data Object

  • Representation Information

  • Provenance Information

  • Fixity Information

  • Reference Information

  • Context Information

  • Access Rights Information

The packaging Information would in such as case be definition of the way in which the pointers may be identified. For example the shows how to identify and extract the various components of the AIP.

A ZIP or TAR or other general "box/holder" containing all the components in a flat structure could also be an AIP as long as it was accompanied by the instructions as to how to identify and extract the various required components, for example having such instructions in a simple text file.

On the other hand, despite the name, the does not seem to be compatible with the OAIS AIP because it does not seem possible to assign a place for the various required components, for example the Representation Information.

XFDU
E-ARK AIP specification
discussion of BAGIT