Presentation on theme: "Platter Planning Tool For Trusted Electronic Repositories"— Presentation transcript:
1Platter Planning Tool For Trusted Electronic Repositories Meeting the challenge of technological changeDeveloping Trust
2Repositories How of you knows how to make a repository? How of you knows how to make a trustworthy repository?What is trust?
3What Is Trust? Trust is demonstrated fitness for purpose Trust must be achievedTrust must be demonstratedTrust must be maintainedPlatter achieves this in combination with auditing tools such as DRAMBORA, nestor and CRL/TRAC
4From Platter to TrustThere is no any internationally recognized authority for certifying repositoriesCriteria for Trust should be established with the stakeholdersCould be passing an audit
5From Platter to TrustThe Strategic Objective Plans have largely been created from the requirements from Nestor and TRAC checklistFollowing PLATTER covers all the major points from these checklistsThe documentation strategy in Platter corresponds well to DRAMBORAThe availability of all the documentation will make a DRAMBORA audit much easier
8Axis 1: Purpose & Function Where does your mandate come from?Self definedAre you a profit-making body?Non profitAre you an existing or new organisation?Not running yet
9Axis 2: Scale of Repository What amount of digital materials do you archive?Expect to archive 10 GB per yearHow many digital objects?Expect to archive 100 new games per yearHow many staff do you (expect to) employ5 people, but all part timeHow many users1000 users per year
10Axis 3: Operation How do you acquire material? Content is uploaded by usersHow complex are your data?Highly complex, programs from many platformsHow specialised are your data?Require some education to use, but not much.How sensitive are your data?All content in public domainWhat are the access rights?Open for all
11Axis 4: Technical Implementation What is the source of your metadata?Added along with the content, or by wiki styleWhich interoperability standards do the repository employ?Atom feeds for metadata harvesting.Which storage strategy do you use?InhouseWhich stragety is used for software management?Open source with community
14Broad organisational focus Function and Goals Basis for detailed planning1. What do we do?2. Who do we do it for?3. How can we excel?Responses to these three questions organisations will encapsulate the repository's mandate (orreference a non-self imposed, e.g., legislative mandate), detail the identities and broad expectations ofprimary stakeholders and describe in general, but tangible terms, the circumstances and performancelevels that will represent success.
15Platter Stage 2: The Planning Cycle Formulating the Strategic Objective Plans
16Platter Stage 2: The Planning Cycle Implementing your objectives
17Platter Stage 2: The Planning Cycle Reflection and ReformulationReview and Reimplementation
18Platter Stage 3: The Strategic Objective Plans Self-defined objectivesAll areas of repository operationCyclic planning process
20Strategic Objective Plans Business PlanFinancial planning, monitoring, and reportingStaffing PlanAcquisition and maintenance of relevant skillset for managing repositoryData PlanSpecification of data and metadata objects, formats, and structures for ingest, storage, and dissemination, together with the relevant transformations and mappings
21Strategic Objective Plans Acquisition PlanManagement of the relationship with depositors and other data providers. Appraisal policyAccess PlanManagement of relationship with end users. Access Policy.Preservation PlanEnsure that the access and usability of material in repository is not adversely affected by technological change and obsolescence
22Strategic Objective Plans Technical System PlanSpecifies goals for hardware, software and networkingSuccession PlanManage obligation to ensure preservation of material beyound the lifetime of the repositoryDisaster PlanRespond the rapid changes to the repository enviroment
23Access Plan – An example Create, Maintain and Review a Mission Statement which reflects the Repositorys mandateOur 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
24Access Plan – An example Develop and maintain a definition and understanding of your Designated CommunitiesFirst 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
25Access Plan – An example Create and implement a Repository Access PolicyThe 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
26Access Plan – An example Specify and fulfill technical requirements for dissemination and accessRepository should have a webpage, and contents should be available for download.A basic search system should allow for resource discoveryThe webpage should be search engine friendlyMetadata should not be downloadable, only online accessible.
27Staffing planDelineate roles, responsibilities and authorizations of repository staffAcquire and maintain adequate staffing to fulfill specified rolesMaintain staff skills
28Succesion PlanThe preservation tasks is ensured even beyond the existence of the digital repository
29Preservation PlanRepository must maintain understanding of contemporary and emerging hardware software and storage technologiesRepository must maintain understanding of all structural (e.g. file encoding) standards and formatsRepository must maintain understanding of identified user communities and their associated competences and knowledge base
30Preservation PlanRepository must maintain understanding of preservation requirements for each stored information asset or class of informationRepository must maintain, exercise and evaluate preservation strategies capable of meeting specific preservation targetsRepository must maintain and exercise appropriate appraisal policies to determine which information must continue to be preserved
33This work is licensed under the Creative Commons Attribution 2 This work is licensed under the Creative Commons Attribution 2.5 Denmark License. To view a copy of this license, visit r send a letter to Creative Commons, 171 Second Street, Suite 300, San Francisco,California, 94105, USA.