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
  • Configuring your OAIS mapping
  • Generating a JSON AIP Package

Was this helpful?

  1. COOKBOOK

Exporting OAIS AIP Packages

The platform provides the capability of exporting any folder (or group of folders) as an OAIS AIP package, encoded in a JSON file.

PreviousConfiguring Azure SAML-based authenticationNextSupported formats for preview

Last updated 1 year ago

Was this helpful?

The platform provides the capability of exporting any folder (or group of folders) as an OAIS AIP package, encoded in a JSON file. Once configured, the JSON file will include all required all required AIP elements according to the OAIS.

Configuring your OAIS mapping

The OAIS AIP definition classifies the information that is related to an AIP package in Representation Information and Preservation Description Information. Additionally, each group contains additional elements. For instance, the Structure Information is part of the Representation Information:

The platform allows the administrator to map the metadata fields used to contain each information type, to its corresponding type according the OAIS AIP definition. For instance, if your "Title" metadata field is part of the Reference Information (which is part of the Preservation Description Information), you can map both elements in the platform in the OAIS AIP Packages configuration section:

And then in the AIP sections field mapping section:

In the left column (1) you have the IECODE of the Metadata field in your platform, and in the right column (2) you have the OAIS section it belongs to.

Using the Add button (3), you can create additional entries:

Organizations can better explain the semantics of their OAIS AIP packages, or even define semantics that apply to the whole AIP package, to better explain OAIS Representation Information Networks or to simply add semantics to the AIP Packaging. In the AIP Packaging information section, the Administrator can provide additional information that will be included in every AIP package generated. This is a good place to include information that will help future users to understand your AIP Packages. Information can be formatted using the Markdown markup language.

Generating a JSON AIP Package

Once the platform has been configured, the user can simply select one or more folders in the File Browser and call the OAIS AIP Generation function:

This function will create the corresponding JSON file including the whole AIP package details and its related elements:

The Function will create a log, like any other function:

And can be called programmatically. Please review the Functions section for additional information.

Finally, you can download your JSON file and their associated folders like any other file in the platform.