TRAC2 Criteria
| Who's working on it? | Approved
| Proofread
| Comments
|
---|
3.1 Governance & Organizational Viability
| Aurianne, Karl, Other | | | |
3.1.1 Mission statement
|
|
|
| |
3.1.2 Preservation strategic plan
| |
|
| |
3.1.2.1 Succession, contigency, escrow plans
| |
|
| |
3.1.2.2 Monitor environment for time to deploy succession,contingency, escrow
| |
|
| |
3.1.3 Collection policy
| |
|
| |
3.2 Organizational Structure & Staffing
| | | | |
3.2.1 Identified duties and appointed staff
| |
| | |
3.2.1.1 Identified and established duties
| |
| | |
3.2.1.2 Appropriate number of staff
| |
| | |
3.2.1.3 Professional development program
| |
| | |
3.3 Procedural Accountability and Preservation Policy Framework
| | | | |
3.3.1 Designated community
| | | | |
3.3.2 Preservation policies
| | | | |
3.3.2.1 Review and update presevation policies
| | | | |
3.3.3 Documented history of changes
| | | | |
3.3.4 Commit to transparency
| | | | |
3.3.5 Information integrity measurements
| | | | |
3.3.6 Self-assessment and external certification
| | | | |
3.4 Financial Sustainability
| | | | |
3.4.1 Business planning processes
| | | | |
3.4.2 Financial transparency, compliance, and audits
| | | | |
3.4.3 Risk, benefit, investment, expenditure
| | | | |
3.5 Contracts, Licenses, & Liabilities
| | | | |
3.5.1 Contracts or deposit agreements for content
| | | | |
3.5.1.1 Contracts or deposit agreements forpreservation rights
| | | | |
3.5.1.2 Completeness of agreements with depositors
| | | | |
3.5.1.3 Policies about preservation responsibility
| | | | |
3.5.1.4 Policies about liability and rights challenges
| | | | |
3.5.2 Track and manage property rights/restrictions
| | | | |
4.1 Ingest - acquisition of content
| | | | |
4.1.1 Identify content information and information properties
| |
| | |
4.1.1.1 Procedures for identifying information properties that we will preserve
| | | | |
4.1.1.2 Record of content information and information properties that we will preserve
| | | | |
4.1.2 Specifiy content information at deposit
| | | | |
4.1.3 Recognition and parsing of SIPs
| | | | |
4.1.4 Verify the identity of the Producer
| | | | |
4.1.5 Verify SIPs for completeness and correctness
| | | | |
4.1.6 Obtain sufficient control over digital objects
| | | | |
4.1.7 Provide depositor with responses
| | | | |
4.1.8 Records of actions and processes related to acquisition
| | | | |
4.2 Ingest - creation of the AIP
| | | | |
4.2.1Associated definitionfor the AIP )The repository shall have for each AIP or class of AIPs preserved by the repositoryan associated definitionthat is adequate for parsing the AIP and fit for long-term preservation needs.[] | | | | |
4.2.1.1 Identify which definition applies to which AIP | | | | |
4.2.1.2 Definition of each AIP that is adequate for long-term preservation | | | | |
4.2.2 Description of how AIPs are constructed from SIPs | | | | |
4.2.3 Document the final disposition of all SIPs | | | | |
4.2.3.1 If a SIP is not incorporated into an AIP or discarded | | | | |
4.2.4 Convention that generates persistent, unique identifiers for all AIPs | | | | |
4.2.4.1 Uniquely identify each AIP within the repository | | | | |
4.2.4.1.1 The repository shall have unique identifiers | | | | |
4.2.4.1.2 Assign and maintain persistent identifiers of the AIP | | | | |
4.2.4.1.3 Describe any processes used for changes to identifiers | | | | |
4.2.4.1.4 Provide list of all identifiers and check for duplications | | | | |
4.2.4.1.5 System of identifiers shall be adequate to fit the repository’s current and foreseeable future requirements | | | | |
4.2.4.2 System of reliable linking/resolution services | | | | |
4.2.5 Tools and resources to provide authoritative Representation Information for all digital objects | | | | |
4.2.5.1 Tools or methods to identify the file type | | | | |
4.2.5.2 Tools or methods to determine what Representation Information is necessary to make each Data Object understandable | | | | |
4.2.5.3 Access to the requisite Representation Information | | | | |
4.2.5.4 Tools or methods to ensure that the requisite Representation Information is persistently associated with the relevant Data Objects | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |