Short pages

Showing below up to 50 results starting with #51.

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

51. (hist) ‎4.2.2 Description of how AIPs are constructed from SIPs ‎[694 bytes]
52. (hist) ‎3.2.1.3 Professional development program ‎[708 bytes]
53. (hist) ‎4.2.6 Documented processes for acquiring PDI for associated Content Information ‎[715 bytes]
54. (hist) ‎4.2.7.1 Processes for testing understandability for Designated Community of the Content Information of AIPs ‎[719 bytes]
55. (hist) ‎CLOCKSS: Mission Statement ‎[719 bytes]
56. (hist) ‎4.2.7.2 Execute testing process of Content Information of AIPs ‎[721 bytes]
57. (hist) ‎4.2.7.3 Bring Content Information of AIP up to level of understandability if it fails testing ‎[721 bytes]
58. (hist) ‎4.2.8 Verify each AIP for completeness and correctness ‎[721 bytes]
59. (hist) ‎4.1.4 Verify the identity of the Producer ‎[725 bytes]
60. (hist) ‎5.1.2 Manage the number and location of copies of all digital objects ‎[732 bytes]
61. (hist) ‎4.3.2.1 Mechanisms for monitoring and notification when Representation Information is inadequate for the Designated Community to understand the data holdings ‎[744 bytes]
62. (hist) ‎4.2.6.3 PDI is persistently associated with Content Information of AIP ‎[760 bytes]
63. (hist) ‎4.4.2.1 Procedures for all actions taken on AIPs ‎[764 bytes]
64. (hist) ‎4.6.2.1 Record and act upon problem reports about errors in data and responses from users ‎[773 bytes]
65. (hist) ‎3.3.2.1 Review and update preservation policies ‎[775 bytes]
66. (hist) ‎4.2.5.4 Tools or methods to ensure that Representation Information is persistently associated with objects ‎[806 bytes]
67. (hist) ‎5.1.1.6 Identified and documented critical processes that affect its ability to comply with its mandatory responsibilities ‎[834 bytes]
68. (hist) ‎4.3.3.1 Mechanisms for creating, identifying or gathering any extra Representation Information required ‎[834 bytes]
69. (hist) ‎4.2.5.2 Tools or methods to determine what Representation Information is necessary for understandability ‎[847 bytes]
70. (hist) ‎5.1.1.5 Defined processes for storage media and/or hardware change (e.g., refreshing, migration) ‎[848 bytes]
71. (hist) ‎4.6.1 Comply with Access Policies ‎[858 bytes]
72. (hist) ‎5.1.1 Identify and manage the risks to its preservation operations and goals associated with system infrastructure ‎[869 bytes]
73. (hist) ‎4.4.1.2 Actively monitor the integrity of AIPs ‎[892 bytes]
74. (hist) ‎3.5.1.4 Policies about liability and rights challenges ‎[900 bytes]
75. (hist) ‎3.4.2 Financial transparency, compliance, and audits ‎[914 bytes]
76. (hist) ‎4.4.1.1 Preserve the Content Information of AIPs ‎[973 bytes]
77. (hist) ‎5.1.1.1.4 Procedures, commitment and funding to replace hardware when evaluation indicates the need to do so ‎[976 bytes]
78. (hist) ‎3.2.1.1 Identified and established duties ‎[1,006 bytes]
79. (hist) ‎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 ‎[1,007 bytes]
80. (hist) ‎CLOCKSS: Succession Plan ‎[1,010 bytes]
81. (hist) ‎4.2.5.3 Have access to the requisite Representation Information ‎[1,019 bytes]
82. (hist) ‎CLOCKSS: Collection Development ‎[1,023 bytes]
83. (hist) ‎4.3.2 Mechanisms for monitoring its preservation environment ‎[1,050 bytes]
84. (hist) ‎3.5.2 Track and manage property rights/restrictions ‎[1,053 bytes]
85. (hist) ‎4.5.3 Create bi-directional linkages between each AIP and its descriptive information ‎[1,065 bytes]
86. (hist) ‎4.2.7 Content Information is understandable for Designated Community at the time of AIP creation ‎[1,072 bytes]
87. (hist) ‎5.1.1.4 Process to record and react to the availability of new security updates based on a risk-benefit assessment ‎[1,090 bytes]
88. (hist) ‎4.3.1 Documented preservation strategies relevant to its holdings ‎[1,123 bytes]
89. (hist) ‎5.1.1.1.6 Procedures in place to monitor and receive notifications when software changes are needed ‎[1,150 bytes]
90. (hist) ‎5.1.1.6.2 Process for testing and evaluating the effect of changes to the repository's critical processes ‎[1,169 bytes]
91. (hist) ‎5.1.1.2 Adequate hardware and software support for backup functionality sufficient for preserving the repository content and tracking repository functions ‎[1,221 bytes]
92. (hist) ‎5.1.1.1.8 Procedures, commitment and funding to replace software when evaluation indicates the need to do so ‎[1,252 bytes]
93. (hist) ‎5.2.3 Staff shall have delineated roles, responsibilities, and authorizations related to implementing changes ‎[1,282 bytes]
94. (hist) ‎4.1.3 Recognition and parsing of SIPs ‎[1,293 bytes]
95. (hist) ‎5.1.1.1.5 Software technologies appropriate to the services it provides to its designated communities ‎[1,314 bytes]
96. (hist) ‎3.3.4 Commit to transparency ‎[1,333 bytes]
97. (hist) ‎3.2.1 Identified duties and appointed staff ‎[1,342 bytes]
98. (hist) ‎5.1.1.1.2 Procedures in place to monitor and receive notifications when hardware technology changes are needed ‎[1,352 bytes]
99. (hist) ‎3.3.6 Self-assessment and external certification ‎[1,380 bytes]
100. (hist) ‎5.1.1.1.1 Hardware technologies appropriate to the services it provides to its designated communities ‎[1,412 bytes]

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