5/24/2016 Indiana Archives and Records Administration’s Accession Profile Use in Bagger https://saaers.wordpress.com/2016/05/17/indianaarchivesandrecordsadministrationsaccessionprofileuseinbagger/ 1/5 Indiana Archives and Records Administration’s Accession Profile Use in Bagger By Tibaut Houzanme and John Scancella This post is the seventh in our Spring 2016 series on processing digital materials . This quick report for the practitioner drew from the “Bagger’s Enhancements for Digital Accessions ” post prepared for the Library of Congress’ blog The Signal. ——— Context In the past, the Indiana Archives and Records Administration (IARA) would simply receive, hash and place digital accessions in storage, with the metadata keyed into a separate Microsoft Access Database. Currently, IARA is automating many of its records processes with the APPXbased Archival Enterprise Management system (AXAEM). When the implementation concludes, this open source, integrated records management and digital preservation system will become the main accessioning tool. For now, and for accessions outside AXAEM’s reach, IARA uses Bagger. Both AXAEM and Bagger comply with the BagIt packaging standard: accessions captured with Bagger can later be readily ingested by AXAEM. IARA anticipates time gains and record/metadata silos reduction. Initial Project Scope IARA aims to capture required metadata for each accession in a consistent manner. Bagger allows this to be done through a standard profile. IARAdeveloped a profile inspired by the fields and dropdown menus on its State Form (SF 48883 ). When that profile was initially implemented, Bagger scrambled the metadata fields order and the accession was not easily understood. John Scancella , the lead Bagger developer at the Library of Congress implemented a change that makes Bagger now keep the metadata sequence as originally intended in the profile. IARA then added additional metadata fields for preservation decisions. Scope Expansion and Metadata Fields With colleagues’ feedback, it appeared IARA’s profile could be useful to other institutions. A generic version of the profile was then created, that uses more generic terms and made all the metadata fields optional. This way, each institution can decide which fields it would enforce the use of. This makes the generic profile useful to most digital records project and collecting institutions. The two profiles display similar metadata fields for context (provenance, records series), identity, integrity, physical, logical, inventory, administrative, digital originality, storage media or carriers types, appraisal and classification values, format openness and curation lifecycle information for each accession. Together with the hash values and files size that Bagger collects, this provides a framework to more effectively help evaluate, manage and preserve long term digital records.