Editing Bagger

{{Infobox_tool
|purpose=GUI application to  facilitate the creation and verification of BagIt bags.
|image=
|homepage=https://github.com/LibraryOfCongress/bagger
|license=Open License, but relies on several Apache based and GNU licensed components.
|platforms=
}}

<!-- Delete the Categories that do not apply -->
[[Category:Fixity]]
[[Category:Transfer]]

= Description =
The BagIt specification is a hierarchical file packaging format for the creation of standardised digital containers called &#39;bags,&#39; 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 &lsquo;payload&rsquo; - the digital content - and &lsquo;tags&#39; - 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. &nbsp;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.&nbsp;
====Platform and interoperability====
Both the BagIt Library and Bagger require Java 6.
====Functional notes====
Bags contain at minimum three elements: a &lsquo;payload&rsquo; and at least two &lsquo;tags.&rsquo; The payload consists of the content being preserved. The first tag is&nbsp;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. &nbsp;The specification additionally allows for several optional tags. &nbsp;
====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&rsquo; protocols. However, for configuration, familiarity with one&rsquo;s own repository&rsquo;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.


= User Experiences =


= Development Activity =

{{Infobox_tool_details
|ohloh_id=Bagger
}}

=== Activity Feed===
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> 

=== Release Feed ===