Popular pages

Showing below up to 50 results starting with #51.

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

51. 3.3.1 Designated community‏‎ (3,718 views)
52. 3.2.1.1 Identified and established duties‏‎ (3,718 views)
53. 3.2.1.2 Appropriate number of staff‏‎ (3,715 views)
54. 3.5.1 Contracts or deposit agreements for content‏‎ (3,678 views)
55. 3.2.1.3 Professional development program‏‎ (3,669 views)
56. 5.1.1.1.5 Software technologies appropriate to the services it provides to its designated communities‏‎ (3,646 views)
57. 4.2.5.1 Tools or methods to identify the file types of all objects‏‎ (3,632 views)
58. 3.1.2.2 Monitor environment for time to deploy succession, contingency, escrow‏‎ (3,625 views)
59. 4.3.4 Provide evidence of the effectiveness of its preservation activities‏‎ (3,624 views)
60. 3.3.2.1 Review and update preservation policies‏‎ (3,624 views)
61. 4.6.1 Comply with Access Policies‏‎ (3,603 views)
62. 5.1.1.4 Process to record and react to the availability of new security updates based on a risk-benefit assessment‏‎ (3,535 views)
63. 3.5.1.1 Contracts or deposit agreements for preservation rights‏‎ (3,531 views)
64. 3.5.1.2 Completeness of agreements with depositors‏‎ (3,524 views)
65. 5.1.1.1.1 Hardware technologies appropriate to the services it provides to its designated communities‏‎ (3,474 views)
66. 5.1.1.5 Defined processes for storage media and/or hardware change (e.g., refreshing, migration)‏‎ (2,550 views)
67. 5.1.1.2 Adequate hardware and software support for backup functionality sufficient for preserving the repository content and tracking repository functions‏‎ (2,517 views)
68. 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‏‎ (2,516 views)
69. 4.2.9 Independent mechanism for verifying the integrity of the content‏‎ (2,473 views)
70. 4.4.2.1 Procedures for all actions taken on AIPs‏‎ (2,464 views)
71. 4.4.1.1 Preserve the Content Information of AIPs‏‎ (2,446 views)
72. 5.1.1.3 Effective mechanisms to detect bit corruption or loss‏‎ (2,438 views)
73. 4.2.6.3 PDI is persistently associated with Content Information of AIP‏‎ (2,396 views)
74. 4.4.1.2 Actively monitor the integrity of AIPs‏‎ (2,394 views)
75. 5.1.2.1 Mechanisms in place to ensure any/multiple copies of digital objects are synchronized‏‎ (2,390 views)
76. 4.2.7.1 Processes for testing understandability for Designated Community of the Content Information of AIPs‏‎ (2,387 views)
77. 4.2.3 Document final disposition of all SIPs‏‎ (2,382 views)
78. 5.2.3 Staff shall have delineated roles, responsibilities, and authorizations related to implementing changes‏‎ (2,372 views)
79. 4.3.1 Documented preservation strategies relevant to its holdings‏‎ (2,370 views)
80. 4.2.1.1 Identify which definition applies to which AIP‏‎ (2,331 views)
81. 4.4.2.2 Demonstrate that any actions taken on AIPs were compliant with the specification of those actions‏‎ (2,316 views)
82. 4.1.3 Recognition and parsing of SIPs‏‎ (2,302 views)
83. 4.1.2 Specify content information at deposit‏‎ (2,289 views)
84. 4.5.3 Create bi-directional linkages between each AIP and its descriptive information‏‎ (2,283 views)
85. 4.1.7 Provide depositor with responses‏‎ (2,271 views)
86. 4.1.5 Verify SIPs for completeness and correctness‏‎ (2,270 views)
87. 4.2.4 Convention that generates persistent, unique identifiers for AIPs‏‎ (2,269 views)
88. 4.2.4.2 System of reliable linking/resolution services in order to find identified objects‏‎ (2,261 views)
89. 4.2.4.1 Uniquely identify each AIP‏‎ (2,260 views)
90. 4.2.6 Documented processes for acquiring PDI for associated Content Information‏‎ (2,256 views)
91. 4.1.4 Verify the identity of the Producer‏‎ (2,253 views)
92. 4.2.6.1 Documented processes for acquiring PDI‏‎ (2,249 views)
93. 4.1.6 Obtain sufficient control over digital objects‏‎ (2,233 views)
94. 4.1.1 Identify content information and information properties‏‎ (2,220 views)
95. 4.2.1 Associated definition for each AIP or class of AIPs‏‎ (2,215 views)
96. 5.1.1.6 Identified and documented critical processes that affect its ability to comply with its mandatory responsibilities‏‎ (2,198 views)
97. 4.2.6.2 Execute documented processes for acquiring PDI‏‎ (2,192 views)
98. 4.2.4.1.5 System of identifiers is adequate now and in the future‏‎ (2,191 views)
99. 4.2.3.1 Procedures if a SIP is not incorporated or discarded‏‎ (2,190 views)
100. 5.1.1.1.2 Procedures in place to monitor and receive notifications when hardware technology changes are needed‏‎ (2,186 views)

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