1. MoPark, METS, and More: Managing the Virtual Future in the Loch Lomond and Trossachs National Park - and learning along the way. Presentation to LIDA 2005 Dennis Nicholson, Director Centre for Digital Library Research, University of Strathclyde, Glasgow, Scotland

2. Key focus: Interpretive Journeys, multimedia presentations on story of Park’s landscape, history, culture, flora, fauna

3. Aims wider Not just PDAs: audio-only tours, ‘talking boards’, leaflets, repository of all digital / non-digital resources Aims wider:

4. Overview [1] n Metadata Options Appraisal n Loch Lomond and the Trossachs National Park n Interreg III Mobility and National Parks Project n MoPark n http://www.mopark.net

6. Overview [2] n About MoPark and the MOA n MOA to MOA Phase1 (and why) n A look at an Interpretive Journey n Why METS, Rest of the framework n DAMS Version #1 n Next Steps n Experiment and Learn

7. The best laid plans… n Plan: 8.5 days MOA to feed into: u DAMS design, creation; Create metadata; Manage repository n Reality: Longer, phased MOA: u Lifetime of MoPark; METS-based framework feeding DAMS design and framing detailed MOA n But overall plan vindicated

8. Current State of Play n Metadata Options Appraisal: u Early work (Phase I) established the need for a phased approach u Phase I complete:  Framework based on METS agreed  Outline requirements for DAMS as regards metadata handling established u Phase II (specifying the detailed requirement) in early stages  Examples of real IJs now exist

9. Metadata Options Appraisal n Requirement: u To examine – and make recommendations on - the needs of the Loch Lomond and Trossachs National Park as regards the metadata, metadata standards, and metadata management required for the competent handling of digital materials both now and in the future. u To cover three levels of need: MoPark project (Level 1); Extension to other topics and Park areas (Level 2); Wider Park beyond MoPark (Level 3)

10. What we found: n Sufficient detail available to enable the general needs of the project and Park in respect of digital object metadata and DAMS functionality to be specified. n Specifying the need in detail more difficult at this stage – the need for a phased approach

11. Why a phased approach? n A need for: u A detailed examination of actual interpretive journeys; components u More staff experience of the associated issues and problems u An in-depth survey other digital objects, their usage, life-cycles.

12. Phased Approach… n Phase 1: u Would set out a framework within which the full requirement could develop u Propose a flexible development path to facilitate the determination of the full requirement n Phase II u Would implement the development path

13. Framework n Three elements: u Adopt METS Metadata Encoding and Transmission Standard u Adopt national and international standards relevant to the field. u Cooperate with other key players on inter-repository interoperability

14. Early Stages of Phase II n Have, are following the framework and the flexible development plan n Have initial METS-based DAMS n Have initial decisions on some attributes and have populated the DAMS with them n Have real IJs, components, and structures; the rest is detail but…

15. Why METS?; Feel for an Interpretive Journey Inchcailloch – an island on Loch Lomond Cover page of 1 st Interpretive Journey; controls

16. Map of Inchcailloch, click-able option throughout, possible to zoom then navigate, key, challenges, METS

17. G FE D C B 4 2 x 7 6 5 x x x INCHCAILLOCH CLAIRINSH The Kitchen BALMAHA PIER Figure 1: Schematic diagram illustrating Inchcailloch journey Numbers refer to interpretive points on plan A H Journeys; Stops; Joint stops; different start + end points, Solar boat

18. Stop features: Highland boundary fault; animated GIF; audio

19. Once upon a time; dropdowns of animals and sounds, guess the animal from the sound etc

20. History and industry

21. Plus: Videos, animations, games, 3D maps and more Etc.

22. Why METS? n METS: u Designed for complex digital objects u Provides for all of the metadata types likely to be required within MoPark and (in time) the Park generally u Sufficiently flexible to allow it to meet the detailed requirements drawn out in Phase II of the appraisal. u Provides a good guide to the areas we need to address

23. METS Overview; Details; all the metadata types needed

24. Why METS? n METS provides for: u Descriptive metadata (MARC, Dublin Core etc) at both individual object and composite (i.e. Interpretive Journey) level, u Administrative metadata (technical metadata, rights metadata, analogue source information, digital object files provenance), u Files metadata (for files containing content which comprise the electronic versions of the digital object)

25. Why METS? n METS provides for: u Structural Map metadata to outline the hierarchical structure of a digital library object such as an Interpretive Journey u Structural Links metadata to allow recording of links between hierarchical levels u Behaviour metadata to allow metadata on ‘executable behaviours’ to be encoded

26. Why METS? n A Safe Path… u METS framework provides for all of the complex issues faced by MoPark; the Park u It is supported or recognised as important by groups like L of C, JISC, Digital Library Federation, British Library, SLIC u A DAMS built round METS (and MoPark) ought to be flexible enough to meet future Park needs in areas such as FoI, Maps, IPR handling, Educational packages, promotional materials control, outreach

27. Screen to enter metadata categories, sub-categories, attributes etc

28. Screen to enter asset types – images, videos, IJ, IJ stops; also composite or not, metadata categories & associated file types

29. Component objects, buttons for approval process – legality, metadata quality, and so on

30. Composite objects: stops, full journeys

31. Screen to enter IJ metadata; most METS top levels

32. Screen to enter descriptive IJ metadata

33. Screen to enter IPR and structural map IJ metadata (still embryonic)

34. What’s next? n Refining the metadata requirement for IJs and other materials – still a major task; finalising descriptions n Writing a procedures and training manual; metadata content standards n Improving DAMS functionality and ergonomics n Identifying huge amount of work that needs to be done in future

35. MoPark: Experiment & Learn n MoPark didn’t go to plan at MOA level n However, the high-level plan was to use the project to experiment and learn – which is what they have done in the metadata area n A good example of how projects can be valuable preliminaries to major organisational commitments

36. Further Information n METS website is at http://www.loc.gov/standards/mets/. http://www.loc.gov/standards/mets/ n Contact: d.m.nicholson@strath.ac.ukd.m.nicholson@strath.ac.uk n CDLR: http://cdlr.strath.ac.uk/http://cdlr.strath.ac.uk/

37. Questions?