1 / 31

Platter Pla nning T ool For T rusted E lectronic R epositories

Meeting the challenge of technological change Developing Trust. Platter Pla nning T ool For T rusted E lectronic R epositories. Repositories. How of you knows how to make a repository? How of you knows how to make a trustworthy repository? What is trust?.

maite-phelps
Download Presentation

Platter Pla nning T ool For T rusted E lectronic R epositories

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Meeting the challenge of technological change Developing Trust PlatterPlanning Tool For Trusted Electronic Repositories

  2. Repositories • How of you knows how to make a repository? • How of you knows how to make a trustworthy repository? • What is trust?

  3. Trust is demonstrated fitness for purpose Trust must be achieved Trust must be demonstrated Trust must be maintained Platter achieves this in combination with auditing tools such as DRAMBORA, nestor and CRL/TRAC What Is Trust?

  4. From Platter to Trust • There is no any internationally recognized authority for certifying repositories • Criteria for Trust should be established with the stakeholders • Could be passing an audit

  5. From Platter to Trust • The Strategic Objective Plans have largely been created from the requirements from Nestor and TRAC checklist • Following PLATTER covers all the major points from these checklists • The documentation strategy in Platter corresponds well to DRAMBORA • The availability of all the documentation will make a DRAMBORA audit much easier

  6. The components of Platter • Repository Classification • The Platter Planning Cycle • Strategic Objective Planning

  7. Platter Stage 1: Classifying Your Repository

  8. Axis 1: Purpose & Function • Where does your mandate come from? • Self defined • Are you a profit-making body? • Non profit • Are you an existing or new organisation? • Not running yet

  9. Axis 2: Scale of Repository • What amount of digital materials do you archive? • Expect to archive 10 GB per year • How many digital objects? • Expect to archive 100 new games per year • How many staff do you (expect to) employ • 5 people, but all part time • How many users • 1000 users per year

  10. Axis 3: Operation • How do you acquire material? • Content is uploaded by users • How complex are your data? • Highly complex, programs from many platforms • How specialised are your data? • Require some education to use, but not much. • How sensitive are your data? • All content in public domain • What are the access rights? • Open for all

  11. Axis 4: Technical Implementation • What is the source of your metadata? • Added along with the content, or by wiki style • Which interoperability standards do the repository employ? • Atom feeds for metadata harvesting. • Which storage strategy do you use? • Inhouse • Which stragety is used for software management? • Open source with community

  12. Platter Stage 1: Classifying Your Repository

  13. Platter Stage 2: The Planning Cycle

  14. Broad organisational focus • Function and Goals • Basis for detailed planning

  15. Platter Stage 2: The Planning Cycle • Formulating the Strategic Objective Plans

  16. Platter Stage 2: The Planning Cycle • Implementing your objectives

  17. Platter Stage 2: The Planning Cycle • Reflection and Reformulation • Review and Reimplementation

  18. Self-defined objectives All areas of repository operation Cyclic planning process Platter Stage 3: The Strategic Objective Plans

  19. The Ten Core Principles

  20. Strategic Objective Plans • Business Plan • Financial planning, monitoring, and reporting • Staffing Plan • Acquisition and maintenance of relevant skillset for managing repository • Data Plan • Specification of data and metadata objects, formats, and structures for ingest, storage, and dissemination, together with the relevant transformations and mappings

  21. Strategic Objective Plans • Acquisition Plan • Management of the relationship with depositors and other data providers. Appraisal policy • Access Plan • Management of relationship with end users. Access Policy. • Preservation Plan • Ensure that the access and usability of material in repository is not adversely affected by technological change and obsolescence

  22. Strategic Objective Plans • Technical System Plan • Specifies goals for hardware, software and networking • Succession Plan • Manage obligation to ensure preservation of material beyound the lifetime of the repository • Disaster Plan • Respond the rapid changes to the repository enviroment

  23. Access Plan – An example • Create, Maintain and Review a Mission Statement which reflects the Repositorys mandate • Our mission is to provide a trustworthy archive for the games developed for the early computer platforms. Games in the public domain should be made available to the public, while protected games should be held until such a time where the license is no longer valid. • This mission statement should be reviewed each year

  24. Access Plan – An example • Develop and maintain a definition and understanding of your Designated Communities • First community is people who remember the games, and would like to reexperience them. The target community is quite large, but shrinking, and extremely diverse. They are technical skilled, but will expect detailed instructions on how to get the games working. They will not expect to be able to access games that they have no memory of. • The designated community definition should be reviewed every 6 months

  25. Access Plan – An example • Create and implement a Repository Access Policy • The repository handles to kinds of material, those in the public domain, and those that are not. All public domain material should be freely available. • There should be a complaints mailbox for take-down notices and other legal problems. Material should be taken down within 24 hours, and without negotiation. • Access to material should always be granted, until complaints are recieved

  26. Access Plan – An example • Specify and fulfill technical requirements for dissemination and access • Repository should have a webpage, and contents should be available for download. • A basic search system should allow for resource discovery • The webpage should be search engine friendly • Metadata should not be downloadable, only online accessible.

  27. Staffing plan • Delineate roles, responsibilities and authorizations of repository staff • Acquire and maintain adequate staffing to fulfill specified roles • Maintain staff skills

  28. Succesion Plan • The preservation tasks is ensured even beyond the existence of the digital repository

  29. Ten Core Principles Repository Characterisation Business Plan Staffing Plan Disaster Plan Repository Profile .......................... Business Actions Goals Staffing Actions Goals Disaster Actions Goals Realisation Reformulation Review

  30. Visit Platter at: http://www.digitalpreservationeurope.org/platter/

  31. This work is licensed under the Creative Commons Attribution 2.5 DenmarkLicense. To view a copy of this license, visithttp://creativecommons.org/licenses/by/2.5/dk/ or send a letter toCreative Commons, 171 Second Street, Suite 300, San Francisco, • California, 94105, USA.

More Related