Uncategorized pages

Jump to: navigation, search

Showing below up to 139 results starting with #1.

View (previous 500 | next 500) (20 | 50 | 100 | 250 | 500)

  1. 3) Organizational Infrastructure
  2. 3.1.1 Mission statement
  3. 3.1.2.1 Succession, contigency, escrow plans
  4. 3.1.2.2 Monitor environment for time to deploy succession, contingency, escrow
  5. 3.1.2 Preservation strategic plan
  6. 3.1.3 Collection policy
  7. 3.2.1.1 Identified and established duties
  8. 3.2.1.2 Appropriate number of staff
  9. 3.2.1.3 Professional development program
  10. 3.2.1 Identified duties and appointed staff
  11. 3.3.1 Designated community
  12. 3.3.2.1 Review and update preservation policies
  13. 3.3.2 Preservation policies
  14. 3.3.3 Documented history of changes
  15. 3.3.4 Commit to transparency
  16. 3.3.5 Information integrity measurements
  17. 3.3.6 Self-assessment and external certification
  18. 3.4.1 Business planning processes
  19. 3.4.2 Financial transparency, compliance, and audits
  20. 3.4.3 Risk, benefit, investment, expenditure
  21. 3.5.1.1 Contracts or deposit agreements for preservation rights
  22. 3.5.1.2 Completeness of agreements with depositors
  23. 3.5.1.3 Policies about preservation responsibility
  24. 3.5.1.4 Policies about liability and rights challenges
  25. 3.5.1 Contracts or deposit agreements for content
  26. 3.5.2 Track and manage property rights/restrictions
  27. 4) Digital Object Management
  28. 4.1.1.1 Procedures for identifying information properties that we will preserve
  29. 4.1.1.2 Record of content information and information properties that we will preserve
  30. 4.1.1 Identify content information and information properties
  31. 4.1.2 Specify content information at deposit
  32. 4.1.3 Recognition and parsing of SIPs
  33. 4.1.4 Verify the identity of the Producer
  34. 4.1.5 Verify SIPs for completeness and correctness
  35. 4.1.6 Obtain sufficient control over digital objects
  36. 4.1.7 Provide depositor with responses
  37. 4.1.8 Records of actions and processes related to acquisition
  38. 4.2.1.1 Identify which definition applies to which AIP
  39. 4.2.1.2 Definition of each AIP
  40. 4.2.10 Contemporaneous records of actions and administration processes relevant to AIP creation
  41. 4.2.1 Associated definition for each AIP or class of AIPs
  42. 4.2.2 Description of how AIPs are constructed from SIPs
  43. 4.2.3.1 Procedures if a SIP is not incorporated or discarded
  44. 4.2.3 Document final disposition of all SIPs
  45. 4.2.4.1.1 Have unique identifiers
  46. 4.2.4.1.2 Assign and maintain persistent identifiers of the AIP and its components
  47. 4.2.4.1.3 Describe any processes for changes to identifiers
  48. 4.2.4.1.4 Provide a list of all identifiers and check for duplications
  49. 4.2.4.1.5 System of identifiers is adequate now and in the future
  50. 4.2.4.1 Uniquely identify each AIP
  51. 4.2.4.2 System of reliable linking/resolution services in order to find identified objects
  52. 4.2.4 Convention that generates persistent, unique identifiers for AIPs
  53. 4.2.5.1 Tools or methods to identify the file types of all objects
  54. 4.2.5.2 Tools or methods to determine what Representation Information is necessary for understandability
  55. 4.2.5.3 Have access to the requisite Representation Information
  56. 4.2.5.4 Tools or methods to ensure that Representation Information is persistently associated with objects
  57. 4.2.5 Tool and resources to provide authoritative Representation Information for all objects
  58. 4.2.6.1 Documented processes for acquiring PDI
  59. 4.2.6.2 Execute documented processes for acquiring PDI
  60. 4.2.6.3 PDI is persistently associated with Content Information of AIP
  61. 4.2.6 Documented processes for acquiring PDI for associated Content Information
  62. 4.2.7.1 Processes for testing understandability for Designated Community of the Content Information of AIPs
  63. 4.2.7.2 Execute testing process of Content Information of AIPs
  64. 4.2.7.3 Bring Content Information of AIP up to level of understandability if it fails testing
  65. 4.2.7 Content Information is understandable for Designated Community at the time of AIP creation
  66. 4.2.8 Verify each AIP for completeness and correctness
  67. 4.2.9 Independent mechanism for verifying the integrity of the content
  68. 4.3.1 Documented preservation strategies relevant to its holdings
  69. 4.3.2.1 Mechanisms for monitoring and notification when Representation Information is inadequate for the Designated Community to understand the data holdings
  70. 4.3.2 Mechanisms for monitoring its preservation environment
  71. 4.3.3.1 Mechanisms for creating, identifying or gathering any extra Representation Information required
  72. 4.3.3 Mechanisms to change preservation plans as a result of its monitoring activities
  73. 4.3.4 Provide evidence of the effectiveness of its preservation activities
  74. 4.4.1.1 Preserve the Content Information of AIPs
  75. 4.4.1.2 Actively monitor the integrity of AIPs
  76. 4.4.1 Specifications for how the AIPs are stored down to the bit level
  77. 4.4.2.1 Procedures for all actions taken on AIPs
  78. 4.4.2.2 Demonstrate that any actions taken on AIPs were compliant with the specification of those actions
  79. 4.4.2 Contemporaneous records of actions and administration processes that are relevant to storage and preservation of the AIPs
  80. 4.5.1 Specify minimum information requirements to enable the Designated Community to discover and identify material
  81. 4.5.2 Capture or create minimum descriptive information for each AIP
  82. 4.5.3 Create bi-directional linkages between each AIP and its descriptive information
  83. 4.6.1.1 Log and review all access management failures and anomalies
  84. 4.6.1 Comply with Access Policies
  85. 4.6.2.1 Record and act upon problem reports about errors in data and responses from users
  86. 4.6.2 Follow policies and procedures that enable the dissemination of digital objects that are traceable to the originals
  87. 5) Infrastructure and Security Risk Management
  88. 5.1.1.1.1 Hardware technologies appropriate to the services it provides to its designated communities
  89. 5.1.1.1.2 Procedures in place to monitor and receive notifications when hardware technology changes are needed
  90. 5.1.1.1.3 Procedures in place to evaluate when changes are needed to current hardware
  91. 5.1.1.1.4 Procedures, commitment and funding to replace hardware when evaluation indicates the need to do so
  92. 5.1.1.1.5 Software technologies appropriate to the services it provides to its designated communities
  93. 5.1.1.1.6 Procedures in place to monitor and receive notifications when software changes are needed
  94. 5.1.1.1.7 Procedures in place to evaluate when changes are needed to current software
  95. 5.1.1.1.8 Procedures, commitment and funding to replace software when evaluation indicates the need to do so
  96. 5.1.1.1 Employ technology watches or other technology monitoring notification systems
  97. 5.1.1.2 Adequate hardware and software support for backup functionality sufficient for preserving the repository content and tracking repository functions
  98. 5.1.1.3.1 Record and report to its administration all incidents of data corruption or loss, and steps shall be taken to repair/replace
  99. 5.1.1.3 Effective mechanisms to detect bit corruption or loss
  100. 5.1.1.4 Process to record and react to the availability of new security updates based on a risk-benefit assessment
  101. 5.1.1.5 Defined processes for storage media and/or hardware change (e.g., refreshing, migration)
  102. 5.1.1.6.1 Documented change management process that identifies changes to critical processes that potentially affect the repository's ability to comply with its mandatory responsibilities
  103. 5.1.1.6.2 Process for testing and evaluating the effect of changes to the repository's critical processes
  104. 5.1.1.6 Identified and documented critical processes that affect its ability to comply with its mandatory responsibilities
  105. 5.1.1 Identify and manage the risks to its preservation operations and goals associated with system infrastructure
  106. 5.1.2.1 Mechanisms in place to ensure any/multiple copies of digital objects are synchronized
  107. 5.1.2 Manage the number and location of copies of all digital objects
  108. 5.2.1 Maintain a systematic analysis of security risk factors associated with data, systems, personnel, and physical plant
  109. 5.2.2 Implemented controls to adequately address each of the defined security risks
  110. 5.2.3 Staff shall have delineated roles, responsibilities, and authorizations related to implementing changes
  111. 5.2.4 Suitable written disaster preparedness and recovery plan(s), including at least one off-site backup of all preserved information together with an offsite copy of the recovery plan(s)
  112. CLOCKSS: Access Policy
  113. CLOCKSS: Box Operations
  114. CLOCKSS: Budget and Planning Process
  115. CLOCKSS: Business History
  116. CLOCKSS: Business Plan Overview
  117. CLOCKSS: Collection Development
  118. CLOCKSS: Designated Community
  119. CLOCKSS: Extracting Triggered Content
  120. CLOCKSS: Governance and Organization
  121. CLOCKSS: Hardware and Software Inventory
  122. CLOCKSS: Ingest Pipeline
  123. CLOCKSS: Logging and Records
  124. CLOCKSS: Mandatory Responsibilities
  125. CLOCKSS: Mission Statement
  126. CLOCKSS: Preservation Strategy
  127. CLOCKSS: Succession Plan
  128. CLOCKSS: Threats and Mitigations
  129. Definition of AIP
  130. Definition of DIP
  131. Definition of SIP
  132. LOCKSS: Basic Concepts
  133. LOCKSS: Extracting Bibliographic Metadata
  134. LOCKSS: Format Migration
  135. LOCKSS: Metadata Database
  136. LOCKSS: Polling and Repair Protocol
  137. LOCKSS: Property Server Operations
  138. LOCKSS: Software Development Process
  139. Main Page

View (previous 500 | next 500) (20 | 50 | 100 | 250 | 500)

Retrieved from "http://documents.clockss.org/index.php/Special:UncategorizedPages"