Popular pages

Showing below up to 39 results starting with #101.

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

101. 5.1.1.1 Employ technology watches or other technology monitoring notification systems‏‎ (2,156 views)
102. 4.1.8 Records of actions and processes related to acquisition‏‎ (2,154 views)
103. 4.2.4.1.4 Provide a list of all identifiers and check for duplications‏‎ (2,151 views)
104. 5.1.1.1.6 Procedures in place to monitor and receive notifications when software changes are needed‏‎ (2,151 views)
105. 4.2.4.1.1 Have unique identifiers‏‎ (2,148 views)
106. 4.2.8 Verify each AIP for completeness and correctness‏‎ (2,146 views)
107. 4.2.5.2 Tools or methods to determine what Representation Information is necessary for understandability‏‎ (2,145 views)
108. 4.3.3.1 Mechanisms for creating, identifying or gathering any extra Representation Information required‏‎ (2,145 views)
109. 4.2.7.2 Execute testing process of Content Information of AIPs‏‎ (2,143 views)
110. 4.2.2 Description of how AIPs are constructed from SIPs‏‎ (2,142 views)
111. 4.2.7.3 Bring Content Information of AIP up to level of understandability if it fails testing‏‎ (2,140 views)
112. 4.2.5 Tool and resources to provide authoritative Representation Information for all objects‏‎ (2,136 views)
113. 5.2.2 Implemented controls to adequately address each of the defined security risks‏‎ (2,130 views)
114. 5.1.1.1.4 Procedures, commitment and funding to replace hardware when evaluation indicates the need to do so‏‎ (2,124 views)
115. 5.1.1.1.3 Procedures in place to evaluate when changes are needed to current hardware‏‎ (2,120 views)
116. 4.3.3 Mechanisms to change preservation plans as a result of its monitoring activities‏‎ (2,116 views)
117. 5.1.1.1.8 Procedures, commitment and funding to replace software when evaluation indicates the need to do so‏‎ (2,115 views)
118. 5.1.1.6.2 Process for testing and evaluating the effect of changes to the repository's critical processes‏‎ (2,108 views)
119. 4.5.1 Specify minimum information requirements to enable the Designated Community to discover and identify material‏‎ (2,107 views)
120. 4.2.5.3 Have access to the requisite Representation Information‏‎ (2,106 views)
121. 5.2.1 Maintain a systematic analysis of security risk factors associated with data, systems, personnel, and physical plant‏‎ (2,103 views)
122. 4.2.4.1.2 Assign and maintain persistent identifiers of the AIP and its components‏‎ (2,096 views)
123. 4.3.2.1 Mechanisms for monitoring and notification when Representation Information is inadequate for the Designated Community to understand the data holdings‏‎ (2,091 views)
124. 4.2.4.1.3 Describe any processes for changes to identifiers‏‎ (2,090 views)
125. 4.1.1.2 Record of content information and information properties that we will preserve‏‎ (2,086 views)
126. 4.3.2 Mechanisms for monitoring its preservation environment‏‎ (2,086 views)
127. 4.4.2 Contemporaneous records of actions and administration processes that are relevant to storage and preservation of the AIPs‏‎ (2,081 views)
128. 4.4.1 Specifications for how the AIPs are stored down to the bit level‏‎ (2,078 views)
129. 5.1.1 Identify and manage the risks to its preservation operations and goals associated with system infrastructure‏‎ (2,074 views)
130. 4.2.10 Contemporaneous records of actions and administration processes relevant to AIP creation‏‎ (2,072 views)
131. 4.1.1.1 Procedures for identifying information properties that we will preserve‏‎ (2,065 views)
132. 4.5.2 Capture or create minimum descriptive information for each AIP‏‎ (2,057 views)
133. 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‏‎ (2,047 views)
134. 4.6.1.1 Log and review all access management failures and anomalies‏‎ (2,029 views)
135. 4.6.2 Follow policies and procedures that enable the dissemination of digital objects that are traceable to the originals‏‎ (2,014 views)
136. 4.2.5.4 Tools or methods to ensure that Representation Information is persistently associated with objects‏‎ (2,014 views)
137. 5.1.1.1.7 Procedures in place to evaluate when changes are needed to current software‏‎ (2,005 views)
138. 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)‏‎ (1,997 views)
139. 4.6.2.1 Record and act upon problem reports about errors in data and responses from users‏‎ (1,885 views)

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