Platter Planning Tool For Trusted Electronic Repositories Meeting the challenge of technological change Developing Trust.

PlatterPlanning Tool For Trusted Electronic Repositories

Meeting the challenge of technological changeDeveloping Trust

Repositories

How of you knows how to make a repository?

How of you knows how to make a trustworthy repository?

What is trust?

What Is Trust?Trust is demonstrated fitness for purpose

Trust must be achievedTrust must be demonstratedTrust must be maintained

Platter achieves this in combination with auditing tools such as DRAMBORA, nestor and CRL/TRAC

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

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

The components of Platter

Repository Classification

The Platter Planning Cycle

Strategic Objective Planning

Platter Stage 1: Classifying Your Repository

Function

ScaleOperation

Implementation

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

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

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

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

Platter Stage 1: Classifying Your Repository

Function

ScaleOperation

Implementation

Platter Stage 2: The Planning Cycle

Broad organisational focus

Function and Goals

Basis for detailed planning

Platter Stage 2: The Planning Cycle

Formulating the Strategic Objective Plans

Platter Stage 2: The Planning Cycle

Implementing your objectives

Platter Stage 2: The Planning Cycle

Reflection and Reformulation

Review and Reimplementation

Platter Stage 3: The Strategic Objective Plans

Self-defined objectivesAll areas of repository operationCyclic planning process

The Ten Core Principles

Commitment

Fitness

Rights

Policies

Acquisition

Data Integrity

Metadata

Dissemination

Preservation

Infrastructure

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

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

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

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

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

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

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.

Staffing plan

Delineate roles, responsibilities and authorizations of repository staff

Acquire and maintain adequate staffing to fulfill specified roles

Maintain staff skills

Succesion Plan

The preservation tasks is ensured even beyond the existence of the digital repository

Ten Core PrinciplesTen Core Principles

BusinessBusinessPlanPlan

StaffingStaffingPlanPlan

DisasterDisasterPlanPlan..........................

Realisation

Reformulation Review

Business ActionsGoals

Staffing ActionsGoals

Disaster ActionsGoals

RepositoryCharacterisation

RepositoryProfile

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

This work is licensed under the Creative Commons Attribution 2.5 Denmark

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