Archivematica - User contributions [en]

Community/Camps/Baltimore2018

2018-04-16T14:46:52Z

Evelyn: /* Camp staff */

The lovely city of Baltimore, Maryland is the location of our next eastern seaboard Archivematica Camp, cohosted by the Sheridan Libraries at [https://www.library.jhu.edu/ Johns Hopkins University].

Inspired by similar events like Hydra Camp, Islandora Camp and Fedora Camp, Archivematica Camp provides a space for anyone interested in or currently using Archivematica to come together, learn about the platform from other users, and share their experiences.

== Dates and Location ==

'''WHEN: Wednesday, June 20 to Friday, June 22, 2018'''

'''WHERE: [https://goo.gl/maps/jagXhcVHK232 Brody Learning Commons Room 5015/5017,]''' Johns Hopkins University, Baltimore, MD.

The Brody Learning Commons is connected to the Milton S. Eisenhower Library, the combination of which is generally known as "the Library." Security guards will be advised that the conference is happening and can direct you to the room. Please bring photo ID.

=== Getting there ===

The Johns Hopkins University campus is located in north Baltimore, approximately 15 minutes by car and 30 minutes by transit from downtown Baltimore. Parking information is here: http://ts.jhu.edu/Parking/Visitors/

Two free bus lines operate that drop riders off at the corner of 33rd Street and Charles Street, just in front of the Library.

* JHU Shuttle: http://ts.jhu.edu/Shuttles/index.html

* Charm City Circulator Purple Line: https://www.charmcitycirculator.com/route/purple

Both of these bus services have apps that we'd recommend downloading to receive real-time updates about timetables. Both buses run roughly every 15 minutes.

=== Accessibility ===

The Brody Learning Commons is wheelchair-accessible from both entrances, but we'd recommend the south entrance from the service road, next to a building called Merrick Barn. Contact info@artefactual.com for more information and we'll put you in touch with JHU staff. We're happy to help!

== Registration ==

[https://www.eventbrite.com/e/archivematica-camp-baltimore-registration-45045169314 '''Register here!''']

Registration will open on April 16.

=== Full registration ===

'''Early bird''': $400 USD, available until May 20th

'''Full price''': $450 USD, available until June 17th (or until we sell out)

Full registration gets you three full days of training, discussion, and deep dive sessions into related topics like METS visualization and preservation planning, taught by experienced Archivematica users and developers! Full registration also includes coffee and tea breaks for all three days and free food at the group social event on Wednesday night.

=== Day 1 only ===

$150 USD - available from May 20th until space is filled

On Day 1 of the camp, we'll focus on basic Archivematica knowledge - what it is, what it does, and how to preserve simple data using common workflows. This is a great opportunity for those who want to get a taste of what Archivematica can do, and don't need the intensive 3-day experience. The 1-day registration includes coffee and tea breaks as well as free food at the group social event on Wednesday night.

Note that we won't know how many one-day registrations we can accommodate until we know how many full registrants don't intend to attend Day 1. It's a bit complex for us to manage, so please be patient! If you really want to attend Day 1 only, please email us at info@artefactual.com with the subject line "Archivematica Camp Baltimore" and let us know - we'll make sure you're notified before tickets go on sale.

==Know before you go==

'''Digital preservation knowledge expectations'''

If you've registered because you are curious about Archivematica but not sure what a SIP, DIP, or AIP is, you might want to do some basic digital preservation reading before Day 1. We recommend Ashley Blewer's [http://training.ashleyblewer.com/presentations/oais.html OAIS slidedeck] as a good starting place to learn about the OAIS reference model, on which Archivematica is based. If you want to dive deeper, there are a lot of OAIS and digital preservation primers out there!

'''Bring a laptop'''

We have hands-on sessions planned and Archivematica pipelines ready for learning. You may want to set up your own pipeline using vagrant and VirtualBox - this isn't required, but if you're keen then more power to you! You'll find instructions to do that [https://www.archivematica.org/en/docs/archivematica-1.7/getting-started/quick-start/quick-start/#quick-start-install here] (please do this before you arrive at camp!).

'''Food'''

Coffee and tea breaks will be catered. However, the rooms where we're hosting the camp do not permit food, so only beverages will be provided. There is a cafe two floors up from the training rooms where you can grab a snack.

As the campus is within an easy walking distance of many restaurants, cafes, and food courts, we decided to keep registration costs lower by not catering in lunches. We'll provide plenty of time for you to seek out nourishment, and have provided a list of nearby dining options below.

'''Code of conduct'''

We are committed to providing a welcoming and positive experience for everyone, whether you are in a session, online, or in a social setting. This means that Archivematica Camp Amsterdam is governed by a Code of Conduct, which you can read at the bottom of this page.

'''Questions or concerns?'''

Please email us at info@artefactual.com with "Archivematica Camp Baltimore" in the subject line and we'll get back to you as soon as possible.

== Camp staff ==

'''Tim Walsh''' is our amazing community counsellor for this camp! Community counsellors are experienced Archivematica users who have a proven track record of working with the software in innovative ways and engaging with the Archivematica community. Tim has worked with Archivematica since 2015 and lead the effort of implementing a largely automated multi-pipeline Archivematica setup at the Canadian Centre for Architecture. Tim is also the developer of METSFlask, a web application for exploring the contents of Archivematica METS files. He'll primarily be talking about his practical experience of using Automation Tools to automate transfer and ingest as well as visualization and post-ingest use of METS files, but is happy to discuss anything related to Archivematica.

'''Sara Allain''' started working at Artefactual on both the AtoM and Archivematica projects in 2016, doing requirements analysis, user documentation, QA testing and community support. Prior to her work at Artefactual Sara worked in academic libraries as an archivist and/or librarian, tackling wide-ranging subjects like archival description, data migration, Islandora implementation, digitization management, and library communications. She'll be teaching introductory Archivematica, preservation planning, and probably several other bits and pieces along the way.

'''Ross Spencer''' is a software developer for Artefactual Systems Inc. Focused primarily on the Archivematica project, Ross has a background in digital preservation research and analysis. Having previously worked for Archives New Zealand, and before then, The National Archives, UK, he has experience with the unique requirements a government workflow. Ross also has a much broader interest in all things digital preservation, archives, and code. Ross will be discussing APIs, optimisation, contributing code, and issues! And much much more.

'''Evelyn McLellan''' is President of Artefactual Systems and has been involved in the Archivematica project since its earliest days. An archivist by training with a strange obsession with preservation metadata, she'll be leading some of the sessions and generally helping out where needed.

== Schedule (subject to change) ==

=== Wednesday, June 20: Day One (optional) - Archivematica for Beginners ===

Archivematica Camp kicks off with an optional day of training aimed at attendees who are new to Archivematica. We'll introduce the project, go over the basics of technical architecture, and look at the core functionality. The goal of this day is to ensure that everyone is on solid ground before we dive into more complex discussions. Note: participants are welcome to join the morning session, afternoon session, or both sessions as they wish. Participants may also wish to join the Camp on Day Two.

{| border="1" style="border-collapse:collapse;"
|style="white-space: nowrap; width: 10%; background-color: #93c9ff;"|'''Time'''
|style="white-space: nowrap; width: 90%; background-color: #93c9ff"|'''Streams 1 & 2'''

|-
|style="white-space: nowrap;"|9:00am - 10:15pm
|'''Module 1: Archivematica in the digital preservation landscape'''
Topics covered include: where does Archivematica fit into the digital preservation landscape, what does Archivematica promise to do, what doesn't Archivematica do

|-
|style="white-space: nowrap;"|10:15am - 10:30pm
|'''Coffee break'''

|-
|style="white-space: nowrap;"|10:30am-12:00pm
|'''Module 2: How does Archivematica actually work?'''
Topics covered include: Archivematica's conceptual model, packages (transfers, bags, SIPs, AIPs, DIPs), microservices as implementations of preservation actions, workflows, storage spaces (how the storage service works and how to get at your content)

|-
|style="white-space: nowrap;"|12:00pm - 1:00pm
|colspan="2"|'''Lunch'''

|-
|style="white-space: nowrap;"|1:00pm - 3:00pm
|'''Module 3: Archivematica's core functionality'''
Topics covered include: understanding Archivematica's dashboard, including the Transfer tab, Ingest tab, Administration tab, and Preservation planning tab plus a first look at an AIP produced by Archivematica. This afternoon session includes hands-on exercises.

|-
|style="white-space: nowrap;"|3:00pm - 3:15pm
|'''Coffee break'''

|-
|style="white-space: nowrap;"|3:15pm - 4:00pm
|'''Module 3: Archivematica's core functionality'''
Continuation of Module 3.
|-
|style="white-space: nowrap;"|5:30pm - 8:30pm
|'''Group social event'''
Happy hour and food at [http://www.peabodyheightsbrewery.com/ Peabody Heights Brewery]! Peabody Heights Brewery is a 15 minute walk from the Library. We'll be ordering in food (pizza? tacos? we haven't decided yet!) and we'll make sure there are nonalcoholic alternatives as well. If the weather is nice, the brewery has a large beer garden where we can relax, chat, and gear up for two more days of learning.
|}


=== Thursday, June 21: Day Two ===

Days Two and Three are divided into two streams. Stream 1 is intended for front-end users who are responsible for day-to-day operations. Stream 2 is intended for back-end users who are responsible for development and maintenance of the software. Streams occasionally converge, and we encourage attendees to choose the session that most interests them - feel free to move around!

{| border="1" style="border-collapse:collapse;"
|style="white-space: nowrap; width: 10%; background-color: #93c9ff"|'''Time'''
|style="white-space: nowrap; width: 45%; background-color: #93c9ff"|'''Stream 1'''
|style="white-space: nowrap; width: 45%; background-color: #93c9ff"|'''Stream 2'''

|-
|style="white-space: nowrap;"|9:00am - 9:30am
|colspan="2"|'''Arrival and registration'''

|-
|style="white-space: nowrap;"|9:30am - 10:45am
|'''Module 4: Building on core: Archivematica's specialized workflows'''
Topics covered include transfers of zipped files, disk images, metadata.csv, manual normalization, and a look at automation tools. This module includes hands-on exercises.
|'''Module 4: Supporting Archivematica workflows'''
Topics covered include how to install automation tools, REST APIs, logs, maintenance, and upgrades.

|-
|style="white-space: nowrap;"|10:45am - 11:00am
|'''Coffee break'''

|-
|style="white-space: nowrap;"|11:00am - 12:00pm
|colspan="2"|'''Community profile: Practical experience with automation tools (Tim Walsh)'''

|-
|style="white-space: nowrap;"|12:00pm - 1:00pm
|colspan="2"|'''Lunch'''

|-
|style="white-space: nowrap;"|1:00pm - 2:45pm
|'''Module 5: Archivematica's non-core functionality'''
Topics covered include a look at the Backlog and Appraisal tab, AIP reingest, AIP encryption, transcription, and using Mediaconch. This module includes hands-on exercises.
|'''Module 5: Understanding Archivematica's logs and peformance evaluation'''

|-
|style="white-space: nowrap;"|2:45pm - 3:00pm
|'''Coffee break'''

|-
|style="white-space: nowrap;"|3:00pm-4:00pm
|colspan="2"|'''Community profile: Johns Hopkins University'''

|-
|style="white-space: nowrap;"|4:00pm - 5:00pm
|colspan="2"| '''Agenda adjustment for Day 3'''
What do you want to talk about tomorrow? Also, wrap-up.

|-
|style="white-space: nowrap;"|6:00pm - late
|colspan="2"| '''Small group dinners'''
We'll create a sign-up sheet containing a list of restaurants nearby. Campers can sign up to attend dinner at whichever restaurant piques their interest! This is a great way to meet new people and get out on the town. We ask that you limit the group size to 4-6 people, so that the restaurants aren't overwhelmed!
|}


=== Friday, June 22: Day Three ===

Day Three is a bit more loosely-structured than Days One and Two. Based on camper interest, the schedule may be adjusted to accommodate new topics. Plus, there's plenty of time to talk about how Archivematica works - or could work - in your institution.

{| border="1" style="border-collapse:collapse; "
|style="white-space: nowrap; width: 10%; background-color: #93c9ff"|'''Time'''
|style="white-space: nowrap; width: 45%; background-color: #93c9ff"|'''Stream 1'''
|style="white-space: nowrap; width: 45%; background-color: #93c9ff"|'''Stream 2'''

|-
|9:00am - 9:30am
|colspan="2" style="white-space: nowrap; width: 90%;"|'''How this day is going to unfold'''

|-
|9:30pm - 10:30pm
|'''Module 6: AIPs for Archivists'''
Topics covered include how the AIP is structured, and a close look at the METS file
|'''Module 6: AIPs for developers/systems administrators'''
Topics covered include how the METS file is written from the database

|-
|style="white-space: nowrap;"|10:30-12:00
|colspan="2"|'''Community topics'''
Based on topics raised from campers at registration and as the camp has progressed. Led by Artefactual staff with lots of input from the community. Breakout into 2 rooms as needed. Informal and fun!

|-
|style="white-space: nowrap;"|12:00pm - 1:00pm
|colspan="2"|Lunch

|-
|style="white-space: nowrap;"|1:00pm - 3:00pm
|colspan="2"|'''Module 7: Implementation roundtable'''
Discussion of various ways Archivematica can be implemented. Campers are invited to share their particular Archivematica implementations, real or imagined, in 10-15 minute informal talks. We'll post a sign-up list on the first day of camp.

|-
|style="white-space: nowrap;"|3:00pm-4:00pm
|colspan="2"|'''Module 8: Archivematica in the community'''
Topics covered include how the code is written, collaborative digital preservation, and a look at the Archivematica roadmap.
Wrap-up and safe travels!
|}

== Local Arrangements ==

=== Hotels ===

As there are few hotel options within walking distance of Johns Hopkins, we've secured room blocks at two hotels: the Inn at the Colonnade and the Radisson at Cross Keys.

====Inn at The Colonnade Baltimore====

[https://www.google.ca/maps/dir/Inn+at+The+Colonnade+Baltimore+-+A+DoubleTree+by+Hilton+Hotel,+West+University+Parkway,+Baltimore,+MD,+USA/Milton+S+Eisenhower+Library,+North+Charles+Street,+Baltimore,+MD,+USA/@39.3313599,-76.6213098,17z/data=!3m2!4b1!5s0x89c804dff3aee8c7:0x5030d558bfc93488!4m13!4m12!1m5!1m1!1s0x89c80521e8b11795:0x9d5a52f5ed8dfc78!2m2!1d-76.619735!2d39.334029!1m5!1m1!1s0x89c804dfa8c04b1f:0xf0f3792b68b355da!2m2!1d-76.619425!2d39.329053 4 West University Parkway, Baltimore, Maryland 21218-2306]

The Inn at the Colonnade is just across the street from Johns Hopkins campus, an 8 minute walk to the Milton S. Eisenhower Library.

To book a room at the Inn at the Colonnade, use [http://doubletree.hilton.com/en/dt/groups/personalized/B/BWICUDT-AMC-20180619/index.jhtml?WT.mc_id=POG this link].

====Radisson at Cross Keys====

[https://www.google.ca/maps/dir/Radisson+Hotel+at+Cross+Keys,+Baltimore,+5100+Falls+Rd,+Baltimore,+MD+21210,+USA/Johns+Hopkins+University,+Baltimore,+MD,+USA/@39.3371967,-76.6496263,14z/data=!3m1!4b1!4m13!4m12!1m5!1m1!1s0x89c81ab45a596f8d:0x73744f706126b216!2m2!1d-76.6467539!2d39.3551217!1m5!1m1!1s0x89c804df8502f88d:0x303d58494fa04c66!2m2!1d-76.6205177!2d39.3299013 5100 Falls Rd, Baltimore, MD 21210]

The Radisson at Cross Keys is a 10 minute drive or 30 minute walk/transit trip to the Milton S. Eisenhower Library (20 minutes walking, 10 minutes on the bus).

To book a room at the Radisson at Cross Keys, follow these steps:

#Go to [https://www.radisson.com/baltimore https://www.radisson.com/baltimore]
#Under Modify Search Select the dates you are checking in and checking out and click More Search Options
#Please enter in the Promotional Code box - '''JHUGRP'''
#Click Search Again
#Select the hotel (only your group’s name should appear) by selecting Book Now
#A Room Options screen will appear. Please select the bed type that you are requesting which is located at the bottom of the page. Once you select the bed type you are requesting you are then prompted to your reservation profile screen where you would input your contact and payment information.

If you have questions, please contact the hotel directly by calling Reservations at 1-800-333-3333 and say you are making a reservation for "The Archives Matika Group" (yes, we're aware this is incorrect!) & the dates you will be staying at the hotel.

====AirBnB====

Any AirBnBs within a 15 walk from campus in all directions are perfectly safe.

The city has two free bus lines (http://ts.jhu.edu/Shuttles/TransLoc/ and https://www.charmcitycirculator.com/route/purple) so you can also stay anywhere between campus and the Inner Harbor and get here within 30 minutes.

=== Food & drink ===

All are within walking distance of the Library.

*[https://r.housebaltimore.com/ R House] - Fancy food court and bar

*[http://www.partsandlaborbutchery.com/ Parts and Labor] - “Everything but the snout”-style restaurant for meat eaters

*[http://places.singleplatform.com/one-world-cafe/menu One World] - Unpretentious vegetarian-ish restaurant dating back to before vegetarian was hip

*[http://www.sweet27.com/ Sweet 27] - Amusing variety of cuisines, but good vegan bakery and Indian food

*[http://www.tambersrestaurant.com/ Tamber’s] - Diner and Indian — a very Baltimore mash-up

*[http://www.charlesvillagepub.net/index.html Charles Village Pub] - Venerable Baltimore/Charles Village dive with straightforward grill fare

*[https://www.eatthb.com/ Towson Hot Bagel] - Omelettes, sandwiches, and (of course) bagels

*[http://www.pekopekoramen.com/ Peko Peko Ramen] - Chicken broth ramen, rice bowls, mochi ice cream

*[https://www.chipotle.com/ Chipotle] - Burritos and the like

*[http://eddiesmarket.com/ Eddies Market of Charles Village] - Supermarket with a deli in the back

==Code of Conduct==

The Archivematica community is dedicated to providing a welcoming and positive experience for everyone, whether they are in a formal session or a social setting related to an Archivematica event, or are taking part in activities online. Archivematica community participants come from all over the world and bring with them a wide variety of professional, personal and social backgrounds; whatever these may be, we treat colleagues with dignity and respect. We are sensitive to the fact that the international nature of the Archivematica community means that we span many different social norms around language and behaviour and we strive to conduct ourselves in ways that are unlikely to cause offense. In the event that someone’s conduct is causing offense or distress, the Archivematica Camp has a detailed Anti-Harassment Policy, details below, which can be applied to address the problem.

The first step in dealing with any serious misconduct is to contact a member of the organizing group, or a counsellor at an Archivematica Camp (please see counsellors, above). These people will be made known before and during any Archivematica Camp event.

'''Anti-Harassment Policy'''

The Archivematica community is dedicated to providing a harassment-free conference/camp experience for everyone. If you have been harassed, please consult this protocol for conflict resolution which makes clear how we can help.

The Archivematica community has established the following policy to make it clear that we do not tolerate harassment in any form. Sexual or discriminatory language and imagery are not appropriate for any event venue, including talks, or any other communication channel used during the conference (such as social media).

Harassment includes:

* offensive verbal comments related to sex, gender, ethnicity, nationality, socioeconomic status, sexual orientation, disability, physical appearance, body size, age, race, religion;
* sexual or discriminatory images in public spaces;
* deliberate intimidation;
* stalking;
* harassing photography or recording;
* sustained disruption of talks or other events;
* inappropriate physical contact; and
* unwelcome sexual attention.

The lingua franca of Archivematica Camp is English; however, English may not be the native language of Archivematica Camp participants. Further, cultural norms around what may be considered obscene and offensive communication will vary among Archivematica Camp attendees. Campers are asked to please be mindful of the international character of Archivematica Camp, and to use respectful and clear language free of slang to facilitate communication.

Participants asked to stop any harassing behavior are expected to comply immediately.

If a participant engages in harassing behavior, event organizers and Archivematica representatives (or their designees) may take any action they deem appropriate, including warning the offender, expulsion from Archivematica Camp, or contacting a higher authority such as a representative from the offender’s institution.

If a participant raises a concern relating to actions covered by this policy in good faith, there will be no retaliation for bringing forward their concern. Threatening or taking action against someone for invoking this policy or for participating in any related investigation will be considered a violation of this policy.

Participants are expected to follow the anti-harassment policy at all Camp-related venues, Camp-related social events, and online communication channels.

We expect attendees and speakers past and present to be respectful to each other, and we will deal with any incidents that arise, including on social media.

We value your participation in the Archivematica community and your support in keeping the Archivematica community a safe, welcoming, and friendly space for fellow participants.

'''Acknowledgments'''

This policy is based on the [http://www.pasignyc.org/#code-of-conduct-section PASIG Code of Conduct], portions of which were modified from the [http://or2016.net/code-of-conduct/ Open Repositories’ code of conduct], which was itself modified from [https://www.seattleattic.com/codeofconduct Seattle Attic’s code of conduct] and the [http://adainitiative.org/what-we-do/events/ada-initiative-event-anti-harassment-policy/ Ada Initiative’s event harassment policy].

'''License'''

This document is licensed under [https://creativecommons.org/licenses/by-sa/3.0/ Creative Commons BY-SA].

Community/Camps/Baltimore2018

2018-04-16T14:44:01Z

Evelyn: /* Registration */

The lovely city of Baltimore, Maryland is the location of our next eastern seaboard Archivematica Camp, cohosted by the Sheridan Libraries at [https://www.library.jhu.edu/ Johns Hopkins University].

Inspired by similar events like Hydra Camp, Islandora Camp and Fedora Camp, Archivematica Camp provides a space for anyone interested in or currently using Archivematica to come together, learn about the platform from other users, and share their experiences.

== Dates and Location ==

'''WHEN: Wednesday, June 20 to Friday, June 22, 2018'''

'''WHERE: [https://goo.gl/maps/jagXhcVHK232 Brody Learning Commons Room 5015/5017,]''' Johns Hopkins University, Baltimore, MD.

The Brody Learning Commons is connected to the Milton S. Eisenhower Library, the combination of which is generally known as "the Library." Security guards will be advised that the conference is happening and can direct you to the room. Please bring photo ID.

=== Getting there ===

The Johns Hopkins University campus is located in north Baltimore, approximately 15 minutes by car and 30 minutes by transit from downtown Baltimore. Parking information is here: http://ts.jhu.edu/Parking/Visitors/

Two free bus lines operate that drop riders off at the corner of 33rd Street and Charles Street, just in front of the Library.

* JHU Shuttle: http://ts.jhu.edu/Shuttles/index.html

* Charm City Circulator Purple Line: https://www.charmcitycirculator.com/route/purple

Both of these bus services have apps that we'd recommend downloading to receive real-time updates about timetables. Both buses run roughly every 15 minutes.

=== Accessibility ===

The Brody Learning Commons is wheelchair-accessible from both entrances, but we'd recommend the south entrance from the service road, next to a building called Merrick Barn. Contact info@artefactual.com for more information and we'll put you in touch with JHU staff. We're happy to help!

== Registration ==

[https://www.eventbrite.com/e/archivematica-camp-baltimore-registration-45045169314 '''Register here!''']

Registration will open on April 16.

=== Full registration ===

'''Early bird''': $400 USD, available until May 20th

'''Full price''': $450 USD, available until June 17th (or until we sell out)

Full registration gets you three full days of training, discussion, and deep dive sessions into related topics like METS visualization and preservation planning, taught by experienced Archivematica users and developers! Full registration also includes coffee and tea breaks for all three days and free food at the group social event on Wednesday night.

=== Day 1 only ===

$150 USD - available from May 20th until space is filled

On Day 1 of the camp, we'll focus on basic Archivematica knowledge - what it is, what it does, and how to preserve simple data using common workflows. This is a great opportunity for those who want to get a taste of what Archivematica can do, and don't need the intensive 3-day experience. The 1-day registration includes coffee and tea breaks as well as free food at the group social event on Wednesday night.

Note that we won't know how many one-day registrations we can accommodate until we know how many full registrants don't intend to attend Day 1. It's a bit complex for us to manage, so please be patient! If you really want to attend Day 1 only, please email us at info@artefactual.com with the subject line "Archivematica Camp Baltimore" and let us know - we'll make sure you're notified before tickets go on sale.

==Know before you go==

'''Digital preservation knowledge expectations'''

If you've registered because you are curious about Archivematica but not sure what a SIP, DIP, or AIP is, you might want to do some basic digital preservation reading before Day 1. We recommend Ashley Blewer's [http://training.ashleyblewer.com/presentations/oais.html OAIS slidedeck] as a good starting place to learn about the OAIS reference model, on which Archivematica is based. If you want to dive deeper, there are a lot of OAIS and digital preservation primers out there!

'''Bring a laptop'''

We have hands-on sessions planned and Archivematica pipelines ready for learning. You may want to set up your own pipeline using vagrant and VirtualBox - this isn't required, but if you're keen then more power to you! You'll find instructions to do that [https://www.archivematica.org/en/docs/archivematica-1.7/getting-started/quick-start/quick-start/#quick-start-install here] (please do this before you arrive at camp!).

'''Food'''

Coffee and tea breaks will be catered. However, the rooms where we're hosting the camp do not permit food, so only beverages will be provided. There is a cafe two floors up from the training rooms where you can grab a snack.

As the campus is within an easy walking distance of many restaurants, cafes, and food courts, we decided to keep registration costs lower by not catering in lunches. We'll provide plenty of time for you to seek out nourishment, and have provided a list of nearby dining options below.

'''Code of conduct'''

We are committed to providing a welcoming and positive experience for everyone, whether you are in a session, online, or in a social setting. This means that Archivematica Camp Amsterdam is governed by a Code of Conduct, which you can read at the bottom of this page.

'''Questions or concerns?'''

Please email us at info@artefactual.com with "Archivematica Camp Baltimore" in the subject line and we'll get back to you as soon as possible.

== Camp staff ==

'''Tim Walsh''' is our amazing community counsellor for this camp! Community counsellors are experienced Archivematica users who have a proven track record of working with the software in innovative ways and engaging with the Archivematica community. Tim has worked with Archivematica since 2015 and lead the effort of implementing a largely automated multi-pipeline Archivematica setup at the Canadian Centre for Architecture. Tim is also the developer of METSFlask, a web application for exploring the contents of Archivematica METS files. He'll primarily be talking about his practical experience of using Automation Tools to automate transfer and ingest as well as visualization and post-ingest use of METS files, but is happy to discuss anything related to Archivematica.

'''Sara Allain''' started working at Artefactual on both the AtoM and Archivematica projects in 2016, doing requirements analysis, user documentation, QA testing and community support. Prior to her work at Artefactual Sara worked in academic libraries as an archivist and/or librarian, tackling wide-ranging subjects like archival description, data migration, Islandora implementation, digitization management, and library communications. She'll be teaching introductory Archivematica, preservation planning, and probably several other bits and pieces along the way.

'''Ross Spencer''' is a software developer for Artefactual Systems Inc. Focused primarily on the Archivematica project, Ross has a background in digital preservation research and analysis. Having previously worked for Archives New Zealand, and before then, The National Archives, UK, he has experience with the unique requirements a government workflow. Ross also has a much broader interest in all things digital preservation, archives, and code. Ross will be discussing APIs, optimisation, contributing code, and issues! And much much more.

'''Evelyn McLellan'''

== Schedule (subject to change) ==

=== Wednesday, June 20: Day One (optional) - Archivematica for Beginners ===

Archivematica Camp kicks off with an optional day of training aimed at attendees who are new to Archivematica. We'll introduce the project, go over the basics of technical architecture, and look at the core functionality. The goal of this day is to ensure that everyone is on solid ground before we dive into more complex discussions. Note: participants are welcome to join the morning session, afternoon session, or both sessions as they wish. Participants may also wish to join the Camp on Day Two.

{| border="1" style="border-collapse:collapse;"
|style="white-space: nowrap; width: 10%; background-color: #93c9ff;"|'''Time'''
|style="white-space: nowrap; width: 90%; background-color: #93c9ff"|'''Streams 1 & 2'''

|-
|style="white-space: nowrap;"|9:00am - 10:15pm
|'''Module 1: Archivematica in the digital preservation landscape'''
Topics covered include: where does Archivematica fit into the digital preservation landscape, what does Archivematica promise to do, what doesn't Archivematica do

|-
|style="white-space: nowrap;"|10:15am - 10:30pm
|'''Coffee break'''

|-
|style="white-space: nowrap;"|10:30am-12:00pm
|'''Module 2: How does Archivematica actually work?'''
Topics covered include: Archivematica's conceptual model, packages (transfers, bags, SIPs, AIPs, DIPs), microservices as implementations of preservation actions, workflows, storage spaces (how the storage service works and how to get at your content)

|-
|style="white-space: nowrap;"|12:00pm - 1:00pm
|colspan="2"|'''Lunch'''

|-
|style="white-space: nowrap;"|1:00pm - 3:00pm
|'''Module 3: Archivematica's core functionality'''
Topics covered include: understanding Archivematica's dashboard, including the Transfer tab, Ingest tab, Administration tab, and Preservation planning tab plus a first look at an AIP produced by Archivematica. This afternoon session includes hands-on exercises.

|-
|style="white-space: nowrap;"|3:00pm - 3:15pm
|'''Coffee break'''

|-
|style="white-space: nowrap;"|3:15pm - 4:00pm
|'''Module 3: Archivematica's core functionality'''
Continuation of Module 3.
|-
|style="white-space: nowrap;"|5:30pm - 8:30pm
|'''Group social event'''
Happy hour and food at [http://www.peabodyheightsbrewery.com/ Peabody Heights Brewery]! Peabody Heights Brewery is a 15 minute walk from the Library. We'll be ordering in food (pizza? tacos? we haven't decided yet!) and we'll make sure there are nonalcoholic alternatives as well. If the weather is nice, the brewery has a large beer garden where we can relax, chat, and gear up for two more days of learning.
|}


=== Thursday, June 21: Day Two ===

Days Two and Three are divided into two streams. Stream 1 is intended for front-end users who are responsible for day-to-day operations. Stream 2 is intended for back-end users who are responsible for development and maintenance of the software. Streams occasionally converge, and we encourage attendees to choose the session that most interests them - feel free to move around!

{| border="1" style="border-collapse:collapse;"
|style="white-space: nowrap; width: 10%; background-color: #93c9ff"|'''Time'''
|style="white-space: nowrap; width: 45%; background-color: #93c9ff"|'''Stream 1'''
|style="white-space: nowrap; width: 45%; background-color: #93c9ff"|'''Stream 2'''

|-
|style="white-space: nowrap;"|9:00am - 9:30am
|colspan="2"|'''Arrival and registration'''

|-
|style="white-space: nowrap;"|9:30am - 10:45am
|'''Module 4: Building on core: Archivematica's specialized workflows'''
Topics covered include transfers of zipped files, disk images, metadata.csv, manual normalization, and a look at automation tools. This module includes hands-on exercises.
|'''Module 4: Supporting Archivematica workflows'''
Topics covered include how to install automation tools, REST APIs, logs, maintenance, and upgrades.

|-
|style="white-space: nowrap;"|10:45am - 11:00am
|'''Coffee break'''

|-
|style="white-space: nowrap;"|11:00am - 12:00pm
|colspan="2"|'''Community profile: Practical experience with automation tools (Tim Walsh)'''

|-
|style="white-space: nowrap;"|12:00pm - 1:00pm
|colspan="2"|'''Lunch'''

|-
|style="white-space: nowrap;"|1:00pm - 2:45pm
|'''Module 5: Archivematica's non-core functionality'''
Topics covered include a look at the Backlog and Appraisal tab, AIP reingest, AIP encryption, transcription, and using Mediaconch. This module includes hands-on exercises.
|'''Module 5: Understanding Archivematica's logs and peformance evaluation'''

|-
|style="white-space: nowrap;"|2:45pm - 3:00pm
|'''Coffee break'''

|-
|style="white-space: nowrap;"|3:00pm-4:00pm
|colspan="2"|'''Community profile: Johns Hopkins University'''

|-
|style="white-space: nowrap;"|4:00pm - 5:00pm
|colspan="2"| '''Agenda adjustment for Day 3'''
What do you want to talk about tomorrow? Also, wrap-up.

|-
|style="white-space: nowrap;"|6:00pm - late
|colspan="2"| '''Small group dinners'''
We'll create a sign-up sheet containing a list of restaurants nearby. Campers can sign up to attend dinner at whichever restaurant piques their interest! This is a great way to meet new people and get out on the town. We ask that you limit the group size to 4-6 people, so that the restaurants aren't overwhelmed!
|}


=== Friday, June 22: Day Three ===

Day Three is a bit more loosely-structured than Days One and Two. Based on camper interest, the schedule may be adjusted to accommodate new topics. Plus, there's plenty of time to talk about how Archivematica works - or could work - in your institution.

{| border="1" style="border-collapse:collapse; "
|style="white-space: nowrap; width: 10%; background-color: #93c9ff"|'''Time'''
|style="white-space: nowrap; width: 45%; background-color: #93c9ff"|'''Stream 1'''
|style="white-space: nowrap; width: 45%; background-color: #93c9ff"|'''Stream 2'''

|-
|9:00am - 9:30am
|colspan="2" style="white-space: nowrap; width: 90%;"|'''How this day is going to unfold'''

|-
|9:30pm - 10:30pm
|'''Module 6: AIPs for Archivists'''
Topics covered include how the AIP is structured, and a close look at the METS file
|'''Module 6: AIPs for developers/systems administrators'''
Topics covered include how the METS file is written from the database

|-
|style="white-space: nowrap;"|10:30-12:00
|colspan="2"|'''Community topics'''
Based on topics raised from campers at registration and as the camp has progressed. Led by Artefactual staff with lots of input from the community. Breakout into 2 rooms as needed. Informal and fun!

|-
|style="white-space: nowrap;"|12:00pm - 1:00pm
|colspan="2"|Lunch

|-
|style="white-space: nowrap;"|1:00pm - 3:00pm
|colspan="2"|'''Module 7: Implementation roundtable'''
Discussion of various ways Archivematica can be implemented. Campers are invited to share their particular Archivematica implementations, real or imagined, in 10-15 minute informal talks. We'll post a sign-up list on the first day of camp.

|-
|style="white-space: nowrap;"|3:00pm-4:00pm
|colspan="2"|'''Module 8: Archivematica in the community'''
Topics covered include how the code is written, collaborative digital preservation, and a look at the Archivematica roadmap.
Wrap-up and safe travels!
|}

== Local Arrangements ==

=== Hotels ===

As there are few hotel options within walking distance of Johns Hopkins, we've secured room blocks at two hotels: the Inn at the Colonnade and the Radisson at Cross Keys.

====Inn at The Colonnade Baltimore====

[https://www.google.ca/maps/dir/Inn+at+The+Colonnade+Baltimore+-+A+DoubleTree+by+Hilton+Hotel,+West+University+Parkway,+Baltimore,+MD,+USA/Milton+S+Eisenhower+Library,+North+Charles+Street,+Baltimore,+MD,+USA/@39.3313599,-76.6213098,17z/data=!3m2!4b1!5s0x89c804dff3aee8c7:0x5030d558bfc93488!4m13!4m12!1m5!1m1!1s0x89c80521e8b11795:0x9d5a52f5ed8dfc78!2m2!1d-76.619735!2d39.334029!1m5!1m1!1s0x89c804dfa8c04b1f:0xf0f3792b68b355da!2m2!1d-76.619425!2d39.329053 4 West University Parkway, Baltimore, Maryland 21218-2306]

The Inn at the Colonnade is just across the street from Johns Hopkins campus, an 8 minute walk to the Milton S. Eisenhower Library.

To book a room at the Inn at the Colonnade, use [http://doubletree.hilton.com/en/dt/groups/personalized/B/BWICUDT-AMC-20180619/index.jhtml?WT.mc_id=POG this link].

====Radisson at Cross Keys====

[https://www.google.ca/maps/dir/Radisson+Hotel+at+Cross+Keys,+Baltimore,+5100+Falls+Rd,+Baltimore,+MD+21210,+USA/Johns+Hopkins+University,+Baltimore,+MD,+USA/@39.3371967,-76.6496263,14z/data=!3m1!4b1!4m13!4m12!1m5!1m1!1s0x89c81ab45a596f8d:0x73744f706126b216!2m2!1d-76.6467539!2d39.3551217!1m5!1m1!1s0x89c804df8502f88d:0x303d58494fa04c66!2m2!1d-76.6205177!2d39.3299013 5100 Falls Rd, Baltimore, MD 21210]

The Radisson at Cross Keys is a 10 minute drive or 30 minute walk/transit trip to the Milton S. Eisenhower Library (20 minutes walking, 10 minutes on the bus).

To book a room at the Radisson at Cross Keys, follow these steps:

#Go to [https://www.radisson.com/baltimore https://www.radisson.com/baltimore]
#Under Modify Search Select the dates you are checking in and checking out and click More Search Options
#Please enter in the Promotional Code box - '''JHUGRP'''
#Click Search Again
#Select the hotel (only your group’s name should appear) by selecting Book Now
#A Room Options screen will appear. Please select the bed type that you are requesting which is located at the bottom of the page. Once you select the bed type you are requesting you are then prompted to your reservation profile screen where you would input your contact and payment information.

If you have questions, please contact the hotel directly by calling Reservations at 1-800-333-3333 and say you are making a reservation for "The Archives Matika Group" (yes, we're aware this is incorrect!) & the dates you will be staying at the hotel.

====AirBnB====

Any AirBnBs within a 15 walk from campus in all directions are perfectly safe.

The city has two free bus lines (http://ts.jhu.edu/Shuttles/TransLoc/ and https://www.charmcitycirculator.com/route/purple) so you can also stay anywhere between campus and the Inner Harbor and get here within 30 minutes.

=== Food & drink ===

All are within walking distance of the Library.

*[https://r.housebaltimore.com/ R House] - Fancy food court and bar

*[http://www.partsandlaborbutchery.com/ Parts and Labor] - “Everything but the snout”-style restaurant for meat eaters

*[http://places.singleplatform.com/one-world-cafe/menu One World] - Unpretentious vegetarian-ish restaurant dating back to before vegetarian was hip

*[http://www.sweet27.com/ Sweet 27] - Amusing variety of cuisines, but good vegan bakery and Indian food

*[http://www.tambersrestaurant.com/ Tamber’s] - Diner and Indian — a very Baltimore mash-up

*[http://www.charlesvillagepub.net/index.html Charles Village Pub] - Venerable Baltimore/Charles Village dive with straightforward grill fare

*[https://www.eatthb.com/ Towson Hot Bagel] - Omelettes, sandwiches, and (of course) bagels

*[http://www.pekopekoramen.com/ Peko Peko Ramen] - Chicken broth ramen, rice bowls, mochi ice cream

*[https://www.chipotle.com/ Chipotle] - Burritos and the like

*[http://eddiesmarket.com/ Eddies Market of Charles Village] - Supermarket with a deli in the back

==Code of Conduct==

The Archivematica community is dedicated to providing a welcoming and positive experience for everyone, whether they are in a formal session or a social setting related to an Archivematica event, or are taking part in activities online. Archivematica community participants come from all over the world and bring with them a wide variety of professional, personal and social backgrounds; whatever these may be, we treat colleagues with dignity and respect. We are sensitive to the fact that the international nature of the Archivematica community means that we span many different social norms around language and behaviour and we strive to conduct ourselves in ways that are unlikely to cause offense. In the event that someone’s conduct is causing offense or distress, the Archivematica Camp has a detailed Anti-Harassment Policy, details below, which can be applied to address the problem.

The first step in dealing with any serious misconduct is to contact a member of the organizing group, or a counsellor at an Archivematica Camp (please see counsellors, above). These people will be made known before and during any Archivematica Camp event.

'''Anti-Harassment Policy'''

The Archivematica community is dedicated to providing a harassment-free conference/camp experience for everyone. If you have been harassed, please consult this protocol for conflict resolution which makes clear how we can help.

The Archivematica community has established the following policy to make it clear that we do not tolerate harassment in any form. Sexual or discriminatory language and imagery are not appropriate for any event venue, including talks, or any other communication channel used during the conference (such as social media).

Harassment includes:

* offensive verbal comments related to sex, gender, ethnicity, nationality, socioeconomic status, sexual orientation, disability, physical appearance, body size, age, race, religion;
* sexual or discriminatory images in public spaces;
* deliberate intimidation;
* stalking;
* harassing photography or recording;
* sustained disruption of talks or other events;
* inappropriate physical contact; and
* unwelcome sexual attention.

The lingua franca of Archivematica Camp is English; however, English may not be the native language of Archivematica Camp participants. Further, cultural norms around what may be considered obscene and offensive communication will vary among Archivematica Camp attendees. Campers are asked to please be mindful of the international character of Archivematica Camp, and to use respectful and clear language free of slang to facilitate communication.

Participants asked to stop any harassing behavior are expected to comply immediately.

If a participant engages in harassing behavior, event organizers and Archivematica representatives (or their designees) may take any action they deem appropriate, including warning the offender, expulsion from Archivematica Camp, or contacting a higher authority such as a representative from the offender’s institution.

If a participant raises a concern relating to actions covered by this policy in good faith, there will be no retaliation for bringing forward their concern. Threatening or taking action against someone for invoking this policy or for participating in any related investigation will be considered a violation of this policy.

Participants are expected to follow the anti-harassment policy at all Camp-related venues, Camp-related social events, and online communication channels.

We expect attendees and speakers past and present to be respectful to each other, and we will deal with any incidents that arise, including on social media.

We value your participation in the Archivematica community and your support in keeping the Archivematica community a safe, welcoming, and friendly space for fellow participants.

'''Acknowledgments'''

This policy is based on the [http://www.pasignyc.org/#code-of-conduct-section PASIG Code of Conduct], portions of which were modified from the [http://or2016.net/code-of-conduct/ Open Repositories’ code of conduct], which was itself modified from [https://www.seattleattic.com/codeofconduct Seattle Attic’s code of conduct] and the [http://adainitiative.org/what-we-do/events/ada-initiative-event-anti-harassment-policy/ Ada Initiative’s event harassment policy].

'''License'''

This document is licensed under [https://creativecommons.org/licenses/by-sa/3.0/ Creative Commons BY-SA].

Community/Camps/Baltimore2018

2018-04-09T07:14:40Z

Evelyn: /* Schedule (subject to change) */

The lovely city of Baltimore, Maryland is the location of our eastern seaboard Archivematica Camp, cohosted by the [https://www.library.jhu.edu/ Sheridan Libraries] at [https://www.jhu.edu/ Johns Hopkins University].

Inspired by similar events like Hydra Camp, Islandora Camp and Fedora Camp, Archivematica Camp provides a space for anyone interested in or currently using Archivematica to come together, learn about the platform from other users, and share their experiences.

== Dates, Location, and Transportation Information ==

'''June 20-22, 2018 - [https://goo.gl/maps/jagXhcVHK232 Brody Learning Commons Room 5015/5017,]''' Johns Hopkins University in Baltimore. The Brody Learning Commons is connected to the Milton S. Eisenhower Library, the combination of which is generally known as "the Library." Security guards will be advised that the conference is happening and can direct you to the room. Please bring photo ID.

The Johns Hopkins University campus is located in north Baltimore, approximately 15 minutes by car and 30 minutes by transit from downtown Baltimore.

Parking information is here: http://ts.jhu.edu/Parking/Visitors/

Two free bus lines operate that drop riders off at the corner of 33rd Street and Charles Street, just in front of the Library.

JHU Shuttle: http://ts.jhu.edu/Shuttles/index.html

Charm City Circulator Purple Line: https://www.charmcitycirculator.com/route/purple

Both of these bus services have apps that we'd recommend downloading to receive real-time updates about timetables. Both buses run roughly every 15 minutes.

Accessibility: the Brody Learning Commons is wheelchair-accessible from both entrances, but we'd recommend the south entrance from the service road, next to a building called Merrick Barn. Contact JHU staff for more information; we're happy to help!

== Registration ==

In the past, registration has been in the $400-$600 USD range. We try to keep registration as low as possible, so this is subject to change.

== Camp Counsellors ==

TBA

== Schedule (subject to change) ==

=== Day One (optional) - Archivematica for Beginners ===

Archivematica Camp kicks off with an optional day of training aimed at attendees who are new to Archivematica. We'll introduce the project, go over the basics of technical architecture, and look at the core functionality. The goal of this day is to ensure that everyone is on solid ground before we dive into more complex discussions. Note: participants are welcome to join the morning session, afternoon session, or both sessions as they wish. Participants may also wish to join the Camp on Day Two.

{| border="1" style="border-collapse:collapse;"
|style="white-space: nowrap; width: 10%; background-color: #93c9ff;"|'''Time'''
|style="white-space: nowrap; width: 90%; background-color: #93c9ff"|'''Streams 1 & 2'''

|-
|style="white-space: nowrap;"|9:00am - 10:30pm
|'''Module 1: Archivematica in the digital preservation landscape'''
Topics covered include: where does Archivematica fit into the digital preservation landscape, what does Archivematica promise to do, what doesn't Archivematica do

|-
|style="white-space: nowrap;"|10:30am-12:00pm
|'''Module 2: How does Archivematica actually work?'''
Topics covered include: Archivematica's conceptual model, packages (transfers, bags, SIPs, AIPs, DIPs), microservices as implementations of preservation actions, workflows, storage spaces (how the storage service works and how to get at your content)

|-
|style="white-space: nowrap;"|12:00pm - 1:00pm
|colspan="2"|Lunch

|-
|style="white-space: nowrap;"|1:00pm - 3:00pm
|'''Module 3: Archivematica's core functionality'''
Topics covered include: understanding Archivematica's dashboard, including the Transfer tab, Ingest tab, Administration tab, and Preservation planning tab plus a first look at an AIP produced by Archivematica. This afternoon session includes hands-on exercises.

|-
|style="white-space: nowrap;"|3:00pm - 3:15pm
|'''Coffee break'''

|-
|style="white-space: nowrap;"|3:15pm - 4:00pm
|'''Module 3: Archivematica's core functionality'''
Continuation of Module 3.
|}


=== Day Two ===

Days Two and Three are divided into two streams. Stream 1 is intended for front-end users who are responsible for day-to-day operations. Stream 2 is intended for back-end users who are responsible for development and maintenance of the software. Streams occasionally converge, and we encourage attendees to choose the session that most interests them - feel free to move around!

{| border="1" style="border-collapse:collapse;"
|style="white-space: nowrap; width: 10%; background-color: #93c9ff"|'''Time'''
|style="white-space: nowrap; width: 45%; background-color: #93c9ff"|'''Stream 1'''
|style="white-space: nowrap; width: 45%; background-color: #93c9ff"|'''Stream 2'''

|-
|style="white-space: nowrap;"|9:00am - 9:30am
|colspan="2"|'''Arrival and registration'''

|-
|style="white-space: nowrap;"|9:30am - 11:00am
|'''Module 4: Building on core: Archivematica's specialized workflows'''
Topics covered include transfers of zipped files, disk images, metadata.csv, manual normalization, and a look at automation tools. This module includes hands-on exercises.
|'''Module 4: Supporting Archivematica workflows'''
Topics covered include how to install automation tools, REST APIs, logs, maintenance, and upgrades.

|-
|style="white-space: nowrap;"|11:00am - 12:00pm
|colspan="2"|'''Community profile: Canadian Centre for Architecture (Tim Walsh)'''

|-
|style="white-space: nowrap;"|12:00pm - 1:00pm
|colspan="2"|Lunch

|-
|style="white-space: nowrap;"|1:00pm - 3:00pm
|'''Module 5: Archivematica's non-core functionality'''
Topics covered include a look at the Backlog and Appraisal tab, AIP reingest, AIP encryption, transcription, and using Mediaconch. This module includes hands-on exercises.
|'''Module 5: Understanding Archivematica's logs and peformance evaluation'''

|-
|style="white-space: nowrap;"|3:00pm-4:00pm
|colspan="2"|'''Community profile: Johns Hopkins University'''

|-
|style="white-space: nowrap;"|4:00pm - 5:00pm
|colspan="2"| Agenda adjustment for Day 3 - what do you want to talk about tomorrow? Also, wrap-up.
|}


=== Day Three ===

Day Three is a bit more loosely-structured than Days One and Two. Based on camper interest, the schedule may be adjusted to accommodate new topics. Plus, there's plenty of time to talk about how Archivematica works - or could work - in your institution.

{| border="1" style="border-collapse:collapse; "
|style="white-space: nowrap; width: 10%; background-color: #93c9ff"|'''Time'''
|style="white-space: nowrap; width: 45%; background-color: #93c9ff"|'''Stream 1'''
|style="white-space: nowrap; width: 45%; background-color: #93c9ff"|'''Stream 2'''

|-
|9:00am - 9:30am
|colspan="2" style="white-space: nowrap; width: 90%;"|'''How this day is going to unfold'''

|-
|9:30pm - 10:30pm
|'''Module 6: AIPs for Archivists'''
Topics covered include how the AIP is structured, and a close look at the METS file
|'''Module 6: AIPs for developers/systems administrators'''
Topics covered include how the METS file is written from the database

|-
|style="white-space: nowrap;"|10:30-12:00
|colspan="2"|'''Community topics'''
Based on topics raised from campers at registration and as the camp has progressed. Led by Artefactual staff with lots of input from the community. Breakout into 2 rooms as needed. Informal and fun!

|-
|style="white-space: nowrap;"|12:00pm - 1:00pm
|colspan="2"|Lunch

|-
|style="white-space: nowrap;"|1:00pm - 3:00pm
|colspan="2"|'''Module 7: Implementation roundtable'''
Discussion of various ways Archivematica can be implemented. Campers are invited to share their particular Archivematica implementations, real or imagined, in 10-15 minute informal talks. We'll post a sign-up list on the first day of camp.

|-
|style="white-space: nowrap;"|3:00pm-4:00pm
|colspan="2"|'''Module 8: Archivematica in the community'''
Topics covered include how the code is written, collaborative digital preservation, and a look at the Archivematica roadmap.
Wrap-up and safe travels!
|}

== Social events ==

TBA

== Local Arrangements ==

=== Hotels ===

As there are few hotel options within walking distance of Johns Hopkins, we've secured room blocks at two hotels: the Inn at the Colonnade and the Radisson at Cross Keys.

====Inn at The Colonnade Baltimore====

[https://www.google.ca/maps/dir/Inn+at+The+Colonnade+Baltimore+-+A+DoubleTree+by+Hilton+Hotel,+West+University+Parkway,+Baltimore,+MD,+USA/Milton+S+Eisenhower+Library,+North+Charles+Street,+Baltimore,+MD,+USA/@39.3313599,-76.6213098,17z/data=!3m2!4b1!5s0x89c804dff3aee8c7:0x5030d558bfc93488!4m13!4m12!1m5!1m1!1s0x89c80521e8b11795:0x9d5a52f5ed8dfc78!2m2!1d-76.619735!2d39.334029!1m5!1m1!1s0x89c804dfa8c04b1f:0xf0f3792b68b355da!2m2!1d-76.619425!2d39.329053 4 West University Parkway, Baltimore, Maryland 21218-2306]

The Inn at the Colonnade is just across the street from Johns Hopkins campus, an 8 minute walk to the Milton S. Eisenhower Library.

To book a room at the Inn at the Colonnade, use [http://doubletree.hilton.com/en/dt/groups/personalized/B/BWICUDT-AMC-20180619/index.jhtml?WT.mc_id=POG this link].

====Radisson at Cross Keys====

[https://www.google.ca/maps/dir/Radisson+Hotel+at+Cross+Keys,+Baltimore,+5100+Falls+Rd,+Baltimore,+MD+21210,+USA/Johns+Hopkins+University,+Baltimore,+MD,+USA/@39.3371967,-76.6496263,14z/data=!3m1!4b1!4m13!4m12!1m5!1m1!1s0x89c81ab45a596f8d:0x73744f706126b216!2m2!1d-76.6467539!2d39.3551217!1m5!1m1!1s0x89c804df8502f88d:0x303d58494fa04c66!2m2!1d-76.6205177!2d39.3299013 5100 Falls Rd, Baltimore, MD 21210]

The Radisson at Cross Keys is a 10 minute drive or 30 minute walk/transit trip to the Milton S. Eisenhower Library (20 minutes walking, 10 minutes on the bus).

To book a room at the Radisson at Cross Keys, follow these steps:

#Go to [https://www.radisson.com/baltimore https://www.radisson.com/baltimore]
#Under Modify Search Select the dates you are checking in and checking out and click More Search Options
#Please enter in the Promotional Code box - '''JHUGRP'''
#Click Search Again
#Select the hotel (only your group’s name should appear) by selecting Book Now
#A Room Options screen will appear. Please select the bed type that you are requesting which is located at the bottom of the page. Once you select the bed type you are requesting you are then prompted to your reservation profile screen where you would input your contact and payment information.

If you have questions, please contact the hotel directly by calling Reservations at 1-800-333-3333 and say you are making a reservation for "The Archives Matika Group" (yes, we're aware this is incorrect!) & the dates you will be staying at the hotel.

==Code of Conduct==

The Archivematica community is dedicated to providing a welcoming and positive experience for everyone, whether they are in a formal session or a social setting related to an Archivematica event, or are taking part in activities online. Archivematica community participants come from all over the world and bring with them a wide variety of professional, personal and social backgrounds; whatever these may be, we treat colleagues with dignity and respect. We are sensitive to the fact that the international nature of the Archivematica community means that we span many different social norms around language and behaviour and we strive to conduct ourselves in ways that are unlikely to cause offense. In the event that someone’s conduct is causing offense or distress, the Archivematica Camp has a detailed Anti-Harassment Policy, details below, which can be applied to address the problem.

The first step in dealing with any serious misconduct is to contact a member of the organizing group, or a counsellor at an Archivematica Camp (please see counsellors, above). These people will be made known before and during any Archivematica Camp event.

'''Anti-Harassment Policy'''

The Archivematica community is dedicated to providing a harassment-free conference/camp experience for everyone. If you have been harassed, please consult this protocol for conflict resolution which makes clear how we can help.

The Archivematica community has established the following policy to make it clear that we do not tolerate harassment in any form. Sexual or discriminatory language and imagery are not appropriate for any event venue, including talks, or any other communication channel used during the conference (such as social media).

Harassment includes:

* offensive verbal comments related to sex, gender, ethnicity, nationality, socioeconomic status, sexual orientation, disability, physical appearance, body size, age, race, religion;
* sexual or discriminatory images in public spaces;
* deliberate intimidation;
* stalking;
* harassing photography or recording;
* sustained disruption of talks or other events;
* inappropriate physical contact; and
* unwelcome sexual attention.

The lingua franca of Archivematica Camp is English; however, English may not be the native language of Archivematica Camp participants. Further, cultural norms around what may be considered obscene and offensive communication will vary among Archivematica Camp attendees. Campers are asked to please be mindful of the international character of Archivematica Camp, and to use respectful and clear language free of slang to facilitate communication.

Participants asked to stop any harassing behavior are expected to comply immediately.

If a participant engages in harassing behavior, event organizers and Archivematica representatives (or their designees) may take any action they deem appropriate, including warning the offender, expulsion from Archivematica Camp, or contacting a higher authority such as a representative from the offender’s institution.

If a participant raises a concern relating to actions covered by this policy in good faith, there will be no retaliation for bringing forward their concern. Threatening or taking action against someone for invoking this policy or for participating in any related investigation will be considered a violation of this policy.

Participants are expected to follow the anti-harassment policy at all Camp-related venues, Camp-related social events, and online communication channels.

We expect attendees and speakers past and present to be respectful to each other, and we will deal with any incidents that arise, including on social media.

We value your participation in the Archivematica community and your support in keeping the Archivematica community a safe, welcoming, and friendly space for fellow participants.

'''Acknowledgments'''

This policy is based on the [http://www.pasignyc.org/#code-of-conduct-section PASIG Code of Conduct], portions of which were modified from the [http://or2016.net/code-of-conduct/ Open Repositories’ code of conduct], which was itself modified from [https://www.seattleattic.com/codeofconduct Seattle Attic’s code of conduct] and the [http://adainitiative.org/what-we-do/events/ada-initiative-event-anti-harassment-policy/ Ada Initiative’s event harassment policy].

'''License'''

This document is licensed under [https://creativecommons.org/licenses/by-sa/3.0/ Creative Commons BY-SA].

Community/Camps/Amsterdam2018

2018-01-12T21:22:20Z

Evelyn:

We're heading back across the Atlantic for a second camp in Europe, cohosted by the International Institute for Social History in Amsterdam! Inspired by similar events like Hydra Camp, Islandora Camp and Fedora Camp, Archivematica Camp is intended to provide a space for anyone interested in or currently using Archivematica to come together, learn about the platform from other users, and share their experiences.

== Dates & Location ==

'''April 11-13, 2018 - [https://socialhistory.org/ International Institute of Social History]''' in Amsterdam.

== Registration ==

[https://www.eventbrite.com/e/archivematica-camp-tickets-42094832778 REGISTER HERE]

*Earlybird registration: 425€ (until February 11, 2018)
*Full registration: 450€
*Day 1 registration only: 175€

== Camp Counsellors ==

*Marco Klindt, [http://www.zib.de/ Zuse Institut Berlin]
*Evelyn McLellan, President, Artefactual Systems
*Justin Simpson, Director of Archivematica Technical Services, Artefactual Systems
*Kelly Stewart, Systems Archivist, Artefactual Systems

Robert Gillesse from IISH will also be providing local support and will be guest speaking during the camp. Thank you Robert!

== Schedule (tentative) ==

=== Wednesday April 11: Day One (optional) Archivematica for Beginners ===

{| border="1" style="border-collapse:collapse;"
|style="white-space: nowrap; width: 10%; background-color: #93c9ff;"|'''Time'''
|style="white-space: nowrap; width: 90%; background-color: #93c9ff"|'''Topic'''

|-
|style="white-space: nowrap;"|9:00am - 10:30pm
|'''Module 1: Archivematica in the digital preservation landscape'''
Topics covered include: where does Archivematica fit into the digital preservation landscape, what does Archivematica promise to do, what doesn't Archivematica do

|-
|style="white-space: nowrap;"|10:30am-12:00pm
|'''Module 2: How does Archivematica actually work?'''
Topics covered include: Archivematica's conceptual model, packages (transfers, bags, SIPs, AIPs, DIPs), microservices as implementations of preservation actions, workflows, storage spaces (how the storage service works and how to get at your content)

|-
|style="white-space: nowrap;"|12:00pm - 1:00pm
|colspan="2"|Lunch

|-
|style="white-space: nowrap;"|1:00pm - 5:00pm
|'''Module 3: Archivematica's core functionality'''
Topics covered include: understanding Archivematica's dashboard, including the Transfer tab, Ingest tab, Administration tab, and Preservation planning tab plus a first look at an AIP produced by Archivematica. This afternoon session includes hands-on exercises.

|}

'''Note''': participants are welcome to join the morning session, afternoon session, or both sessions as they wish. Participants may also wish to join the Camp on Day Two.


=== Thursday, April 12: Day Two Archivematica Camp===

{| border="1" style="border-collapse:collapse;"
|style="white-space: nowrap; width: 10%; background-color: #93c9ff"|'''Time'''
|style="white-space: nowrap; width: 45%; background-color: #93c9ff"|'''Room 1 TBA'''
|style="white-space: nowrap; width: 45%; background-color: #93c9ff"|'''Room 2 TBA'''

|-
|style="white-space: nowrap;"|9:00am - 9:30am
|colspan="2"|'''Arrival and registration'''

|-
|style="white-space: nowrap;"|9:30am - 11:00am
|'''Module 4: Stream 1 - Building on core: Archivematica's specialized workflows'''
Topics covered include transfers of zipped files, disk images, metadata.csv, manual normalization, and a look at automation tools. This module includes hands-on exercises.
|'''Module 4: Stream 2 - Supporting Archivematica workflows'''
Topics covered include how to install automation tools, REST APIs, logs, maintenance, and upgrades.

|-
|style="white-space: nowrap;"|11:00am - 12:00pm
|colspan="2"|'''Community profile: IISH'''

|-
|style="white-space: nowrap;"|12:00pm - 1:00pm
|colspan="2"|Lunch

|-
|style="white-space: nowrap;"|1:00pm - 3:00pm
|'''Module 5: Stream 1 - Archivematica's non-core functionality'''
Topics covered include a look at the Backlog and Appraisal tab, AIP reingest, AIP encryption, transcription, and using Mediaconch. This module includes hands-on exercises.
|'''Module 5: Stream 2 - Understanding Archivematica's logs and peformance evaluation'''

|-
|style="white-space: nowrap;"|3:00pm-4:00pm
|colspan="2"|'''Community profile: Zuse Institute Berlin'''

|-
|style="white-space: nowrap;"|4:00pm - 5:00pm
|colspan="2"| Agenda adjustment for Day 3 - what do you want to talk about tomorrow? Also, wrap-up.
|}


=== Thursday, April 13: Day Three Archivematica Camp ===

{| border="1" style="border-collapse:collapse; "
|style="white-space: nowrap; width: 10%; background-color: #93c9ff"|'''Time'''
|style="white-space: nowrap; width: 45%; background-color: #93c9ff"|'''Room 1 TBA'''
|style="white-space: nowrap; width: 45%; background-color: #93c9ff"|'''Room 2 TBA'''

|-
|9:00am - 9:30am
|colspan="2" style="white-space: nowrap; width: 90%;"|'''How this day is going to unfold'''

|-
|9:30pm - 10:30pm
|'''Module 6: Stream 1 - AIPs for Archivists'''
Topics covered include how the AIP is structured, and a close look at the METS file
|'''Module 6: Stream 2 - AIPs for developers/systems administrators'''
Topics covered include how the METS file is written from the database

|-
|style="white-space: nowrap;"|10:30-12:00
|colspan="2"|'''Community topics'''
Based on topics raised from campers at registration and as the camp has progressed. Led by Artefactual staff with lots of input from the community. Breakout into 2 rooms as needed. Informal and fun!

|-
|style="white-space: nowrap;"|12:00pm - 1:00pm
|colspan="2"|Lunch

|-
|style="white-space: nowrap;"|1:00pm - 3:00pm
|colspan="2"|'''Module 7: Implementation roundtable'''
Discussion of various ways Archivematica can be implemented with a checklist of what you need to actually run Archivematica. Campers are invited to share their particular Archivematica implementations, real or imagined. Questions and participation mandatory!

|-
|style="white-space: nowrap;"|3:00pm-4:00pm
|colspan="2"|'''Module 8: Archivematica in the community'''
Topics covered include how the code is written, collaborative digital preservation, and a look at the Archivematica roadmap.
Wrap-up and safe travels!
|}

'''Note on agenda adjusting''': based on camper interest, the schedule may be adjusted to accommodate topics of interest that will be covered during the concurrent sessions.

== Social events ==

=== Wednesday, April 11th: Small group dinners ===
*details to be announced

=== Thursday, April 12th: Reception at IISH ===
*details to be announced

== Local Arrangements ==
The [https://socialhistory.org/en International Institute of Social History] is located at [https://www.google.ca/maps/place/Cruquiusweg+31,+1019+AT+Amsterdam,+Netherlands/@52.3689741,4.9042646,13z/data=!4m5!3m4!1s0x47c60913c722f233:0xe7cee7a1e120697f!8m2!3d52.3689708!4d4.9392835 Cruquiusweg 31 1019 AT Amsterdam]

=== Hotels ===
There are lots of places to stay in Amsterdam! More information can be found at [https://www.amsterdam.info/tips/touristoffice/ Amsterdam Tourist Office]. We have blocked rooms at the [http://www.lloydhotel.com/ Lloyd Hotel] at a rate of 140.00€. Rooms at this rate are available on a first come first served basis and must be booked before February 9th, 2018. Booking information will be included in your registration confirmation email.

==Code of Conduct==

The Archivematica community is dedicated to providing a welcoming and positive experience for everyone, whether they are in a formal session or a social setting related to an Archivematica event, or are taking part in activities online. Archivematica community participants come from all over the world and bring with them a wide variety of professional, personal and social backgrounds; whatever these may be, we treat colleagues with dignity and respect. We are sensitive to the fact that the international nature of the Archivematica community means that we span many different social norms around language and behaviour and we strive to conduct ourselves in ways that are unlikely to cause offense. In the event that someone’s conduct is causing offense or distress, the Archivematica Camp has a detailed Anti-Harassment Policy, details below, which can be applied to address the problem.

The first step in dealing with any serious misconduct is to contact a member of the organizing group, or a counsellor at an Archivematica Camp (please see counsellors, above). These people will be made known before and during any Archivematica Camp event.

'''Anti-Harassment Policy'''

The Archivematica community is dedicated to providing a harassment-free conference/camp experience for everyone. If you have been harassed, please consult this protocol for conflict resolution which makes clear how we can help.

The Archivematica community has established the following policy to make it clear that we do not tolerate harassment in any form. Sexual or discriminatory language and imagery are not appropriate for any event venue, including talks, or any other communication channel used during the conference (such as social media).

Harassment includes:

* offensive verbal comments related to sex, gender, ethnicity, nationality, socioeconomic status, sexual orientation, disability, physical appearance, body size, age, race, religion;
* sexual or discriminatory images in public spaces;
* deliberate intimidation;
* stalking;
* harassing photography or recording;
* sustained disruption of talks or other events;
* inappropriate physical contact; and
* unwelcome sexual attention.

The lingua franca of Archivematica Camp is English; however, English may not be the native language of Archivematica Camp participants. Further, cultural norms around what may be considered obscene and offensive communication will vary among Archivematica Camp attendees. Campers are asked to please be mindful of the international character of Archivematica Camp, and to use respectful and clear language free of slang to facilitate communication.

Participants asked to stop any harassing behavior are expected to comply immediately.

If a participant engages in harassing behavior, event organizers and Archivematica representatives (or their designees) may take any action they deem appropriate, including warning the offender, expulsion from Archivematica Camp, or contacting a higher authority such as a representative from the offender’s institution.

If a participant raises a concern relating to actions covered by this policy in good faith, there will be no retaliation for bringing forward their concern. Threatening or taking action against someone for invoking this policy or for participating in any related investigation will be considered a violation of this policy.

Participants are expected to follow the anti-harassment policy at all Camp-related venues, Camp-related social events, and online communication channels.

We expect attendees and speakers past and present to be respectful to each other, and we will deal with any incidents that arise, including on social media.

We value your participation in the Archivematica community and your support in keeping the Archivematica community a safe, welcoming, and friendly space for fellow participants.

'''Acknowledgments'''

This policy is based on the [http://www.pasignyc.org/#code-of-conduct-section PASIG Code of Conduct], portions of which were modified from the [http://or2016.net/code-of-conduct/ Open Repositories’ code of conduct], which was itself modified from [https://www.seattleattic.com/codeofconduct Seattle Attic’s code of conduct] and the [http://adainitiative.org/what-we-do/events/ada-initiative-event-anti-harassment-policy/ Ada Initiative’s event harassment policy].

'''License'''

This document is licensed under [https://creativecommons.org/licenses/by-sa/3.0/ Creative Commons BY-SA].

Main Page

2017-11-17T22:41:42Z

Evelyn:

<div style="background: #fff; float: right; padding: 1em; width: 30%">
<div class="download">

== Free Demo and Download ==
* [http://sandbox.archivematica.org Demo] - see [[Sandbox|Sandbox info]] for login
* [[Release Notes|Release notes]]
* [https://ww.archivematica.org/en/docs/latest/admin-manual/installation/installation/#installation Installation]
* [http://www.artefactual.com/services/ Installation services]

</div>

<div class="documentation">

== [https://www.archivematica.org/ How to use Archivematica] ==
* User and administrative manuals at [http://www.archivematica.org archivematica.org]
* [https://www.artefactual.com/services/training/ Training services]

</div>

<div class="development">

== [[Development|Developer resources]] ==
*[[Development roadmap: Archivematica|Development roadmap]]
* Development [[Documentation|documentation]]
*[[Improvements|Proposed Improvements]]
*[https://projects.artefactual.com/projects/archivematica Issues list]
*[https://www.artefactual.com/partners/ Become an innovation partner]

</div>

<div class="community">

== [[Community|Community]] ==
*[https://groups.google.com/group/archivematica Discussion list]
*[[Community|Free community resources]]
*[http://www.artefactual.com/services/archivematica/maintenance/ Get support]
*[[Contributors|Contributors]]

</div>

<div class="twitter">

== Twitter ==

{{#widget:Twitter Search}}

</div>

<div class="news">

</div>

</div><div style="overflow: hidden;">

== ''This is the Archivematica development wiki. For user and administrative manuals, as well as installation information, please visit [http://www.archivematica.org archivematica.org].'' ==

='''What is Archivematica?'''=

Archivematica is a free and open-source [[wikipedia:Digital preservation|digital preservation]] system that is designed to maintain long-term access to digital memory. Archivematica is packaged with the web-based content management system [https://www.accesstomemory.org/ AtoM] for access to your digital objects.

The [[overview]] section provides a detailed description of Archivematica's functionality and technical architecture. This screencast gives a demo of the core features in the most current release of the system.

{| width="100%" border="0" style="margin: 20px 0;" class="youtube"
| align="center" | <youtube>EjStNDXK48U</youtube>
|}

==='''Standards-based'''===

Archivematica uses a [http://en.wikipedia.org/wiki/Microservices micro-services] design pattern to provide an integrated suite of software tools that allows users to process digital objects from ingest to access in compliance with the ISO-OAIS functional model. Users monitor and control the micro-services via a web-based dashboard. Archivematica uses METS, PREMIS (events, agents, rights and restrictions), Dublin Core, the Library of Congress BagIt specification and other best practice standards and practices to provide trustworthy, authentic, reliable, and interoperable archival packages (AIPs) for storage in your preferred repository.

==='''Open source'''===

All Archivematica code is released under a GNU Affero General Public License ([http://www.gnu.org/licenses/agpl.html AGPL 3.0]) – giving you the freedom to study, modify, improve, and distribute it. We believe that an important part of preservation is transparency, and that memory institutions should be able to demonstrate at every stage what happens when they process cultural heritage materials for preservation. Archivematica [https://github.com/artefactual code] is always freely available, and our documentation is also released under a Creative Commons Share-alike license.

==='''Flexible and customizable'''===

Archivematica provides several decision points that give the user control over choices about format identification tools, printing the original order of the directories ingested, examining contents for private and personal information, extracting contents of packages and forensic images, transcribing content, and more. Users may also preconfigure most of these options for seamless ingest to archival storage and access. Archivematica offers many ingest workflows: metadata and submission documentation import, zipped and unzipped Bag ingest, digital forensic image processing, SIP arrangement, manual normalization, and dataset management.

==='''Compatible with hundreds of formats'''===

In the Format Policy Registry (FPR), Archivematica implements its default [[media type preservation plans|format policies]] based on an analysis of the [[significant characteristics]] of file formats. The FPR also offers an editable, flexible framework for format identification, package extraction, transcription and normalization for preservation and access. Your institution can update tools, rules and commands in your local FPR from the Artefactual-managed FPR server. You can also add your own, local policies to your internal FPR. The FPR is integrated with PRONOM.

==='''Advanced search and storage management'''===

You can easily search your backlog and your archival storage from within your Archivematica web-based dashboard. This means you can download stored AIPs as complete packages, individual objects, or every package in an AIC. You can also manage your storage and processing locations using the Archivematica Storage Service, including a two-step deletion process that requires justification and approval to eliminate a stored AIP.

==='''Integration with third-parties'''===

Memory institutions have dedicated voluminous resources over the past couple of decades to implement various software platforms and tools to manage digital objects. For this reason, we believe in leveraging the strength of other tools and integrating with them wherever possible. Highlights include: [https://www.accesstomemory.org/en/ AtoM], [http://www.dspace.org/ DSpace], [http://www.contentdm.org/ CONTENTdm], [http://islandora.ca/ Islandora], [http://www.lockss.org/ LOCKSS], [http://www.duracloud.org/ DuraCloud], [http://www.openstack.org/ OpenStack] and [http://www.archiviststoolkit.org/ Archivists' Toolkit]

The software applications integrated into Archivematica are each released under their own open source license. These are checked for license compatibility before they are integrated into the project. A full list of applications with their respective license is available on the [[External tools|external software tools]] page.

==='''Lead developers and partners'''===
This project is managed by [http://artefactual.com/archivematica.html Artefactual Systems]. Key funding contrbutors have included UNESCO Memory of the World's [http://portal.unesco.org/ci/en/ev.php-URL_ID=1720&URL_DO=DO_TOPIC&URL_SECTION=201.html Subcommittee on Technology], the [http://vancouver.ca/ctyclerk/archives/ City of Vancouver Archives], [http://www.library.hbs.edu/ Harvard Business School Baker Library], the [http://www.moma.org/ Museum of Modern Art (MoMA)], the [http://www.library.ualberta.ca/ University of Alberta Libraries], the [http://diginit.library.ubc.ca/ University of British Columbia Library], the [http://rockarch.org/ Rockefeller Archive Center], [http://www.sfu.ca/archives/ Simon Fraser University Archives and Records Management], [http://www.library.yale.edu/ Yale University Library], [http://www.zib.de/en/home.html Zuse-Institute Berlin], [http://www.coppul.ca/ Council of Prairie and Pacific University Libraries (COPPUL)], [http://bentley.umich.edu/ Bentley Historical Library, University of Michigan], [http://duraspace.org Duraspace], [http://libraries.mit.edu/ MIT Libraries], [http://www.ocul.on.ca/ Ontario Council of University Libraries], [https://www.llgc.org.uk/ National Library of Wales], [http://www.archivescanada.ca/ Canadian Council of Archives] and a number of other collaborators.
</div>

[[File:Artefactual_Logo.png|240px|center|link=http://www.artefactual.com/]] [[File:Cva.gif|160px]] [[File:Ubcblue_full.png|80px]] [[File:RAC-logo.png|80px]] [[File:Logo_en.gif|140px]][[File:SFULogo.jpg|150px]] [[File:UofAlogo.png|180px]][[File:LOGO_ulib_4cp_under75_png_4f05de2698.png|200px]] [[File:MoMA.png|180px]] [[File:FinalULBlues_copy.png|300px]] [[File:ZIBlogo-mediumlines.png|75px]] [[File:HarvardBaker30_image.png|250px]] [[File:Coppullogo.jpg‎]] [[File:UM-BHL-logo.png|120px]] [[File:DuraSpace_logo_horiz_300.png|260px]][[File:Mit_logo.png]] [[File:ocul_logo.png|200 px]] [[File:york_logo.png|240px]] [[File:hull_logo.png|220px]] [[File:NLW_logo1.jpg|330px]] [[File:Blue_Eng_First.png|360 px]] [[File:logo-en.png|360 px]]

__NOTOC__

File:Logo-en.png

2017-11-17T22:40:20Z

Evelyn:

Main Page

2017-11-17T22:40:04Z

Evelyn:

Archivematica 1.6.1 release notes

2017-08-01T18:58:55Z

Evelyn: /* Archivematica 1.6.1 */

[[Main_Page|Home]] > [[Release_Notes|Release Notes]] > Archivematica 1.6.1 release notes

'''NOTE: these release notes are a work in progress and are subject to change.'''

Primarily a bugfix release - August 1st, 2017.

This is the first Archivematica release to provide packages for Ubuntu 16.04 (xenial). Support for xenial is considered beta. Ubuntu 14.04 (trusty) and CentOS 7.x are also supported.

==== Tool Updates ====
* Support for PRONOM 90
* siegfried updated to version 1.7.3
* FIDO updated to version 1.3.6
* ffmpeg updated to version 3.3.2 (Ubuntu only)

=== Archivematica 1.6.1 ===
* '''Sponsored''' (Rockefeller Archive Center) Object Level Premis Rights Import - [https://github.com/artefactual/archivematica/pull/575| PR575] [https://www.archivematica.org/en/docs/archivematica-1.6/user-manual/transfer/import-metadata/#rights-csv| Docs]
* '''Sponsored''' (Canadian Centre for Architecture) Update METS to encode in UTF-8 instead of ASCII - [https://projects.artefactual.com/issues/11163| Issue #11163] [https://github.com/artefactual/archivematica/pull/541| PR541]
* '''Sponsored''' (Canadian Centre for Architecture) Increase Elasticsearch timeout limit - [https://projects.artefactual.com/issues/11294| Issue #11294] [https://github.com/artefactual/archivematica/pull/556| PR556]
* '''Sponsored''' (University of Saskatchewan Library) Allow UTF8-encoded transfer directory names - [https://projects.artefactual.com/issues/10712| Issue #10712] [https://github.com/artefactual/archivematica/pull/520| PR520]

* '''Contributed''' ([https://github.com/djpillen| Dallas Pillen]) Use display_title instead of title for sip_name in Appraisal tab - [https://github.com/artefactual-labs/appraisal-tab/pull/158| PR158]
* '''Contributed''' ([https://github.com/djpillen| Dallas Pillen]) Use display_string instead of title for digital object title with ArchivesSpace integration - [https://github.com/artefactual-labs/agentarchives/pull/41| PR41]
* Support for [https://www.nationalarchives.gov.uk/aboutapps/pronom/release-notes.xml| PRONOM 89 and 90] - [https://projects.artefactual.com/issues/10982| Issue #10982] [https://github.com/artefactual/archivematica/pull/660| PR660]
* Fix upgrades when FPR Rules have been customised - [https://github.com/artefactual/archivematica-fpr-admin/issues/46| FPR Admin Issue #46] [https://github.com/artefactual/archivematica/pull/609| PR609]
* ArchivesSpace: Don't special case first note when editing a record - [https://github.com/artefactual-labs/agentarchives/pull/40| PR40]
* Set filepath for zip files correctly when starting transfer - [https://projects.artefactual.com/issues/11224| #11224] [https://github.com/artefactual/archivematica/pull/626| PR626]
* Change date format in verifyMD5.sh - [https://github.com/artefactual/archivematica/pull/629| PR629]

=== Archivematica Storage Service 0.10.1 ===
* '''Sponsored''' (University of British Columbia Library) Improvements to editing pipelines - [https://github.com/artefactual/archivematica-storage-service/pull/194| PR194]
* '''Sponsored''' (City of Vancouver Archives) Correctly update pointer files when reingesting uncompressed AIP's [https://github.com/artefactual/archivematica-storage-service/pull/203| PR203] [https://github.com/artefactual/archivematica-storage-service/pull/214| PR214]
* Update Bagit-python to version 1.5.4 [https://github.com/artefactual/archivematica-storage-service/pull/207| PR207]

Archivematica 1.6.1 release notes

2017-08-01T18:54:34Z

Evelyn: /* Archivematica 1.6.1 */

[[Main_Page|Home]] > [[Release_Notes|Release Notes]] > Archivematica 1.6.1 release notes

'''NOTE: these release notes are a work in progress and are subject to change.'''

Primarily a bugfix release - August 1st, 2017.

This is the first Archivematica release to provide packages for Ubuntu 16.04 (xenial). Support for xenial is considered beta. Ubuntu 14.04 (trusty) and CentOS 7.x are also supported.

==== Tool Updates ====
* Support for PRONOM 90
* siegfried updated to version 1.7.3
* FIDO updated to version 1.3.6
* ffmpeg updated to version 3.3.2 (Ubuntu only)

=== Archivematica 1.6.1 ===
* '''Sponsored''' (Rockefeller Archive Center) Object Level Premis Rights Import - [https://github.com/artefactual/archivematica/pull/575| PR575] [https://www.archivematica.org/en/docs/archivematica-1.6/user-manual/transfer/import-metadata/#rights-csv| Docs]
* '''Sponsored''' (Canadian Centre for Architecture) Update METS to encode in UTF-8 instead of ASCII - [https://projects.artefactual.com/issues/11163| Issue #11163] [https://github.com/artefactual/archivematica/pull/541| PR541]
* '''Sponsored''' (Canadian Centre for Architecture) Increase Elasticsearch timeout limit - [https://projects.artefactual.com/issues/11294| Issue #11294] [https://github.com/artefactual/archivematica/pull/556| PR556]
* '''Sponsored''' (University of Saskatchewan Library) Allow UTF8-encoded transfer directory names - [https://projects.artefactual.com/issues/10712| Issue #10712] [https://github.com/artefactual/archivematica/pull/520| PR520]

* '''Contributed''' ([https://github.com/djpillen| Dallas Pillen]) Use display_title instead of title for sip_name in Appraisal tab - [https://github.com/artefactual-labs/appraisal-tab/pull/158| PR158]
* '''Contributed''' ([https://github.com/djpillen| Dallas Pillen]) Use display_string instead of title for digital object title with ArchivesSpace integration - [https://github.com/artefactual-labs/agentarchives/pull/41| PR41]
* Support for [http://www.nationalarchives.gov.uk/aboutapps/pronom/release-notes.xml| PRONOM 89 and 90] - [https://projects.artefactual.com/issues/10982| Issue #10982] [https://github.com/artefactual/archivematica/pull/660| PR660]
* Fix upgrades when FPR Rules have been customised - [https://github.com/artefactual/archivematica-fpr-admin/issues/46| FPR Admin Issue #46] [https://github.com/artefactual/archivematica/pull/609| PR609]
* ArchivesSpace: Don't special case first note when editing a record - [https://github.com/artefactual-labs/agentarchives/pull/40| PR40]
* Set filepath for zip files correctly when starting transfer - [https://projects.artefactual.com/issues/11224| #11224] [https://github.com/artefactual/archivematica/pull/626| PR626]
* Change date format in verifyMD5.sh - [https://github.com/artefactual/archivematica/pull/629| PR629]

=== Archivematica Storage Service 0.10.1 ===
* '''Sponsored''' (University of British Columbia Library) Improvements to editing pipelines - [https://github.com/artefactual/archivematica-storage-service/pull/194| PR194]
* '''Sponsored''' (City of Vancouver Archives) Correctly update pointer files when reingesting uncompressed AIP's [https://github.com/artefactual/archivematica-storage-service/pull/203| PR203] [https://github.com/artefactual/archivematica-storage-service/pull/214| PR214]
* Update Bagit-python to version 1.5.4 [https://github.com/artefactual/archivematica-storage-service/pull/207| PR207]

Archivematica 1.6.1 release notes

2017-08-01T18:52:34Z

Evelyn:

[[Main_Page|Home]] > [[Release_Notes|Release Notes]] > Archivematica 1.6.1 release notes

'''NOTE: these release notes are a work in progress and are subject to change.'''

Primarily a bugfix release - August 1st, 2017.

This is the first Archivematica release to provide packages for Ubuntu 16.04 (xenial). Support for xenial is considered beta. Ubuntu 14.04 (trusty) and CentOS 7.x are also supported.

==== Tool Updates ====
* Support for PRONOM 90
* siegfried updated to version 1.7.3
* FIDO updated to version 1.3.6
* ffmpeg updated to version 3.3.2 (Ubuntu only)

=== Archivematica 1.6.1 ===
* '''Sponsored''' (Rockefeller Archive Center) Object Level Premis Rights Import - [https://github.com/artefactual/archivematica/pull/575| PR575] [https://www.archivematica.org/en/docs/archivematica-1.6/user-manual/transfer/import-metadata/#importing-rights-metadata-with-rights-csv| Docs]
* '''Sponsored''' (Canadian Centre for Architecture) Update METS to encode in UTF-8 instead of ASCII - [https://projects.artefactual.com/issues/11163| Issue #11163] [https://github.com/artefactual/archivematica/pull/541| PR541]
* '''Sponsored''' (Canadian Centre for Architecture) Increase Elasticsearch timeout limit - [https://projects.artefactual.com/issues/11294| Issue #11294] [https://github.com/artefactual/archivematica/pull/556| PR556]
* '''Sponsored''' (University of Saskatchewan Library) Allow UTF8-encoded transfer directory names - [https://projects.artefactual.com/issues/10712| Issue #10712] [https://github.com/artefactual/archivematica/pull/520| PR520]

* '''Contributed''' ([https://github.com/djpillen| Dallas Pillen]) Use display_title instead of title for sip_name in Appraisal tab - [https://github.com/artefactual-labs/appraisal-tab/pull/158| PR158]
* '''Contributed''' ([https://github.com/djpillen| Dallas Pillen]) Use display_string instead of title for digital object title with ArchivesSpace integration - [https://github.com/artefactual-labs/agentarchives/pull/41| PR41]
* Support for [http://www.nationalarchives.gov.uk/aboutapps/pronom/release-notes.xml| PRONOM 89 and 90] - [https://projects.artefactual.com/issues/10982| Issue #10982] [https://github.com/artefactual/archivematica/pull/660| PR660]
* Fix upgrades when FPR Rules have been customised - [https://github.com/artefactual/archivematica-fpr-admin/issues/46| FPR Admin Issue #46] [https://github.com/artefactual/archivematica/pull/609| PR609]
* ArchivesSpace: Don't special case first note when editing a record - [https://github.com/artefactual-labs/agentarchives/pull/40| PR40]
* Set filepath for zip files correctly when starting transfer - [https://projects.artefactual.com/issues/11224| #11224] [https://github.com/artefactual/archivematica/pull/626| PR626]
* Change date format in verifyMD5.sh - [https://github.com/artefactual/archivematica/pull/629| PR629]

=== Archivematica Storage Service 0.10.1 ===
* '''Sponsored''' (University of British Columbia Library) Improvements to editing pipelines - [https://github.com/artefactual/archivematica-storage-service/pull/194| PR194]
* '''Sponsored''' (City of Vancouver Archives) Correctly update pointer files when reingesting uncompressed AIP's [https://github.com/artefactual/archivematica-storage-service/pull/203| PR203] [https://github.com/artefactual/archivematica-storage-service/pull/214| PR214]
* Update Bagit-python to version 1.5.4 [https://github.com/artefactual/archivematica-storage-service/pull/207| PR207]

Release 1.6.1

2017-07-31T18:52:04Z

Evelyn:

[[Main Page]] > [[External_tools|External software tools]]> Release 1.6.1

Archivematica integrates a suite of free and open-source tools that allows users to process digital objects from ingest to access in compliance with the ISO-OAIS functional model. In addition to the core Archivematica which is released under AGPL v3 license, the following tools are bundled with Archivematica 1.6.0:

{| border="1" cellpadding="10" cellspacing="0" width=90%
|-
|- style="background-color:#cccccc;"
!style="width:20%"|'''Tool'''
!style="width:40%"|'''Description'''
!style="width:30%"|'''License'''
|-
|-
|[http://www.accesstomemory.org AtoM]
|Web-based archival description and access tool.
|GNU General Public License (GPL)
|-
|[https://github.com/LibraryOfCongress/bagit-java/ BagIt]
|Standard and script to package digital objects and metadata for archival storage
|BSD License
|-
|[https://github.com/simsong/bulk_extractor bulk_extractor]
|Disk image and file contents analysis tool
|Public domain
|-
|[http://www.clamav.net/ Clam AV (anti-virus)]
|Anti-virus toolkit for UNIX
|GNU General Public License (GPL)
|-
|[https://www.djangoproject.com/ Django]
|Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design.
|BSD License
|-
|[http://www.elasticsearch.org/ ElasticSearch]
|Indexing and search
|Apache License 2.0
|-
|[http://www.sno.phy.queensu.ca/~phil/exiftool/index.html ExifTool]
|Multimedia metadata extraction
|GNU General Public License and Artistic License
|-
|[http://ffmpeg.org/ FFmpeg]
|Converts a wide variety of audio and video formats
|GNU Lesser General Public License (LGPL)
|-
|[https://github.com/openplanets/fido fido]
|File format identification tool
|Licensed under the Apache License, Version 2.0 (the "License")
|-
|[http://code.google.com/p/fits/ File Information Tool Set (FITS)]
|File format identification and validation software integration tool
|GNU Lesser General Public License (LGPL)
|-
|[http://gearman.org/ Gearman]
|Gearman provides a generic application framework to farm out work to other machines or processes that are better suited to do the work.
|BSD License
|-
|[http://www.imagemagick.org/script/index.php Imagemagick]
|Converts a wide variety of bitmap images
|GPL compatible [http://www.imagemagick.org/script/license.php Imagemagick license]
|-
|[http://www.inkscape.org/ Inkscape]
|Converts vector images to Scalable Vector Graphic (SVG) format
|GNU General Public License (GPL) version 2
|-
|[http://jhove.sourceforge.net/ JHOVE]
|File format validation tool
|GNU Lesser General Public License (LGPL)
|-
|[http://md5deep.sourceforge.net/ md5deep]
|Checksum generation and verification scripts
|GNU General Public License (GPL)
|-
|[https://mediaarea.net/en/MediaInfo MediaInfo]
|Multimedia metadata extraction
|BSD (2-clause), Zlib
|-
|[http://linux.about.com/cs/linux101/g/nfscommon.htm NFS-common]
|Network File System Access - allows access to files on network storage devices.
|GNU General Public License (GPL)
|-
|[http://p7zip.sourceforge.net/ p7zip]
|7-Zip is a file archiver with a high compression ratio. (LZMA)
|GNU General Public License (GPL)
|-
|[http://packages.ubuntu.com/lucid/python-lxml Python-lxml]
|Python binding for libxml2 and libxslt
|GNU General Public License (GPL)
|-
|[https://github.com/richardlehane/siegfried Seigfried]
|File format identification tool
|Licensed under the Apache License, Version 2.0 (the "License")
|-
|[http://www.sleuthkit.org/ Sleuthkit]
|Disk image management and extraction toolkit
|Common Public License / IBM Public License
|-
|[http://code.google.com/p/tesseract-ocr/ Tesseract]
|Optical Character Recognition -read image files and convert to text
|Apache Licence Vesion 2
|-
|[http://www.ubuntu.org/ Ubuntu Linux]
|Interface with computing hardware. Ubuntu Linux server edition.
|GNU General Public License (GPL)
|-
|[http://www.ossp.org/pkg/lib/uuid/ UUID]
|command line interface (CLI) for the generation of DCE 1.1, ISO/IEC 11578:1996 and IETF RFC-4122 compliant Universally Unique Identifier (UUID).
|GNU General Public License (GPL)
|-
|[http://unarchiver.c3.cx/commandline unar]
|The Unarchiver is an archive unpacker program
|GNU General Public License (GPL)
|-
|[http://manpages.ubuntu.com/manpages/hardy/man1/zip.1.html Zip]
|Utility called by Bagit to create AIP package
|Info-Zip license: "Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely"
|-
|}

External tools

2017-07-31T18:42:57Z

Evelyn:

[[Main Page]] > [[Documentation]] > External tools

=External software tools used in Archivematica=

'''[[Release 1.7.0]]''' (In development)

'''[[Release 1.6.1]]''' (In development)

'''[[Release 1.6.0]]''' (March 2017)

'''[[Release 1.5]]''' (June 2016)

'''[[Release 1.4.1]]''' (June 2015)

'''[[Release 1.4]]''' (May 2015)

'''[[Release 1.3.1]]''' (February 2015)

'''[[Release 1.0]]''' (September 2014)

'''[[Release 0.10-beta]]''' (April 2013)

'''[[Release 0.9-beta]]''' (Aug 2012)

'''[[Release 0.8-alpha]]''' (Jan 2012)

'''[[Release 0.7.1-alpha]]''' (June 2011)

'''[[Release 0.7-alpha]]''' (Feb 2011)

'''[[Release 0.6.2-alpha]]''' (November 2010)

'''[[Release 0.6-alpha]]''' (May 2010)

'''[[Release 0.5-alpha]]''' (November 2009)

'''[[Release 0.4-alpha]]''' (October 2009)

'''[[Release 0.3.5-alpha]]''' (September 2009)

'''[[Release 0.3-alpha]]''' (June 2009)

'''[[Release 0.2-alpha]]''' (May 2009)

'''[[Release 0.1-alpha]]''' (Feb 2009)

Release 1.6.1

2017-07-31T17:06:36Z

Evelyn:

[[Main Page]] > [[External_tools|External software tools]]> Release 1.6.1

Archivematica integrates a suite of free and open-source tools that allows users to process digital objects from ingest to access in compliance with the ISO-OAIS functional model. In addition to the core Archivematica which is released under AGPL v3 license, the following tools are bundled with Archivematica 1.6.0:

{| border="1" cellpadding="10" cellspacing="0" width=90%
|-
|- style="background-color:#cccccc;"
!style="width:20%"|'''Tool'''
!style="width:10%"|'''Version'''
!style="width:40%"|'''Description'''
!style="width:30%"|'''License'''
|-
|-
|[http://www.accesstomemory.org AtoM]
|Tested with 2.3.0, 2.3.1, qa/2.4.x
|Web-based archival description and access tool.
|GNU General Public License (GPL)
|-
|[https://github.com/LibraryOfCongress/bagit-java/ BagIt]
|4.9.0
|Standard and script to package digital objects and metadata for archival storage
|BSD License
|-
|[https://github.com/simsong/bulk_extractor bulk_extractor]
|1.5.5
|Disk image and file contents analysis tool
|Public domain
|-
|[http://www.clamav.net/ Clam AV (anti-virus)]
|0.99.2
|Anti-virus toolkit for UNIX
|GNU General Public License (GPL)
|-
|[https://www.djangoproject.com/ Django]
|1.8.x
|Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design.
|BSD License
|-
|[http://www.elasticsearch.org/ ElasticSearch]
|1.7.5
|Indexing and search
|Apache License 2.0
|-
|[http://www.sno.phy.queensu.ca/~phil/exiftool/index.html ExifTool]
|10.10
|Multimedia metadata extraction
|GNU General Public License and Artistic License
|-
|[http://ffmpeg.org/ FFmpeg]
|
|Converts a wide variety of audio and video formats
|GNU Lesser General Public License (LGPL)
|-
|[https://github.com/openplanets/fido fido]
|1.3.5
|File format identification tool
|Licensed under the Apache License, Version 2.0 (the "License")
|-
|[http://code.google.com/p/fits/ File Information Tool Set (FITS)]
|
|File format identification and validation software integration tool
|GNU Lesser General Public License (LGPL)
|-
|[http://gearman.org/ Gearman]
|
|Gearman provides a generic application framework to farm out work to other machines or processes that are better suited to do the work.
|BSD License
|-
|[http://www.imagemagick.org/script/index.php Imagemagick]
|
|Converts a wide variety of bitmap images
|GPL compatible [http://www.imagemagick.org/script/license.php Imagemagick license]
|-
|[http://www.inkscape.org/ Inkscape]
|
|Converts vector images to Scalable Vector Graphic (SVG) format
|GNU General Public License (GPL) version 2
|-
|[http://jhove.sourceforge.net/ JHOVE]
|
|File format validation tool
|GNU Lesser General Public License (LGPL)
|-
|[http://md5deep.sourceforge.net/ md5deep]
|
|Checksum generation and verification scripts
|GNU General Public License (GPL)
|-
|[https://mediaarea.net/en/MediaInfo MediaInfo]
|
|Multimedia metadata extraction
|BSD (2-clause), Zlib
|-
|[http://linux.about.com/cs/linux101/g/nfscommon.htm NFS-common]
|
|Network File System Access - allows access to files on network storage devices.
|GNU General Public License (GPL)
|-
|[http://p7zip.sourceforge.net/ p7zip]
|
|7-Zip is a file archiver with a high compression ratio. (LZMA)
|GNU General Public License (GPL)
|-
|[http://packages.ubuntu.com/lucid/python-lxml Python-lxml]
|
|Python binding for libxml2 and libxslt
|GNU General Public License (GPL)
|-
|[https://github.com/richardlehane/siegfried Seigfried]
| 1.6.7
|File format identification tool
|Licensed under the Apache License, Version 2.0 (the "License")
|-
|[http://www.sleuthkit.org/ Sleuthkit]
|
|Disk image management and extraction toolkit
|Common Public License / IBM Public License
|-
|[http://code.google.com/p/tesseract-ocr/ Tesseract]
|
|Optical Character Recognition -read image files and convert to text
|Apache Licence Vesion 2
|-
|[http://www.ubuntu.org/ Ubuntu Linux]
|
|Interface with computing hardware. Ubuntu Linux server edition.
|GNU General Public License (GPL)
|-
|[http://www.ossp.org/pkg/lib/uuid/ UUID]
|
|command line interface (CLI) for the generation of DCE 1.1, ISO/IEC 11578:1996 and IETF RFC-4122 compliant Universally Unique Identifier (UUID).
|GNU General Public License (GPL)
|-
|[http://unarchiver.c3.cx/commandline unar]
|
|The Unarchiver is an archive unpacker program
|GNU General Public License (GPL)
|-
|[http://manpages.ubuntu.com/manpages/hardy/man1/zip.1.html Zip]
|
|Utility called by Bagit to create AIP package
|Info-Zip license: "Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely"
|-
|}

Release 1.6.1

2017-07-31T16:50:39Z

Evelyn: Created page with "Main Page > External software tools> Release 1.6.1 Archivematica integrates a suite of free and open-source tools that allows users to process digital ..."

[[Main Page]] > [[External_tools|External software tools]]> Release 1.6.1

Archivematica integrates a suite of free and open-source tools that allows users to process digital objects from ingest to access in compliance with the ISO-OAIS functional model. In addition to the core Archivematica which is released under AGPL v3 license, the following tools are bundled with Archivematica 1.6.0:

{| border="1" cellpadding="10" cellspacing="0" width=90%
|-
|- style="background-color:#cccccc;"
!style="width:20%"|'''Tool'''
!style="width:10%"|'''Version'''
!style="width:40%"|'''Description'''
!style="width:30%"|'''License'''
|-
|-
|[http://www.accesstomemory.org AtoM]
|Tested with 2.3.0, 2.3.1, qa/2.4.x
|Web-based archival description and access tool.
|GNU General Public License (GPL)
|-
|[https://github.com/LibraryOfCongress/bagit-java/ BagIt]
| 1.5.0 - 1.5.4
|Standard and script to package digital objects and metadata for archival storage
|BSD License
|-
|[https://github.com/simsong/bulk_extractor bulk_extractor]
|
|Disk image and file contents analysis tool
|Public domain
|-
|[http://www.clamav.net/ Clam AV (anti-virus)]
|
|Anti-virus toolkit for UNIX
|GNU General Public License (GPL)
|-
|[https://www.djangoproject.com/ Django]
|1.8.x
|Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design.
|BSD License
|-
|[http://www.elasticsearch.org/ ElasticSearch]
|1.7.5
|Indexing and search
|Apache License 2.0
|-
|[http://www.sno.phy.queensu.ca/~phil/exiftool/index.html ExifTool]
|
|Multimedia metadata extraction
|GNU General Public License and Artistic License
|-
|[http://ffmpeg.org/ FFmpeg]
|
|Converts a wide variety of audio and video formats
|GNU Lesser General Public License (LGPL)
|-
|[https://github.com/openplanets/fido fido]
|1.3.5
|File format identification tool
|Licensed under the Apache License, Version 2.0 (the "License")
|-
|[http://code.google.com/p/fits/ File Information Tool Set (FITS)]
|
|File format identification and validation software integration tool
|GNU Lesser General Public License (LGPL)
|-
|[http://gearman.org/ Gearman]
|
|Gearman provides a generic application framework to farm out work to other machines or processes that are better suited to do the work.
|BSD License
|-
|[http://www.imagemagick.org/script/index.php Imagemagick]
|
|Converts a wide variety of bitmap images
|GPL compatible [http://www.imagemagick.org/script/license.php Imagemagick license]
|-
|[http://www.inkscape.org/ Inkscape]
|
|Converts vector images to Scalable Vector Graphic (SVG) format
|GNU General Public License (GPL) version 2
|-
|[http://jhove.sourceforge.net/ JHOVE]
|
|File format validation tool
|GNU Lesser General Public License (LGPL)
|-
|[http://md5deep.sourceforge.net/ md5deep]
|
|Checksum generation and verification scripts
|GNU General Public License (GPL)
|-
|[https://mediaarea.net/en/MediaInfo MediaInfo]
|
|Multimedia metadata extraction
|BSD (2-clause), Zlib
|-
|[http://linux.about.com/cs/linux101/g/nfscommon.htm NFS-common]
|
|Network File System Access - allows access to files on network storage devices.
|GNU General Public License (GPL)
|-
|[http://p7zip.sourceforge.net/ p7zip]
|
|7-Zip is a file archiver with a high compression ratio. (LZMA)
|GNU General Public License (GPL)
|-
|[http://packages.ubuntu.com/lucid/python-lxml Python-lxml]
|
|Python binding for libxml2 and libxslt
|GNU General Public License (GPL)
|-
|[https://github.com/richardlehane/siegfried Seigfried]
| 1.6.7
|File format identification tool
|Licensed under the Apache License, Version 2.0 (the "License")
|-
|[http://www.sleuthkit.org/ Sleuthkit]
|
|Disk image management and extraction toolkit
|Common Public License / IBM Public License
|-
|[http://code.google.com/p/tesseract-ocr/ Tesseract]
|
|Optical Character Recognition -read image files and convert to text
|Apache Licence Vesion 2
|-
|[http://www.ubuntu.org/ Ubuntu Linux]
|
|Interface with computing hardware. Ubuntu Linux server edition.
|GNU General Public License (GPL)
|-
|[http://www.ossp.org/pkg/lib/uuid/ UUID]
|
|command line interface (CLI) for the generation of DCE 1.1, ISO/IEC 11578:1996 and IETF RFC-4122 compliant Universally Unique Identifier (UUID).
|GNU General Public License (GPL)
|-
|[http://unarchiver.c3.cx/commandline unar]
|
|The Unarchiver is an archive unpacker program
|GNU General Public License (GPL)
|-
|[http://manpages.ubuntu.com/manpages/hardy/man1/zip.1.html Zip]
|
|Utility called by Bagit to create AIP package
|Info-Zip license: "Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely"
|-
|}

Release 1.6.0

2017-07-31T16:49:57Z

Evelyn:

[[Main Page]] > [[External_tools|External software tools]]> Release 1.6.0

Archivematica integrates a suite of free and open-source tools that allows users to process digital objects from ingest to access in compliance with the ISO-OAIS functional model. In addition to the core Archivematica which is released under AGPL v3 license, the following tools are bundled with Archivematica 1.6.0:

{| border="1" cellpadding="10" cellspacing="0" width=90%
|-
|- style="background-color:#cccccc;"
!style="width:20%"|'''Tool'''
!style="width:10%"|'''Version'''
!style="width:40%"|'''Description'''
!style="width:30%"|'''License'''
|-
|-
|[http://www.accesstomemory.org AtoM]
|Tested with 2.3.0, 2.3.1, qa/2.4.x
|Web-based archival description and access tool.
|GNU General Public License (GPL)
|-
|[https://github.com/LibraryOfCongress/bagit-java/ BagIt]
| 1.5.0 - 1.5.4
|Standard and script to package digital objects and metadata for archival storage
|BSD License
|-
|[https://github.com/simsong/bulk_extractor bulk_extractor]
|
|Disk image and file contents analysis tool
|Public domain
|-
|[http://www.clamav.net/ Clam AV (anti-virus)]
|
|Anti-virus toolkit for UNIX
|GNU General Public License (GPL)
|-
|[https://www.djangoproject.com/ Django]
|1.8.x
|Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design.
|BSD License
|-
|[http://www.elasticsearch.org/ ElasticSearch]
|1.7.5
|Indexing and search
|Apache License 2.0
|-
|[http://www.sno.phy.queensu.ca/~phil/exiftool/index.html ExifTool]
|
|Multimedia metadata extraction
|GNU General Public License and Artistic License
|-
|[http://ffmpeg.org/ FFmpeg]
|
|Converts a wide variety of audio and video formats
|GNU Lesser General Public License (LGPL)
|-
|[https://github.com/openplanets/fido fido]
|1.3.5
|File format identification tool
|Licensed under the Apache License, Version 2.0 (the "License")
|-
|[http://code.google.com/p/fits/ File Information Tool Set (FITS)]
|
|File format identification and validation software integration tool
|GNU Lesser General Public License (LGPL)
|-
|[http://gearman.org/ Gearman]
|
|Gearman provides a generic application framework to farm out work to other machines or processes that are better suited to do the work.
|BSD License
|-
|[http://www.imagemagick.org/script/index.php Imagemagick]
|
|Converts a wide variety of bitmap images
|GPL compatible [http://www.imagemagick.org/script/license.php Imagemagick license]
|-
|[http://www.inkscape.org/ Inkscape]
|
|Converts vector images to Scalable Vector Graphic (SVG) format
|GNU General Public License (GPL) version 2
|-
|[http://jhove.sourceforge.net/ JHOVE]
|
|File format validation tool
|GNU Lesser General Public License (LGPL)
|-
|[http://md5deep.sourceforge.net/ md5deep]
|
|Checksum generation and verification scripts
|GNU General Public License (GPL)
|-
|[https://mediaarea.net/en/MediaInfo MediaInfo]
|
|Multimedia metadata extraction
|BSD (2-clause), Zlib
|-
|[http://linux.about.com/cs/linux101/g/nfscommon.htm NFS-common]
|
|Network File System Access - allows access to files on network storage devices.
|GNU General Public License (GPL)
|-
|[http://p7zip.sourceforge.net/ p7zip]
|
|7-Zip is a file archiver with a high compression ratio. (LZMA)
|GNU General Public License (GPL)
|-
|[http://packages.ubuntu.com/lucid/python-lxml Python-lxml]
|
|Python binding for libxml2 and libxslt
|GNU General Public License (GPL)
|-
|[https://github.com/richardlehane/siegfried Seigfried]
| 1.6.7
|File format identification tool
|Licensed under the Apache License, Version 2.0 (the "License")
|-
|[http://www.sleuthkit.org/ Sleuthkit]
|
|Disk image management and extraction toolkit
|Common Public License / IBM Public License
|-
|[http://code.google.com/p/tesseract-ocr/ Tesseract]
|
|Optical Character Recognition -read image files and convert to text
|Apache Licence Vesion 2
|-
|[http://www.ubuntu.org/ Ubuntu Linux]
|
|Interface with computing hardware. Ubuntu Linux server edition.
|GNU General Public License (GPL)
|-
|[http://www.ossp.org/pkg/lib/uuid/ UUID]
|
|command line interface (CLI) for the generation of DCE 1.1, ISO/IEC 11578:1996 and IETF RFC-4122 compliant Universally Unique Identifier (UUID).
|GNU General Public License (GPL)
|-
|[http://unarchiver.c3.cx/commandline unar]
|
|The Unarchiver is an archive unpacker program
|GNU General Public License (GPL)
|-
|[http://manpages.ubuntu.com/manpages/hardy/man1/zip.1.html Zip]
|
|Utility called by Bagit to create AIP package
|Info-Zip license: "Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely"
|-
|}

Improvements/aipreadme

2017-06-20T18:12:06Z

Evelyn: /* Sample README file text */

== User story ==

As a repository manager, I would like AIP's to be as self describing as possible, so that future users, with little or no information about Archivematica or what an AIP is, will be able to understand the structure and contents of the AIP's I produce now.

== Status ==

2017-06-01 - New Proposal

== Interest ==

If you'd like to get involved in this development, please feel free to contribute to this wiki page or start a discussion on our [https://groups.google.com/forum/#!forum/archivematica| user forum].

== Analysis: ==

Currently, Archivematica AIP's are structured as a Bag (https://tools.ietf.org/html/draft-kunze-bagit-14) and contain a METS file, which describes the contents of the AIP. Details about the Archivematica AIP structure are here: https://www.archivematica.org/en/docs/archivematica-1.6/user-manual/archival-storage/aip-structure/

METS files are machine readable, but are not human friendly formats.

Adding a human readable index or description into an AIP would improve the chances of a future user understanding the structure.

Archivematica structures AIP's in a specific way, but that is not documented within the AIP. Adding more explicit documentation about the structure would help users test that AIP's are valid, and help them to understand the structure.

There is a similar proposal outlined here: https://github.com/UTS-eResearch/datacrate

=== Use case: Add a README to each AIP ===

In the data/ directory (beside the mets file) add a README.html or README.md file. This would be intended as the first file to be opened by a human being trying to examine an AIP.

The README file would include
* some boilerplate text, describing what an AIP is
* links to the Archivematica documentation, to METS documentation, to PREMIS docs, etc.
* a link to the METS file
* optionally a link to a CATALOG.html file, that includes more detailed information about the contents of the AIP.

====Sample README file text====

This readme file describes the basic structure of an AIP generated by Archivematica.

'''Acronyms'''

AIP = Archival Information Package
METS = Metadata Encoding and Transmission Standard
OAIS = Open Archival Information System
PDI = Preservation Description Information
PREMIS = Preservation Metadata Implementation Strategies
UUID = Unique Universal Identifier

'''Introduction'''

Archivematica is an open-source suite of tools designed to ingest diverse digital content and prepare AIPs for long-term storage. Once an AIP is generated it is not dependent on Archivematica for retrieval, and can be opened using any standard file browser. The concept of an AIP is derived from the ISO 14721:2012 ''Reference Model for an Open Archival Information System (OAIS)'', which defines it as “[a]n Information Package, consisting of the Content Information and the associated Preservation Description Information (PDI), which is preserved within an OAIS.”

'''Content Information'''

In an Archivematica AIP, the Content Information consists primarily of the originally ingested digital objects and any preservation versions of the objects created to mitigate the risk of format obsolescence over time. The preservation copies typically have the same filenames as the original objects but with different file extensions and with UUIDs appended to the filename. For example, for an original file named ''BBhelmet.ai'' the preservation version may be named ''BBhelmet-e3a3988d-8149-49ea-adc5-c255fb68d4f9.pdf''.

The originally ingested digital objects and any preservation versions are located in the ''objects'' directory of the AIP. There will be nested subdirectories in the ''objects'' directory if these subdirectories were included in the original transfer or added during SIP arrangement. The ''objects'' directory also includes a ''submissionDocumentation'' folder and a ''metadata'' folder. The ''submissionDocumentation'' folder contains documentation such as donor agreements and transfer forms, if these are included in the AIP, as well as a METS file that records the contents of the original transfer(s) from which the AIP was created. The ''metadata'' folder holds any metadata files included in the original transfer(s), and any OCR text files generated during processing.

'''Preservation Description Information (PDI)'''

The PDI in an Archivematica AIP is recorded in a METS XML file. METS is maintained by the Library of Congress, which defines it as “a standard for encoding descriptive, administrative, and structural metadata regarding objects within a digital library, expressed using the XML schema language of the World Wide Web Consortium.” In the Archivematica AIP the METS filename is composed of the name METS with a UUID file extension and an XML file extension; for example ''METS.0ad8cdab-dbbf-4863-8a4d-9a675c227216.xml''. The METS file typically consists of the following standard METS sections:
<mets:metsHdr> (METS header): basic information about the METS file;
<mets:dmdSec> (descriptive metadata section): descriptive metadata about the digital objects;
<mets:amdSec> (administrative metadata section): technical and provenance information about the digital objects;
<mets:fileSec> (file section): a list of the digital objects and an indication of their role in the AIP (original, preservation, metadata, submission documentation, license etc.);
<mets:structMap> (structural map): a physical or logical ordering of the digital objects.

The technical and provenance information in the METS amdSec is recorded as PREMIS metadata. PREMIS is also a Library of Congress standard, and is described as "the international standard for metadata to support the preservation of digital objects and ensure their long-term usability." The PREMIS entities are wrapped in the METS file as follows:

<mets:amdSec>
--<mets:techMD> (technical metadata)
----<premis:object> e.g. UUID, size, checksum, format, original name, extracted technical metadata
--<mets:digiprovMD> (digital provenance metadata)
----<premis:event> e.g. ingestion, message digest calculation, virus scan, format identification, validation, normalization, fixity check
----<premis:agent> for each PREMIS Event there are three associated Agents: the organization, the digital preservation system (e.g. Archivematica 1.x) and the logged-in user
--<mets:rightsMD> (rights metadata)
----<premis:rights> Rights pertaining to the preservation, reproduction and use of the preserved digital objects (only included if the user added rights metadata prior to or during ingest)

The fileSec and structMap use identifier attributes to link a digital object to its amdSec and (if used) dmdSec. For example, if a file entry in the fileSec has the attribute ''ADMID="amdSec_1"'' this means that the amdSec with the identifier ''amdSec_1'' contains the administrative (i.e. technical and provenance) metadata for that file. The fileSec also uses a group identifier attribute to indicate relationships between digital objects. For example, if file A in ''fileGrp "USE=original"'' and file B in ''fileGrp "USE="preservation"'' both have the group identifier attribute ''"Group-269b494d-01cb-451b-8d5e-590d57126d3d"'', then file B is a preservation version generated from file A.

'''AIP structure'''

An Archivematica AIP is packaged into a bag in accordance with the IETF Trust ''BagIt File Packaging Format'', and contains some contents not described in the sections above. This tree structure depicts a typical Archivematica AIP:

<pre>
(1) AIP-name-e3a3988d-8149-49ea-adc5-c255fb68d4f9
(2) ├── bag-info.txt
(3) ├── bagit.txt
(4) ├── manifest-sha512.txt
(5) ├── tagmanifest-md5.txt
(6) └── data
(7) ├── logs
(8) ├── objects
(9) ├── thumbnails
(10) ├── METS.0ad8cdab-dbbf-4863-8a4d-9a675c227216.xml
(11) └── README.txt
</pre>

(1) AIP root directory, with an appended UUID
(2)-(5): Standard packaging files produced in accordance with the BagIt specification.
(6): data directory - this is also a standard directory specified by the BagIt specification. The data directory contains the AIP Content Information and PDI
(7) logs directory - contains log outputs of some of the tools that Archivematica uses in generating the AIP
(8) objects directory - contains the original digital objects as well as normalized versions
(9) thumbnails directory - contains thumbnails generated from the original object for use in the Archivematica user interface
(10) the Archivematica METS file
(11) this README text file

=== Use case: Create and Use a Bag Profile ===

https://github.com/ruebot/bagit-profiles

Archivematica could define a bag profile and reference this in the AIP's it produces. This would help make AIP's more easily machine readable.

Improvements/aipreadme

2017-06-20T18:10:52Z

Evelyn: /* Sample README file text */

== User story ==

As a repository manager, I would like AIP's to be as self describing as possible, so that future users, with little or no information about Archivematica or what an AIP is, will be able to understand the structure and contents of the AIP's I produce now.

== Status ==

2017-06-01 - New Proposal

== Interest ==

If you'd like to get involved in this development, please feel free to contribute to this wiki page or start a discussion on our [https://groups.google.com/forum/#!forum/archivematica| user forum].

== Analysis: ==

Currently, Archivematica AIP's are structured as a Bag (https://tools.ietf.org/html/draft-kunze-bagit-14) and contain a METS file, which describes the contents of the AIP. Details about the Archivematica AIP structure are here: https://www.archivematica.org/en/docs/archivematica-1.6/user-manual/archival-storage/aip-structure/

METS files are machine readable, but are not human friendly formats.

Adding a human readable index or description into an AIP would improve the chances of a future user understanding the structure.

Archivematica structures AIP's in a specific way, but that is not documented within the AIP. Adding more explicit documentation about the structure would help users test that AIP's are valid, and help them to understand the structure.

There is a similar proposal outlined here: https://github.com/UTS-eResearch/datacrate

=== Use case: Add a README to each AIP ===

In the data/ directory (beside the mets file) add a README.html or README.md file. This would be intended as the first file to be opened by a human being trying to examine an AIP.

The README file would include
* some boilerplate text, describing what an AIP is
* links to the Archivematica documentation, to METS documentation, to PREMIS docs, etc.
* a link to the METS file
* optionally a link to a CATALOG.html file, that includes more detailed information about the contents of the AIP.

====Sample README file text====

This readme file describes the basic structure of an AIP generated by Archivematica.

'''Acronyms'''

AIP = Archival Information Package
METS = Metadata Encoding and Transmission Standard
OAIS = Open Archival Information System
PDI = Preservation Description Information
PREMIS = Preservation Metadata Implementation Strategies
UUID = Unique Universal Identifier

'''Introduction'''

Archivematica is an open-source suite of tools designed to ingest diverse digital content and prepare AIPs for long-term storage. Once an AIP is generated it is not dependent on Archivematica for retrieval, and can be opened using any standard file browser. The concept of an AIP is derived from the ISO 14721:2012 ''Reference Model for an Open Archival Information System (OAIS)'', which defines it as “[a]n Information Package, consisting of the Content Information and the associated Preservation Description Information (PDI), which is preserved within an OAIS.”

'''Content Information'''

In an Archivematica AIP, the Content Information consists primarily of the originally ingested digital objects and any preservation versions of the objects created to mitigate the risk of format obsolescence over time. The preservation copies typically have the same filenames as the original objects but with different file extensions and with UUIDs appended to the filename. For example, for an original file named ''BBhelmet.ai'' the preservation version may be named ''BBhelmet-e3a3988d-8149-49ea-adc5-c255fb68d4f9.pdf''.

The originally ingested digital objects and any preservation versions are located in the ''objects'' directory of the AIP. There will be nested subdirectories in the ''objects'' directory if these subdirectories were included in the original transfer or added during SIP arrangement. The ''objects'' directory also includes a ''submissionDocumentation'' folder and a ''metadata'' folder. The ''submissionDocumentation'' folder contains documentation such as donor agreements and transfer forms, if these are included in the AIP, as well as a METS file that records the contents of the original transfer(s) from which the AIP was created. The ''metadata'' folder holds any metadata files included in the original transfer(s), and any OCR text files generated during processing.

'''Preservation Description Information (PDI)'''

The PDI in an Archivematica AIP is recorded in a METS XML file. METS is maintained by the Library of Congress, which defines it as “a standard for encoding descriptive, administrative, and structural metadata regarding objects within a digital library, expressed using the XML schema language of the World Wide Web Consortium.” In the Archivematica AIP the METS filename is composed of the name METS with a UUID file extension and an XML file extension; for example ''METS.0ad8cdab-dbbf-4863-8a4d-9a675c227216.xml''. The METS file typically consists of the following standard METS sections:
<mets:metsHdr> (METS header): basic information about the METS file;
<mets:dmdSec> (descriptive metadata section): descriptive metadata about the digital objects;
<mets:amdSec> (administrative metadata section): technical and provenance information about the digital objects;
<mets:fileSec> (file section): a list of the digital objects and an indication of their role in the AIP (original, preservation, metadata, submission documentation, license etc.);
<mets:structMap> (structural map): a physical or logical ordering of the digital objects.

The technical and provenance information in the METS amdSec is recorded as PREMIS metadata. PREMIS is also a Library of Congress standard, and is described as "the international standard for metadata to support the preservation of digital objects and ensure their long-term usability." The PREMIS entities are wrapped in the METS file as follows:

<mets:amdSec>
--<mets:techMD> (technical metadata)
----<premis:object> e.g. UUID, size, checksum, format, original name, extracted technical metadata
--<mets:digiprovMD> (digital provenance metadata)
----<premis:event> e.g. ingestion, message digest calculation, virus scan, format identification, validation, normalization, fixity check
----<premis:agent> for each PREMIS Event there are three associated Agents: the organization, the digital preservation system (e.g. Archivematica 1.x) and the logged-in user
--<mets:rightsMD> (rights metadata)
----<premis:rights> Rights pertaining to the preservation, reproduction and use of the preserved digital objects (only included if the user added rights metadata prior to or during ingest)

The fileSec and structMap use identifier attributes to link a digital object to its amdSec and (if used) dmdSec. For example, if a file entry in the fileSec has the attribute ''ADMID="amdSec_1"'' this means that the amdSec with the identifier ''amdSec_1'' contains the administrative (i.e. technical and provenance) metadata for that file. The fileSec also uses a group identifier attribute to indicate relationships between digital objects. For example, if file A in ''fileGrp "USE=original"'' and file B in ''fileGrp "USE="preservation"'' both have the group identifier attribute ''"Group-269b494d-01cb-451b-8d5e-590d57126d3d"'', then file B is a preservation version generated from file A.

'''AIP structure'''

An Archivematica AIP is packaged into a bag in accordance with the IETF Trust ''BagIt File Packaging Format'', and contains some contents not described in the sections above. This tree structure depicts a typical Archivematica AIP:

<pre>
(1) AIP-name-e3a3988d-8149-49ea-adc5-c255fb68d4f9
(2) ├── bag-info.txt
(3) ├── bagit.txt
(4) ├── manifest-sha512.txt
(5) ├── tagmanifest-md5.txt
(6) └── data
(7) ├── logs
(8) ├── objects
(9) ├── thumbnails
(10) ├── METS.0ad8cdab-dbbf-4863-8a4d-9a675c227216.xml
(11) └── README.txt
</pre>

(1) AIP root directory, with an appended UUID
(2)-(5): Standard packaging files produced in accordance with the BagIt specification.
(6): data directory - this is also a standard directory specified by the BagIt specification. The data directory contains the AIP Content Information and PDI file
(7) logs directory - contains log outputs of some of the tools that Archivematica uses in generating the AIP
(8) objects directory - contains the original digital objects as well as normalized versions
(9) thumbnails directory - contains thumbnails generated from the original object for use in the Archivematica user interface
(10) the Archivematica METS file
(11) this README text file

=== Use case: Create and Use a Bag Profile ===

https://github.com/ruebot/bagit-profiles

Archivematica could define a bag profile and reference this in the AIP's it produces. This would help make AIP's more easily machine readable.

Improvements/aipreadme

2017-06-20T18:05:37Z

Evelyn: /* Sample README file text */

== User story ==

As a repository manager, I would like AIP's to be as self describing as possible, so that future users, with little or no information about Archivematica or what an AIP is, will be able to understand the structure and contents of the AIP's I produce now.

== Status ==

2017-06-01 - New Proposal

== Interest ==

If you'd like to get involved in this development, please feel free to contribute to this wiki page or start a discussion on our [https://groups.google.com/forum/#!forum/archivematica| user forum].

== Analysis: ==

Currently, Archivematica AIP's are structured as a Bag (https://tools.ietf.org/html/draft-kunze-bagit-14) and contain a METS file, which describes the contents of the AIP. Details about the Archivematica AIP structure are here: https://www.archivematica.org/en/docs/archivematica-1.6/user-manual/archival-storage/aip-structure/

METS files are machine readable, but are not human friendly formats.

Adding a human readable index or description into an AIP would improve the chances of a future user understanding the structure.

Archivematica structures AIP's in a specific way, but that is not documented within the AIP. Adding more explicit documentation about the structure would help users test that AIP's are valid, and help them to understand the structure.

There is a similar proposal outlined here: https://github.com/UTS-eResearch/datacrate

=== Use case: Add a README to each AIP ===

In the data/ directory (beside the mets file) add a README.html or README.md file. This would be intended as the first file to be opened by a human being trying to examine an AIP.

The README file would include
* some boilerplate text, describing what an AIP is
* links to the Archivematica documentation, to METS documentation, to PREMIS docs, etc.
* a link to the METS file
* optionally a link to a CATALOG.html file, that includes more detailed information about the contents of the AIP.

====Sample README file text====

This readme file describes the basic structure of an AIP generated by Archivematica.

'''Acronyms'''

AIP = Archival Information Package
METS = Metadata Encoding and Transmission Standard
OAIS = Open Archival Information System
PDI = Preservation Description Information
PREMIS = Preservation Metadata Implementation Strategies
UUID = Unique Universal Identifier

'''Introduction'''

Archivematica is an open-source suite of tools designed to ingest diverse digital content and prepare AIPs for long-term storage. Once an AIP is generated it is not dependent on Archivematica for retrieval, and can be opened using any standard file browser. The concept of an AIP is derived from the ISO 14721:2012 ''Reference Model for an Open Archival Information System (OAIS)'', which defines it as “[a]n Information Package, consisting of the Content Information and the associated Preservation Description Information (PDI), which is preserved within an OAIS.”

'''Content Information'''

In an Archivematica AIP, the Content Information consists primarily of the originally ingested digital objects and any preservation versions of the objects created to mitigate the risk of format obsolescence over time. The preservation copies typically have the same filenames as the original objects but with different file extensions and with UUIDs appended to the filename. For example, for an original file named ''BBhelmet.ai'' the preservation version may be named ''BBhelmet-e3a3988d-8149-49ea-adc5-c255fb68d4f9.pdf''.

The originally ingested digital objects and any preservation versions are located in the ''objects'' directory of the AIP. There will be nested subdirectories in the ''objects'' directory if these subdirectories were included in the original transfer or added during SIP arrangement. The ''objects'' directory also includes a ''submissionDocumentation'' folder and a ''metadata'' folder. The ''submissionDocumentation'' folder contains documentation such as donor agreements and transfer forms, if these are included in the AIP, as well as a METS file that records the contents of the original transfer(s) from which the AIP was created. The ''metadata'' folder holds any metadata files included in the original transfer(s), and any OCR text files generated during processing.

'''Preservation Description Information (PDI)'''

The PDI in an Archivematica AIP is recorded in a METS XML file. METS is maintained by the Library of Congress, which defines it as “a standard for encoding descriptive, administrative, and structural metadata regarding objects within a digital library, expressed using the XML schema language of the World Wide Web Consortium.” In the Archivematica AIP the METS filename is composed of the name METS with a UUID file extension and an XML file extension; for example ''METS.0ad8cdab-dbbf-4863-8a4d-9a675c227216.xml''. The METS file typically consists of the following standard METS sections:
<mets:metsHdr> (METS header): basic information about the METS file;
<mets:dmdSec> (descriptive metadata section): descriptive metadata about the digital objects;
<mets:amdSec> (administrative metadata section): technical and provenance information about the digital objects;
<mets:fileSec> (file section): a list of the digital objects and an indication of their role in the AIP (original, preservation, metadata, submission documentation, license etc.);
<mets:structMap> (structural map): a physical or logical ordering of the digital objects.

The technical and provenance information in the METS amdSec is recorded as PREMIS metadata. PREMIS is also a Library of Congress standard, and is described as "the international standard for metadata to support the preservation of digital objects and ensure their long-term usability." The PREMIS entities are wrapped in the METS file as follows:

<mets:amdSec>
--<mets:techMD> (technical metadata)
----<premis:object> e.g. UUID, size, checksum, format, original name, extracted technical metadata
--<mets:digiprovMD> (digital provenance metadata)
----<premis:event> e.g. ingestion, message digest calculation, virus scan, format identification, validation, normalization, fixity check
----<premis:agent> for each PREMIS Event there are three associated Agents: the organization, the digital preservation system (e.g. Archivematica 1.x) and the logged-in user
--<mets:rightsMD> (rights metadata)
----<premis:rights> Rights pertaining to the preservation, reproduction and use of the preserved digital objects (only included if the user added rights metadata prior to or during ingest)

The fileSec and structMap use identifier attributes to link a digital object to its amdSec and (if used) dmdSec. For example, if a file entry in the fileSec has the attribute ''ADMID="amdSec_1"'' this means that the amdSec with the identifier ''amdSec_1'' contains the administrative (i.e. technical and provenance) metadata for that file. The fileSec also uses a group identifier attribute to indicate relationships between digital objects. For example, if file A in ''fileGrp "USE=original"'' and file B in ''fileGrp "USE="preservation"'' both have the group identifier attribute ''"Group-269b494d-01cb-451b-8d5e-590d57126d3d"'', then file B is a preservation version generated from file A.

'''AIP structure'''

An Archivematica AIP is packaged into a bag in accordance with the IETF Trust ''BagIt File Packaging Format'', and contains some contents not described in the sections above. This tree structure depicts a typical Archivematica AIP:

<pre>
(1) AIP-name-e3a3988d-8149-49ea-adc5-c255fb68d4f9
(2) ├── bag-info.txt
(3) ├── bagit.txt
(4) ├── manifest-sha512.txt
(5) ├── tagmanifest-md5.txt
(6) └── data
(7) ├── logs
(8) ├── objects
(9) ├── thumbnails
(10) ├── METS.0ad8cdab-dbbf-4863-8a4d-9a675c227216.xml
(11) └── README.txt
</pre>

(1) AIP root directory, with an appended UUID
(2)-(5): Standard packaging files produced in accordance with the IETF Trust ''BagIt File Packaging Format'' specification.
(6): data directory - contains subdirectories logs, objects, and thumbnails, as well as the METS file
(7) logs directory - contains the log outputs of the various tools that Archivematica uses in generating the AIP (8) objects directory - contains the original digital objects as well as normalized versions
(9) thumbnails directory - contains thumbnails generated from the original object for use in the Archivematica user interface
(10) the Archivematica METS file
(11) this README text file

=== Use case: Create and Use a Bag Profile ===

https://github.com/ruebot/bagit-profiles

Archivematica could define a bag profile and reference this in the AIP's it produces. This would help make AIP's more easily machine readable.

Improvements/aipreadme

2017-06-20T18:03:43Z

Evelyn: /* Sample README file text */

== User story ==

As a repository manager, I would like AIP's to be as self describing as possible, so that future users, with little or no information about Archivematica or what an AIP is, will be able to understand the structure and contents of the AIP's I produce now.

== Status ==

2017-06-01 - New Proposal

== Interest ==

If you'd like to get involved in this development, please feel free to contribute to this wiki page or start a discussion on our [https://groups.google.com/forum/#!forum/archivematica| user forum].

== Analysis: ==

Currently, Archivematica AIP's are structured as a Bag (https://tools.ietf.org/html/draft-kunze-bagit-14) and contain a METS file, which describes the contents of the AIP. Details about the Archivematica AIP structure are here: https://www.archivematica.org/en/docs/archivematica-1.6/user-manual/archival-storage/aip-structure/

METS files are machine readable, but are not human friendly formats.

Adding a human readable index or description into an AIP would improve the chances of a future user understanding the structure.

Archivematica structures AIP's in a specific way, but that is not documented within the AIP. Adding more explicit documentation about the structure would help users test that AIP's are valid, and help them to understand the structure.

There is a similar proposal outlined here: https://github.com/UTS-eResearch/datacrate

=== Use case: Add a README to each AIP ===

In the data/ directory (beside the mets file) add a README.html or README.md file. This would be intended as the first file to be opened by a human being trying to examine an AIP.

The README file would include
* some boilerplate text, describing what an AIP is
* links to the Archivematica documentation, to METS documentation, to PREMIS docs, etc.
* a link to the METS file
* optionally a link to a CATALOG.html file, that includes more detailed information about the contents of the AIP.

====Sample README file text====

This readme file describes the basic structure of an AIP generated by Archivematica.

'''Acronyms'''

AIP = Archival Information Package
METS = Metadata Encoding and Transmission Standard
OAIS = Open Archival Information System
PDI = Preservation Description Information
PREMIS = Preservation Metadata Implementation Strategies
UUID = Unique Universal Identifier

'''Introduction'''

Archivematica is an open-source suite of tools designed to ingest diverse digital content and prepare AIPs for long-term storage. Once an AIP is generated it is not dependent on Archivematica for retrieval, and can be opened using any standard file browser. The concept of an AIP is derived from the ISO 14721:2012 Reference Model for an ''Open Archival Information System (OAIS)'', which defines it as “[a]n Information Package, consisting of the Content Information and the associated Preservation Description Information (PDI), which is preserved within an OAIS.”

'''Content Information'''

In an Archivematica AIP, the Content Information consists primarily of the originally ingested digital objects and any preservation versions of the objects created to mitigate the risk of format obsolescence over time. The preservation copies typically have the same filenames as the original objects but with different file extensions and with UUIDs appended to the filename. For example, for an original file named ''BBhelmet.ai'' the preservation version may be named ''BBhelmet-e3a3988d-8149-49ea-adc5-c255fb68d4f9.pdf''.

The originally ingested digital objects and any preservation versions are located in the ''objects'' directory of the AIP. There will be nested subdirectories in the ''objects'' directory if these subdirectories were included in the original transfer or added during SIP arrangement. The ''objects'' directory also includes a ''submissionDocumentation'' folder and a ''metadata'' folder. The ''submissionDocumentation'' folder contains documentation such as donor agreements and transfer forms, if these are included in the AIP, as well as a METS file that records the contents of the original transfer(s) from which the AIP was created. The ''metadata'' folder holds any metadata files included in the original transfer(s), and any OCR text files generated during processing.

'''Preservation Description Information (PDI)'''

The PDI in an Archivematica AIP is recorded in a METS XML file. METS is maintained by the Library of Congress, which defines it as “a standard for encoding descriptive, administrative, and structural metadata regarding objects within a digital library, expressed using the XML schema language of the World Wide Web Consortium.” In the Archivematica AIP the METS filename is composed of the name METS with a UUID file extension and an XML file extension; for example ''METS.0ad8cdab-dbbf-4863-8a4d-9a675c227216.xml''. The METS file typically consists of the following standard METS sections:
<mets:metsHdr> (METS header): basic information about the METS file;
<mets:dmdSec> (descriptive metadata section): descriptive metadata about the digital objects;
<mets:amdSec> (administrative metadata section): technical and provenance information about the digital objects;
<mets:fileSec> (file section): a list of the digital objects and an indication of their role in the AIP (original, preservation, metadata, submission documentation, license etc.);
<mets:structMap> (structural map): a physical or logical ordering of the digital objects.

The technical and provenance information in the METS amdSec is recorded as PREMIS metadata. PREMIS is also a Library of Congress standard, and is described as "the international standard for metadata to support the preservation of digital objects and ensure their long-term usability." The PREMIS entities are wrapped in the METS file as follows:

<mets:amdSec>
--<mets:techMD> (technical metadata)
----<premis:object> e.g. UUID, size, checksum, format, original name, extracted technical metadata
--<mets:digiprovMD> (digital provenance metadata)
----<premis:event> e.g. ingestion, message digest calculation, virus scan, format identification, validation, normalization, fixity check
----<premis:agent> for each PREMIS Event there are three associated Agents: the organization, the digital preservation system (e.g. Archivematica 1.x) and the logged-in user
--<mets:rightsMD> (rights metadata)
----<premis:rights> Rights pertaining to the preservation, reproduction and use of the preserved digital objects (only included if the user added rights metadata prior to or during ingest)

The fileSec and structMap use identifier attributes to link a digital object to its amdSec and (if used) dmdSec. For example, if a file entry in the fileSec has the attribute ''ADMID="amdSec_1"'' this means that the amdSec with the identifier ''amdSec_1'' contains the administrative (i.e. technical and provenance) metadata for that file. The fileSec also uses a group identifier attribute to indicate relationships between digital objects. For example, if file A in ''fileGrp "USE=original"'' and file B in ''fileGrp "USE="preservation"'' both have the group identifier attribute ''"Group-269b494d-01cb-451b-8d5e-590d57126d3d"'', then file B is a preservation version generated from file A.

'''AIP structure'''

An Archivematica AIP is packaged into a bag in accordance with the IETF Trust ''BagIt File Packaging Format'', and contains some contents not described in the sections above. This tree structure depicts a typical Archivematica AIP:

<pre>
(1) AIP-name-e3a3988d-8149-49ea-adc5-c255fb68d4f9
(2) ├── bag-info.txt
(3) ├── bagit.txt
(4) ├── manifest-sha512.txt
(5) ├── tagmanifest-md5.txt
(6) └── data
(7) ├── logs
(8) ├── objects
(9) ├── thumbnails
(10) ├── METS.0ad8cdab-dbbf-4863-8a4d-9a675c227216.xml
(11) └── README.txt
</pre>

(1) AIP root directory, with an appended UUID
(2)-(5): Standard packaging files produced in accordance with the IETF Trust ''BagIt File Packaging Format'' specification.
(6): data directory - contains subdirectories logs, objects, and thumbnails, as well as the METS file
(7) logs directory - contains the log outputs of the various tools that Archivematica uses in generating the AIP (8) objects directory - contains the original digital objects as well as normalized versions
(9) thumbnails directory - contains thumbnails generated from the original object for use in the Archivematica user interface
(10) the Archivematica METS file
(11) this README text file

=== Use case: Create and Use a Bag Profile ===

https://github.com/ruebot/bagit-profiles

Archivematica could define a bag profile and reference this in the AIP's it produces. This would help make AIP's more easily machine readable.

Improvements/aipreadme

2017-06-20T17:56:10Z

Evelyn: /* Sample README file text */

== User story ==

As a repository manager, I would like AIP's to be as self describing as possible, so that future users, with little or no information about Archivematica or what an AIP is, will be able to understand the structure and contents of the AIP's I produce now.

== Status ==

2017-06-01 - New Proposal

== Interest ==

If you'd like to get involved in this development, please feel free to contribute to this wiki page or start a discussion on our [https://groups.google.com/forum/#!forum/archivematica| user forum].

== Analysis: ==

Currently, Archivematica AIP's are structured as a Bag (https://tools.ietf.org/html/draft-kunze-bagit-14) and contain a METS file, which describes the contents of the AIP. Details about the Archivematica AIP structure are here: https://www.archivematica.org/en/docs/archivematica-1.6/user-manual/archival-storage/aip-structure/

METS files are machine readable, but are not human friendly formats.

Adding a human readable index or description into an AIP would improve the chances of a future user understanding the structure.

Archivematica structures AIP's in a specific way, but that is not documented within the AIP. Adding more explicit documentation about the structure would help users test that AIP's are valid, and help them to understand the structure.

There is a similar proposal outlined here: https://github.com/UTS-eResearch/datacrate

=== Use case: Add a README to each AIP ===

In the data/ directory (beside the mets file) add a README.html or README.md file. This would be intended as the first file to be opened by a human being trying to examine an AIP.

The README file would include
* some boilerplate text, describing what an AIP is
* links to the Archivematica documentation, to METS documentation, to PREMIS docs, etc.
* a link to the METS file
* optionally a link to a CATALOG.html file, that includes more detailed information about the contents of the AIP.

====Sample README file text====

This readme file describes the basic structure of an AIP generated by Archivematica.

'''Acronyms'''

AIP = Archival Information Package
METS = Metadata Encoding and Transmission Standard
OAIS = Open Archival Information System
PDI = Preservation Description Information
PREMIS = Preservation Metadata Implementation Strategies
UUID = Unique Universal Identifier

'''Introduction'''

Archivematica is an open-source suite of tools designed to ingest diverse digital content and prepare AIPs for long-term storage. Once an AIP is generated it is not dependent on Archivematica for retrieval, and can be opened using any standard file browser. The concept of an AIP is derived from the ISO 14721:2012 Reference Model for an ''Open Archival Information System (OAIS)'', which defines it as “[a]n Information Package, consisting of the Content Information and the associated Preservation Description Information (PDI), which is preserved within an OAIS.”

'''Content Information'''

In an Archivematica AIP, the Content Information consists primarily of the originally ingested digital objects and any preservation versions of the objects created to mitigate the risk of format obsolescence over time. The preservation copies typically have the same filenames as the original objects but with different file extensions and with UUIDs appended to the filename. For example, for an original file named ''BBhelmet.ai'' the preservation version may be named ''BBhelmet-e3a3988d-8149-49ea-adc5-c255fb68d4f9.pdf''.

The originally ingested digital objects and any preservation versions are located in the ''objects'' directory of the AIP. There will be nested subdirectories in the ''objects'' directory if these subdirectories were included in the original transfer or added during SIP arrangement. The ''objects'' directory also includes a ''submissionDocumentation'' folder and a ''metadata'' folder. The ''submissionDocumentation'' folder contains documentation such as donor agreements and transfer forms, if these are included in the AIP, as well as a METS file that records the contents of the original transfer(s) from which the AIP was created. The ''metadata'' folder holds any metadata files included in the original transfer(s), and any OCR text files generated during processing.

'''Preservation Description Information (PDI)'''

The PDI in an Archivematica AIP is recorded in a METS XML file. METS is maintained by the Library of Congress, which defines it as “a standard for encoding descriptive, administrative, and structural metadata regarding objects within a digital library, expressed using the XML schema language of the World Wide Web Consortium.” In the Archivematica AIP the METS filename is composed of the name METS with a UUID file extension and an XML file extension; for example ''METS.0ad8cdab-dbbf-4863-8a4d-9a675c227216.xml''. The METS file typically consists of the following standard METS sections:
<mets:metsHdr> (METS header): basic information about the METS file;
<mets:dmdSec> (descriptive metadata section): descriptive metadata about the digital objects;
<mets:amdSec> (administrative metadata section): technical and provenance information about the digital objects;
<mets:fileSec> (file section): a list of the digital objects and an indication of their role in the AIP (original, preservation, metadata, submission documentation, license etc.);
<mets:structMap> (structural map): a physical or logical ordering of the digital objects.

The technical and provenance information in the METS amdSec is recorded as PREMIS metadata. PREMIS is also a Library of Congress standard, and is described as "the international standard for metadata to support the preservation of digital objects and ensure their long-term usability." The PREMIS entities are wrapped in the METS file as follows:

<mets:amdSec>
--<mets:techMD> (technical metadata)
----<premis:object> e.g. UUID, size, checksum, format, original name, extracted technical metadata
--<mets:digiprovMD> (digital provenance metadata)
----<premis:event> e.g. ingestion, message digest calculation, virus scan, format identification, validation, normalization, fixity check
----<premis:agent> for each PREMIS Event there are three associated Agents: the organization, the digital preservation system (e.g. Archivematica 1.x) and the logged-in user
--<mets:rightsMD> (rights metadata)
----<premis:rights> Rights pertaining to the preservation, reproduction and use of the preserved digital objects (only included if the user added rights metadata prior to or during ingest)

The fileSec and structMap use identifier attributes to link a digital object to its amdSec and (if used) dmdSec. For example, if a file entry in the fileSec has the attribute ''ADMID="amdSec_1"'' this means that the amdSec with the identifier ''amdSec_1'' contains the administrative (i.e. technical and provenance) metadata for that file. The fileSec also uses a group identifier attribute to indicate relationships between digital objects. For example, if file A in ''fileGrp "USE=original"'' and file B in ''fileGrp "USE="preservation"'' both have the group identifier attribute ''"Group-269b494d-01cb-451b-8d5e-590d57126d3d"'', then file B is a preservation version generated from file A.

'''AIP structure'''

An Archivematica AIP is packaged into a bag in accordance with the Library of Congress BagIt specification, and contains some contents not described in the sections above. This tree structure depicts a typical Archivematica AIP:

<pre>
(1) AIP-name-e3a3988d-8149-49ea-adc5-c255fb68d4f9
(2) ├── bag-info.txt
(3) ├── bagit.txt
(4) ├── manifest-sha512.txt
(5) ├── tagmanifest-md5.txt
(6) └── data
(7) ├── logs
(8) ├── objects
(9) ├── thumbnails
(10) ├── METS.0ad8cdab-dbbf-4863-8a4d-9a675c227216.xml
(11) └── README.txt
</pre>

(1) AIP root directory, with an appended UUID
(2)-(5): Standard packaging files produced in accordance with the Bagit Specification. See the specification for more information
(6): data directory - contains subdirectories logs, objects, and thumbnails, as well as the METS file
(7) logs directory - contains the log outputs of the various tools that Archivematica uses in generating the AIP (8) objects directory - contains the original digital objects as well as normalized versions
(9) thumbnails directory - contains thumbnails generated from the original object for use in the Archivematica user interface
(10) the Archivematica METS file
(11) this README text file

=== Use case: Create and Use a Bag Profile ===

https://github.com/ruebot/bagit-profiles

Archivematica could define a bag profile and reference this in the AIP's it produces. This would help make AIP's more easily machine readable.

Improvements/aipreadme

2017-06-20T17:55:07Z

Evelyn: /* Sample README file text */

== User story ==

As a repository manager, I would like AIP's to be as self describing as possible, so that future users, with little or no information about Archivematica or what an AIP is, will be able to understand the structure and contents of the AIP's I produce now.

== Status ==

2017-06-01 - New Proposal

== Interest ==

If you'd like to get involved in this development, please feel free to contribute to this wiki page or start a discussion on our [https://groups.google.com/forum/#!forum/archivematica| user forum].

== Analysis: ==

Currently, Archivematica AIP's are structured as a Bag (https://tools.ietf.org/html/draft-kunze-bagit-14) and contain a METS file, which describes the contents of the AIP. Details about the Archivematica AIP structure are here: https://www.archivematica.org/en/docs/archivematica-1.6/user-manual/archival-storage/aip-structure/

METS files are machine readable, but are not human friendly formats.

Adding a human readable index or description into an AIP would improve the chances of a future user understanding the structure.

Archivematica structures AIP's in a specific way, but that is not documented within the AIP. Adding more explicit documentation about the structure would help users test that AIP's are valid, and help them to understand the structure.

There is a similar proposal outlined here: https://github.com/UTS-eResearch/datacrate

=== Use case: Add a README to each AIP ===

In the data/ directory (beside the mets file) add a README.html or README.md file. This would be intended as the first file to be opened by a human being trying to examine an AIP.

The README file would include
* some boilerplate text, describing what an AIP is
* links to the Archivematica documentation, to METS documentation, to PREMIS docs, etc.
* a link to the METS file
* optionally a link to a CATALOG.html file, that includes more detailed information about the contents of the AIP.

====Sample README file text====

This readme file describes the basic structure of an AIP generated by Archivematica.

'''Acronyms'''

AIP = Archival Information Package
METS = Metadata Encoding and Transmission Standard
OAIS = Open Archival Information System
PDI = Preservation Description Information
PREMIS = Preservation Metadata Implementation Strategies
UUID = Unique Universal Identifier

'''Introduction'''

Archivematica is an open-source suite of tools designed to ingest diverse digital content and prepare AIPs for long-term storage. Once an AIP is generated it is not dependent on Archivematica for retrieval, and can be opened using any standard file browser. The concept of an AIP is derived from the ISO 14721:2012 Reference Model for an ''Open Archival Information System (OAIS)'', which defines it as “[a]n Information Package, consisting of the Content Information and the associated Preservation Description Information (PDI), which is preserved within an OAIS.”

'''Content Information'''

In an Archivematica AIP, the Content Information consists primarily of the originally ingested digital objects and any preservation versions of the objects created to mitigate the risk of format obsolescence over time. The preservation copies typically have the same filenames as the original objects but with different file extensions and with UUIDs appended to the filename. For example, for an original file named ''BBhelmet.ai'' the preservation version may be named ''BBhelmet-e3a3988d-8149-49ea-adc5-c255fb68d4f9.pdf''.

The originally ingested digital objects and any preservation versions are located in the ''objects'' directory of the AIP. There will be nested subdirectories in the ''objects'' directory if these subdirectories were included in the original transfer or added during SIP arrangement. The ''objects'' directory also includes a ''submissionDocumentation'' folder and a ''metadata'' folder. The ''submissionDocumentation'' folder contains documentation such as donor agreements and transfer forms, if these are included in the AIP, as well as a METS file that records the contents of the original transfer(s) from which the AIP was created. The ''metadata'' folder holds any metadata files included in the original transfer(s), and any OCR text files generated during processing.

'''Preservation Description Information (PDI)'''

The PDI in an Archivematica AIP is recorded in a METS XML file. METS is maintained by the Library of Congress, which defines it as “a standard for encoding descriptive, administrative, and structural metadata regarding objects within a digital library, expressed using the XML schema language of the World Wide Web Consortium.” In the Archivematica AIP the METS filename is composed of the name METS with a UUID file extension and an XML file extension; for example ''METS.0ad8cdab-dbbf-4863-8a4d-9a675c227216.xml''. The METS file typically consists of the following standard METS sections:
<mets:metsHdr> (METS header): basic information about the METS file;
<mets:dmdSec> (descriptive metadata section): descriptive metadata about the digital objects;
<mets:amdSec> (administrative metadata section): technical and provenance information about the digital objects;
<mets:fileSec> (file section): a list of the digital objects and an indication of their role in the AIP (original, preservation, metadata, submission documentation, license etc.);
<mets:structMap> (structural map): a physical or logical ordering of the digital objects.

The technical and provenance information in the METS amdSec is recorded as PREMIS metadata. PREMIS is also a Library of Congress standard, and is described as "the international standard for metadata to support the preservation of digital objects and ensure their long-term usability." The PREMIS entities are wrapped in the METS file as follows:

<mets:amdSec>
--<mets:techMD> (technical metadata)
----<premis:object> e.g. UUID, size, checksum, format, original name, extracted technical metadata
--<mets:digiprovMD> (digital provenance metadata)
----<premis:event> e.g. ingestion, message digest calculation, virus scan, format identification, validation, normalization, fixity check
----<premis:agent> for each PREMIS Event there are three associated Agents: the organization, the digital preservation system (e.g. Archivematica 1.x) and the logged-in user
--<mets:rightsMD> (rights metadata)
----<premis:rights> Rights pertaining to the preservation, reproduction and use of the preserved digital objects (only included if the user added rights metadata prior to or during ingest)

The fileSec and structMap use identifier attributes to link a digital object to its amdSec and (if used) dmdSec. For example, if a file entry in the fileSec has the attribute ''ADMID="amdSec_1"'' this means that the amdSec with the identifier ''amdSec_1'' contains the administrative (i.e. technical and provenance) metadata for that file. The fileSec also uses a group identifier attribute to indicate relationships between digital objects. For example, if file A in ''fileGrp "USE=original"'' and file B in ''fileGrp "USE="preservation"'' both have the group identifier attribute ''"Group-269b494d-01cb-451b-8d5e-590d57126d3d"'', then file B is a preservation version generated from file A.

'''AIP structure'''

An Archivematica AIP is packaged into a bag in accordance with the Library of Congress BagIt specification, and contains some contents not described in the sections above. This tree structure depicts a typical Archivematica AIP:

<pre>
(1) AIP-name-e3a3988d-8149-49ea-adc5-c255fb68d4f9
(2) ├── bag-info.txt
(3) ├── bagit.txt
(4) ├── manifest-sha512.txt
(5) ├── tagmanifest-md5.txt
(6) └── data
(7) ├── logs
(8) ├── objects
(9) ├── thumbnails
(10) ├── METS.0ad8cdab-dbbf-4863-8a4d-9a675c227216.xml
(11) └── README.txt
</pre>

(1) AIP root directory, with an appended UUID
(2)-(5): Standard packaging files produced in accordance with the Bagit Specification. See the specification for more information
(6): data directory - contains subdirectories logs, objects, and thumbnails, as well as the METS file
(7) logs directory - contains the log outputs of the various tools that Archivematica uses in generating the AIP (8) objects directory - contains the original digital objects as well as normalized versions
(9) thumbnails directory - contains thumbnails generated from the original object for use in the Archivematica user interface (10) the Archivematica METS file

=== Use case: Create and Use a Bag Profile ===

https://github.com/ruebot/bagit-profiles

Archivematica could define a bag profile and reference this in the AIP's it produces. This would help make AIP's more easily machine readable.

Improvements/aipreadme

2017-06-19T17:55:48Z

Evelyn: /* Sample README file text */

== User story ==

As a repository manager, I would like AIP's to be as self describing as possible, so that future users, with little or no information about Archivematica or what an AIP is, will be able to understand the structure and contents of the AIP's I produce now.

== Status ==

2017-06-01 - New Proposal

== Interest ==

If you'd like to get involved in this development, please feel free to contribute to this wiki page or start a discussion on our [https://groups.google.com/forum/#!forum/archivematica| user forum].

== Analysis: ==

Currently, Archivematica AIP's are structured as a Bag (https://tools.ietf.org/html/draft-kunze-bagit-14) and contain a METS file, which describes the contents of the AIP. Details about the Archivematica AIP structure are here: https://www.archivematica.org/en/docs/archivematica-1.6/user-manual/archival-storage/aip-structure/

METS files are machine readable, but are not human friendly formats.

Adding a human readable index or description into an AIP would improve the chances of a future user understanding the structure.

Archivematica structures AIP's in a specific way, but that is not documented within the AIP. Adding more explicit documentation about the structure would help users test that AIP's are valid, and help them to understand the structure.

There is a similar proposal outlined here: https://github.com/UTS-eResearch/datacrate

=== Use case: Add a README to each AIP ===

In the data/ directory (beside the mets file) add a README.html or README.md file. This would be intended as the first file to be opened by a human being trying to examine an AIP.

The README file would include
* some boilerplate text, describing what an AIP is
* links to the Archivematica documentation, to METS documentation, to PREMIS docs, etc.
* a link to the METS file
* optionally a link to a CATALOG.html file, that includes more detailed information about the contents of the AIP.

====Sample README file text====

This readme file describes the basic structure of an AIP generated by Archivematica.

'''Acronyms'''

AIP = Archival Information Package
METS = Metadata Encoding and Transmission Standard
OAIS = Open Archival Information System
PDI = Preservation Description Information
PREMIS = Preservation Metadata Implementation Strategies
UUID = Unique Universal Identifier

'''Introduction'''

Archivematica is an open-source suite of tools designed to ingest diverse digital content and prepare AIPs for long-term storage. Once an AIP is generated it is not dependent on Archivematica for retrieval, and can be opened using any standard file browser. The concept of an AIP is derived from the ISO 14721:2012 Reference Model for an ''Open Archival Information System (OAIS)'', which defines it as “[a]n Information Package, consisting of the Content Information and the associated Preservation Description Information (PDI), which is preserved within an OAIS.”

'''Content Information'''

In an Archivematica AIP, the Content Information consists primarily of the originally ingested digital objects and any preservation versions of the objects created to mitigate the risk of format obsolescence over time. The preservation copies typically have the same filenames as the original objects but with different file extensions and with UUIDs appended to the filename. For example, for an original file named ''BBhelemet.ai'' the preservation version may be named ''BBhelmet-e3a3988d-8149-49ea-adc5-c255fb68d4f9.pdf''.

The originally ingested digital objects and any preservation versions are located in the ''objects'' directory of the AIP. There will be nested subdirectories in the ''object'' directory if these subdirectories were included in the original transfer or added during SIP arrangement. The ''objects'' directory also includes a ''submissiondocumentation'' folder and a ''metadata'' folder. The ''submissiondocumentation'' folder contains documentation such as donor agreements and transfer forms, if these are included in the AIP, as well as a METS file that records the contents of the original transfer(s) from which the AIP was created. The ''metadata'' folder holds any metadata files included in the original transfer(s), and any OCR text files generated during processing.

'''Preservation Description Information (PDI)'''

The PDI in an Archivematica AIP is recorded in a METS XML file. METS is maintained by the Library of Congress, which defines it as “a standard for encoding descriptive, administrative, and structural metadata regarding objects within a digital library, expressed using the XML schema language of the World Wide Web Consortium.” In the Archivematica AIP the METS filename is composed of the name METS with a UUID file extension and an XML file extension; for example ''METS.0ad8cdab-dbbf-4863-8a4d-9a675c227216.xml''. The METS file typically consists of the following standard METS sections:
<mets:metsHdr> (METS header): basic information about the METS file;
<mets:dmdSec> (descriptive metadata section): descriptive metadata about the digital objects;
<mets:amdSec> (administrative metadata section): technical and provenance information about the digital objects;
<mets:fileSec> (file section): a list of the digital objects and an indication of their role in the AIP (original, preservation, metadata, submission documentation, license etc.);
<mets:structMap> (structural map): a physical or logical ordering of the digital objects.

The technical and provenance information in the METS amdSec is recorded as PREMIS metadata. PREMIS is also a Library of Congress standard, and is described as "the international standard for metadata to support the preservation of digital objects and ensure their long-term usability." The PREMIS entities are wrapped in the METS file as follows:

<mets:amdSec>
--<mets:techMD> (technical metadata)
----<premis:object> e.g. UUID, size, checksum, format, original name, extracted technical metadata
--<mets:digiprovMD> (digital provenance metadata)
----<premis:event> e.g. ingestion, message digest calculation, virus scan, format identification, validation, normalization, fixity check
----<premis:agent> for each PREMIS Event there are three associated Agents: the organization, the digital preservation system (e.g. Archivematica 1.x) and the logged-in user
--<mets:rightsMD> (rights metadata)
----<premis:rights> Rights pertaining to the preservation, reproduction and use of the preserved digital objects (only included if the user added rights metadata prior to or during ingest)

The fileSec and structMap use identifier attributes to link a digital object to its amdSec and (if used) dmdSec. For example, if a file entry in the fileSec has the attribute ''ADMID="amdSec_1"'' this means that the amdSec with the identifier ''amdSec_1'' contains the administrative (i.e. technical and provenance) metadata for that file. The fileSec also uses a group identifier attribute to indicate relationships between digital objects. For example, if file A in ''fileGrp "USE=original"'' and file B in ''fileGrp "USE="preservation"'' both have the group identifier attribute ''"Group-269b494d-01cb-451b-8d5e-590d57126d3d"'', then file B is a preservation version generated from file A.

=== Use case: Create and Use a Bag Profile ===

https://github.com/ruebot/bagit-profiles

Archivematica could define a bag profile and reference this in the AIP's it produces. This would help make AIP's more easily machine readable.

Improvements/aipreadme

2017-06-19T17:47:31Z

Evelyn: /* Sample README file text */

== User story ==

As a repository manager, I would like AIP's to be as self describing as possible, so that future users, with little or no information about Archivematica or what an AIP is, will be able to understand the structure and contents of the AIP's I produce now.

== Status ==

2017-06-01 - New Proposal

== Interest ==

If you'd like to get involved in this development, please feel free to contribute to this wiki page or start a discussion on our [https://groups.google.com/forum/#!forum/archivematica| user forum].

== Analysis: ==

Currently, Archivematica AIP's are structured as a Bag (https://tools.ietf.org/html/draft-kunze-bagit-14) and contain a METS file, which describes the contents of the AIP. Details about the Archivematica AIP structure are here: https://www.archivematica.org/en/docs/archivematica-1.6/user-manual/archival-storage/aip-structure/

METS files are machine readable, but are not human friendly formats.

Adding a human readable index or description into an AIP would improve the chances of a future user understanding the structure.

Archivematica structures AIP's in a specific way, but that is not documented within the AIP. Adding more explicit documentation about the structure would help users test that AIP's are valid, and help them to understand the structure.

There is a similar proposal outlined here: https://github.com/UTS-eResearch/datacrate

=== Use case: Add a README to each AIP ===

In the data/ directory (beside the mets file) add a README.html or README.md file. This would be intended as the first file to be opened by a human being trying to examine an AIP.

The README file would include
* some boilerplate text, describing what an AIP is
* links to the Archivematica documentation, to METS documentation, to PREMIS docs, etc.
* a link to the METS file
* optionally a link to a CATALOG.html file, that includes more detailed information about the contents of the AIP.

====Sample README file text====

This readme file describes the basic structure of an AIP generated by Archivematica.

'''Acronyms'''

AIP = Archival Information Package
METS = Metadata Encoding and Transmission Standard
OAIS = Open Archival Information System
PDI = Preservation Description Information
PREMIS = Preservation Metadata Implementation Strategies
UUID = Unique Universal Identifier

'''Introduction'''

Archivematica is an open-source suite of tools designed to ingest diverse digital content and prepare AIPs for long-term storage. Once an AIP is generated it is not dependent on Archivematica for retrieval, and can be opened using any standard file browser. The concept of an AIP is derived from the ISO 14721:2012 Reference Model for an ''Open Archival Information System (OAIS)'', which defines it as “[a]n Information Package, consisting of the Content Information and the associated Preservation Description Information (PDI), which is preserved within an OAIS.”

'''Content Information'''

In an Archivematica AIP, the Content Information consists primarily of the originally ingested digital objects and any preservation versions of the objects created to mitigate the risk of format obsolescence over time. The preservation copies typically have the same filenames as the original objects but with different file extensions and with UUIDs appended to the filename. For example, for an original file named ''BBhelemet.ai'' the preservation version may be named ''BBhelmet-e3a3988d-8149-49ea-adc5-c255fb68d4f9.pdf''.

The originally ingested digital objects and any preservation versions are located in the ''objects'' directory of the AIP. There will be nested subdirectories in the ''object'' directory if these subdirectories were included in the original transfer or added during SIP arrangement. The ''objects'' directory also includes a ''submissiondocumentation'' folder and a ''metadata'' folder. The ''submissiondocumentation'' folder contains documentation such as donor agreements and transfer forms, if included the original transfer, as well as a METS file that records the contents of the original transfer(s) from which the AIP was created. The ''metadata'' folder holds any metadata files included in the original transfer, and any OCR text files generated during processing.

'''Preservation Description Information (PDI)'''

The PDI in an Archivematica AIP is recorded in a METS XML file. METS is maintained by the Library of Congress, which defines it as “a standard for encoding descriptive, administrative, and structural metadata regarding objects within a digital library, expressed using the XML schema language of the World Wide Web Consortium.” In the Archivematica AIP the METS filename is composed of the name METS with a UUID file extension and an XML file extension; for example ''METS.0ad8cdab-dbbf-4863-8a4d-9a675c227216.xml''. The METS file typically consists of the following standard METS sections:
<metsHdr> (METS header): basic information about the METS file;
<mets:dmdSec> (descriptive metadata section): descriptive metadata about the digital objects;
<mets:amdSec> (administrative metadata section): technical and provenance information about the digital objects;
<mets:fileSec> (file section): a list of the digital objects and an indication of their role in the AIP (original, preservation, metadata, submission documentation, license etc.);
<mets:structMap> (structural map): a physical or logical ordering of the digital objects.

The technical and provenance information in the METS amdSec is recorded as PREMIS metadata. PREMIS is also a Library of Congress standard, and is described as "the international standard for metadata to support the preservation of digital objects and ensure their long-term usability." The PREMIS entities are wrapped in the METS file as follows:

<mets:amdSec>
--<mets:techMD> (technical metadata)
----<premis:object> (e.g. UUID, size, checksum, format, original name, extracted technical metadata)
--<mets:digiprovMD> (digital provenance metadata)
----<premis:event> (e.g. ingestion, message digest calculation, virus scan, format identification, validation, normalization, fixity check)
----<premis:agent> for each PREMIS Event there are three associated Agents: the organization, the digital preservation system (e.g. Archivematica 1.x) and the logged-in user
--<mets:rightsMD> (rights metadata)
----<premis:rights> Rights pertaining to the preservation, reproduction and use of the preserved digital objects (only included if the user added rights metadata prior to or during ingest)

The fileSec and structMap use identifier attributes to link a digital object to its amdSec and (if used) dmdSec. For example, if a file entry in the fileSec has the attribute ''ADMID="amdSec_1"'' this means that the amdSec with the identifier ''amdSec_1'' contains the administrative (i.e. technical and provenance) metadata for that file. The fileSec also uses a group identifier attribute to indicate relationships between digital objects. For example, if file 1 ''fileGrp "USE=original"'' and file 2 in ''fileGrp "USE="preservation'' both have the group identifier attribute ''"Group-269b494d-01cb-451b-8d5e-590d57126d3d"'', then file 2 is a preservation version generated from file 1.

=== Use case: Create and Use a Bag Profile ===

https://github.com/ruebot/bagit-profiles

Archivematica could define a bag profile and reference this in the AIP's it produces. This would help make AIP's more easily machine readable.

Improvements/aipreadme

2017-06-19T17:46:06Z

Evelyn: /* Sample README file text */

== User story ==

As a repository manager, I would like AIP's to be as self describing as possible, so that future users, with little or no information about Archivematica or what an AIP is, will be able to understand the structure and contents of the AIP's I produce now.

== Status ==

2017-06-01 - New Proposal

== Interest ==

If you'd like to get involved in this development, please feel free to contribute to this wiki page or start a discussion on our [https://groups.google.com/forum/#!forum/archivematica| user forum].

== Analysis: ==

Currently, Archivematica AIP's are structured as a Bag (https://tools.ietf.org/html/draft-kunze-bagit-14) and contain a METS file, which describes the contents of the AIP. Details about the Archivematica AIP structure are here: https://www.archivematica.org/en/docs/archivematica-1.6/user-manual/archival-storage/aip-structure/

METS files are machine readable, but are not human friendly formats.

Adding a human readable index or description into an AIP would improve the chances of a future user understanding the structure.

Archivematica structures AIP's in a specific way, but that is not documented within the AIP. Adding more explicit documentation about the structure would help users test that AIP's are valid, and help them to understand the structure.

There is a similar proposal outlined here: https://github.com/UTS-eResearch/datacrate

=== Use case: Add a README to each AIP ===

In the data/ directory (beside the mets file) add a README.html or README.md file. This would be intended as the first file to be opened by a human being trying to examine an AIP.

The README file would include
* some boilerplate text, describing what an AIP is
* links to the Archivematica documentation, to METS documentation, to PREMIS docs, etc.
* a link to the METS file
* optionally a link to a CATALOG.html file, that includes more detailed information about the contents of the AIP.

====Sample README file text====

This readme file describes the basic structure of an AIP generated by Archivematica.

'''Acronyms'''

AIP = Archival Information Package
METS = Metadata Encoding and Transmission Standard
OAIS = Open Archival Information System
PDI = Preservation Description Information
PREMIS = Preservation Metadata Implementation Strategies
UUID = Unique Universal Identifier

'''Introduction'''

Archivematica is an open-source suite of tools designed to ingest diverse digital content and prepare AIPs for long-term storage. Once an AIP is generated it is not dependent on Archivematica for retrieval, and can be opened using any standard file browser. The concept of an AIP is derived from the ISO 14721:2012 Reference Model for an ''Open Archival Information System (OAIS)'', which defines it as “[a]n Information Package, consisting of the Content Information and the associated Preservation Description Information (PDI), which is preserved within an OAIS.”

'''Content Information'''

In an Archivematica AIP, the Content Information consists primarily of the originally ingested digital objects and any preservation versions of the objects created to mitigate the risk of format obsolescence over time. The preservation copies typically have the same filenames as the original objects but with different file extensions and with UUIDs appended to the filename. For example, for an original file named ''BBhelemet.ai'' the preservation version may be named ''BBhelmet-e3a3988d-8149-49ea-adc5-c255fb68d4f9.pdf''.

The originally ingested digital objects and any preservation versions are located in the ''objects'' directory of the AIP. There will be nested subdirectories in the ''object'' directory if these subdirectories were included in the original transfer or added during SIP arrangement. The ''objects'' directory also includes a ''submissiondocumentation'' folder and a ''metadata'' folder. The ''submissiondocumentation'' folder contains documentation such as donor agreements and transfer forms, if included the original transfer, as well as a METS file that records the contents of the original transfer(s) from which the AIP was created. The ''metadata'' folder holds any metadata files included in the original transfer, and any OCR text files generated during processing.

'''Preservation Description Information (PDI)'''

The PDI in an Archivematica AIP is recorded in a METS XML file. METS is maintained by the Library of Congress, which defines it as “a standard for encoding descriptive, administrative, and structural metadata regarding objects within a digital library, expressed using the XML schema language of the World Wide Web Consortium.” In the Archivematica AIP the METS filename is composed of the name METS with a UUID file extension and an XML file extension; for example ''METS.0ad8cdab-dbbf-4863-8a4d-9a675c227216.xml''. The METS file typically consists of the following standard METS sections:
<metsHdr> (METS header): basic information about the METS file;
<mets:dmdSec> (descriptive metadata section): descriptive metadata about the digital objects;
<mets:amdSec> (administrative metadata section): technical and provenance information about the digital objects;
<mets:fileSec> (file section): a list of the digital objects and an indication of their role in the AIP (original, preservation, metadata, submission documentation, license etc.);
<mets:structMap> (structural map): a physical or logical ordering of the digital objects.

The technical and provenance information in the METS amdSec is recorded as PREMIS metadata. PREMIS is also a Library of Congress standard, and is described as "the international standard for metadata to support the preservation of digital objects and ensure their long-term usability." The PREMIS entities are wrapped in the METS file as follows:

<mets:amdSec>
 <mets:techMD> (technical metadata)
 <premis:object> (e.g. UUID, size, checksum, format, original name, extracted technical metadata)
 <mets:digiprovMD> (digital provenance metadata)
 <premis:event> (e.g. ingestion, message digest calculation, virus scan, format identification, validation, normalization, fixity check)
 <premis:agent> for each PREMIS Event there are three associated Agents: the organization, the digital preservation system (e.g. Archivematica 1.x) and the logged-in user
 <mets:rightsMD> (rights metadata)
 <premis:rights> Rights pertaining to the preservation, reproduction and use of the preserved digital objects (only included if the user added rights metadata prior to or during ingest)

The fileSec and structMap use identifier attributes to link a digital object to its amdSec and (if used) dmdSec. For example, if a file entry in the fileSec has the attribute ''ADMID="amdSec_1"'' this means that the amdSec with the identifier ''amdSec_1'' contains the administrative (i.e. technical and provenance) metadata for that file. The fileSec also uses a group identifier attribute to indicate relationships between digital objects. For example, if file 1 ''fileGrp "USE=original"'' and file 2 in ''fileGrp "USE="preservation'' both have the group identifier attribute ''"Group-269b494d-01cb-451b-8d5e-590d57126d3d"'', then file 2 is a preservation version generated from file 1.

=== Use case: Create and Use a Bag Profile ===

https://github.com/ruebot/bagit-profiles

Archivematica could define a bag profile and reference this in the AIP's it produces. This would help make AIP's more easily machine readable.

Improvements/aipreadme

2017-06-19T17:44:03Z

Evelyn: /* Sample README file text */

== User story ==

As a repository manager, I would like AIP's to be as self describing as possible, so that future users, with little or no information about Archivematica or what an AIP is, will be able to understand the structure and contents of the AIP's I produce now.

== Status ==

2017-06-01 - New Proposal

== Interest ==

If you'd like to get involved in this development, please feel free to contribute to this wiki page or start a discussion on our [https://groups.google.com/forum/#!forum/archivematica| user forum].

== Analysis: ==

Currently, Archivematica AIP's are structured as a Bag (https://tools.ietf.org/html/draft-kunze-bagit-14) and contain a METS file, which describes the contents of the AIP. Details about the Archivematica AIP structure are here: https://www.archivematica.org/en/docs/archivematica-1.6/user-manual/archival-storage/aip-structure/

METS files are machine readable, but are not human friendly formats.

Adding a human readable index or description into an AIP would improve the chances of a future user understanding the structure.

Archivematica structures AIP's in a specific way, but that is not documented within the AIP. Adding more explicit documentation about the structure would help users test that AIP's are valid, and help them to understand the structure.

There is a similar proposal outlined here: https://github.com/UTS-eResearch/datacrate

=== Use case: Add a README to each AIP ===

In the data/ directory (beside the mets file) add a README.html or README.md file. This would be intended as the first file to be opened by a human being trying to examine an AIP.

The README file would include
* some boilerplate text, describing what an AIP is
* links to the Archivematica documentation, to METS documentation, to PREMIS docs, etc.
* a link to the METS file
* optionally a link to a CATALOG.html file, that includes more detailed information about the contents of the AIP.

====Sample README file text====

This readme file describes the basic structure of an AIP generated by Archivematica.

'''Acronyms'''

AIP = Archival Information Package
METS = Metadata Encoding and Transmission Standard
OAIS = Open Archival Information System
PDI = Preservation Description Information
PREMIS = Preservation Metadata Implementation Strategies
UUID = Unique Universal Identifier

'''Introduction'''

Archivematica is an open-source suite of tools designed to ingest diverse digital content and prepare AIPs for long-term storage. Once an AIP is generated it is not dependent on Archivematica for retrieval, and can be opened using any standard file browser. The concept of an AIP is derived from the ISO 14721:2012 Reference Model for an ''Open Archival Information System (OAIS)'', which defines it as “[a]n Information Package, consisting of the Content Information and the associated Preservation Description Information (PDI), which is preserved within an OAIS.”

'''Content Information'''

In an Archivematica AIP, the Content Information consists primarily of the originally ingested digital objects and any preservation versions of the objects created to mitigate the risk of format obsolescence over time. The preservation copies typically have the same filenames as the original objects but with different file extensions and with UUIDs appended to the filename. For example, for an original file named ''BBhelemet.ai'' the preservation version may be named ''BBhelmet-e3a3988d-8149-49ea-adc5-c255fb68d4f9.pdf''.

The originally ingested digital objects and any preservation versions are located in the ''objects'' directory of the AIP. There will be nested subdirectories in the ''object'' directory if these subdirectories were included in the original transfer or added during SIP arrangement. The ''objects'' directory also includes a ''submissiondocumentation'' folder and a ''metadata'' folder. The ''submissiondocumentation'' folder contains documentation such as donor agreements and transfer forms, if included the original transfer, as well as a METS file that records the contents of the original transfer(s) from which the AIP was created. The ''metadata'' folder holds any metadata files included in the original transfer, and any OCR text files generated during processing.

'''Preservation Description Information (PDI)'''

The PDI in an Archivematica AIP is recorded in a METS XML file. METS is maintained by the Library of Congress, which defines it as “a standard for encoding descriptive, administrative, and structural metadata regarding objects within a digital library, expressed using the XML schema language of the World Wide Web Consortium.” In the Archivematica AIP the METS filename is composed of the name METS with a UUID file extension and an XML file extension; for example ''METS.0ad8cdab-dbbf-4863-8a4d-9a675c227216.xml''. The METS file typically consists of the following standard METS sections:
<metsHdr> (METS header): basic information about the METS file;
<mets:dmdSec> (descriptive metadata section): descriptive metadata about the digital objects;
<mets:amdSec> (administrative metadata section): technical and provenance information about the digital objects;
<mets:fileSec> (file section): a list of the digital objects and an indication of their role in the AIP (original, preservation, metadata, submission documentation, license etc.);
<mets:structMap> (structural map): a physical or logical ordering of the digital objects.

The technical and provenance information in the METS amdSec is recorded as PREMIS metadata. PREMIS is also a Library of Congress standard, and is described as "the international standard for metadata to support the preservation of digital objects and ensure their long-term usability." The PREMIS entities are wrapped in the METS file as follows:

<mets:amdSec>
 <mets:techMD> (technical metadata)
 <premis:object> (e.g. UUID, size, checksum, format, original name, extracted technical metadata)
 <mets:digiprovMD> (digital provenance metadata)
 <premis:event> (e.g. ingestion, message digest calculation, virus scan, format identification, validation, normalization, fixity check)
 <premis:agent> for each PREMIS Event there are three associated Agents: the organization, the digital preservation system (e.g. Archivematica 1.x) and the logged-in user
 <mets:rightsMD> (rights metadata)
 <premis:rights> Rights pertaining to the preservation, reproduction and use of the preserved digital objects (only included if the user added rights metadata prior to or during ingest)

The fileSec and structMap use identifier attributes to link a digital object to its amdSec and (if used) dmdSec. For example, if a file entry in the fileSec has the attribute ''ADMID="amdSec_1"'' this means that the amdSec with the identifier ''amdSec_1'' contains the administrative (i.e. technical and provenance) metadata for that file. The fileSec also uses a group identifier attribute to indicated relationships between digital objects. For example, if a file entry in ''fileGrp "USE=original"'' and a file entry in ''fileGrp "USE="preservation'' both have the group identifier attribute ''"Group-269b494d-01cb-451b-8d5e-590d57126d3d"'', then the second file is a preservation version generated from the first file.

=== Use case: Create and Use a Bag Profile ===

https://github.com/ruebot/bagit-profiles

Archivematica could define a bag profile and reference this in the AIP's it produces. This would help make AIP's more easily machine readable.

Improvements/aipreadme

2017-06-19T17:39:42Z

Evelyn: /* Sample README file text */

== User story ==

As a repository manager, I would like AIP's to be as self describing as possible, so that future users, with little or no information about Archivematica or what an AIP is, will be able to understand the structure and contents of the AIP's I produce now.

== Status ==

2017-06-01 - New Proposal

== Interest ==

If you'd like to get involved in this development, please feel free to contribute to this wiki page or start a discussion on our [https://groups.google.com/forum/#!forum/archivematica| user forum].

== Analysis: ==

Currently, Archivematica AIP's are structured as a Bag (https://tools.ietf.org/html/draft-kunze-bagit-14) and contain a METS file, which describes the contents of the AIP. Details about the Archivematica AIP structure are here: https://www.archivematica.org/en/docs/archivematica-1.6/user-manual/archival-storage/aip-structure/

METS files are machine readable, but are not human friendly formats.

Adding a human readable index or description into an AIP would improve the chances of a future user understanding the structure.

Archivematica structures AIP's in a specific way, but that is not documented within the AIP. Adding more explicit documentation about the structure would help users test that AIP's are valid, and help them to understand the structure.

There is a similar proposal outlined here: https://github.com/UTS-eResearch/datacrate

=== Use case: Add a README to each AIP ===

In the data/ directory (beside the mets file) add a README.html or README.md file. This would be intended as the first file to be opened by a human being trying to examine an AIP.

The README file would include
* some boilerplate text, describing what an AIP is
* links to the Archivematica documentation, to METS documentation, to PREMIS docs, etc.
* a link to the METS file
* optionally a link to a CATALOG.html file, that includes more detailed information about the contents of the AIP.

====Sample README file text====

This readme file describes the basic structure of an AIP generated by Archivematica.

'''Acronyms'''

AIP = Archival Information Package
METS = Metadata Encoding and Transmission Standard
OAIS = Open Archival Information System
PDI = Preservation Description Information
PREMIS = Preservation Metadata Implementation Strategies
UUID = Unique Universal Identifier

'''Introduction'''

Archivematica is an open-source suite of tools designed to ingest diverse digital content and prepare AIPs for long-term storage. Once an AIP is generated it is not dependent on Archivematica for retrieval, and can be opened using any standard file browser. The concept of an AIP is derived from the ISO 14721:2012 Reference Model for an ''Open Archival Information System (OAIS)'', which defines it as “[a]n Information Package, consisting of the Content Information and the associated Preservation Description Information (PDI), which is preserved within an OAIS.”

'''Content Information'''

In an Archivematica AIP, the Content Information consists primarily of the originally ingested digital objects and any preservation versions of the objects created to mitigate the risk of format obsolescence over time. The preservation copies typically have the same filenames as the original objects but with different file extensions and with UUIDs appended to the filename. For example, for an original file named ''BBhelemet.ai'' the preservation version may be named ''BBhelmet-e3a3988d-8149-49ea-adc5-c255fb68d4f9.pdf''.

The originally ingested digital objects and any preservation versions are located in the ''objects'' directory of the AIP. There will be nested subdirectories in the ''object'' directory if these subdirectories were included in the original transfer or added during SIP arrangement. The ''objects'' directory also includes a ''submissiondocumentation'' folder and a ''metadata'' folder. The ''submissiondocumentation'' folder contains documentation such as donor agreements and transfer forms, if included the original transfer, as well as a METS file that records the contents of the original transfer(s) from which the AIP was created. The ''metadata'' folder holds any metadata files included in the original transfer, and any OCR text files generated during processing.

'''Preservation Description Information (PDI)'''

The PDI in an Archivematica AIP is recorded in a METS XML file. METS is maintained by the Library of Congress, which defines it as “a standard for encoding descriptive, administrative, and structural metadata regarding objects within a digital library, expressed using the XML schema language of the World Wide Web Consortium.” In the Archivematica AIP the METS filename is composed of the name METS with a UUID file extension and an XML file extension; for example ''METS.0ad8cdab-dbbf-4863-8a4d-9a675c227216.xml''. The METS file typically consists of the following standard METS sections:
<metsHdr> (METS header): basic information about the METS file;
<mets:dmdSec> (descriptive metadata section): descriptive metadata about the digital objects;
<mets:amdSec> (administrative metadata section): technical and provenance information about the digital objects;
<mets:fileSec> (file section): a list of the digital objects and an indication of their role in the AIP (original, preservation, metadata, submission documentation, license etc.);
<mets:structMap> (structural map): a physical or logical ordering of the digital objects.

The technical and provenance information in the METS amdSec is recorded as PREMIS metadata. PREMIS is also a Library of Congress standard, and is described as "the international standard for metadata to support the preservation of digital objects and ensure their long-term usability." The PREMIS entities are wrapped in the METS file as follows:

<mets:amdSec>
 <mets:techMD> (technical metadata)
 <premis:object> (e.g. UUID, size, checksum, format, original name, extracted technical metadata)
 <mets:digiprovMD> (digital provenance metadata)
 <premis:event> (e.g. ingestion, message digest calculation, virus scan, format identification, validation, normalization, fixity check)
 <premis:agent> for each PREMIS Event there are three associated Agents: the organization, the digital preservation system (e.g. Archivematica 1.x) and the logged-in user
 <mets:rightsMD> (rights metadata)
 <premis:rights> Rights pertaining to the preservation, reproduction and use of the preserved digital objects (only included if the user added rights metadata prior to or during ingest)

The fileSec and structMap use identifier attributes to link a digital object to its amdSec and (if used) dmdSec. For example, if a file entry in the fileSec has the attribute ''ADMID="amdSec_1"'' this means that the amdSec with the identifier ''amdSec_1'' contains the administrative (i.e. technical and provenance) metadata for that file.

=== Use case: Create and Use a Bag Profile ===

https://github.com/ruebot/bagit-profiles

Archivematica could define a bag profile and reference this in the AIP's it produces. This would help make AIP's more easily machine readable.

Improvements/aipreadme

2017-06-19T17:35:36Z

Evelyn: /* Sample README file text */

== User story ==

As a repository manager, I would like AIP's to be as self describing as possible, so that future users, with little or no information about Archivematica or what an AIP is, will be able to understand the structure and contents of the AIP's I produce now.

== Status ==

2017-06-01 - New Proposal

== Interest ==

If you'd like to get involved in this development, please feel free to contribute to this wiki page or start a discussion on our [https://groups.google.com/forum/#!forum/archivematica| user forum].

== Analysis: ==

Currently, Archivematica AIP's are structured as a Bag (https://tools.ietf.org/html/draft-kunze-bagit-14) and contain a METS file, which describes the contents of the AIP. Details about the Archivematica AIP structure are here: https://www.archivematica.org/en/docs/archivematica-1.6/user-manual/archival-storage/aip-structure/

METS files are machine readable, but are not human friendly formats.

Adding a human readable index or description into an AIP would improve the chances of a future user understanding the structure.

Archivematica structures AIP's in a specific way, but that is not documented within the AIP. Adding more explicit documentation about the structure would help users test that AIP's are valid, and help them to understand the structure.

There is a similar proposal outlined here: https://github.com/UTS-eResearch/datacrate

=== Use case: Add a README to each AIP ===

In the data/ directory (beside the mets file) add a README.html or README.md file. This would be intended as the first file to be opened by a human being trying to examine an AIP.

The README file would include
* some boilerplate text, describing what an AIP is
* links to the Archivematica documentation, to METS documentation, to PREMIS docs, etc.
* a link to the METS file
* optionally a link to a CATALOG.html file, that includes more detailed information about the contents of the AIP.

====Sample README file text====

This readme file describes the basic structure of an AIP generated by Archivematica.

'''Acronyms'''

AIP = Archival Information Package
METS = Metadata Encoding and Transmission Standard
OAIS = Open Archival Information System
PDI = Preservation Description Information
PREMIS = Preservation Metadata Implementation Strategies
UUID = Unique Universal Identifier

'''Introduction'''

Archivematica is an open-source suite of tools designed to ingest diverse digital content and prepare AIPs for long-term storage. Once an AIP is generated it is not dependent on Archivematica for retrieval, and can be opened using any standard file browser. The concept of an AIP is derived from the ISO 14721:2012 Reference Model for an ''Open Archival Information System (OAIS)'', which defines it as “[a]n Information Package, consisting of the Content Information and the associated Preservation Description Information (PDI), which is preserved within an OAIS.”

'''Content Information'''

In an Archivematica AIP, the Content Information consists primarily of the originally ingested digital objects and any preservation versions of the objects created to mitigate the risk of format obsolescence over time. The preservation copies typically have the same filenames as the original objects but with different file extensions and with UUIDs appended to the filename. For example, for an original file named ''BBhelemet.ai'' the preservation version may be named ''BBhelmet-e3a3988d-8149-49ea-adc5-c255fb68d4f9.pdf''.

The originally ingested digital objects and any preservation versions are located in the ''objects'' directory of the AIP. There will be nested subdirectories in the ''object'' directory if these subdirectories were included in the original transfer or added during SIP arrangement. The ''objects'' directory also includes a ''submissiondocumentation'' folder and a ''metadata'' folder. The ''submissiondocumentation'' folder contains documentation such as donor agreements and transfer forms, if included the original transfer, as well as a METS file that records the contents of the original transfer(s) from which the AIP was created. The ''metadata'' folder holds any metadata files included in the original transfer, and any OCR text files generated during processing.

'''Preservation Description Information (PDI)'''

The PDI in an Archivematica AIP is recorded in a METS XML file. METS is maintained by the Library of Congress, which defines it as “a standard for encoding descriptive, administrative, and structural metadata regarding objects within a digital library, expressed using the XML schema language of the World Wide Web Consortium.” In the Archivematica AIP the METS filename is composed of the name METS with a UUID file extension and an XML file extension; for example ''METS.0ad8cdab-dbbf-4863-8a4d-9a675c227216.xml''. The METS file typically consists of the following standard METS sections:
<metsHdr> (METS header): basic information about the METS file;
<mets:dmdSec> (descriptive metadata section): descriptive metadata about the digital objects;
<mets:amdSec> (administrative metadata section): technical and provenance information about the digital objects;
<mets:fileSec> (file section): a list of the digital objects and an indication of their role in the AIP (original, preservation, metadata, submission documentation, license etc.);
<mets:structMap> (structural map): a physical or logical ordering of the digital objects.

The technical and provenance information in the METS amdSec is recorded as PREMIS metadata. PREMIS is also a Library of Congress standard, and is described as "the international standard for metadata to support the preservation of digital objects and ensure their long-term usability." The PREMIS entities are wrapped in the METS file as follows:

<mets:amdSec>
 <mets:techMD> (technical metadata)
 <premis:object> (e.g. UUID, size, checksum, format, original name, extracted technical metadata)
 <mets:digiprovMD> (digital provenance metadata)
 <premis:event> (e.g. ingestion, message digest calculation, virus scan, format identification, validation, normalization, fixity check)
 <premis:agent> for each PREMIS Event there are three associated Agents: the organization, the digital preservation system (e.g. Archivematica 1.x) and the logged-in user
 <mets:rightsMD> (rights metadata)
 <premis:rights> Rights pertaining to the preservation, reproduction and use of the preserved digital objects (only included if the user added rights metadata prior to or during ingest)

The fileSec and structMap use identifiers to link a digital object to its amdSec and (if used) dmdSec. For example, if a file in the fileSec has the attribute ''ADMID="amdSec_1"'' this means that the amdSec with the identifier amdSec_1 contains the administrative (i.e. technical and provenance) metadata for that file.

=== Use case: Create and Use a Bag Profile ===

https://github.com/ruebot/bagit-profiles

Archivematica could define a bag profile and reference this in the AIP's it produces. This would help make AIP's more easily machine readable.

Improvements/aipreadme

2017-06-19T17:29:26Z

Evelyn: /* Sample README file text */

== User story ==

As a repository manager, I would like AIP's to be as self describing as possible, so that future users, with little or no information about Archivematica or what an AIP is, will be able to understand the structure and contents of the AIP's I produce now.

== Status ==

2017-06-01 - New Proposal

== Interest ==

If you'd like to get involved in this development, please feel free to contribute to this wiki page or start a discussion on our [https://groups.google.com/forum/#!forum/archivematica| user forum].

== Analysis: ==

Currently, Archivematica AIP's are structured as a Bag (https://tools.ietf.org/html/draft-kunze-bagit-14) and contain a METS file, which describes the contents of the AIP. Details about the Archivematica AIP structure are here: https://www.archivematica.org/en/docs/archivematica-1.6/user-manual/archival-storage/aip-structure/

METS files are machine readable, but are not human friendly formats.

Adding a human readable index or description into an AIP would improve the chances of a future user understanding the structure.

Archivematica structures AIP's in a specific way, but that is not documented within the AIP. Adding more explicit documentation about the structure would help users test that AIP's are valid, and help them to understand the structure.

There is a similar proposal outlined here: https://github.com/UTS-eResearch/datacrate

=== Use case: Add a README to each AIP ===

In the data/ directory (beside the mets file) add a README.html or README.md file. This would be intended as the first file to be opened by a human being trying to examine an AIP.

The README file would include
* some boilerplate text, describing what an AIP is
* links to the Archivematica documentation, to METS documentation, to PREMIS docs, etc.
* a link to the METS file
* optionally a link to a CATALOG.html file, that includes more detailed information about the contents of the AIP.

====Sample README file text====

This readme file describes the basic structure of an AIP generated by Archivematica.

'''Acronyms'''

AIP = Archival Information Package
METS = Metadata Encoding and Transmission Standard
OAIS = Open Archival Information System
PDI = Preservation Description Information
PREMIS = Preservation Metadata Implementation Strategies
UUID = Unique Universal Identifier

'''Introduction'''

Archivematica is an open-source suite of tools designed to ingest diverse digital content and prepare AIPs for long-term storage. Once an AIP is generated it is not dependent on Archivematica for retrieval, and can be opened using any standard file browser. The concept of an AIP is derived from the ISO 14721:2012 Reference Model for an ''Open Archival Information System (OAIS)'', which defines it as “[a]n Information Package, consisting of the Content Information and the associated Preservation Description Information (PDI), which is preserved within an OAIS.”

'''Content Information'''

In an Archivematica AIP, the Content Information consists primarily of the originally ingested digital objects and any preservation versions of the objects created to mitigate the risk of format obsolescence over time. The preservation copies typically have the same filenames as the original objects but with different file extensions and with UUIDs appended to the filename. For example, for an original file named ''BBhelemet.ai'' the preservation version may be named ''BBhelmet-e3a3988d-8149-49ea-adc5-c255fb68d4f9.pdf''.

The originally ingested digital objects and any preservation versions are located in the ''objects'' directory of the AIP. There will be nested subdirectories in the ''object'' directory if these subdirectories were included in the original transfer or added during SIP arrangement. The ''objects'' directory also includes a ''submissiondocumentation'' folder and a ''metadata'' folder. The ''submissiondocumentation'' folder contains documentation such as donor agreements and transfer forms, if included the original transfer, as well as a METS file that records the contents of the original transfer(s) from which the AIP was created. The ''metadata'' folder holds any metadata files included in the original transfer, and any OCR text files generated during processing.

'''Preservation Description Information (PDI)'''

The PDI in an Archivematica AIP is recorded in a METS XML file. METS is maintained by the Library of Congress, which defines it as “a standard for encoding descriptive, administrative, and structural metadata regarding objects within a digital library, expressed using the XML schema language of the World Wide Web Consortium.” In the Archivematica AIP the METS filename is composed of the name METS with a UUID file extension and an XML file extension; for example ''METS.0ad8cdab-dbbf-4863-8a4d-9a675c227216.xml''. The METS file typically consists of the following standard METS sections:
<metsHdr> (METS header): basic information about the METS file;
<mets:dmdSec> (descriptive metadata section): descriptive metadata about the digital objects;
<mets:amdSec> (administrative metadata section): technical and provenance information about the digital objects;
<mets:fileSec> (file section): a list of the digital objects and an indication of their role in the AIP (original, preservation, metadata, submission documentation, license etc.);
<mets:structMap> (structural map): a physical or logical ordering of the digital objects.

The technical and provenance information in the METS amdSec is recorded as PREMIS metadata. PREMIS is also a Library of Congress standard, and is described as "the international standard for metadata to support the preservation of digital objects and ensure their long-term usability." The PREMIS entities are wrapped in the METS file as follows:

<mets:amdSec>
 <mets:techMD> (technical metadata)
 <premis:object> (e.g. UUID, size, checksum, format, original name, extracted technical metadata)
 <mets:digiprovMD> (digital provenance metadata)
 <premis:event> (e.g. ingestion, message digest calculation, virus scan, format identification, validation, normalization, fixity check)
 <premis:agent> for each PREMIS Event there are three associated Agents: the organization, the digital preservation system (e.g. Archivematica 1.x) and the logged-in user
 <mets:rightsMD> (rights metadata)
 <premis:rights> Rights pertaining to the preservation, reproduction and use of the preserved digital objects (only included if the user added rights metadata prior to or during ingest)

=== Use case: Create and Use a Bag Profile ===

https://github.com/ruebot/bagit-profiles

Archivematica could define a bag profile and reference this in the AIP's it produces. This would help make AIP's more easily machine readable.

Improvements/aipreadme

2017-06-19T17:28:06Z

Evelyn: /* Sample README file text */

== User story ==

As a repository manager, I would like AIP's to be as self describing as possible, so that future users, with little or no information about Archivematica or what an AIP is, will be able to understand the structure and contents of the AIP's I produce now.

== Status ==

2017-06-01 - New Proposal

== Interest ==

If you'd like to get involved in this development, please feel free to contribute to this wiki page or start a discussion on our [https://groups.google.com/forum/#!forum/archivematica| user forum].

== Analysis: ==

Currently, Archivematica AIP's are structured as a Bag (https://tools.ietf.org/html/draft-kunze-bagit-14) and contain a METS file, which describes the contents of the AIP. Details about the Archivematica AIP structure are here: https://www.archivematica.org/en/docs/archivematica-1.6/user-manual/archival-storage/aip-structure/

METS files are machine readable, but are not human friendly formats.

Adding a human readable index or description into an AIP would improve the chances of a future user understanding the structure.

Archivematica structures AIP's in a specific way, but that is not documented within the AIP. Adding more explicit documentation about the structure would help users test that AIP's are valid, and help them to understand the structure.

There is a similar proposal outlined here: https://github.com/UTS-eResearch/datacrate

=== Use case: Add a README to each AIP ===

In the data/ directory (beside the mets file) add a README.html or README.md file. This would be intended as the first file to be opened by a human being trying to examine an AIP.

The README file would include
* some boilerplate text, describing what an AIP is
* links to the Archivematica documentation, to METS documentation, to PREMIS docs, etc.
* a link to the METS file
* optionally a link to a CATALOG.html file, that includes more detailed information about the contents of the AIP.

====Sample README file text====

This readme file describes the basic structure of an AIP generated by Archivematica.

'''Acronyms'''

AIP = Archival Information Package
METS = Metadata Encoding and Transmission Standard
OAIS = Open Archival Information System
PDI = Preservation Description Information
PREMIS = Preservation Metadata Implementation Strategies
UUID = Unique Universal Identifier

'''Introduction'''

Archivematica is an open-source suite of tools designed to ingest diverse digital content and prepare AIPs for long-term storage. Once an AIP is generated it is not dependent on Archivematica for retrieval, and can be opened using any standard file browser. The concept of an AIP is derived from the ISO 14721:2012 Reference Model for an ''Open Archival Information System (OAIS)'', which defines it as “[a]n Information Package, consisting of the Content Information and the associated Preservation Description Information (PDI), which is preserved within an OAIS.”

'''Content Information'''

In an Archivematica AIP, the Content Information consists primarily of the originally ingested digital objects and any preservation versions of the objects created to mitigate the risk of format obsolescence over time. The preservation copies typically have the same filenames as the original objects but with different file extensions and with UUIDs appended to the filename. For example, for an original file named ''BBhelemet.ai'' the preservation version may be named ''BBhelmet-e3a3988d-8149-49ea-adc5-c255fb68d4f9.pdf''.

The originally ingested digital objects and any preservation versions are located in the ''objects'' directory of the AIP. There will be nested subdirectories in the ''object'' directory if these subdirectories were included in the original transfer or added during SIP arrangement. The ''objects'' directory also includes a ''submissiondocumentation'' folder and a ''metadata'' folder. The ''submissiondocumentation'' folder contains documentation such as donor agreements and transfer forms, if included the original transfer, as well as a METS file that records the contents of the original transfer(s) from which the AIP was created. The ''metadata'' folder holds any metadata files included in the original transfer, and any OCR text files generated during processing.

'''Preservation Description Information (PDI)'''

The PDI in an Archivematica AIP is recorded in a METS XML file. METS is maintained by the Library of Congress, which defines it as “a standard for encoding descriptive, administrative, and structural metadata regarding objects within a digital library, expressed using the XML schema language of the World Wide Web Consortium.” In the Archivematica AIP the METS filename is composed of the name METS with a UUID file extension and an XML file extension; for example ''METS.0ad8cdab-dbbf-4863-8a4d-9a675c227216.xml''. The METS file typically consists of the following standard METS sections:
<metsHdr> (METS header): basic information about the METS file;
<mets:dmdSec> (descriptive metadata section): descriptive metadata about the digital objects;
<mets:amdSec> (administrative metadata section): technical and provenance information about the digital objects;
<mets:fileSec> (file section): a list of the digital objects and an indication of their role in the AIP (original, preservation, metadata, submission documentation, license etc.);
<mets:structMap> (structural map): a physical or logical ordering of the digital objects.

The technical and provenance information in the METS amdSec is recorded as PREMIS metadata. PREMIS is also a Library of Congress standard, and is described as "the international standard for metadata to support the preservation of digital objects and ensure their long-term usability." The PREMIS entities are wrapped in the METS file as follows:

<mets:amdSec>
<mets:techMD> (technical metadata)
<premis:object> (e.g. UUID, size, checksum, format, original name, extracted technical metadata)
<mets:digiprovMD> (digital provenance metadata)
<premis:event> (e.g. ingestion, message digest calculation, virus scan, format identification, validation, normalization, fixity check)
<premis:agent> for each PREMIS Event there are three associated Agents: the organization, the digital preservation system (e.g. Archivematica 1.x) and the logged-in user
<mets:rightsMD> (rights metadata)
<premis:rights> Rights pertaining to the preservation, reproduction and use of the preserved digital objects (only included if the user added rights metadata prior to or during ingest)

=== Use case: Create and Use a Bag Profile ===

https://github.com/ruebot/bagit-profiles

Archivematica could define a bag profile and reference this in the AIP's it produces. This would help make AIP's more easily machine readable.

Improvements/aipreadme

2017-06-19T17:27:03Z

Evelyn: /* Sample README file text */

== User story ==

As a repository manager, I would like AIP's to be as self describing as possible, so that future users, with little or no information about Archivematica or what an AIP is, will be able to understand the structure and contents of the AIP's I produce now.

== Status ==

2017-06-01 - New Proposal

== Interest ==

If you'd like to get involved in this development, please feel free to contribute to this wiki page or start a discussion on our [https://groups.google.com/forum/#!forum/archivematica| user forum].

== Analysis: ==

Currently, Archivematica AIP's are structured as a Bag (https://tools.ietf.org/html/draft-kunze-bagit-14) and contain a METS file, which describes the contents of the AIP. Details about the Archivematica AIP structure are here: https://www.archivematica.org/en/docs/archivematica-1.6/user-manual/archival-storage/aip-structure/

METS files are machine readable, but are not human friendly formats.

Adding a human readable index or description into an AIP would improve the chances of a future user understanding the structure.

Archivematica structures AIP's in a specific way, but that is not documented within the AIP. Adding more explicit documentation about the structure would help users test that AIP's are valid, and help them to understand the structure.

There is a similar proposal outlined here: https://github.com/UTS-eResearch/datacrate

=== Use case: Add a README to each AIP ===

In the data/ directory (beside the mets file) add a README.html or README.md file. This would be intended as the first file to be opened by a human being trying to examine an AIP.

The README file would include
* some boilerplate text, describing what an AIP is
* links to the Archivematica documentation, to METS documentation, to PREMIS docs, etc.
* a link to the METS file
* optionally a link to a CATALOG.html file, that includes more detailed information about the contents of the AIP.

====Sample README file text====

This readme file describes the basic structure of an AIP generated by Archivematica.

Acronyms

AIP = Archival Information Package
METS = Metadata Encoding and Transmission Standard
OAIS = Open Archival Information System
PDI = Preservation Description Information
PREMIS = Preservation Metadata Implementation Strategies
UUID = Unique Universal Identifier

What is Archivematica?

Archivematica is an open-source suite of tools designed to ingest diverse digital content and prepare AIPs for long-term storage. Once an AIP is generated it is not dependent on Archivematica for retrieval, and can be opened using any standard file browser. The concept of an AIP is derived from the ISO 14721:2012 Reference Model for an ''Open Archival Information System (OAIS)'', which defines it as “[a]n Information Package, consisting of the Content Information and the associated Preservation Description Information (PDI), which is preserved within an OAIS.”

Content Information

In an Archivematica AIP, the Content Information consists primarily of the originally ingested digital objects and any preservation versions of the objects created to mitigate the risk of format obsolescence over time. The preservation copies typically have the same filenames as the original objects but with different file extensions and with UUIDs appended to the filename. For example, for an original file named ''BBhelemet.ai'' the preservation version may be named ''BBhelmet-e3a3988d-8149-49ea-adc5-c255fb68d4f9.pdf''.

The originally ingested digital objects and any preservation versions are located in the ''objects'' directory of the AIP. There will be nested subdirectories in the ''object'' directory if these subdirectories were included in the original transfer or added during SIP arrangement. The ''objects'' directory also includes a ''submissiondocumentation'' folder and a ''metadata'' folder. The ''submissiondocumentation'' folder contains documentation such as donor agreements and transfer forms, if included the original transfer, as well as a METS file that records the contents of the original transfer(s) from which the AIP was created. The ''metadata'' folder holds any metadata files included in the original transfer, and any OCR text files generated during processing.

Preservation Description Information (PDI)

The PDI in an Archivematica AIP is recorded in a METS XML file. METS is maintained by the Library of Congress, which defines it as “a standard for encoding descriptive, administrative, and structural metadata regarding objects within a digital library, expressed using the XML schema language of the World Wide Web Consortium.” In the Archivematica AIP the METS filename is composed of the name METS with a UUID file extension and an XML file extension; for example ''METS.0ad8cdab-dbbf-4863-8a4d-9a675c227216.xml''. The METS file typically consists of the following standard METS sections:
<metsHdr> (METS header): basic information about the METS file;
<mets:dmdSec> (descriptive metadata section): descriptive metadata about the digital objects;
<mets:amdSec> (administrative metadata section): technical and provenance information about the digital objects;
<mets:fileSec> (file section): a list of the digital objects and an indication of their role in the AIP (original, preservation, metadata, submission documentation, license etc.);
<mets:structMap> (structural map): a physical or logical ordering of the digital objects.

The technical and provenance information in the METS amdSec is recorded as PREMIS metadata. PREMIS is also a Library of Congress standard, and is described as "the international standard for metadata to support the preservation of digital objects and ensure their long-term usability." The PREMIS entities are wrapped in the METS file as follows:

<mets:amdSec>
<mets:techMD> (technical metadata)
<premis:object> (e.g. UUID, size, checksum, format, original name, extracted technical metadata)
<mets:digiprovMD> (digital provenance metadata)
<premis:event> (e.g. ingestion, message digest calculation, virus scan, format identification, validation, normalization, fixity check)
<premis:agent> for each PREMIS Event there are three associated Agents: the organization, the digital preservation system (e.g. Archivematica 1.x) and the logged-in user
<mets:rightsMD> (rights metadata)
<premis:rights> Rights pertaining to the preservation, reproduction and use of the preserved digital objects (only included if the user added rights metadata prior to or during ingest)

=== Use case: Create and Use a Bag Profile ===

https://github.com/ruebot/bagit-profiles

Archivematica could define a bag profile and reference this in the AIP's it produces. This would help make AIP's more easily machine readable.

Improvements/aipreadme

2017-06-19T17:20:41Z

Evelyn: /* Sample README file text */

== User story ==

As a repository manager, I would like AIP's to be as self describing as possible, so that future users, with little or no information about Archivematica or what an AIP is, will be able to understand the structure and contents of the AIP's I produce now.

== Status ==

2017-06-01 - New Proposal

== Interest ==

If you'd like to get involved in this development, please feel free to contribute to this wiki page or start a discussion on our [https://groups.google.com/forum/#!forum/archivematica| user forum].

== Analysis: ==

Currently, Archivematica AIP's are structured as a Bag (https://tools.ietf.org/html/draft-kunze-bagit-14) and contain a METS file, which describes the contents of the AIP. Details about the Archivematica AIP structure are here: https://www.archivematica.org/en/docs/archivematica-1.6/user-manual/archival-storage/aip-structure/

METS files are machine readable, but are not human friendly formats.

Adding a human readable index or description into an AIP would improve the chances of a future user understanding the structure.

Archivematica structures AIP's in a specific way, but that is not documented within the AIP. Adding more explicit documentation about the structure would help users test that AIP's are valid, and help them to understand the structure.

There is a similar proposal outlined here: https://github.com/UTS-eResearch/datacrate

=== Use case: Add a README to each AIP ===

In the data/ directory (beside the mets file) add a README.html or README.md file. This would be intended as the first file to be opened by a human being trying to examine an AIP.

The README file would include
* some boilerplate text, describing what an AIP is
* links to the Archivematica documentation, to METS documentation, to PREMIS docs, etc.
* a link to the METS file
* optionally a link to a CATALOG.html file, that includes more detailed information about the contents of the AIP.

====Sample README file text====

This readme file describes the basic structure of an AIP generated by Archivematica.

Acronyms

AIP = Archival Information Package
METS = Metadata Encoding and Transmission Standard
OAIS = Open Archival Information System
PDI = Preservation Description Information
PREMIS = Preservation Metadata Implementation Strategies
UUID = Unique Universal Identifier

What is Archivematica?

Archivematica is an open-source suite of tools designed to ingest diverse digital content and prepare AIPs for long-term storage. Once an AIP is generated it is not dependent on Archivematica for retrieval, and can be opened using any standard file browser. The concept of an AIP is derived from the ISO 14721:2012 Reference Model for an ''Open Archival Information System (OAIS)'', which defines it as “[a]n Information Package, consisting of the Content Information and the associated Preservation Description Information (PDI), which is preserved within an OAIS.”

Content Information

In an Archivematica AIP, the Content Information consists primarily of the originally ingested digital objects and any preservation versions of the objects created to mitigate the risk of format obsolescence over time. The preservation copies typically have the same filenames as the original objects but with different file extensions and with UUIDs appended to the filename. For example, for an original file named ''BBhelemet.ai'' the preservation version may be named ''BBhelmet-e3a3988d-8149-49ea-adc5-c255fb68d4f9.pdf''.

The originally ingested digital objects and any preservation versions are located in the ''objects'' directory of the AIP. There will be nested subdirectories in the ''object'' directory if these subdirectories were included in the original transfer or added during SIP arrangement. The ''objects'' directory also includes a ''submissiondocumentation'' folder and a ''metadata'' folder. The ''submissiondocumentation'' folder contains documentation such as donor agreements and transfer forms, if included the original transfer, as well as a METS file that records the contents of the original transfer(s) from which the AIP was created. The ''metadata'' folder holds any metadata files included in the original transfer, and any OCR text files generated during processing.

Preservation Description Information (PDI)

The PDI in an Archivematica AIP is recorded in a METS XML file. METS is maintained by the Library of Congress, which defines it as “a standard for encoding descriptive, administrative, and structural metadata regarding objects within a digital library, expressed using the XML schema language of the World Wide Web Consortium.” In the Archivematica AIP the METS filename is composed of the name METS with a UUID file extension and an XML file extension; for example ''METS.0ad8cdab-dbbf-4863-8a4d-9a675c227216.xml''. The METS file typically consists of the following standard METS sections:
<metsHdr> (METS header): basic information about the METS file;
<mets:dmdSec> (descriptive metadata section): descriptive metadata about the digital objects;
<mets:amdSec> (administrative metadata section): technical and provenance information about the digital objects;
<mets:fileSec> (file section): a list of the digital objects and an indication of their role in the AIP (original, preservation, metadata, submission documentation, license etc.);
<mets:structMap> (structural map): a physical or logical ordering of the digital objects.

The technical and provenance information in the METS amdSec is recorded as PREMIS metadata. PREMIS is also a Library of Congress standard, and is described as "the international standard for metadata to support the preservation of digital objects and ensure their long-term usability." The PREMIS entities are wrapped in the METS file as follows:

<mets:amdSec>
<mets:techMD> (technical metadata)
<bject (e.g. UUID, size, checksum, format, original name, extracted technical metadata)
--mets:digiprovMD (digital provenance metadata)
PREMIS Event (e.g. ingestion, message digest calculation, virus scan, format identification, validation, normalization, fixity check)
PREMIS Agent for each PREMIS Event there are three Agents: the organization, the digital preservation system (e.g. Archivematica 1.x) and the logged-in user
--mets:rightsMD (rights metadata)
PREMIS Rights (only included if the user added rights metadata prior to or during ingest)

=== Use case: Create and Use a Bag Profile ===

https://github.com/ruebot/bagit-profiles

Archivematica could define a bag profile and reference this in the AIP's it produces. This would help make AIP's more easily machine readable.

Improvements/aipreadme

2017-06-19T17:17:51Z

Evelyn: /* Sample README file text */

== User story ==

As a repository manager, I would like AIP's to be as self describing as possible, so that future users, with little or no information about Archivematica or what an AIP is, will be able to understand the structure and contents of the AIP's I produce now.

== Status ==

2017-06-01 - New Proposal

== Interest ==

If you'd like to get involved in this development, please feel free to contribute to this wiki page or start a discussion on our [https://groups.google.com/forum/#!forum/archivematica| user forum].

== Analysis: ==

Currently, Archivematica AIP's are structured as a Bag (https://tools.ietf.org/html/draft-kunze-bagit-14) and contain a METS file, which describes the contents of the AIP. Details about the Archivematica AIP structure are here: https://www.archivematica.org/en/docs/archivematica-1.6/user-manual/archival-storage/aip-structure/

METS files are machine readable, but are not human friendly formats.

Adding a human readable index or description into an AIP would improve the chances of a future user understanding the structure.

Archivematica structures AIP's in a specific way, but that is not documented within the AIP. Adding more explicit documentation about the structure would help users test that AIP's are valid, and help them to understand the structure.

There is a similar proposal outlined here: https://github.com/UTS-eResearch/datacrate

=== Use case: Add a README to each AIP ===

In the data/ directory (beside the mets file) add a README.html or README.md file. This would be intended as the first file to be opened by a human being trying to examine an AIP.

The README file would include
* some boilerplate text, describing what an AIP is
* links to the Archivematica documentation, to METS documentation, to PREMIS docs, etc.
* a link to the METS file
* optionally a link to a CATALOG.html file, that includes more detailed information about the contents of the AIP.

====Sample README file text====

This readme file describes the basic structure of an AIP generated by Archivematica.

Acronyms

AIP = Archival Information Package
METS = Metadata Encoding and Transmission Standard
OAIS = Open Archival Information System
PDI = Preservation Description Information
PREMIS = Preservation Metadata Implementation Strategies
UUID = Unique Universal Identifier

What is Archivematica?

Archivematica is an open-source suite of tools designed to ingest diverse digital content and prepare AIPs for long-term storage. Once an AIP is generated it is not dependent on Archivematica for retrieval, and can be opened using any standard file browser. The concept of an AIP is derived from the ISO 14721:2012 Reference Model for an ''Open Archival Information System (OAIS)'', which defines it as “[a]n Information Package, consisting of the Content Information and the associated Preservation Description Information (PDI), which is preserved within an OAIS.”

Content Information

In an Archivematica AIP, the Content Information consists primarily of the originally ingested digital objects and any preservation versions of the objects created to mitigate the risk of format obsolescence over time. The preservation copies typically have the same filenames as the original objects but with different file extensions and with UUIDs appended to the filename. For example, for an original file named ''BBhelemet.ai'' the preservation version may be named ''BBhelmet-e3a3988d-8149-49ea-adc5-c255fb68d4f9.pdf''.

The originally ingested digital objects and any preservation versions are located in the ''objects'' directory of the AIP. There will be nested subdirectories in the ''object'' directory if these subdirectories were included in the original transfer or added during SIP arrangement. The ''objects'' directory also includes a ''submissiondocumentation'' folder and a ''metadata'' folder. The ''submissiondocumentation'' folder contains documentation such as donor agreements and transfer forms, if included the original transfer, as well as a METS file that records the contents of the original transfer(s) from which the AIP was created. The ''metadata'' folder holds any metadata files included in the original transfer, and any OCR text files generated during processing.

Preservation Description Information (PDI)

The PDI in an Archivematica AIP is recorded in a METS XML file. METS is maintained by the Library of Congress, which defines it as “a standard for encoding descriptive, administrative, and structural metadata regarding objects within a digital library, expressed using the XML schema language of the World Wide Web Consortium.” In the Archivematica AIP the METS filename is composed of the name METS with a UUID file extension and an XML file extension; for example ''METS.0ad8cdab-dbbf-4863-8a4d-9a675c227216.xml''. The METS file typically consists of the following standard METS sections:
-metsHdr (METS header): basic information about the METS file;
-dmdSec (descriptive metadata section): descriptive metadata about the digital objects;
-amdSec (administrative metadata section): technical and provenance information about the digital objects;
-fileSec (file section): a list of the digital objects and an indication of their role in the AIP (original, preservation, metadata, submission documentation, license etc.);
-structMap (structural map): a physical or logical ordering of the digital objects.

The technical and provenance information in the METS amdSec is recorded as PREMIS metadata. PREMIS is also a Library of Congress standard, and is described as "the international standard for metadata to support the preservation of digital objects and ensure their long-term usability." The PREMIS entities are wrapped in the METS file as follows:

amdSec
--mets:techMD (technical metadata)
PREMIS Object (e.g. UUID, size, checksum, format, original name, extracted technical metadata)
--mets:digiprovMD (digital provenance metadata)
PREMIS Event (e.g. ingestion, message digest calculation, virus scan, format identification, validation, normalization, fixity check)
PREMIS Agent for each PREMIS Event there are three Agents: the organization, the digital preservation system (e.g. Archivematica 1.x) and the logged-in user
--mets:rightsMD (rights metadata)
PREMIS Rights (only included if the user added rights metadata prior to or during ingest)

=== Use case: Create and Use a Bag Profile ===

https://github.com/ruebot/bagit-profiles

Archivematica could define a bag profile and reference this in the AIP's it produces. This would help make AIP's more easily machine readable.

Improvements/aipreadme

2017-06-18T17:25:34Z

Evelyn: /* Sample README file text */

Improvements/aipreadme

2017-06-18T17:21:28Z

Evelyn: /* Sample README file text */

Improvements/aipreadme

2017-06-18T17:19:58Z

Evelyn: /* Sample README file text */

Improvements/aipreadme

2017-06-18T17:16:27Z

Evelyn: /* Sample README file text */

Improvements/aipreadme

2017-06-18T17:14:13Z

Evelyn: /* Sample README file text */

Improvements/aipreadme

2017-06-18T17:13:02Z

Evelyn: /* Sample README file text */

Improvements/aipreadme

2017-06-18T17:11:05Z

Evelyn: /* Sample README file text */

Improvements/aipreadme

2017-06-18T17:10:00Z

Evelyn: /* Sample README file test */

Improvements/aipreadme

2017-06-18T17:08:27Z

Evelyn: /* Analysis: */

Release 1.6.0

2017-06-03T00:00:04Z

Evelyn:

[[Main Page]] > [[External_tools|External software tools]]> Release 1.6.0

This is a draft document, the details listed here are not finalized.

Archivematica integrates a suite of free and open-source tools that allows users to process digital objects from ingest to access in compliance with the ISO-OAIS functional model. In addition to the core Archivematica which is released under AGPL v3 license, the following tools are bundled with Archivematica 1.6.0:

{| border="1" cellpadding="10" cellspacing="0" width=90%
|-
|- style="background-color:#cccccc;"
!style="width:20%"|'''Tool'''
!style="width:10%"|'''Version'''
!style="width:40%"|'''Description'''
!style="width:30%"|'''License'''
|-
|-
|[http://www.accesstomemory.org AtoM]
|Tested with 2.3.0, 2.3.1, qa/2.4.x
|Web-based archival description and access tool.
|GNU General Public License (GPL)
|-
|[https://github.com/LibraryOfCongress/bagit-java/ BagIt]
| 1.5.0 - 1.5.4
|Standard and script to package digital objects and metadata for archival storage
|BSD License
|-
|[https://github.com/simsong/bulk_extractor bulk_extractor]
|
|Disk image and file contents analysis tool
|Public domain
|-
|[http://www.clamav.net/ Clam AV (anti-virus)]
|
|Anti-virus toolkit for UNIX
|GNU General Public License (GPL)
|-
|[https://www.djangoproject.com/ Django]
|1.8.x
|Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design.
|BSD License
|-
|[http://www.elasticsearch.org/ ElasticSearch]
|1.7.5
|Indexing and search
|Apache License 2.0
|-
|[http://www.sno.phy.queensu.ca/~phil/exiftool/index.html ExifTool]
|
|Multimedia metadata extraction
|GNU General Public License and Artistic License
|-
|[http://ffmpeg.org/ FFmpeg]
|
|Converts a wide variety of audio and video formats
|GNU Lesser General Public License (LGPL)
|-
|[https://github.com/openplanets/fido fido]
|1.3.5
|File format identification tool
|Licensed under the Apache License, Version 2.0 (the "License")
|-
|[http://code.google.com/p/fits/ File Information Tool Set (FITS)]
|
|File format identification and validation software integration tool
|GNU Lesser General Public License (LGPL)
|-
|[http://gearman.org/ Gearman]
|
|Gearman provides a generic application framework to farm out work to other machines or processes that are better suited to do the work.
|BSD License
|-
|[http://www.imagemagick.org/script/index.php Imagemagick]
|
|Converts a wide variety of bitmap images
|GPL compatible [http://www.imagemagick.org/script/license.php Imagemagick license]
|-
|[http://www.inkscape.org/ Inkscape]
|
|Converts vector images to Scalable Vector Graphic (SVG) format
|GNU General Public License (GPL) version 2
|-
|[http://jhove.sourceforge.net/ JHOVE]
|
|File format validation tool
|GNU Lesser General Public License (LGPL)
|-
|[http://md5deep.sourceforge.net/ md5deep]
|
|Checksum generation and verification scripts
|GNU General Public License (GPL)
|-
|[https://mediaarea.net/en/MediaInfo MediaInfo]
|
|Multimedia metadata extraction
|BSD (2-clause), Zlib
|-
|[http://linux.about.com/cs/linux101/g/nfscommon.htm NFS-common]
|
|Network File System Access - allows access to files on network storage devices.
|GNU General Public License (GPL)
|-
|[http://p7zip.sourceforge.net/ p7zip]
|
|7-Zip is a file archiver with a high compression ratio. (LZMA)
|GNU General Public License (GPL)
|-
|[http://packages.ubuntu.com/lucid/python-lxml Python-lxml]
|
|Python binding for libxml2 and libxslt
|GNU General Public License (GPL)
|-
|[https://github.com/richardlehane/siegfried Seigfried]
| 1.6.7
|File format identification tool
|Licensed under the Apache License, Version 2.0 (the "License")
|-
|[http://www.sleuthkit.org/ Sleuthkit]
|
|Disk image management and extraction toolkit
|Common Public License / IBM Public License
|-
|[http://code.google.com/p/tesseract-ocr/ Tesseract]
|
|Optical Character Recognition -read image files and convert to text
|Apache Licence Vesion 2
|-
|[http://www.ubuntu.org/ Ubuntu Linux]
|
|Interface with computing hardware. Ubuntu Linux server edition.
|GNU General Public License (GPL)
|-
|[http://www.ossp.org/pkg/lib/uuid/ UUID]
|
|command line interface (CLI) for the generation of DCE 1.1, ISO/IEC 11578:1996 and IETF RFC-4122 compliant Universally Unique Identifier (UUID).
|GNU General Public License (GPL)
|-
|[http://unarchiver.c3.cx/commandline unar]
|
|The Unarchiver is an archive unpacker program
|GNU General Public License (GPL)
|-
|[http://manpages.ubuntu.com/manpages/hardy/man1/zip.1.html Zip]
|
|Utility called by Bagit to create AIP package
|Info-Zip license: "Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely"
|-
|}

Release 1.6.0

2017-06-02T23:12:37Z

Evelyn:

[[Main Page]] > [[External_tools|External software tools]]> Release 1.6.0

This is a draft document, the details listed here are not finalized.

Archivematica integrates a suite of free and open-source tools that allows users to process digital objects from ingest to access in compliance with the ISO-OAIS functional model. In addition to the core Archivematica which is released under AGPL v3 license, the following tools are bundled with Archivematica 1.6.0:

{| border="1" cellpadding="10" cellspacing="0" width=90%
|-
|- style="background-color:#cccccc;"
!style="width:20%"|'''Tool'''
!style="width:10%"|'''Version'''
!style="width:40%"|'''Description'''
!style="width:30%"|'''License'''
|-
|-
|[http://www.accesstomemory.org AtoM]
|Tested with 2.3.0, 2.3.1, qa/2.4.x
|Web-based archival description and access tool.
|GNU General Public License (GPL)
|-
|[https://github.com/LibraryOfCongress/bagit-java/ BagIt]
| 1.5.0 - 1.5.4
|Standard and script to package digital objects and metadata for archival storage
|BSD License
|-
|[https://github.com/simsong/bulk_extractor bulk_extractor]
|
|Disk image and file contents analysis tool
|Public domain
|-
|[http://www.clamav.net/ Clam AV (anti-virus)]
|
|Anti-virus toolkit for UNIX
|GNU General Public License (GPL)
|-
|[https://www.djangoproject.com/ Django]
|1.8.x
|Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design.
|BSD License
|-
|[http://www.elasticsearch.org/ ElasticSearch]
|1.7.5
|Indexing and search
|Apache License 2.0
|-
|[http://www.sno.phy.queensu.ca/~phil/exiftool/index.html ExifTool]
|
|Multimedia metadata extraction
|GNU General Public License and Artistic License
|-
|[http://ffmpeg.org/ FFmpeg]
|
|Converts a wide variety of audio and video formats
|GNU Lesser General Public License (LGPL)
|-
|[https://github.com/openplanets/fido fido]
|1.3.5
|File format identification tool
|Licensed under the Apache License, Version 2.0 (the "License")
|-
|[http://code.google.com/p/fits/ File Information Tool Set (FITS)]
|
|File format identification and validation software integration tool
|GNU Lesser General Public License (LGPL)
|-
|[http://gearman.org/ Gearman]
|
|Gearman provides a generic application framework to farm out work to other machines or processes that are better suited to do the work.
|BSD License
|-
|[http://www.imagemagick.org/script/index.php Imagemagick]
|
|Converts a wide variety of bitmap images
|GPL compatible [http://www.imagemagick.org/script/license.php Imagemagick license]
|-
|[http://www.inkscape.org/ Inkscape]
|
|Converts vector images to Scalable Vector Graphic (SVG) format
|GNU General Public License (GPL) version 2
|-
|[http://jhove.sourceforge.net/ JHOVE]
|
|File format validation tool
|GNU Lesser General Public License (LGPL)
|-
|[http://md5deep.sourceforge.net/ md5deep]
|
|Checksum generation and verification scripts
|GNU General Public License (GPL)
|-
|[https://mediaarea.net/en/MediaInfo MediaInfo]
|
|Multimedia metadata extraction
|BSD (2-clause), Zlib
|-
|[http://linux.about.com/cs/linux101/g/nfscommon.htm NFS-common]
|
|Network File System Access - allows access to files on network storage devices.
|GNU General Public License (GPL)
|-
|[http://p7zip.sourceforge.net/ p7zip]
|
|7-Zip is a file archiver with a high compression ratio. (LZMA)
|GNU General Public License (GPL)
|-
|[http://packages.ubuntu.com/lucid/python-lxml Python-lxml]
|
|Python binding for libxml2 and libxslt
|GNU General Public License (GPL)
|-
|[https://github.com/richardlehane/siegfried Seigfried]
| 1.6.7
|
|File format identification tool
|Licensed under the Apache License, Version 2.0 (the "License")
|-
|[http://www.sleuthkit.org/ Sleuthkit]
|
|Disk image management and extraction toolkit
|Common Public License / IBM Public License
|-
|[http://code.google.com/p/tesseract-ocr/ Tesseract]
|
|Optical Character Recognition -read image files and convert to text
|Apache Licence Vesion 2
|-
|[http://www.ubuntu.org/ Ubuntu Linux]
|
|Interface with computing hardware. Ubuntu Linux server edition.
|GNU General Public License (GPL)
|-
|[http://www.ossp.org/pkg/lib/uuid/ UUID]
|
|command line interface (CLI) for the generation of DCE 1.1, ISO/IEC 11578:1996 and IETF RFC-4122 compliant Universally Unique Identifier (UUID).
|GNU General Public License (GPL)
|-
|[http://unarchiver.c3.cx/commandline unar]
|
|The Unarchiver is an archive unpacker program
|GNU General Public License (GPL)
|-
|[http://manpages.ubuntu.com/manpages/hardy/man1/zip.1.html Zip]
|
|Utility called by Bagit to create AIP package
|Info-Zip license: "Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely"
|-
|}

External tools

2017-06-02T23:12:19Z

Evelyn:

[[Main Page]] > [[Documentation]] > External tools

=External software tools used in Archivematica=

'''[[Release 1.7.0]]''' (In development)

'''[[Release 1.6.0]]''' (March 2017)

'''[[Release 1.5]]''' (June 2016)

'''[[Release 1.4.1]]''' (June 2015)

'''[[Release 1.4]]''' (May 2015)

'''[[Release 1.3.1]]''' (February 2015)

'''[[Release 1.0]]''' (September 2014)

'''[[Release 0.10-beta]]''' (April 2013)

'''[[Release 0.9-beta]]''' (Aug 2012)

'''[[Release 0.8-alpha]]''' (Jan 2012)

'''[[Release 0.7.1-alpha]]''' (June 2011)

'''[[Release 0.7-alpha]]''' (Feb 2011)

'''[[Release 0.6.2-alpha]]''' (November 2010)

'''[[Release 0.6-alpha]]''' (May 2010)

'''[[Release 0.5-alpha]]''' (November 2009)

'''[[Release 0.4-alpha]]''' (October 2009)

'''[[Release 0.3.5-alpha]]''' (September 2009)

'''[[Release 0.3-alpha]]''' (June 2009)

'''[[Release 0.2-alpha]]''' (May 2009)

'''[[Release 0.1-alpha]]''' (Feb 2009)

Community/Camps/York2017

2017-03-29T18:50:26Z

Evelyn: /* Tuesday, April 4: Day One (optional) */

We're excited to announce the first Archivematica Camp being held in Europe, cohosted by the University of York and Artefactual! Inspired by similar events like Hydra Camp, Islandora Camp and Fedora Camp, Archivematica Camp is intended to provide a space for anyone interested in or currently using Archivematica to come together, learn about the platform from other users, and share their experiences.

== Dates & Location ==

'''April 4-6, 2017 - [https://www.york.ac.uk/hub/ The Ron Cooke Hub] at the University of York'''

The Ron Cooke Hub is located just outside of York at the University of York's Heslington East campus. It is approximately 15 minutes by car and 30 minutes by bus from York city centre.

For information about directions to the Ron Cooke Hub, transit options, and parking, please see the [http://www.york.ac.uk/hub/directions/ Ron Cooke Hub website].

== '''REGISTRATION''' ==

'''Registration rate''': £425

Registration opens on Wednesday, February 22nd at 10:00am GMT!

[https://www.eventbrite.com/e/archivematica-camp-york-uk-registration-31851507717 '''REGISTER HERE''']

The registration rate includes three full days of camp-related activity, lunch and continental breakfast each day, a camp-wide social event, and - most importantly - cake.

== Camp Counsellors ==

*Sara Allain, Systems Archivist, Artefactual Systems
*Kirsty Lee, Digital Preservation Coordinator, University of Edinburgh
*Evelyn McLellan, President, Artefactual Systems
*Justin Simpson, Director of Archivematica Technical Services, Artefactual Systems

Jen Mitcham from University of York is also providing local support and will be guest speaking during the camp. Thank you Jen!

== Schedule ==

Based on early registration feedback, below is the revised schedule for Archivematica Camp York. Some sessions are held together as one large group, while others are held concurrently. For the latter, there will generally be a session that is more suited to end-users at the same time as one more suited to systems administrators or developers. Campers should feel free to attend whatever sessions sound the most useful to them!

There is some built-in flexibility for last minute changes or ideas.

=== Tuesday, April 4: Day One (optional) ===

{| border="1" style="border-collapse:collapse;"
|colspan="2"|'''Main room'''
|-
|style="white-space: nowrap;"|9:00am - 12:00pm
|'''Archivematica for Absolute Beginners'''
During the morning of Day One we'll ensure that everyone is comfortable with Archivematica, whether they're archivists, developers, or systems administrators. This is a half-day session intended for participants with no previous Archivematica experience whatsoever.
|-
|style="white-space: nowrap;"|12:00pm - 1:00pm
|colspan="2"|Lunch
|-
|style="white-space: nowrap;"|1:00pm - 5:00pm
|'''Archivematica and AtoM'''
The afternoon of Day One will be spent completing hands-on Archivematica exercises and looking at how Archivematica integrates with [https://www.accesstomemory.org/en/ AtoM], a widely used open-source web based tool designed for archival description and online metadata and digital object discovery.

'''Note''': participants are welcome to join the morning session, afternoon session, or both sessions as they wish. Participants may also wish to join the Camp on Day Two.

{| border="1" style="border-collapse:collapse;"
|colspan="2"|'''Breakout room'''
|-
|style="white-space: nowrap;"|9:00am - 5:00pm
|'''Advanced Archivematica Drop-In Clinic'''
All day we'll have experts available to help you with your Archivematica problems. No appointment necessary - just drop by with a laptop and a problem and we'll be happy to chat!
|}

=== Wednesday, April 5: Day Two ===

{| border="1" style="border-collapse:collapse;"
|'''Time'''
|'''Main room'''
|'''Breakout room'''
|-
|style="white-space: nowrap;"|9:00am - 9:30am
|colspan="2"|'''Arrival and registration'''
|-
|style="white-space: nowrap;"|9:30am - 9:45am
|colspan="2"|'''Camp orientation'''
|-
|style="white-space: nowrap;"|9:45am - 11:00am
|colspan="2"|'''Workflow and deployment tours'''
To kick off the camp, users of all stripes have the opportunity to show off their current implementations - or to discuss future implementations! If you're interested in discussing how Archivematica works (or might work) in your institution, come prepared with a 5-10 minute informal presentation and/or your questions.
|-
|style="white-space: nowrap;"|11:00am - 11:15am
|colspan="2"|'''Coffee/tea break'''
|-
|style="white-space: nowrap;"|11:15am - 12:00pm
|colspan="2"|'''Metadata deep dive'''
During the Metadata Deep Dive we'll look at how Archivematica creates and handles metadata, focusing on the backbone of an Archivematica AIP: the METS.xml file.
|-
|style="white-space: nowrap;"|12:00pm - 1:00pm
|colspan="2"|Lunch
|-
|style="white-space: nowrap;"|1:30pm - 2:30pm
|'''Specialized workflows'''
Archivematica's specialized transfer types kick off different kinds of workflows within the system. In this session, we'll provide an overview of the transfer types (Standard, Zipped Bag, Unzipped Bag, etc.) and the tools and processes that make these workflows unique.
|'''Technical architecture overview'''
Take a peek under the hood at Archivematica's bones. We'll walk campers through the main technologies and tools that make up Archivematica and talk about the framework that keeps it all together.
|-
|style="white-space: nowrap;"|2:30pm - 3:15pm
|'''Introduction to the Appraisal tab'''
The Appraisal tab is a brand-new addition to Archivematica's user interface. In this session, we'll demo how it currently works and start thinking about ways that it could be extended.
|'''Storage Service management'''
Archivematica works with your storage system through an application called the Storage Service. In this session, we'll talk about how to configure the Storage Service and the different types of storage that work with Archivematica.
|-
|style="white-space: nowrap;"|3:15pm - 3:30pm
|colspan="2"|Agenda adjusting
|-
|style="white-space: nowrap;"|3:30pm - 3:45pm
|colspan="2"|Break
|-
|style="white-space: nowrap;"|3:45pm - 4:30pm
|'''Validation micro-service developments'''
We've been working on file validation! Integrating PREFORMA with Archivematica means that file validation is better than ever. We'll walk you through the new functionality that PREFORMA offers and discuss the integration project.
|'''PREMIS as Linked Data'''
The future is linked - should Archivematica be linked too? We'll talk about how PREMIS 3 might serve long-term goals by providing a linked open data solution for Archivematica.
|-
|style="white-space: nowrap;"|4:30pm - 5:00pm
|colspan="2"|Wrap-up
|}

'''Note on agenda adjusting''': based on camper interest, the schedule may be adjusted to accommodate topics of interest that will be covered during the concurrent sessions.

=== Thursday, April 6: Day Three ===

{| border="1" style="border-collapse:collapse;"
|'''Time'''
|'''Main room'''
|'''Breakout room'''
|-
|style="white-space: nowrap;"|9:00am - 10:15am
|'''Deployment practices for development and production'''
|'''User interface focus group'''
Sure, we can make nice AIPs and DIPs, but is it pretty? This is a chance to chat about the user interface and usability in general, including how integrations with other systems look to the end user.
|-
|style="white-space: nowrap;"|10:15am - 10:45am
|colspan="2"|Coffee/tea break
|-
|style="white-space: nowrap;"|10:45am - 12:00pm
|colspan="2"|'''Automation tools'''
The Automation Tools project is a set of python scripts that are designed to automate the processing of transfers in an Archivematica pipeline. Learn more about installing, configuring and running these scripts for large-scale processing or for pulling in content from other systems such as DSpace.
|-
|style="white-space: nowrap;"|12:00pm - 1:00pm
|colspan="2"|Lunch
|-
|style="white-space: nowrap;"|1:00pm - 2:15pm
|'''Customizing the FPR'''
Learn more about using the Format Policy Registry to add and edit tools, rules and commands for format identification, metadata extraction, normalization and other Archivematica micro-services.
|'''Research Data Management / Deeper dive into format ID'''
Research data management and format identification go together nicely as topics, since research data often have a long tail of niche file formats that pose a challenge for long-term preservation. At this session Jen Mitcham from University of York will talk about her institution's work on using Archivematica for research data preservation and on submitting new formats to PRONOM, and Evelyn McLellan will talk about Archivematica integration with Dataverse and the Jisc Research Data Shared Services pilot project.
|-
|style="white-space: nowrap;"|2:15pm - 2:45pm
|colspan="2"|'''Concurrent sessions debrief'''
|-
|style="white-space: nowrap;"|2:45pm - 3:00pm
|colspan="2"|Coffee/tea break
|-
|style="white-space: nowrap;"|3:00pm - 4:00pm
|colspan="2"|'''Archivematica roadmap and upcoming developments'''
|-
|style="white-space: nowrap;"|4:00pm - 5:00pm
|colspan="2"|'''Project community and governance talk'''

|}

== Social events ==

=== Tuesday, April 4th: Small group dinners ===

More information forthcoming!

=== Wednesday April 5th: Group social ===

More information forthcoming!

== Local Arrangements ==

=== Hotels ===

There are lots of places to stay in York. Information can be found at [http://www.visityork.org/book/thedms_hotels.aspx?dms=1&at=1&mstat=1&msg=Book+York+Hotels Visit York]. However, we have negotiated a special Archivematica Camp price at two of the York accommodation options that you can book yourself, quoting the booking code. Details below:

==== [https://www.staycity.com/york/paragon-street/ Staycity Aparthotels Paragon Street] ====

We have reserved a block of self-catering rooms at the [https://www.staycity.com/york/paragon-street/ Staycity Aparthotels Paragon Street] for a nightly rate of £74. There are 20 rooms available for attendees who wish to stay from 3-6 April. The hotel is a 15 minute walk to York city centre, and a 15 minute bus ride (10 minute drive, 45 minute walk) to The Ron Cooke Hub. Every room includes with a small kitchenette.

* '''One Bedroom Apartments''': The rooms can accommodate up to 4 people, with a choice of 1 double bed or 2 single beds. There is also a twin sofa bed in the lounge area.

* '''Breakfast''': Price includes a Grab and Go breakfast box.

* '''Car Parking''': There is a Q Park car park located on Kent Street, priced from £11 per 24hours. More information can be found on the following link: http://www.q-park.co.uk/parking/york/q-park-barbican

* '''Booking''': Please note that to book at the preferred rate, you must contact Staycity York directly. Contact information, as well as the booking reference code, will be included in your registration confirmation email. Rooms at this special rate are available on a first come first served basis and must be booked before 27th March in order to qualify for the reduced price.

==== [http://www.queenshotel-york.com/ Queens Hotel] ====

We have reserved a block of double rooms at the [http://www.queenshotel-york.com/ Queens Hotel] for a nightly rate of £68 bed and breakfast. This is a central city centre hotel, next to the river and a short walk from the train station. There are frequent buses between the city centre and The Ron Cooke Hub at Heslington East via the number 4 and UoY66 (allow 30 mins for your journey), or the Ron Cooke Hub can be reached by foot if you have 55 minutes to spare!

* '''Double rooms''': The rooms have a double bed.

* '''Breakfast''': Sit down breakfast in the hotel restaurant facility is included in the price.

* '''Booking''': Please note that to book at the preferred rate, quote the booking code which will be included in your registration confirmation email. Rooms at this special rate are available on a first come first served basis and must be booked before 20th March in order to qualify for the reduced price.

=== Transit ===

Further information about how to find the Ron Cooke Hub are available [https://www.york.ac.uk/hub/directions/ here]

==Code of Conduct==

The Archivematica community is dedicated to providing a welcoming and positive experience for everyone, whether they are in a formal session or a social setting related to an Archivematica event, or are taking part in activities online. Archivematica community participants come from all over the world and bring with them a wide variety of professional, personal and social backgrounds; whatever these may be, we treat colleagues with dignity and respect. We are sensitive to the fact that the international nature of the Archivematica community means that we span many different social norms around language and behaviour and we strive to conduct ourselves in ways that are unlikely to cause offense. In the event that someone’s conduct is causing offense or distress, the Archivematica Camp has a detailed Anti-Harassment Policy, details below, which can be applied to address the problem.

The first step in dealing with any serious misconduct is to contact a member of the organizing group, or a counsellor at an Archivematica Camp (please see counsellors, above). These people will be made known before and during any Archivematica Camp event.

'''Anti-Harassment Policy'''

The Archivematica community is dedicated to providing a harassment-free conference/camp experience for everyone. If you have been harassed, please consult this protocol for conflict resolution which makes clear how we can help.

The Archivematica community has established the following policy to make it clear that we do not tolerate harassment in any form. Sexual or discriminatory language and imagery are not appropriate for any event venue, including talks, or any other communication channel used during the conference (such as social media).

Harassment includes:

* offensive verbal comments related to sex, gender, ethnicity, nationality, socioeconomic status, sexual orientation, disability, physical appearance, body size, age, race, religion;
* sexual or discriminatory images in public spaces;
* deliberate intimidation;
* stalking;
* harassing photography or recording;
* sustained disruption of talks or other events;
* inappropriate physical contact; and
* unwelcome sexual attention.

The lingua franca of Archivematica Camp is English; however, English may not be the native language of Archivematica Camp participants. Further, cultural norms around what may be considered obscene and offensive communication will vary among Archivematica Camp attendees. Campers are asked to please be mindful of the international character of Archivematica Camp, and to use respectful and clear language free of slang to facilitate communication.

Participants asked to stop any harassing behavior are expected to comply immediately.

If a participant engages in harassing behavior, event organizers and Archivematica representatives (or their designees) may take any action they deem appropriate, including warning the offender, expulsion from Archivematica Camp, or contacting a higher authority such as a representative from the offender’s institution.

If a participant raises a concern relating to actions covered by this policy in good faith, there will be no retaliation for bringing forward their concern. Threatening or taking action against someone for invoking this policy or for participating in any related investigation will be considered a violation of this policy.

Participants are expected to follow the anti-harassment policy at all Camp-related venues, Camp-related social events, and online communication channels.

We expect attendees and speakers past and present to be respectful to each other, and we will deal with any incidents that arise, including on social media.

We value your participation in the Archivematica community and your support in keeping the Archivematica community a safe, welcoming, and friendly space for fellow participants.

'''Acknowledgments'''

This policy is based on the [http://www.pasignyc.org/#code-of-conduct-section PASIG Code of Conduct], portions of which were modified from the [http://or2016.net/code-of-conduct/ Open Repositories’ code of conduct], which was itself modified from [https://www.seattleattic.com/codeofconduct Seattle Attic’s code of conduct] and the [http://adainitiative.org/what-we-do/events/ada-initiative-event-anti-harassment-policy/ Ada Initiative’s event harassment policy].

'''License'''

This document is licensed under [https://creativecommons.org/licenses/by-sa/3.0/ Creative Commons BY-SA].

Community/Camps/York2017

2017-03-29T15:50:30Z

Evelyn:

We're excited to announce the first Archivematica Camp being held in Europe, cohosted by the University of York and Artefactual! Inspired by similar events like Hydra Camp, Islandora Camp and Fedora Camp, Archivematica Camp is intended to provide a space for anyone interested in or currently using Archivematica to come together, learn about the platform from other users, and share their experiences.

== Dates & Location ==

'''April 4-6, 2017 - [https://www.york.ac.uk/hub/ The Ron Cooke Hub] at the University of York'''

The Ron Cooke Hub is located just outside of York at the University of York's Heslington East campus. It is approximately 15 minutes by car and 30 minutes by bus from York city centre.

For information about directions to the Ron Cooke Hub, transit options, and parking, please see the [http://www.york.ac.uk/hub/directions/ Ron Cooke Hub website].

== '''REGISTRATION''' ==

'''Registration rate''': £425

Registration opens on Wednesday, February 22nd at 10:00am GMT!

[https://www.eventbrite.com/e/archivematica-camp-york-uk-registration-31851507717 '''REGISTER HERE''']

The registration rate includes three full days of camp-related activity, lunch and continental breakfast each day, a camp-wide social event, and - most importantly - cake.

== Camp Counsellors ==

*Sara Allain, Systems Archivist, Artefactual Systems
*Kirsty Lee, Digital Preservation Coordinator, University of Edinburgh
*Evelyn McLellan, President, Artefactual Systems
*Justin Simpson, Director of Archivematica Technical Services, Artefactual Systems

Jen Mitcham from University of York is also providing local support and will be guest speaking during the camp. Thank you Jen!

== Schedule ==

Based on early registration feedback, below is the revised schedule for Archivematica Camp York. Some sessions are held together as one large group, while others are held concurrently. For the latter, there will generally be a session that is more suited to end-users at the same time as one more suited to systems administrators or developers. Campers should feel free to attend whatever sessions sound the most useful to them!

There is some built-in flexibility for last minute changes or ideas.

=== Tuesday, April 4: Day One (optional) ===

{| border="1" style="border-collapse:collapse;"
|colspan="2"|'''Main room'''
|-
|style="white-space: nowrap;"|9:00am - 12:00pm
|'''Archivematica for Absolute Beginners'''
During the morning of Day One we'll ensure that everyone is comfortable with Archivematica, whether they're archivists, developers, or systems administrators. This is a half-day session intended for participants with no previous Archivematica experience whatsoever.
|-
|style="white-space: nowrap;"|12:00pm - 1:00pm
|colspan="2"|Lunch
|-
|style="white-space: nowrap;"|1:00pm - 5:00pm
|'''Archivematica and AtoM'''
The afternoon of Day One will be spent on completing hands-on Archivematica exercises and looking at how Archivematica integrates with [https://www.accesstomemory.org/en/ AtoM], a widely-used archival description system. This half-day session will be spent exploring Archivematica and AtoM integration, including both present functionality and future possibilities.
|}

'''Note''': participants are welcome to join the morning session, afternoon session, or both sessions as they wish. Participants may also wish to join the Camp on Day Two.

{| border="1" style="border-collapse:collapse;"
|colspan="2"|'''Breakout room'''
|-
|style="white-space: nowrap;"|9:00am - 5:00pm
|'''Advanced Archivematica Drop-In Clinic'''
All day we'll have experts available to help you with your Archivematica problems. No appointment necessary - just drop by with a laptop and a problem and we'll be happy to chat!
|}

=== Wednesday, April 5: Day Two ===

{| border="1" style="border-collapse:collapse;"
|'''Time'''
|'''Main room'''
|'''Breakout room'''
|-
|style="white-space: nowrap;"|9:00am - 9:30am
|colspan="2"|'''Arrival and registration'''
|-
|style="white-space: nowrap;"|9:30am - 9:45am
|colspan="2"|'''Camp orientation'''
|-
|style="white-space: nowrap;"|9:45am - 11:00am
|colspan="2"|'''Workflow and deployment tours'''
To kick off the camp, users of all stripes have the opportunity to show off their current implementations - or to discuss future implementations! If you're interested in discussing how Archivematica works (or might work) in your institution, come prepared with a 5-10 minute informal presentation and/or your questions.
|-
|style="white-space: nowrap;"|11:00am - 11:15am
|colspan="2"|'''Coffee/tea break'''
|-
|style="white-space: nowrap;"|11:15am - 12:00pm
|colspan="2"|'''Metadata deep dive'''
During the Metadata Deep Dive we'll look at how Archivematica creates and handles metadata, focusing on the backbone of an Archivematica AIP: the METS.xml file.
|-
|style="white-space: nowrap;"|12:00pm - 1:00pm
|colspan="2"|Lunch
|-
|style="white-space: nowrap;"|1:30pm - 2:30pm
|'''Specialized workflows'''
Archivematica's specialized transfer types kick off different kinds of workflows within the system. In this session, we'll provide an overview of the transfer types (Standard, Zipped Bag, Unzipped Bag, etc.) and the tools and processes that make these workflows unique.
|'''Technical architecture overview'''
Take a peek under the hood at Archivematica's bones. We'll walk campers through the main technologies and tools that make up Archivematica and talk about the framework that keeps it all together.
|-
|style="white-space: nowrap;"|2:30pm - 3:15pm
|'''Introduction to the Appraisal tab'''
The Appraisal tab is a brand-new addition to Archivematica's user interface. In this session, we'll demo how it currently works and start thinking about ways that it could be extended.
|'''Storage Service management'''
Archivematica works with your storage system through an application called the Storage Service. In this session, we'll talk about how to configure the Storage Service and the different types of storage that work with Archivematica.
|-
|style="white-space: nowrap;"|3:15pm - 3:30pm
|colspan="2"|Agenda adjusting
|-
|style="white-space: nowrap;"|3:30pm - 3:45pm
|colspan="2"|Break
|-
|style="white-space: nowrap;"|3:45pm - 4:30pm
|'''Validation micro-service developments'''
We've been working on file validation! Integrating PREFORMA with Archivematica means that file validation is better than ever. We'll walk you through the new functionality that PREFORMA offers and discuss the integration project.
|'''PREMIS as Linked Data'''
The future is linked - should Archivematica be linked too? We'll talk about how PREMIS 3 might serve long-term goals by providing a linked open data solution for Archivematica.
|-
|style="white-space: nowrap;"|4:30pm - 5:00pm
|colspan="2"|Wrap-up
|}

'''Note on agenda adjusting''': based on camper interest, the schedule may be adjusted to accommodate topics of interest that will be covered during the concurrent sessions.

=== Thursday, April 6: Day Three ===

{| border="1" style="border-collapse:collapse;"
|'''Time'''
|'''Main room'''
|'''Breakout room'''
|-
|style="white-space: nowrap;"|9:00am - 10:15am
|'''Deployment practices for development and production'''
|'''User interface focus group'''
Sure, we can make nice AIPs and DIPs, but is it pretty? This is a chance to chat about the user interface and usability in general, including how integrations with other systems look to the end user.
|-
|style="white-space: nowrap;"|10:15am - 10:45am
|colspan="2"|Coffee/tea break
|-
|style="white-space: nowrap;"|10:45am - 12:00pm
|colspan="2"|'''Automation tools'''
The Automation Tools project is a set of python scripts that are designed to automate the processing of transfers in an Archivematica pipeline. Learn more about installing, configuring and running these scripts for large-scale processing or for pulling in content from other systems such as DSpace.
|-
|style="white-space: nowrap;"|12:00pm - 1:00pm
|colspan="2"|Lunch
|-
|style="white-space: nowrap;"|1:00pm - 2:15pm
|'''Customizing the FPR'''
Learn more about using the Format Policy Registry to add and edit tools, rules and commands for format identification, metadata extraction, normalization and other Archivematica micro-services.
|'''Research Data Management / Deeper dive into format ID'''
Research data management and format identification go together nicely as topics, since research data often have a long tail of niche file formats that pose a challenge for long-term preservation. At this session Jen Mitcham from University of York will talk about her institution's work on using Archivematica for research data preservation and on submitting new formats to PRONOM, and Evelyn McLellan will talk about Archivematica integration with Dataverse and the Jisc Research Data Shared Services pilot project.
|-
|style="white-space: nowrap;"|2:15pm - 2:45pm
|colspan="2"|'''Concurrent sessions debrief'''
|-
|style="white-space: nowrap;"|2:45pm - 3:00pm
|colspan="2"|Coffee/tea break
|-
|style="white-space: nowrap;"|3:00pm - 4:00pm
|colspan="2"|'''Archivematica roadmap and upcoming developments'''
|-
|style="white-space: nowrap;"|4:00pm - 5:00pm
|colspan="2"|'''Project community and governance talk'''

|}

== Social events ==

=== Tuesday, April 4th: Small group dinners ===

More information forthcoming!

=== Wednesday April 5th: Group social ===

More information forthcoming!

== Local Arrangements ==

=== Hotels ===

There are lots of places to stay in York. Information can be found at [http://www.visityork.org/book/thedms_hotels.aspx?dms=1&at=1&mstat=1&msg=Book+York+Hotels Visit York]. However, we have negotiated a special Archivematica Camp price at two of the York accommodation options that you can book yourself, quoting the booking code. Details below:

==== [https://www.staycity.com/york/paragon-street/ Staycity Aparthotels Paragon Street] ====

We have reserved a block of self-catering rooms at the [https://www.staycity.com/york/paragon-street/ Staycity Aparthotels Paragon Street] for a nightly rate of £74. There are 20 rooms available for attendees who wish to stay from 3-6 April. The hotel is a 15 minute walk to York city centre, and a 15 minute bus ride (10 minute drive, 45 minute walk) to The Ron Cooke Hub. Every room includes with a small kitchenette.

* '''One Bedroom Apartments''': The rooms can accommodate up to 4 people, with a choice of 1 double bed or 2 single beds. There is also a twin sofa bed in the lounge area.

* '''Breakfast''': Price includes a Grab and Go breakfast box.

* '''Car Parking''': There is a Q Park car park located on Kent Street, priced from £11 per 24hours. More information can be found on the following link: http://www.q-park.co.uk/parking/york/q-park-barbican

* '''Booking''': Please note that to book at the preferred rate, you must contact Staycity York directly. Contact information, as well as the booking reference code, will be included in your registration confirmation email. Rooms at this special rate are available on a first come first served basis and must be booked before 27th March in order to qualify for the reduced price.

==== [http://www.queenshotel-york.com/ Queens Hotel] ====

We have reserved a block of double rooms at the [http://www.queenshotel-york.com/ Queens Hotel] for a nightly rate of £68 bed and breakfast. This is a central city centre hotel, next to the river and a short walk from the train station. There are frequent buses between the city centre and The Ron Cooke Hub at Heslington East via the number 4 and UoY66 (allow 30 mins for your journey), or the Ron Cooke Hub can be reached by foot if you have 55 minutes to spare!

* '''Double rooms''': The rooms have a double bed.

* '''Breakfast''': Sit down breakfast in the hotel restaurant facility is included in the price.

* '''Booking''': Please note that to book at the preferred rate, quote the booking code which will be included in your registration confirmation email. Rooms at this special rate are available on a first come first served basis and must be booked before 20th March in order to qualify for the reduced price.

=== Transit ===

Further information about how to find the Ron Cooke Hub are available [https://www.york.ac.uk/hub/directions/ here]

==Code of Conduct==

The Archivematica community is dedicated to providing a welcoming and positive experience for everyone, whether they are in a formal session or a social setting related to an Archivematica event, or are taking part in activities online. Archivematica community participants come from all over the world and bring with them a wide variety of professional, personal and social backgrounds; whatever these may be, we treat colleagues with dignity and respect. We are sensitive to the fact that the international nature of the Archivematica community means that we span many different social norms around language and behaviour and we strive to conduct ourselves in ways that are unlikely to cause offense. In the event that someone’s conduct is causing offense or distress, the Archivematica Camp has a detailed Anti-Harassment Policy, details below, which can be applied to address the problem.

The first step in dealing with any serious misconduct is to contact a member of the organizing group, or a counsellor at an Archivematica Camp (please see counsellors, above). These people will be made known before and during any Archivematica Camp event.

'''Anti-Harassment Policy'''

The Archivematica community is dedicated to providing a harassment-free conference/camp experience for everyone. If you have been harassed, please consult this protocol for conflict resolution which makes clear how we can help.

The Archivematica community has established the following policy to make it clear that we do not tolerate harassment in any form. Sexual or discriminatory language and imagery are not appropriate for any event venue, including talks, or any other communication channel used during the conference (such as social media).

Harassment includes:

* offensive verbal comments related to sex, gender, ethnicity, nationality, socioeconomic status, sexual orientation, disability, physical appearance, body size, age, race, religion;
* sexual or discriminatory images in public spaces;
* deliberate intimidation;
* stalking;
* harassing photography or recording;
* sustained disruption of talks or other events;
* inappropriate physical contact; and
* unwelcome sexual attention.

The lingua franca of Archivematica Camp is English; however, English may not be the native language of Archivematica Camp participants. Further, cultural norms around what may be considered obscene and offensive communication will vary among Archivematica Camp attendees. Campers are asked to please be mindful of the international character of Archivematica Camp, and to use respectful and clear language free of slang to facilitate communication.

Participants asked to stop any harassing behavior are expected to comply immediately.

If a participant engages in harassing behavior, event organizers and Archivematica representatives (or their designees) may take any action they deem appropriate, including warning the offender, expulsion from Archivematica Camp, or contacting a higher authority such as a representative from the offender’s institution.

If a participant raises a concern relating to actions covered by this policy in good faith, there will be no retaliation for bringing forward their concern. Threatening or taking action against someone for invoking this policy or for participating in any related investigation will be considered a violation of this policy.

Participants are expected to follow the anti-harassment policy at all Camp-related venues, Camp-related social events, and online communication channels.

We expect attendees and speakers past and present to be respectful to each other, and we will deal with any incidents that arise, including on social media.

We value your participation in the Archivematica community and your support in keeping the Archivematica community a safe, welcoming, and friendly space for fellow participants.

'''Acknowledgments'''

This policy is based on the [http://www.pasignyc.org/#code-of-conduct-section PASIG Code of Conduct], portions of which were modified from the [http://or2016.net/code-of-conduct/ Open Repositories’ code of conduct], which was itself modified from [https://www.seattleattic.com/codeofconduct Seattle Attic’s code of conduct] and the [http://adainitiative.org/what-we-do/events/ada-initiative-event-anti-harassment-policy/ Ada Initiative’s event harassment policy].

'''License'''

This document is licensed under [https://creativecommons.org/licenses/by-sa/3.0/ Creative Commons BY-SA].

Community/Camps/York2017

2017-03-28T23:46:52Z

Evelyn: /* Thursday, April 6: Day Three */

We're excited to announce the first Archivematica Camp being held in Europe, cohosted by the University of York and Artefactual! Inspired by similar events like Hydra Camp, Islandora Camp and Fedora Camp, Archivematica Camp is intended to provide a space for anyone interested in or currently using Archivematica to come together, learn about the platform from other users, and share their experiences.

== Dates & Location ==

'''April 4-6, 2017 - [https://www.york.ac.uk/hub/ The Ron Cooke Hub] at the University of York'''

The Ron Cooke Hub is located just outside of York at the University of York's Heslington East campus. It is approximately 15 minutes by car and 30 minutes by bus from York city centre.

For information about directions to the Ron Cooke Hub, transit options, and parking, please see the [http://www.york.ac.uk/hub/directions/ Ron Cooke Hub website].

== '''REGISTRATION''' ==

'''Registration rate''': £425

Registration opens on Wednesday, February 22nd at 10:00am GMT!

[https://www.eventbrite.com/e/archivematica-camp-york-uk-registration-31851507717 '''REGISTER HERE''']

The registration rate includes three full days of camp-related activity, lunch and continental breakfast each day, a camp-wide social event, and - most importantly - cake.

== Camp Counsellors ==

*Sara Allain, Systems Archivist, Artefactual Systems
*Kirsty Lee, Digital Preservation Coordinator, University of Edinburgh
*Evelyn McLellan, President, Artefactual Systems
*Justin Simpson, Director of Archivematica Technical Services, Artefactual Systems

Jen Mitcham from University of York is also providing local support and will be guest speaking during the camp. Thank you Jen!

== Schedule ==

Based on early registration feedback, below is the revised schedule for Archivematica Camp York. Some sessions are held together as one large group, while others are held concurrently. For the latter, there will generally be a session that is more suited to end-users at the same time as one more suited to systems administrators or developers. Campers should feel free to attend whatever sessions sound the most useful to them!

There is some built-in flexibility for last minute changes or ideas.

=== Tuesday, April 4: Day One (optional) ===

{| border="1" style="border-collapse:collapse;"
|colspan="2"|'''Main room'''
|-
|style="white-space: nowrap;"|9:00am - 12:00pm
|'''Archivematica for Absolute Beginners'''
During the morning of Day One we'll ensure that everyone is comfortable with Archivematica, whether they're archivists, developers, or systems administrators. This is a half-day session intended for participants with no previous Archivematica experience whatsoever.
|-
|style="white-space: nowrap;"|12:00pm - 1:00pm
|colspan="2"|Lunch
|-
|style="white-space: nowrap;"|1:00pm - 5:00pm
|'''Archivematica and AtoM'''
The afternoon of Day One will be spent on completing hands-on Archivematica exercises and looking at how Archivematica integrates with [https://www.accesstomemory.org/en/ AtoM], a widely-used archival description system. This half-day session will be spent exploring Archivematica and AtoM integration, including both present functionality and future possibilities.
|}

'''Note''': participants are welcome to join the morning session, afternoon session, or both sessions as they wish. Participants may also wish to join the Camp on Day Two.

{| border="1" style="border-collapse:collapse;"
|colspan="2"|'''Breakout room'''
|-
|style="white-space: nowrap;"|9:00am - 5:00pm
|'''Advanced Archivematica Drop-In Clinic'''
All day we'll have experts available to help you with your Archivematica problems. No appointment necessary - just drop by with a laptop and a problem and we'll be happy to chat!
|}

=== Wednesday, April 5: Day Two ===

{| border="1" style="border-collapse:collapse;"
|'''Time'''
|'''Main room'''
|'''Breakout room'''
|-
|style="white-space: nowrap;"|9:00am - 9:30am
|colspan="2"|'''Arrival and registration'''
|-
|style="white-space: nowrap;"|9:30am - 9:45am
|colspan="2"|'''Camp orientation'''
|-
|style="white-space: nowrap;"|9:45am - 11:00am
|colspan="2"|'''Workflow and deployment tours'''
To kick off the camp, users of all stripes have the opportunity to show off their current implementations - or to discuss future implementations! If you're interested in discussing how Archivematica works (or might work) in your institution, come prepared with a 5-10 minute informal presentation and/or your questions.
|-
|style="white-space: nowrap;"|11:00am - 11:15am
|colspan="2"|'''Coffee/tea break'''
|-
|style="white-space: nowrap;"|11:15am - 12:00pm
|colspan="2"|'''Metadata deep dive'''
During the Metadata Deep Dive we'll look at how Archivematica creates and handles metadata, focusing on the backbone of an Archivematica AIP: the METS.xml file.
|-
|style="white-space: nowrap;"|12:00pm - 1:00pm
|colspan="2"|Lunch
|-
|style="white-space: nowrap;"|1:30pm - 2:30pm
|'''Specialized workflows'''
Archivematica's specialized transfer types kick off different kinds of workflows within the system. In this session, we'll provide an overview of the transfer types (Standard, Zipped Bag, Unzipped Bag, etc.) and the tools and processes that make these workflows unique.
|'''Technical architecture overview'''
Take a peek under the hood at Archivematica's bones. We'll walk campers through the main technologies and tools that make up Archivematica and talk about the framework that keeps it all together.
|-
|style="white-space: nowrap;"|2:30pm - 3:15pm
|'''Introduction to the Appraisal tab'''
The Appraisal tab is a brand-new addition to Archivematica's user interface. In this session, we'll demo how it currently works and start thinking about ways that it could be extended.
|'''Storage Service management'''
Archivematica works with your storage system through an application called the Storage Service. In this session, we'll talk about how to configure the Storage Service and the different types of storage that work with Archivematica.
|-
|style="white-space: nowrap;"|3:15pm - 3:30pm
|colspan="2"|Agenda adjusting
|-
|style="white-space: nowrap;"|3:30pm - 3:45pm
|colspan="2"|Break
|-
|style="white-space: nowrap;"|3:45pm - 4:30pm
|'''Validation micro-service developments'''
We've been working on file validation! Integrating PREFORMA with Archivematica means that file validation is better than ever. We'll walk you through the new functionality that PREFORMA offers and discuss the integration project.
|'''PREMIS as Linked Data'''
The future is linked - should Archivematica be linked too? We'll talk about how PREMIS 3 might serve long-term goals by providing a linked open data solution for Archivematica.
|-
|style="white-space: nowrap;"|4:30pm - 5:00pm
|colspan="2"|Wrap-up
|}

'''Note on agenda adjusting''': based on camper interest, the schedule may be adjusted to accommodate topics of interest that will be covered during the concurrent sessions.

=== Thursday, April 6: Day Three ===

{| border="1" style="border-collapse:collapse;"
|'''Time'''
|'''Main room'''
|'''Breakout room'''
|-
|style="white-space: nowrap;"|9:00am - 10:15am
|'''Deployment practices for development and production'''
|'''User interface focus group'''
Sure, we can make nice AIPs and DIPs, but is it pretty? This is a chance to chat about the user interface and usability in general, including how integrations with other systems look to the end user.
|-
|style="white-space: nowrap;"|10:15am - 10:45am
|colspan="2"|Coffee/tea break
|-
|style="white-space: nowrap;"|10:45am - 12:00pm
|colspan="2"|'''Automation tools'''
The Automation Tools project is a set of python scripts that are designed to automate the processing of transfers in an Archivematica pipeline. Learn more about installing, configuring and running these scripts for large-scale processing or for pulling in content from other systems such as DSpace.
|-
|style="white-space: nowrap;"|12:00pm - 1:00pm
|colspan="2"|Lunch
|-
|style="white-space: nowrap;"|1:00pm - 2:15pm
|'''Customizing the FPR'''
Learn more about using the Format Policy Registry to add and edit tools, rules and commands for format identification, metadata extraction, normalization and other Archivematica micro-services.
|'''Research Data Management / Deeper dive into format ID'''
Research data management and format identification go together nicely as topics, since research data often have a long tail of niche file formats that pose a challenge for long-term preservation. At this session Jen Mitcham from University of York will talk about her institution's work on using Archivematica for research data preservation and on submitting new formats to PRONOM, and Evelyn McLellan will talk about the Jisc Research Data Shared Services pilot project.
|-
|style="white-space: nowrap;"|2:15pm - 2:45pm
|colspan="2"|'''Concurrent sessions debrief'''
|-
|style="white-space: nowrap;"|2:45pm - 3:00pm
|colspan="2"|Coffee/tea break
|-
|style="white-space: nowrap;"|3:00pm - 4:00pm
|colspan="2"|'''Archivematica roadmap and upcoming developments'''
|-
|style="white-space: nowrap;"|4:00pm - 5:00pm
|colspan="2"|'''Project community and governance talk'''

|}

== Social events ==

=== Tuesday, April 4th: Small group dinners ===

More information forthcoming!

=== Wednesday April 5th: Group social ===

More information forthcoming!

== Local Arrangements ==

=== Hotels ===

There are lots of places to stay in York. Information can be found at [http://www.visityork.org/book/thedms_hotels.aspx?dms=1&at=1&mstat=1&msg=Book+York+Hotels Visit York]. However, we have negotiated a special Archivematica Camp price at two of the York accommodation options that you can book yourself, quoting the booking code. Details below:

==== [https://www.staycity.com/york/paragon-street/ Staycity Aparthotels Paragon Street] ====

We have reserved a block of self-catering rooms at the [https://www.staycity.com/york/paragon-street/ Staycity Aparthotels Paragon Street] for a nightly rate of £74. There are 20 rooms available for attendees who wish to stay from 3-6 April. The hotel is a 15 minute walk to York city centre, and a 15 minute bus ride (10 minute drive, 45 minute walk) to The Ron Cooke Hub. Every room includes with a small kitchenette.

* '''One Bedroom Apartments''': The rooms can accommodate up to 4 people, with a choice of 1 double bed or 2 single beds. There is also a twin sofa bed in the lounge area.

* '''Breakfast''': Price includes a Grab and Go breakfast box.

* '''Car Parking''': There is a Q Park car park located on Kent Street, priced from £11 per 24hours. More information can be found on the following link: http://www.q-park.co.uk/parking/york/q-park-barbican

* '''Booking''': Please note that to book at the preferred rate, you must contact Staycity York directly. Contact information, as well as the booking reference code, will be included in your registration confirmation email. Rooms at this special rate are available on a first come first served basis and must be booked before 27th March in order to qualify for the reduced price.

==== [http://www.queenshotel-york.com/ Queens Hotel] ====

We have reserved a block of double rooms at the [http://www.queenshotel-york.com/ Queens Hotel] for a nightly rate of £68 bed and breakfast. This is a central city centre hotel, next to the river and a short walk from the train station. There are frequent buses between the city centre and The Ron Cooke Hub at Heslington East via the number 4 and UoY66 (allow 30 mins for your journey), or the Ron Cooke Hub can be reached by foot if you have 55 minutes to spare!

* '''Double rooms''': The rooms have a double bed.

* '''Breakfast''': Sit down breakfast in the hotel restaurant facility is included in the price.

* '''Booking''': Please note that to book at the preferred rate, quote the booking code which will be included in your registration confirmation email. Rooms at this special rate are available on a first come first served basis and must be booked before 20th March in order to qualify for the reduced price.

=== Transit ===

Further information about how to find the Ron Cooke Hub are available [https://www.york.ac.uk/hub/directions/ here]

==Code of Conduct==

The Archivematica community is dedicated to providing a welcoming and positive experience for everyone, whether they are in a formal session or a social setting related to an Archivematica event, or are taking part in activities online. Archivematica community participants come from all over the world and bring with them a wide variety of professional, personal and social backgrounds; whatever these may be, we treat colleagues with dignity and respect. We are sensitive to the fact that the international nature of the Archivematica community means that we span many different social norms around language and behaviour and we strive to conduct ourselves in ways that are unlikely to cause offense. In the event that someone’s conduct is causing offense or distress, the Archivematica Camp has a detailed Anti-Harassment Policy, details below, which can be applied to address the problem.

The first step in dealing with any serious misconduct is to contact a member of the organizing group, or a counsellor at an Archivematica Camp (please see counsellors, above). These people will be made known before and during any Archivematica Camp event.

'''Anti-Harassment Policy'''

The Archivematica community is dedicated to providing a harassment-free conference/camp experience for everyone. If you have been harassed, please consult this protocol for conflict resolution which makes clear how we can help.

The Archivematica community has established the following policy to make it clear that we do not tolerate harassment in any form. Sexual or discriminatory language and imagery are not appropriate for any event venue, including talks, or any other communication channel used during the conference (such as social media).

Harassment includes:

* offensive verbal comments related to sex, gender, ethnicity, nationality, socioeconomic status, sexual orientation, disability, physical appearance, body size, age, race, religion;
* sexual or discriminatory images in public spaces;
* deliberate intimidation;
* stalking;
* harassing photography or recording;
* sustained disruption of talks or other events;
* inappropriate physical contact; and
* unwelcome sexual attention.

The lingua franca of Archivematica Camp is English; however, English may not be the native language of Archivematica Camp participants. Further, cultural norms around what may be considered obscene and offensive communication will vary among Archivematica Camp attendees. Campers are asked to please be mindful of the international character of Archivematica Camp, and to use respectful and clear language free of slang to facilitate communication.

Participants asked to stop any harassing behavior are expected to comply immediately.

If a participant engages in harassing behavior, event organizers and Archivematica representatives (or their designees) may take any action they deem appropriate, including warning the offender, expulsion from Archivematica Camp, or contacting a higher authority such as a representative from the offender’s institution.

If a participant raises a concern relating to actions covered by this policy in good faith, there will be no retaliation for bringing forward their concern. Threatening or taking action against someone for invoking this policy or for participating in any related investigation will be considered a violation of this policy.

Participants are expected to follow the anti-harassment policy at all Camp-related venues, Camp-related social events, and online communication channels.

We expect attendees and speakers past and present to be respectful to each other, and we will deal with any incidents that arise, including on social media.

We value your participation in the Archivematica community and your support in keeping the Archivematica community a safe, welcoming, and friendly space for fellow participants.

'''Acknowledgments'''

This policy is based on the [http://www.pasignyc.org/#code-of-conduct-section PASIG Code of Conduct], portions of which were modified from the [http://or2016.net/code-of-conduct/ Open Repositories’ code of conduct], which was itself modified from [https://www.seattleattic.com/codeofconduct Seattle Attic’s code of conduct] and the [http://adainitiative.org/what-we-do/events/ada-initiative-event-anti-harassment-policy/ Ada Initiative’s event harassment policy].

'''License'''

This document is licensed under [https://creativecommons.org/licenses/by-sa/3.0/ Creative Commons BY-SA].

Community/Camps/York2017

2017-03-28T23:43:08Z

Evelyn: /* Thursday, April 6: Day Three */

We're excited to announce the first Archivematica Camp being held in Europe, cohosted by the University of York and Artefactual! Inspired by similar events like Hydra Camp, Islandora Camp and Fedora Camp, Archivematica Camp is intended to provide a space for anyone interested in or currently using Archivematica to come together, learn about the platform from other users, and share their experiences.

== Dates & Location ==

'''April 4-6, 2017 - [https://www.york.ac.uk/hub/ The Ron Cooke Hub] at the University of York'''

The Ron Cooke Hub is located just outside of York at the University of York's Heslington East campus. It is approximately 15 minutes by car and 30 minutes by bus from York city centre.

For information about directions to the Ron Cooke Hub, transit options, and parking, please see the [http://www.york.ac.uk/hub/directions/ Ron Cooke Hub website].

== '''REGISTRATION''' ==

'''Registration rate''': £425

Registration opens on Wednesday, February 22nd at 10:00am GMT!

[https://www.eventbrite.com/e/archivematica-camp-york-uk-registration-31851507717 '''REGISTER HERE''']

The registration rate includes three full days of camp-related activity, lunch and continental breakfast each day, a camp-wide social event, and - most importantly - cake.

== Camp Counsellors ==

*Sara Allain, Systems Archivist, Artefactual Systems
*Kirsty Lee, Digital Preservation Coordinator, University of Edinburgh
*Evelyn McLellan, President, Artefactual Systems
*Justin Simpson, Director of Archivematica Technical Services, Artefactual Systems

Jen Mitcham from University of York is also providing local support and will be guest speaking during the camp. Thank you Jen!

== Schedule ==

Based on early registration feedback, below is the revised schedule for Archivematica Camp York. Some sessions are held together as one large group, while others are held concurrently. For the latter, there will generally be a session that is more suited to end-users at the same time as one more suited to systems administrators or developers. Campers should feel free to attend whatever sessions sound the most useful to them!

There is some built-in flexibility for last minute changes or ideas.

=== Tuesday, April 4: Day One (optional) ===

{| border="1" style="border-collapse:collapse;"
|colspan="2"|'''Main room'''
|-
|style="white-space: nowrap;"|9:00am - 12:00pm
|'''Archivematica for Absolute Beginners'''
During the morning of Day One we'll ensure that everyone is comfortable with Archivematica, whether they're archivists, developers, or systems administrators. This is a half-day session intended for participants with no previous Archivematica experience whatsoever.
|-
|style="white-space: nowrap;"|12:00pm - 1:00pm
|colspan="2"|Lunch
|-
|style="white-space: nowrap;"|1:00pm - 5:00pm
|'''Archivematica and AtoM'''
The afternoon of Day One will be spent on completing hands-on Archivematica exercises and looking at how Archivematica integrates with [https://www.accesstomemory.org/en/ AtoM], a widely-used archival description system. This half-day session will be spent exploring Archivematica and AtoM integration, including both present functionality and future possibilities.
|}

'''Note''': participants are welcome to join the morning session, afternoon session, or both sessions as they wish. Participants may also wish to join the Camp on Day Two.

{| border="1" style="border-collapse:collapse;"
|colspan="2"|'''Breakout room'''
|-
|style="white-space: nowrap;"|9:00am - 5:00pm
|'''Advanced Archivematica Drop-In Clinic'''
All day we'll have experts available to help you with your Archivematica problems. No appointment necessary - just drop by with a laptop and a problem and we'll be happy to chat!
|}

=== Wednesday, April 5: Day Two ===

{| border="1" style="border-collapse:collapse;"
|'''Time'''
|'''Main room'''
|'''Breakout room'''
|-
|style="white-space: nowrap;"|9:00am - 9:30am
|colspan="2"|'''Arrival and registration'''
|-
|style="white-space: nowrap;"|9:30am - 9:45am
|colspan="2"|'''Camp orientation'''
|-
|style="white-space: nowrap;"|9:45am - 11:00am
|colspan="2"|'''Workflow and deployment tours'''
To kick off the camp, users of all stripes have the opportunity to show off their current implementations - or to discuss future implementations! If you're interested in discussing how Archivematica works (or might work) in your institution, come prepared with a 5-10 minute informal presentation and/or your questions.
|-
|style="white-space: nowrap;"|11:00am - 11:15am
|colspan="2"|'''Coffee/tea break'''
|-
|style="white-space: nowrap;"|11:15am - 12:00pm
|colspan="2"|'''Metadata deep dive'''
During the Metadata Deep Dive we'll look at how Archivematica creates and handles metadata, focusing on the backbone of an Archivematica AIP: the METS.xml file.
|-
|style="white-space: nowrap;"|12:00pm - 1:00pm
|colspan="2"|Lunch
|-
|style="white-space: nowrap;"|1:30pm - 2:30pm
|'''Specialized workflows'''
Archivematica's specialized transfer types kick off different kinds of workflows within the system. In this session, we'll provide an overview of the transfer types (Standard, Zipped Bag, Unzipped Bag, etc.) and the tools and processes that make these workflows unique.
|'''Technical architecture overview'''
Take a peek under the hood at Archivematica's bones. We'll walk campers through the main technologies and tools that make up Archivematica and talk about the framework that keeps it all together.
|-
|style="white-space: nowrap;"|2:30pm - 3:15pm
|'''Introduction to the Appraisal tab'''
The Appraisal tab is a brand-new addition to Archivematica's user interface. In this session, we'll demo how it currently works and start thinking about ways that it could be extended.
|'''Storage Service management'''
Archivematica works with your storage system through an application called the Storage Service. In this session, we'll talk about how to configure the Storage Service and the different types of storage that work with Archivematica.
|-
|style="white-space: nowrap;"|3:15pm - 3:30pm
|colspan="2"|Agenda adjusting
|-
|style="white-space: nowrap;"|3:30pm - 3:45pm
|colspan="2"|Break
|-
|style="white-space: nowrap;"|3:45pm - 4:30pm
|'''Validation micro-service developments'''
We've been working on file validation! Integrating PREFORMA with Archivematica means that file validation is better than ever. We'll walk you through the new functionality that PREFORMA offers and discuss the integration project.
|'''PREMIS as Linked Data'''
The future is linked - should Archivematica be linked too? We'll talk about how PREMIS 3 might serve long-term goals by providing a linked open data solution for Archivematica.
|-
|style="white-space: nowrap;"|4:30pm - 5:00pm
|colspan="2"|Wrap-up
|}

'''Note on agenda adjusting''': based on camper interest, the schedule may be adjusted to accommodate topics of interest that will be covered during the concurrent sessions.

=== Thursday, April 6: Day Three ===

{| border="1" style="border-collapse:collapse;"
|'''Time'''
|'''Main room'''
|'''Breakout room'''
|-
|style="white-space: nowrap;"|9:00am - 10:15am
|'''Deployment practices for development and production'''
|'''User interface focus group'''
Sure, we can make nice AIPs and DIPs, but is it pretty? This is a chance to chat about the user interface and usability in general, including how integrations with other systems look to the end user.
|-
|style="white-space: nowrap;"|10:15am - 10:45am
|colspan="2"|Coffee/tea break
|-
|style="white-space: nowrap;"|10:45am - 12:00pm
|colspan="2"|'''Automation tools'''
The Automation Tools project is a set of python scripts that are designed to automate the processing of transfers in an Archivematica pipeline. Learn more about installing, configuring and running these scripts for large-scale processing or for pulling in content from other systems such as DSpace.
|-
|style="white-space: nowrap;"|12:00pm - 1:00pm
|colspan="2"|Lunch
|-
|style="white-space: nowrap;"|1:00pm - 2:15pm
|'''Customizing the FPR'''
Learn more about using the Format Policy Registry to add and edit tools, rules and commands for format identification, metadata extraction, normalization and other Archivematica micro-services.
|'''Research Data Management / Deeper dive into format ID'''
|-
|style="white-space: nowrap;"|2:15pm - 2:45pm
|colspan="2"|'''Concurrent sessions debrief'''
|-
|style="white-space: nowrap;"|2:45pm - 3:00pm
|colspan="2"|Coffee/tea break
|-
|style="white-space: nowrap;"|3:00pm - 4:00pm
|colspan="2"|'''Archivematica roadmap and upcoming developments'''
|-
|style="white-space: nowrap;"|4:00pm - 5:00pm
|colspan="2"|'''Project community and governance talk'''

|}

== Social events ==

=== Tuesday, April 4th: Small group dinners ===

More information forthcoming!

=== Wednesday April 5th: Group social ===

More information forthcoming!

== Local Arrangements ==

=== Hotels ===

There are lots of places to stay in York. Information can be found at [http://www.visityork.org/book/thedms_hotels.aspx?dms=1&at=1&mstat=1&msg=Book+York+Hotels Visit York]. However, we have negotiated a special Archivematica Camp price at two of the York accommodation options that you can book yourself, quoting the booking code. Details below:

==== [https://www.staycity.com/york/paragon-street/ Staycity Aparthotels Paragon Street] ====

We have reserved a block of self-catering rooms at the [https://www.staycity.com/york/paragon-street/ Staycity Aparthotels Paragon Street] for a nightly rate of £74. There are 20 rooms available for attendees who wish to stay from 3-6 April. The hotel is a 15 minute walk to York city centre, and a 15 minute bus ride (10 minute drive, 45 minute walk) to The Ron Cooke Hub. Every room includes with a small kitchenette.

* '''One Bedroom Apartments''': The rooms can accommodate up to 4 people, with a choice of 1 double bed or 2 single beds. There is also a twin sofa bed in the lounge area.

* '''Breakfast''': Price includes a Grab and Go breakfast box.

* '''Car Parking''': There is a Q Park car park located on Kent Street, priced from £11 per 24hours. More information can be found on the following link: http://www.q-park.co.uk/parking/york/q-park-barbican

* '''Booking''': Please note that to book at the preferred rate, you must contact Staycity York directly. Contact information, as well as the booking reference code, will be included in your registration confirmation email. Rooms at this special rate are available on a first come first served basis and must be booked before 27th March in order to qualify for the reduced price.

==== [http://www.queenshotel-york.com/ Queens Hotel] ====

We have reserved a block of double rooms at the [http://www.queenshotel-york.com/ Queens Hotel] for a nightly rate of £68 bed and breakfast. This is a central city centre hotel, next to the river and a short walk from the train station. There are frequent buses between the city centre and The Ron Cooke Hub at Heslington East via the number 4 and UoY66 (allow 30 mins for your journey), or the Ron Cooke Hub can be reached by foot if you have 55 minutes to spare!

* '''Double rooms''': The rooms have a double bed.

* '''Breakfast''': Sit down breakfast in the hotel restaurant facility is included in the price.

* '''Booking''': Please note that to book at the preferred rate, quote the booking code which will be included in your registration confirmation email. Rooms at this special rate are available on a first come first served basis and must be booked before 20th March in order to qualify for the reduced price.

=== Transit ===

Further information about how to find the Ron Cooke Hub are available [https://www.york.ac.uk/hub/directions/ here]

==Code of Conduct==

The Archivematica community is dedicated to providing a welcoming and positive experience for everyone, whether they are in a formal session or a social setting related to an Archivematica event, or are taking part in activities online. Archivematica community participants come from all over the world and bring with them a wide variety of professional, personal and social backgrounds; whatever these may be, we treat colleagues with dignity and respect. We are sensitive to the fact that the international nature of the Archivematica community means that we span many different social norms around language and behaviour and we strive to conduct ourselves in ways that are unlikely to cause offense. In the event that someone’s conduct is causing offense or distress, the Archivematica Camp has a detailed Anti-Harassment Policy, details below, which can be applied to address the problem.

The first step in dealing with any serious misconduct is to contact a member of the organizing group, or a counsellor at an Archivematica Camp (please see counsellors, above). These people will be made known before and during any Archivematica Camp event.

'''Anti-Harassment Policy'''

The Archivematica community is dedicated to providing a harassment-free conference/camp experience for everyone. If you have been harassed, please consult this protocol for conflict resolution which makes clear how we can help.

The Archivematica community has established the following policy to make it clear that we do not tolerate harassment in any form. Sexual or discriminatory language and imagery are not appropriate for any event venue, including talks, or any other communication channel used during the conference (such as social media).

Harassment includes:

* offensive verbal comments related to sex, gender, ethnicity, nationality, socioeconomic status, sexual orientation, disability, physical appearance, body size, age, race, religion;
* sexual or discriminatory images in public spaces;
* deliberate intimidation;
* stalking;
* harassing photography or recording;
* sustained disruption of talks or other events;
* inappropriate physical contact; and
* unwelcome sexual attention.

The lingua franca of Archivematica Camp is English; however, English may not be the native language of Archivematica Camp participants. Further, cultural norms around what may be considered obscene and offensive communication will vary among Archivematica Camp attendees. Campers are asked to please be mindful of the international character of Archivematica Camp, and to use respectful and clear language free of slang to facilitate communication.

Participants asked to stop any harassing behavior are expected to comply immediately.

If a participant engages in harassing behavior, event organizers and Archivematica representatives (or their designees) may take any action they deem appropriate, including warning the offender, expulsion from Archivematica Camp, or contacting a higher authority such as a representative from the offender’s institution.

If a participant raises a concern relating to actions covered by this policy in good faith, there will be no retaliation for bringing forward their concern. Threatening or taking action against someone for invoking this policy or for participating in any related investigation will be considered a violation of this policy.

Participants are expected to follow the anti-harassment policy at all Camp-related venues, Camp-related social events, and online communication channels.

We expect attendees and speakers past and present to be respectful to each other, and we will deal with any incidents that arise, including on social media.

We value your participation in the Archivematica community and your support in keeping the Archivematica community a safe, welcoming, and friendly space for fellow participants.

'''Acknowledgments'''

This policy is based on the [http://www.pasignyc.org/#code-of-conduct-section PASIG Code of Conduct], portions of which were modified from the [http://or2016.net/code-of-conduct/ Open Repositories’ code of conduct], which was itself modified from [https://www.seattleattic.com/codeofconduct Seattle Attic’s code of conduct] and the [http://adainitiative.org/what-we-do/events/ada-initiative-event-anti-harassment-policy/ Ada Initiative’s event harassment policy].

'''License'''

This document is licensed under [https://creativecommons.org/licenses/by-sa/3.0/ Creative Commons BY-SA].

Community/Camps/York2017

2017-03-28T23:40:52Z

Evelyn: /* Tuesday, April 4: Day One (optional) */

We're excited to announce the first Archivematica Camp being held in Europe, cohosted by the University of York and Artefactual! Inspired by similar events like Hydra Camp, Islandora Camp and Fedora Camp, Archivematica Camp is intended to provide a space for anyone interested in or currently using Archivematica to come together, learn about the platform from other users, and share their experiences.

== Dates & Location ==

'''April 4-6, 2017 - [https://www.york.ac.uk/hub/ The Ron Cooke Hub] at the University of York'''

The Ron Cooke Hub is located just outside of York at the University of York's Heslington East campus. It is approximately 15 minutes by car and 30 minutes by bus from York city centre.

For information about directions to the Ron Cooke Hub, transit options, and parking, please see the [http://www.york.ac.uk/hub/directions/ Ron Cooke Hub website].

== '''REGISTRATION''' ==

'''Registration rate''': £425

Registration opens on Wednesday, February 22nd at 10:00am GMT!

[https://www.eventbrite.com/e/archivematica-camp-york-uk-registration-31851507717 '''REGISTER HERE''']

The registration rate includes three full days of camp-related activity, lunch and continental breakfast each day, a camp-wide social event, and - most importantly - cake.

== Camp Counsellors ==

*Sara Allain, Systems Archivist, Artefactual Systems
*Kirsty Lee, Digital Preservation Coordinator, University of Edinburgh
*Evelyn McLellan, President, Artefactual Systems
*Justin Simpson, Director of Archivematica Technical Services, Artefactual Systems

Jen Mitcham from University of York is also providing local support and will be guest speaking during the camp. Thank you Jen!

== Schedule ==

Based on early registration feedback, below is the revised schedule for Archivematica Camp York. Some sessions are held together as one large group, while others are held concurrently. For the latter, there will generally be a session that is more suited to end-users at the same time as one more suited to systems administrators or developers. Campers should feel free to attend whatever sessions sound the most useful to them!

There is some built-in flexibility for last minute changes or ideas.

=== Tuesday, April 4: Day One (optional) ===

{| border="1" style="border-collapse:collapse;"
|colspan="2"|'''Main room'''
|-
|style="white-space: nowrap;"|9:00am - 12:00pm
|'''Archivematica for Absolute Beginners'''
During the morning of Day One we'll ensure that everyone is comfortable with Archivematica, whether they're archivists, developers, or systems administrators. This is a half-day session intended for participants with no previous Archivematica experience whatsoever.
|-
|style="white-space: nowrap;"|12:00pm - 1:00pm
|colspan="2"|Lunch
|-
|style="white-space: nowrap;"|1:00pm - 5:00pm
|'''Archivematica and AtoM'''
The afternoon of Day One will be spent on completing hands-on Archivematica exercises and looking at how Archivematica integrates with [https://www.accesstomemory.org/en/ AtoM], a widely-used archival description system. This half-day session will be spent exploring Archivematica and AtoM integration, including both present functionality and future possibilities.
|}

'''Note''': participants are welcome to join the morning session, afternoon session, or both sessions as they wish. Participants may also wish to join the Camp on Day Two.

{| border="1" style="border-collapse:collapse;"
|colspan="2"|'''Breakout room'''
|-
|style="white-space: nowrap;"|9:00am - 5:00pm
|'''Advanced Archivematica Drop-In Clinic'''
All day we'll have experts available to help you with your Archivematica problems. No appointment necessary - just drop by with a laptop and a problem and we'll be happy to chat!
|}

=== Wednesday, April 5: Day Two ===

{| border="1" style="border-collapse:collapse;"
|'''Time'''
|'''Main room'''
|'''Breakout room'''
|-
|style="white-space: nowrap;"|9:00am - 9:30am
|colspan="2"|'''Arrival and registration'''
|-
|style="white-space: nowrap;"|9:30am - 9:45am
|colspan="2"|'''Camp orientation'''
|-
|style="white-space: nowrap;"|9:45am - 11:00am
|colspan="2"|'''Workflow and deployment tours'''
To kick off the camp, users of all stripes have the opportunity to show off their current implementations - or to discuss future implementations! If you're interested in discussing how Archivematica works (or might work) in your institution, come prepared with a 5-10 minute informal presentation and/or your questions.
|-
|style="white-space: nowrap;"|11:00am - 11:15am
|colspan="2"|'''Coffee/tea break'''
|-
|style="white-space: nowrap;"|11:15am - 12:00pm
|colspan="2"|'''Metadata deep dive'''
During the Metadata Deep Dive we'll look at how Archivematica creates and handles metadata, focusing on the backbone of an Archivematica AIP: the METS.xml file.
|-
|style="white-space: nowrap;"|12:00pm - 1:00pm
|colspan="2"|Lunch
|-
|style="white-space: nowrap;"|1:30pm - 2:30pm
|'''Specialized workflows'''
Archivematica's specialized transfer types kick off different kinds of workflows within the system. In this session, we'll provide an overview of the transfer types (Standard, Zipped Bag, Unzipped Bag, etc.) and the tools and processes that make these workflows unique.
|'''Technical architecture overview'''
Take a peek under the hood at Archivematica's bones. We'll walk campers through the main technologies and tools that make up Archivematica and talk about the framework that keeps it all together.
|-
|style="white-space: nowrap;"|2:30pm - 3:15pm
|'''Introduction to the Appraisal tab'''
The Appraisal tab is a brand-new addition to Archivematica's user interface. In this session, we'll demo how it currently works and start thinking about ways that it could be extended.
|'''Storage Service management'''
Archivematica works with your storage system through an application called the Storage Service. In this session, we'll talk about how to configure the Storage Service and the different types of storage that work with Archivematica.
|-
|style="white-space: nowrap;"|3:15pm - 3:30pm
|colspan="2"|Agenda adjusting
|-
|style="white-space: nowrap;"|3:30pm - 3:45pm
|colspan="2"|Break
|-
|style="white-space: nowrap;"|3:45pm - 4:30pm
|'''Validation micro-service developments'''
We've been working on file validation! Integrating PREFORMA with Archivematica means that file validation is better than ever. We'll walk you through the new functionality that PREFORMA offers and discuss the integration project.
|'''PREMIS as Linked Data'''
The future is linked - should Archivematica be linked too? We'll talk about how PREMIS 3 might serve long-term goals by providing a linked open data solution for Archivematica.
|-
|style="white-space: nowrap;"|4:30pm - 5:00pm
|colspan="2"|Wrap-up
|}

'''Note on agenda adjusting''': based on camper interest, the schedule may be adjusted to accommodate topics of interest that will be covered during the concurrent sessions.

=== Thursday, April 6: Day Three ===

{| border="1" style="border-collapse:collapse;"
|'''Time'''
|'''Main room'''
|'''Breakout room'''
|-
|style="white-space: nowrap;"|9:00am - 10:15am
|'''Deployment practices for development and production'''
|'''User interface focus group'''
Sure, we can make nice AIPs and DIPs, but is it pretty? This is a chance to chat about the user interface and usability in general, including how integrations with other systems look to the end user.
|-
|style="white-space: nowrap;"|10:15am - 10:45am
|colspan="2"|Coffee/tea break
|-
|style="white-space: nowrap;"|10:45am - 12:00pm
|colspan="2"|'''Automation tools'''
The Automation Tools project is a set of python scripts that are designed to automate the processing of transfers in an Archivematica pipeline. Learn more about installing, configuring and running these scripts for large-scale processing or for pulling in content from other systems such as DSpace.
|-
|style="white-space: nowrap;"|12:00pm - 1:00pm
|colspan="2"|Lunch
|-
|style="white-space: nowrap;"|1:00pm - 2:15pm
|'''Customizing the FPR'''
|'''Research Data Management / Deeper dive into format ID'''
|-
|style="white-space: nowrap;"|2:15pm - 2:45pm
|colspan="2"|'''Concurrent sessions debrief'''
|-
|style="white-space: nowrap;"|2:45pm - 3:00pm
|colspan="2"|Coffee/tea break
|-
|style="white-space: nowrap;"|3:00pm - 4:00pm
|colspan="2"|'''Archivematica roadmap and upcoming developments'''
|-
|style="white-space: nowrap;"|4:00pm - 5:00pm
|colspan="2"|'''Project community and governance talk'''

|}

== Social events ==

=== Tuesday, April 4th: Small group dinners ===

More information forthcoming!

=== Wednesday April 5th: Group social ===

More information forthcoming!

== Local Arrangements ==

=== Hotels ===

There are lots of places to stay in York. Information can be found at [http://www.visityork.org/book/thedms_hotels.aspx?dms=1&at=1&mstat=1&msg=Book+York+Hotels Visit York]. However, we have negotiated a special Archivematica Camp price at two of the York accommodation options that you can book yourself, quoting the booking code. Details below:

==== [https://www.staycity.com/york/paragon-street/ Staycity Aparthotels Paragon Street] ====

We have reserved a block of self-catering rooms at the [https://www.staycity.com/york/paragon-street/ Staycity Aparthotels Paragon Street] for a nightly rate of £74. There are 20 rooms available for attendees who wish to stay from 3-6 April. The hotel is a 15 minute walk to York city centre, and a 15 minute bus ride (10 minute drive, 45 minute walk) to The Ron Cooke Hub. Every room includes with a small kitchenette.

* '''One Bedroom Apartments''': The rooms can accommodate up to 4 people, with a choice of 1 double bed or 2 single beds. There is also a twin sofa bed in the lounge area.

* '''Breakfast''': Price includes a Grab and Go breakfast box.

* '''Car Parking''': There is a Q Park car park located on Kent Street, priced from £11 per 24hours. More information can be found on the following link: http://www.q-park.co.uk/parking/york/q-park-barbican

* '''Booking''': Please note that to book at the preferred rate, you must contact Staycity York directly. Contact information, as well as the booking reference code, will be included in your registration confirmation email. Rooms at this special rate are available on a first come first served basis and must be booked before 27th March in order to qualify for the reduced price.

==== [http://www.queenshotel-york.com/ Queens Hotel] ====

We have reserved a block of double rooms at the [http://www.queenshotel-york.com/ Queens Hotel] for a nightly rate of £68 bed and breakfast. This is a central city centre hotel, next to the river and a short walk from the train station. There are frequent buses between the city centre and The Ron Cooke Hub at Heslington East via the number 4 and UoY66 (allow 30 mins for your journey), or the Ron Cooke Hub can be reached by foot if you have 55 minutes to spare!

* '''Double rooms''': The rooms have a double bed.

* '''Breakfast''': Sit down breakfast in the hotel restaurant facility is included in the price.

* '''Booking''': Please note that to book at the preferred rate, quote the booking code which will be included in your registration confirmation email. Rooms at this special rate are available on a first come first served basis and must be booked before 20th March in order to qualify for the reduced price.

=== Transit ===

Further information about how to find the Ron Cooke Hub are available [https://www.york.ac.uk/hub/directions/ here]

==Code of Conduct==

The Archivematica community is dedicated to providing a welcoming and positive experience for everyone, whether they are in a formal session or a social setting related to an Archivematica event, or are taking part in activities online. Archivematica community participants come from all over the world and bring with them a wide variety of professional, personal and social backgrounds; whatever these may be, we treat colleagues with dignity and respect. We are sensitive to the fact that the international nature of the Archivematica community means that we span many different social norms around language and behaviour and we strive to conduct ourselves in ways that are unlikely to cause offense. In the event that someone’s conduct is causing offense or distress, the Archivematica Camp has a detailed Anti-Harassment Policy, details below, which can be applied to address the problem.

The first step in dealing with any serious misconduct is to contact a member of the organizing group, or a counsellor at an Archivematica Camp (please see counsellors, above). These people will be made known before and during any Archivematica Camp event.

'''Anti-Harassment Policy'''

The Archivematica community is dedicated to providing a harassment-free conference/camp experience for everyone. If you have been harassed, please consult this protocol for conflict resolution which makes clear how we can help.

The Archivematica community has established the following policy to make it clear that we do not tolerate harassment in any form. Sexual or discriminatory language and imagery are not appropriate for any event venue, including talks, or any other communication channel used during the conference (such as social media).

Harassment includes:

* offensive verbal comments related to sex, gender, ethnicity, nationality, socioeconomic status, sexual orientation, disability, physical appearance, body size, age, race, religion;
* sexual or discriminatory images in public spaces;
* deliberate intimidation;
* stalking;
* harassing photography or recording;
* sustained disruption of talks or other events;
* inappropriate physical contact; and
* unwelcome sexual attention.

The lingua franca of Archivematica Camp is English; however, English may not be the native language of Archivematica Camp participants. Further, cultural norms around what may be considered obscene and offensive communication will vary among Archivematica Camp attendees. Campers are asked to please be mindful of the international character of Archivematica Camp, and to use respectful and clear language free of slang to facilitate communication.

Participants asked to stop any harassing behavior are expected to comply immediately.

If a participant engages in harassing behavior, event organizers and Archivematica representatives (or their designees) may take any action they deem appropriate, including warning the offender, expulsion from Archivematica Camp, or contacting a higher authority such as a representative from the offender’s institution.

If a participant raises a concern relating to actions covered by this policy in good faith, there will be no retaliation for bringing forward their concern. Threatening or taking action against someone for invoking this policy or for participating in any related investigation will be considered a violation of this policy.

Participants are expected to follow the anti-harassment policy at all Camp-related venues, Camp-related social events, and online communication channels.

We expect attendees and speakers past and present to be respectful to each other, and we will deal with any incidents that arise, including on social media.

We value your participation in the Archivematica community and your support in keeping the Archivematica community a safe, welcoming, and friendly space for fellow participants.

'''Acknowledgments'''

This policy is based on the [http://www.pasignyc.org/#code-of-conduct-section PASIG Code of Conduct], portions of which were modified from the [http://or2016.net/code-of-conduct/ Open Repositories’ code of conduct], which was itself modified from [https://www.seattleattic.com/codeofconduct Seattle Attic’s code of conduct] and the [http://adainitiative.org/what-we-do/events/ada-initiative-event-anti-harassment-policy/ Ada Initiative’s event harassment policy].

'''License'''

This document is licensed under [https://creativecommons.org/licenses/by-sa/3.0/ Creative Commons BY-SA].

Community/Camps/York2017

2017-03-28T23:40:01Z

Evelyn:

We're excited to announce the first Archivematica Camp being held in Europe, cohosted by the University of York and Artefactual! Inspired by similar events like Hydra Camp, Islandora Camp and Fedora Camp, Archivematica Camp is intended to provide a space for anyone interested in or currently using Archivematica to come together, learn about the platform from other users, and share their experiences.

== Dates & Location ==

'''April 4-6, 2017 - [https://www.york.ac.uk/hub/ The Ron Cooke Hub] at the University of York'''

The Ron Cooke Hub is located just outside of York at the University of York's Heslington East campus. It is approximately 15 minutes by car and 30 minutes by bus from York city centre.

For information about directions to the Ron Cooke Hub, transit options, and parking, please see the [http://www.york.ac.uk/hub/directions/ Ron Cooke Hub website].

== '''REGISTRATION''' ==

'''Registration rate''': £425

Registration opens on Wednesday, February 22nd at 10:00am GMT!

[https://www.eventbrite.com/e/archivematica-camp-york-uk-registration-31851507717 '''REGISTER HERE''']

The registration rate includes three full days of camp-related activity, lunch and continental breakfast each day, a camp-wide social event, and - most importantly - cake.

== Camp Counsellors ==

*Sara Allain, Systems Archivist, Artefactual Systems
*Kirsty Lee, Digital Preservation Coordinator, University of Edinburgh
*Evelyn McLellan, President, Artefactual Systems
*Justin Simpson, Director of Archivematica Technical Services, Artefactual Systems

Jen Mitcham from University of York is also providing local support and will be guest speaking during the camp. Thank you Jen!

== Schedule ==

Based on early registration feedback, below is the revised schedule for Archivematica Camp York. Some sessions are held together as one large group, while others are held concurrently. For the latter, there will generally be a session that is more suited to end-users at the same time as one more suited to systems administrators or developers. Campers should feel free to attend whatever sessions sound the most useful to them!

There is some built-in flexibility for last minute changes or ideas.

=== Tuesday, April 4: Day One (optional) ===

{| border="1" style="border-collapse:collapse;"
|colspan="2"|'''Main room'''
|-
|style="white-space: nowrap;"|9:00am - 12:00pm
|'''Archivematica for Absolute Beginners'''
During the morning of Day One we'll ensure that everyone is comfortable with Archivematica, whether they're archivists, developers, or systems administrators. This is a half-day session intended for participants with no previous Archivematica experience whatsoever.
|-
|style="white-space: nowrap;"|12:00pm - 1:00pm
|colspan="2"|Lunch
|-
|style="white-space: nowrap;"|1:00pm - 5:00pm
|'''Archivematica and AtoM'''
The afternoon of Day One will be spent looking at how Archivematica integrates with [https://www.accesstomemory.org/en/ AtoM], a widely-used archival description system. This half-day session will be spent exploring Archivematica and AtoM integration, including both present functionality and future possibilities.
|}

'''Note''': participants are welcome to join the morning session, afternoon session, or both sessions as they wish. Participants may also wish to join the Camp on Day Two.

{| border="1" style="border-collapse:collapse;"
|colspan="2"|'''Breakout room'''
|-
|style="white-space: nowrap;"|9:00am - 5:00pm
|'''Advanced Archivematica Drop-In Clinic'''
All day we'll have experts available to help you with your Archivematica problems. No appointment necessary - just drop by with a laptop and a problem and we'll be happy to chat!
|}

=== Wednesday, April 5: Day Two ===

{| border="1" style="border-collapse:collapse;"
|'''Time'''
|'''Main room'''
|'''Breakout room'''
|-
|style="white-space: nowrap;"|9:00am - 9:30am
|colspan="2"|'''Arrival and registration'''
|-
|style="white-space: nowrap;"|9:30am - 9:45am
|colspan="2"|'''Camp orientation'''
|-
|style="white-space: nowrap;"|9:45am - 11:00am
|colspan="2"|'''Workflow and deployment tours'''
To kick off the camp, users of all stripes have the opportunity to show off their current implementations - or to discuss future implementations! If you're interested in discussing how Archivematica works (or might work) in your institution, come prepared with a 5-10 minute informal presentation and/or your questions.
|-
|style="white-space: nowrap;"|11:00am - 11:15am
|colspan="2"|'''Coffee/tea break'''
|-
|style="white-space: nowrap;"|11:15am - 12:00pm
|colspan="2"|'''Metadata deep dive'''
During the Metadata Deep Dive we'll look at how Archivematica creates and handles metadata, focusing on the backbone of an Archivematica AIP: the METS.xml file.
|-
|style="white-space: nowrap;"|12:00pm - 1:00pm
|colspan="2"|Lunch
|-
|style="white-space: nowrap;"|1:30pm - 2:30pm
|'''Specialized workflows'''
Archivematica's specialized transfer types kick off different kinds of workflows within the system. In this session, we'll provide an overview of the transfer types (Standard, Zipped Bag, Unzipped Bag, etc.) and the tools and processes that make these workflows unique.
|'''Technical architecture overview'''
Take a peek under the hood at Archivematica's bones. We'll walk campers through the main technologies and tools that make up Archivematica and talk about the framework that keeps it all together.
|-
|style="white-space: nowrap;"|2:30pm - 3:15pm
|'''Introduction to the Appraisal tab'''
The Appraisal tab is a brand-new addition to Archivematica's user interface. In this session, we'll demo how it currently works and start thinking about ways that it could be extended.
|'''Storage Service management'''
Archivematica works with your storage system through an application called the Storage Service. In this session, we'll talk about how to configure the Storage Service and the different types of storage that work with Archivematica.
|-
|style="white-space: nowrap;"|3:15pm - 3:30pm
|colspan="2"|Agenda adjusting
|-
|style="white-space: nowrap;"|3:30pm - 3:45pm
|colspan="2"|Break
|-
|style="white-space: nowrap;"|3:45pm - 4:30pm
|'''Validation micro-service developments'''
We've been working on file validation! Integrating PREFORMA with Archivematica means that file validation is better than ever. We'll walk you through the new functionality that PREFORMA offers and discuss the integration project.
|'''PREMIS as Linked Data'''
The future is linked - should Archivematica be linked too? We'll talk about how PREMIS 3 might serve long-term goals by providing a linked open data solution for Archivematica.
|-
|style="white-space: nowrap;"|4:30pm - 5:00pm
|colspan="2"|Wrap-up
|}

'''Note on agenda adjusting''': based on camper interest, the schedule may be adjusted to accommodate topics of interest that will be covered during the concurrent sessions.

=== Thursday, April 6: Day Three ===

{| border="1" style="border-collapse:collapse;"
|'''Time'''
|'''Main room'''
|'''Breakout room'''
|-
|style="white-space: nowrap;"|9:00am - 10:15am
|'''Deployment practices for development and production'''
|'''User interface focus group'''
Sure, we can make nice AIPs and DIPs, but is it pretty? This is a chance to chat about the user interface and usability in general, including how integrations with other systems look to the end user.
|-
|style="white-space: nowrap;"|10:15am - 10:45am
|colspan="2"|Coffee/tea break
|-
|style="white-space: nowrap;"|10:45am - 12:00pm
|colspan="2"|'''Automation tools'''
The Automation Tools project is a set of python scripts that are designed to automate the processing of transfers in an Archivematica pipeline. Learn more about installing, configuring and running these scripts for large-scale processing or for pulling in content from other systems such as DSpace.
|-
|style="white-space: nowrap;"|12:00pm - 1:00pm
|colspan="2"|Lunch
|-
|style="white-space: nowrap;"|1:00pm - 2:15pm
|'''Customizing the FPR'''
|'''Research Data Management / Deeper dive into format ID'''
|-
|style="white-space: nowrap;"|2:15pm - 2:45pm
|colspan="2"|'''Concurrent sessions debrief'''
|-
|style="white-space: nowrap;"|2:45pm - 3:00pm
|colspan="2"|Coffee/tea break
|-
|style="white-space: nowrap;"|3:00pm - 4:00pm
|colspan="2"|'''Archivematica roadmap and upcoming developments'''
|-
|style="white-space: nowrap;"|4:00pm - 5:00pm
|colspan="2"|'''Project community and governance talk'''

|}

== Social events ==

=== Tuesday, April 4th: Small group dinners ===

More information forthcoming!

=== Wednesday April 5th: Group social ===

More information forthcoming!

== Local Arrangements ==

=== Hotels ===

There are lots of places to stay in York. Information can be found at [http://www.visityork.org/book/thedms_hotels.aspx?dms=1&at=1&mstat=1&msg=Book+York+Hotels Visit York]. However, we have negotiated a special Archivematica Camp price at two of the York accommodation options that you can book yourself, quoting the booking code. Details below:

==== [https://www.staycity.com/york/paragon-street/ Staycity Aparthotels Paragon Street] ====

We have reserved a block of self-catering rooms at the [https://www.staycity.com/york/paragon-street/ Staycity Aparthotels Paragon Street] for a nightly rate of £74. There are 20 rooms available for attendees who wish to stay from 3-6 April. The hotel is a 15 minute walk to York city centre, and a 15 minute bus ride (10 minute drive, 45 minute walk) to The Ron Cooke Hub. Every room includes with a small kitchenette.

* '''One Bedroom Apartments''': The rooms can accommodate up to 4 people, with a choice of 1 double bed or 2 single beds. There is also a twin sofa bed in the lounge area.

* '''Breakfast''': Price includes a Grab and Go breakfast box.

* '''Car Parking''': There is a Q Park car park located on Kent Street, priced from £11 per 24hours. More information can be found on the following link: http://www.q-park.co.uk/parking/york/q-park-barbican

* '''Booking''': Please note that to book at the preferred rate, you must contact Staycity York directly. Contact information, as well as the booking reference code, will be included in your registration confirmation email. Rooms at this special rate are available on a first come first served basis and must be booked before 27th March in order to qualify for the reduced price.

==== [http://www.queenshotel-york.com/ Queens Hotel] ====

We have reserved a block of double rooms at the [http://www.queenshotel-york.com/ Queens Hotel] for a nightly rate of £68 bed and breakfast. This is a central city centre hotel, next to the river and a short walk from the train station. There are frequent buses between the city centre and The Ron Cooke Hub at Heslington East via the number 4 and UoY66 (allow 30 mins for your journey), or the Ron Cooke Hub can be reached by foot if you have 55 minutes to spare!

* '''Double rooms''': The rooms have a double bed.

* '''Breakfast''': Sit down breakfast in the hotel restaurant facility is included in the price.

* '''Booking''': Please note that to book at the preferred rate, quote the booking code which will be included in your registration confirmation email. Rooms at this special rate are available on a first come first served basis and must be booked before 20th March in order to qualify for the reduced price.

=== Transit ===

Further information about how to find the Ron Cooke Hub are available [https://www.york.ac.uk/hub/directions/ here]

==Code of Conduct==

The Archivematica community is dedicated to providing a welcoming and positive experience for everyone, whether they are in a formal session or a social setting related to an Archivematica event, or are taking part in activities online. Archivematica community participants come from all over the world and bring with them a wide variety of professional, personal and social backgrounds; whatever these may be, we treat colleagues with dignity and respect. We are sensitive to the fact that the international nature of the Archivematica community means that we span many different social norms around language and behaviour and we strive to conduct ourselves in ways that are unlikely to cause offense. In the event that someone’s conduct is causing offense or distress, the Archivematica Camp has a detailed Anti-Harassment Policy, details below, which can be applied to address the problem.

The first step in dealing with any serious misconduct is to contact a member of the organizing group, or a counsellor at an Archivematica Camp (please see counsellors, above). These people will be made known before and during any Archivematica Camp event.

'''Anti-Harassment Policy'''

The Archivematica community is dedicated to providing a harassment-free conference/camp experience for everyone. If you have been harassed, please consult this protocol for conflict resolution which makes clear how we can help.

The Archivematica community has established the following policy to make it clear that we do not tolerate harassment in any form. Sexual or discriminatory language and imagery are not appropriate for any event venue, including talks, or any other communication channel used during the conference (such as social media).

Harassment includes:

* offensive verbal comments related to sex, gender, ethnicity, nationality, socioeconomic status, sexual orientation, disability, physical appearance, body size, age, race, religion;
* sexual or discriminatory images in public spaces;
* deliberate intimidation;
* stalking;
* harassing photography or recording;
* sustained disruption of talks or other events;
* inappropriate physical contact; and
* unwelcome sexual attention.

The lingua franca of Archivematica Camp is English; however, English may not be the native language of Archivematica Camp participants. Further, cultural norms around what may be considered obscene and offensive communication will vary among Archivematica Camp attendees. Campers are asked to please be mindful of the international character of Archivematica Camp, and to use respectful and clear language free of slang to facilitate communication.

Participants asked to stop any harassing behavior are expected to comply immediately.

If a participant engages in harassing behavior, event organizers and Archivematica representatives (or their designees) may take any action they deem appropriate, including warning the offender, expulsion from Archivematica Camp, or contacting a higher authority such as a representative from the offender’s institution.

If a participant raises a concern relating to actions covered by this policy in good faith, there will be no retaliation for bringing forward their concern. Threatening or taking action against someone for invoking this policy or for participating in any related investigation will be considered a violation of this policy.

Participants are expected to follow the anti-harassment policy at all Camp-related venues, Camp-related social events, and online communication channels.

We expect attendees and speakers past and present to be respectful to each other, and we will deal with any incidents that arise, including on social media.

We value your participation in the Archivematica community and your support in keeping the Archivematica community a safe, welcoming, and friendly space for fellow participants.

'''Acknowledgments'''

This policy is based on the [http://www.pasignyc.org/#code-of-conduct-section PASIG Code of Conduct], portions of which were modified from the [http://or2016.net/code-of-conduct/ Open Repositories’ code of conduct], which was itself modified from [https://www.seattleattic.com/codeofconduct Seattle Attic’s code of conduct] and the [http://adainitiative.org/what-we-do/events/ada-initiative-event-anti-harassment-policy/ Ada Initiative’s event harassment policy].

'''License'''

This document is licensed under [https://creativecommons.org/licenses/by-sa/3.0/ Creative Commons BY-SA].