Difference between revisions of "Bagger"

From COPTR
Jump to navigation Jump to search
(Trial import from script.)
 
(8 intermediate revisions by 5 users not shown)
Line 1: Line 1:
{{Infobox_tool
+
{{Infobox tool
|purpose=GUI application to  facilitate the creation and verification of BagIt bags.
+
|purpose=GUI application to  facilitate the creation and verification of [[BagIt]] bags.
|image=
+
|homepage=https://github.com/LibraryOfCongress/bagger
|homepage=http://sourceforge.net/projects/loc-xferutils/files/loc-bagger/
 
 
|license=Open License, but relies on several Apache based and GNU licensed components.
 
|license=Open License, but relies on several Apache based and GNU licensed components.
|platforms=
+
|function=Fixity, Transfer
 
}}
 
}}
 +
{{Infobox tool details
 +
|ohloh_id=Bagger
 +
}}
 +
= Description =
 +
The [[BagIt]] specification is a hierarchical file packaging format for the creation of standardised digital containers called 'bags,' which are used for storing and transferring digital content. Derived from work by the Library of Congress and the California Digital Library, a bag consists of a ‘payload’ - the digital content - and ‘tags' - metadata files to document the storage and transfer of the bag. There are a number of [http://sourceforge.net/projects/loc-xferutils/ Bagit-specific tools] to ease bag creation, including the BagIt Library, a Java-based software library to support the creation, manipulation, and validation of bags. For those less comfortable with command-line interface, the Bagger application provides a graphical user interface to the BagIt Library.
 +
====Provider====
 +
The United States Library of Congress, and the National Digital Information Infrastructure and Preservation Program (NDIIPP)
 +
====Licensing and cost====
 +
