IQSS / IQSS/dataverse

Add Additional Bag-info.txt Configuration

Open
#10,226 6 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

GREI 6 Type: Feature
Dominant language
Java
Stars
1.1k
Forks
564
Avg merge
2d 2h
Merged PRs (30d)
29

Description

Overview of the Feature Request
UVA is ingesting bags to APTrust and would like to have the tag (line) "Bag-Group-Identifier" in bag-info.txt. This tag is part of APTrust's spec: https://aptrust.github.io/userguide/bagging/

What kind of user is the feature intended for?
Sysadmin

What inspired the request?
Ingesting bags into APTrust which ingests many different collections. APTrust uses the tag "Bag-Group-Identifier" to find all items for a given "group" in APTrust's interface.

What existing behavior do you want changed?
To add a new JVM option to customize this new bagit-info.txt configuration:
https://guides.dataverse.org/en/latest/installation/config.html#configuring-bag-info-txt

Suggesting to have a new customization configuration to add

Bag-Group-Identifier

to the bag-info.txt file with a JVM configuration option, like this:

dataverse.bagit.sourceorg.groupidentifier

and have out of the box configuration write bag-info.txt files with:

Bag-Group-Identifier: <Group identifier>

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the bag-info.txt configuration described in the installation config guide and trace the JVM-option entry point that writes bag metadata. Done means the new Bag-Group-Identifier setting can be customized and generated bag-info.txt files contain the requested tag and value.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
56/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.