Lightening talks

Each delegate will be asked to present a 5 minute lightening talk at the start of Day 1 as an ice-breaker to the unconference on a pre-prepared subject of their choice

Proposed topics

In addition to a 5 minute lightening talk (see above) we also encourage everybody to make suggestions about proposed topics this could be:

• topics you would like to discuss in more detail with the group - eg a problem (or a solution) you have encountered 
• an aspect of your work that you would like to share with the group (please bring examples of workflow, documentation etc with you
• a tool or piece of software that you would like to demonstrate to the group (please ensure that you are able to bring a laptop with you with the appropriate software etc on
• a topic they would like to learn more about
• the deadline for this is Friday 29th April - we will then turn this into a list and ask people to indicate their preferences/interests ahead of the event and use this to shape the discussions 

In each please explain your level of knowledge or experience and comment on the proposals 

1. Simon Wilson, Hull University (AIMS Project)  
   I would like to ....
2. Tom Laudeman, University of Virginia (AIMS Project)
   I would like to demonstrate Rubymatica and discuss issues related to processing of files to make them suitable for a Submission Information Package (SIP). I am the author of Rubymatica. It is a Ruby port of the SIP creation phase of Archivematica. My efforts were supported by the AIMS team, especially the digital archivists. (Many thanks to the Archivematica people for blazing the trail.) A key question is: How much processing should we do before initial assessment? The demo will fit in 5 minutes, but the discussion could last much longer.
3. Tom Laudeman, University of Virginia (AIMS Project)
   I would like to talk about minimum requirements for a Linux server to host modern web applications. The point of this talk would be to share typical low-end costs, and then to gather feedback from technology consumers (Librarians and Archivists). This is possible on commodity (off the shelf) computers, even decent laptops. However, the process is easier if there are software developers and system administrators on the team. It is also important to understand that the Total Cost of Ownership (TCO) of software and hardware goes beyond purchase price.