Skip to main content
ExLibris
  • Subscribe by RSS
  • Ex Libris Knowledge Center

    How to Deposit a BagIt! bag into Rosetta

    • Product: Rosetta
    • Product Version: v5.2+
    • Relevant for Installation Type: Local

     

    Description

    BagIt deposit method supports only a single REP IE, and only one IE per SIP.
    All files under /data should be included in the fileSec (and physical StrucMap), whether or not they appear in any given manifest.
    Rosetta attempts to sort according to the order in the manifest.
    If there are 1+ manifests with conflicting file orders, Rosetta will pick one randomly.
    The dc:title for ingest is taken from the folder/directory name.
    You can define the title and other dc tags in the content structure.
    If no title is mapped Rosetta will take the bag folder name as title (DC)
    - Tag File – the name of the txt file that contains the BagIt metadata tags
    - Tag – the BagIt metadata tag to which you want to map the METS field
    - Property – the METS field to which you want to map the BagIt metadata tag
    It's not possible to use a Submission Job for automated BagIt ingest as the BagIt bag doesn't adhere to the submission folder structure that Rosetta expects (e.g. content/streams/).
    It's also not possible to map metadata tags to the IE or REP in the DNX.
    Although the bag-info.txt, manifest.txt, tagmanifest.txt are discarded after ingest, you can see BagIt! references in the following section in the METS.
    First display the IE in the Web Editor, then click on the Versions Tab, METS (e.g.):

          <mets:sourceMD ID="ie-amd-source-OTHER-2">
            <mets:mdWrap MDTYPE="OTHER">
              <mets:xmlData>
                <ser:bag xmlns:ser="http://www.exlibrisgroup.com/xsd/dps/deposit/service">
                  <file name="bag-info.txt">
                    <tag key="Bag-Software-Agent">bagit.py v1.7.0 &lt;https://github.com/LibraryOfCongress/bagit-python></tag>
                    <tag key="Bagging-Date">2018-09-20</tag>
                    <tag key="Internal-Sender-Description">Test BagIt ingest of simple object</tag>
                    <tag key="Internal-Sender-Identifier">123456789</tag>
                    <tag key="Partner">Leo Baeck Institute</tag>
                    <tag key="Payload-Oxum">818887561.21</tag>
                    <tag key="Processor">Kevin Powell</tag>
                    <tag key="Source-Organization">Center for Jewish History</tag>
                    <tag key="Title">Bag Test for Ex Libris</tag>
                  </file>
                  <file name="tagmanifest-sha1.txt">
                    <tag key="0b3d99008e4195ad7053abb0581420bbd30ce3">bag-info.txt</tag>
                    <tag key="a7679d9bd2d9211ba88af47e52390187076cc6e4">bagit.txt</tag>
                    <tag key="390c11ea741c64b7561df816fdc456878abe06e7">manifest-sha1.txt</tag>
                  </file>
                  <file name="manifest-sha1.txt">
                    <tag key="c04e51136bfb25fafdb9ba6451ccf565534237f6">data/coffeeclipart.jpg</tag>
                    <tag key="f897e1507f101528b773e50a06002f77235916fd">data/IMG_1411.JPG</tag>
                    <tag key="a3cb570315911452f6630df4ed52086dd5620544">data/EventList.xls</tag>
                  </file>
                  <file name="bagit.txt">
                    <tag key="BagIt">Version: 0.97</tag>
                    <tag key="Tag-File-Character-Encoding">UTF-8</tag>
                  </file>
                </ser:bag>
              </mets:xmlData>
            </mets:mdWrap>
          </mets:sourceMD>

    Procedure

    BagIT manual Deposit Material Flow Procedure:

    I. Confirm that your BagIt! bag conforms to the BagIt! standard and includes the following components: bag-info.txt, manifest.txt, tagmanifest.txt, and a /data/ folder containing the files to be ingested.

    II. BagIT Material Flow Setup

    a. Define the Content Structure: Deposits > Deposit Arrangements > Content Structure > Add Content Structure: Bagit Converter > Add
    Configure Profile for IE metadata that will be be stored in the METS, indexed, and searchable.
    Add Tag File, Tag, and Property for all relevant metadata elements from the bag-info.txt (e.g.):
      Store Tags as Source Metadata: Yes.
      Tag File   Tag    Property  
      bag-info.txt  Title    Title (DC)
      bag-info.txt  Internal-Sender-Description  Description (DC)
      bag-info.txt  Bagging-Date   Date (DC)
      bag-info.txt  Internal-Sender-Identifier  Identifier (DC)

    b. Define the Submission Format: Deposits > Deposit Arrangements > Submission Format > Add Submission Format > NFS
    Example: /operational_shared/submissions/ABC01/BAGIT in the “NFS Path” field in the submission format.

    c. Define the Material Flow: Deposits > Deposit Arrangements > Material Flows > Material Flow List > Add Material Flow
    Note: you must add the newly-created Material Flow to the Producer Profile's Material Flow List in order to use it during deposit.

    d. Define the SIP Processing Configuration: Submissions > Advanced Tools > SIP Processing Configuration >Add Processing Configuration

    e. Define the SIP Routing Rules: Submissions > Advanced Tools > SIP Routing Rules > Add Rule

    III. Procedure
    1. As per the Submission Format (above), go to the NFS directory on the server and create a new folder (e.g.): /operational_shared/submissions/ABC01/BAGIT/test1/
    This folder should include the following files: bag-info.txt, manifest.txt, and tagmanifest.txt.

    2. /test1/ it should have a /data/ subdirectory (e.g.): /operational_shared/submissions/ABC01/BAGIT/test1/data/
    This folder should include the files (objects) you want to ingest.

    3. Connect to the Rosetta Deposit module and choose the appropriate Producer, click “Continue,” then “Add Deposit Activity”

    4. Choose the appropriate Type of Material (‘bag’) from the list, click “Next,” then select the appropriate 'bag' for the Material Type, then “Submit Deposit”

    5. Click on the “Submitted” folder in the Deposit Module and note the SIP ID (e.g. 347).

    6. From the Management Module’s landing page enter the SIP ID (e.g. “347”) into the Submissions search box which takes you to a summary page.
    From this landing page you can where you can click “Report” to see a BIRT report where the SIP stage is identified.
    “Finished” means that the IE has been saved to the Permanent repository.

     

    • Was this article helpful?