1. Joachim Rausch 13.05.2011 BET– The preservation-planning tool of the Federal Archives - DLM-Forum, Budapest, May 2011

2. Joachim Rausch The Federal Archives: Introduction Koblenz(Headquarter) 1952 Foundation ~ 800 Staff members 7 Departments in 9 Locations 300 km archived paper materials 12 million photos (analog) …. Since 1970 (1990) Electronic materials

3. Joachim Rausch Law on the Preservation and Use of Federal Archival Documents (Bundesarchivgesetz - BArchG) …...have the legal responsibility of permanently preserving the federal archival documents and making them available for use. …...This includes documents (files, papers, cartographic records, pictures, posters, films, sound recordings and machine-readable data) arising from the central institutions of ……the German Democratic Republic (1949-1990) and the Federal Republic of Germany (since 1949).

4. Joachim Rausch Administration / Agencies: reords or document management systems “Digital Archiv”: Challenge / Initial Situation in 2006 Interfaces: variety of metadata and document formats ? LegalBasisBArchG § 2 DOMEASERVISkompaktFabasoftMACHindividual solutions [...]

5. Joachim Rausch Productive Solution since 2008 - Objecttype „EAkte“ DMS-Disposal-module DMS-Systems File-Systems „DigitalesArchiv“ XBARCH Mapping (Mapping) Structuring-Editor

6. Joachim Rausch SIP‏ Preservation Planning‏ INGEST Archival Storage‏ Data Management ‏ ACCESS‏ Administration ‏ DIP ‏ AIPAIP Workflow component Archiving component OAIS-Model ?

7. Joachim Rausch Tool – Drivers and Goals DRIVERS  Regular Changes in organization (people) and Technology Many sources of information about preservation have to be monitored Fragmented documentation GOALS  Apply an operational organization (Aufbauorganisation) versus project organization (Projektorganisation) Going from project oriented operation (Projektorientiert) to normal operation (Regelbetrieb) Monitoring of all aspects by using different information sources Preservation from a solution based view

8. Joachim Rausch digital preservation-lifecycle (Realisation) (Planning) (Status Quo – Preservation Planning) (Alert) (Properties)

9. Joachim Rausch Architecture Generally  Browser-based Tool Server: Webserver/Servlet-Engine  Tomcat Database /Persistence Layer  Oracle 11g / Hibernate Document-Repository  Apache Jackrabbit Client: Java-Runtime-Environment (JRE) 1.6

10. Joachim Rausch Overview Main-Tabs

11. Joachim Rausch Tab „Status Quo“ – List of all themes

12. Joachim Rausch Tab „Status Quo“ – Detail-Mask

13. Joachim Rausch Tab „Monitoring“ – List of monitored and activated themes

14. Joachim Rausch Tab „Monitoring“ – Detail Mask

15. Joachim Rausch Tab „Monitoring“ – List of monitored themes

16. Joachim Rausch Tab „Monitoring“ – Detail Mask Alert

17. Joachim Rausch Tab „Planning“ – List of Alerts

18. Joachim Rausch Tab „Planning“ – Detail Mask Plan 1

19. Joachim Rausch Tab „Planning“ – Detail Mask Plan 2

20. Joachim Rausch Tab „Planning“ – List of Plans

21. Joachim Rausch Tab „Planning“ – Detail Mask Realisation

22. Joachim Rausch Tab „Realisation“ – List of Realisations

23. Joachim Rausch Tab „Monitoring“ – List of monitored themes

24. Joachim Rausch Tab „History“

25. Joachim Rausch Next steps Going Live in autumn 2011 Documentation of all solution aspects (Status Quo) and establishing of the monitoring Future features that are in evaluation right now: Sources for monitoring: internet (e.g. Google Alert for Links), control center with report information about the digital fonds Dashboard

26. Joachim Rausch Thank you for your kind attention! Contact: a.haenger@bundesarchiv.de j.rausch@bundesarchiv.de