Platter Planning Tool For Trusted Electronic Repositories

1
PlatterPlanning Tool For Trusted Electronic
Repositories

• Meeting the challenge of technological change
• Developing Trust
• WePreserve 2009

2
What is Platter

• Developed by the DPE in 2008 by Colin Rosenthal
  and associates
• Platter is a guide to making a new repository or
  archive
• The future of Platter is linked with the future
  of DPE and/or DRAMBORA

3
What Is Trust?

• 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

4
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

5
The components of Platter

• Repository Classification
• The Platter Planning Cycle
• Strategic Objective Planning

6
Platter Stage 1 Classifying Your Repository

7
Axis 1 Purpose Function

• Where does your mandate come from?
• Are you a profit-making body?
• Are you an existing or new organisation?

8
Axis 2 Scale of Repository

• What amount of digital materials do you archive?
• How many digital objects?
• How many staff do you (expect to) employ
• How many users

9
Axis 3 Operation

• How do you acquire material?
• How complex are your data?
• How specialised are your data?
• How sensitive are your data?
• What are the access rights?

10
Axis 4 Technical Implementation

• What is the source of your metadata?
• Which interoperability standards do the
  repository employ?
• Which storage strategy do you use?
• Which stragety is used for software management?

11
Platter Stage 1 Classifying Your Repository

12
Platter Stage 2 The Planning Cycle
13

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

14
Platter Stage 2 The Planning Cycle
15
Platter Stage 2 The Planning Cycle
16
Platter Stage 2 The Planning Cycle
17
Platter Stage 3 The Strategic Objective Plans

• Self-defined objectives
• All areas of repository operation
• Cyclic planning process

18
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

19
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

20
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

21
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

22
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

23
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

24
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.

25
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
26

• Visit Platter at
• http//www.digitalpreservationeurope.org/platter/

27

• 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.