[http://www.linfo.org/bsdlicense.html BSD License] - free.  The BagIt Library is public domain.
 +
====Development activity====
 +
Bagger 2.1.2 was released in February 2012. BagIt Library 4.1 was released in January 2012.
 +
The Library of Congress website implies ongoing development of the Transfer Utilities. 
 +
====Platform and interoperability====
 +
Both the BagIt Library and Bagger require Java 6.
 +
====Functional notes====
 +
Bags contain at minimum three elements: a ‘payload’ and at least two ‘tags.’ The payload consists of the content being preserved. The first tag is a manifest itemising the files making up the content along with their checksums; the second is a bagit.txt file identifying the container as a bag and giving the version of the specification used and the character encoding of the tags.  The specification additionally allows for several optional tags.  
 +
====Documentation and user support====
 +
Documentation is extremely sparse, primarily consisting of README files detailing release notes. The [http://www.digitalpreservation.gov/documents/bagitspec.pdf BagIt specification itself ]can be found through the Library of Congress website.
 +
It appears that the main user support consists of a mailing list hosted by Sourceforge; however, the list archive only shows 11 posts for 2011.
 +
====Usability====
 +
The BagIt Library uses a command-line interface, while Bagger provides a graphical user interface. No installation is required; the tools can simply be downloaded and run, although it may not be immediately clear to users how to do so.
 +
====Expertise required====
 +
BagIt is designed to create a common language for users exchanging digital materials, essentially negating the need for expertise about others’ protocols. However, for configuration, familiarity with one’s own repository’s technical protocols is essential.
 +
====Standards compliance====
 +
The BagIt specification is an Internet Engineering Task Force (IETF) internet draft.
 +
====Influence and take-up====
 +
The BagIt specification has become widely accepted in the preservation community, and is used by the Library of Congress, Chronopolis, and The Stanford Digital Repository, among others. The Transfer Utilities have been downloaded nearly 4000 times from Sourceforge.
  
<!-- Delete the Categories that do not apply -->
 
[[Category:Fixity]]
 
 
 
= Description =
 
Tool to produce a package of data files according to the BagIt specification. It's a Java Spring based application using the Spring Rich Client framework. Developed by Library of Congress.
 
  
 
= User Experiences =
 
= User Experiences =
Line 19: Line 39:
 
= Development Activity =
 
= Development Activity =
  
{{Infobox_tool_details
 
|ohloh_id=Bagger
 
}}
 
  
=== Activity Feed===
+
 
 +
=== Activity Feed===
 
Link to any RSS feed that is updated when issue or code updates occur, if any, e.g:
 
Link to any RSS feed that is updated when issue or code updates occur, if any, e.g:
<rss max=7>http://sourceforge.net/api/file/index/project-id/247203/mtime/desc/limit/20/rss</rss>  
+
<rss max=7>https://github.com/LibraryOfCongress/bagger/commits/master.atom</rss>
  
 
=== Release Feed ===
 
=== Release Feed ===

Latest revision as of 14:28, 25 November 2022




GUI application to facilitate the creation and verification of BagIt bags.
Homepage:https://github.com/LibraryOfCongress/bagger
License:Open License, but relies on several Apache based and GNU licensed components.
Function:Fixity,Transfer
Appears in COW:Digital archiving workflow (high-level)



Description[edit]

The BagIt specification is a hierarchical file packaging format for the creation of standardised digital containers called 'bags,' which are used for storing and transferring digital content. Derived from work by the Library of Congress and the California Digital Library, a bag consists of a ‘payload’ - the digital content - and ‘tags' - metadata files to document the storage and transfer of the bag. There are a number of Bagit-specific tools to ease bag creation, including the BagIt Library, a Java-based software library to support the creation, manipulation, and validation of bags. For those less comfortable with command-line interface, the Bagger application provides a graphical user interface to the BagIt Library.

Provider[edit]

The United States Library of Congress, and the National Digital Information Infrastructure and Preservation Program (NDIIPP)

Licensing and cost[edit]

BSD License - free.  The BagIt Library is public domain.

Development activity[edit]

Bagger 2.1.2 was released in February 2012. BagIt Library 4.1 was released in January 2012. The Library of Congress website implies ongoing development of the Transfer Utilities. 

Platform and interoperability[edit]

Both the BagIt Library and Bagger require Java 6.

Functional notes[edit]

Bags contain at minimum three elements: a ‘payload’ and at least two ‘tags.’ The payload consists of the content being preserved. The first tag is a manifest itemising the files making up the content along with their checksums; the second is a bagit.txt file identifying the container as a bag and giving the version of the specification used and the character encoding of the tags.  The specification additionally allows for several optional tags.  

Documentation and user support[edit]

Documentation is extremely sparse, primarily consisting of README files detailing release notes. The BagIt specification itself can be found through the Library of Congress website. It appears that the main user support consists of a mailing list hosted by Sourceforge; however, the list archive only shows 11 posts for 2011.

Usability[edit]

The BagIt Library uses a command-line interface, while Bagger provides a graphical user interface. No installation is required; the tools can simply be downloaded and run, although it may not be immediately clear to users how to do so.

Expertise required[edit]

BagIt is designed to create a common language for users exchanging digital materials, essentially negating the need for expertise about others’ protocols. However, for configuration, familiarity with one’s own repository’s technical protocols is essential.

Standards compliance[edit]

The BagIt specification is an Internet Engineering Task Force (IETF) internet draft.

Influence and take-up[edit]

The BagIt specification has become widely accepted in the preservation community, and is used by the Library of Congress, Chronopolis, and The Stanford Digital Repository, among others. The Transfer Utilities have been downloaded nearly 4000 times from Sourceforge.


User Experiences[edit]

Development Activity[edit]

Activity Feed[edit]

Link to any RSS feed that is updated when issue or code updates occur, if any, e.g:

2022-09-27 21:10:53
[tag:github.com,2008:Grit::Commit/dff49de4e74f075b7451aed574b053b6b02fda83 Merge pull request #71 from LibraryOfCongress/add-rfq-information]
by acdha https://github.com/acdha
2022-09-27 20:10:09
[tag:github.com,2008:Grit::Commit/8373c1858c990f08a20872261c88677dd1898704 Add RFQ announcement]
by acdha https://github.com/acdha
2018-04-30 14:00:15
[tag:github.com,2008:Grit::Commit/d3856aa3f048740d996dda494cc9cf1d47533a70 updated issue template for github]
by johnscancella https://github.com/johnscancella
2018-04-18 13:35:21
[tag:github.com,2008:Grit::Commit/ecd742ed0f6e81e4f3875e2f8826dbf6416cb225 include new profiles when copying default profiles]
by johnscancella https://github.com/johnscancella
2018-04-16 15:41:51
[tag:github.com,2008:Grit::Commit/41c07101d44d16755d05009d2fc9c67140b760fe Merge pull request #52 from StateArchivesOfNorthCarolina/master]
by johnscancella https://github.com/johnscancella
2018-04-16 13:35:37
[tag:github.com,2008:Grit::Commit/1d3e1f693dc95158c8806674ead3fb8b59455b67 Profiles for North Carolina State and Local government]
by jmgibson71 https://github.com/jmgibson71
2018-01-26 20:53:09
[tag:github.com,2008:Grit::Commit/b8865dcd2ed6a23370491160155f549d5e108338 remove repo-dev email from support listing]
by johnscancella https://github.com/johnscancella

Release Feed[edit]