Popular pages

Showing below up to 50 results starting with #51.

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

51. 3.1.2.2 Monitor environment for time to deploy succession, contingency, escrow‏‎ (4,940 views)
52. 3.3.2.1 Review and update preservation policies‏‎ (4,915 views)
53. 4.2.1.2 Definition of each AIP‏‎ (4,799 views)
54. 5.1.2 Manage the number and location of copies of all digital objects‏‎ (4,783 views)
55. 5.1.1.1.5 Software technologies appropriate to the services it provides to its designated communities‏‎ (4,571 views)
56. 3.4.3 Risk, benefit, investment, expenditure‏‎ (4,509 views)
57. 3.5.1.4 Policies about liability and rights challenges‏‎ (4,503 views)
58. 4.6.1 Comply with Access Policies‏‎ (4,399 views)
59. 3.5.1 Contracts or deposit agreements for content‏‎ (4,387 views)
60. 4.2.5.1 Tools or methods to identify the file types of all objects‏‎ (4,320 views)
61. 3.5.1.2 Completeness of agreements with depositors‏‎ (4,305 views)
62. 5.1.1.4 Process to record and react to the availability of new security updates based on a risk-benefit assessment‏‎ (4,301 views)
63. 4.3.4 Provide evidence of the effectiveness of its preservation activities‏‎ (4,286 views)
64. 5.1.1.1.1 Hardware technologies appropriate to the services it provides to its designated communities‏‎ (4,273 views)
65. 3.5.1.1 Contracts or deposit agreements for preservation rights‏‎ (4,194 views)
66. (Cheats) Free High Seas Hero Resources Generator APK MOD (HAzVfB)‏‎ (3,223 views)
67. 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‏‎ (3,049 views)
68. 5.1.1.5 Defined processes for storage media and/or hardware change (e.g., refreshing, migration)‏‎ (3,006 views)
69. 5.1.1.2 Adequate hardware and software support for backup functionality sufficient for preserving the repository content and tracking repository functions‏‎ (2,961 views)
70. 4.4.2.1 Procedures for all actions taken on AIPs‏‎ (2,911 views)
71. 4.2.9 Independent mechanism for verifying the integrity of the content‏‎ (2,892 views)
72. 5.1.1.3 Effective mechanisms to detect bit corruption or loss‏‎ (2,860 views)
73. 4.4.1.1 Preserve the Content Information of AIPs‏‎ (2,848 views)
74. 4.4.1.2 Actively monitor the integrity of AIPs‏‎ (2,825 views)
75. 4.2.3 Document final disposition of all SIPs‏‎ (2,816 views)
76. 4.2.1.1 Identify which definition applies to which AIP‏‎ (2,797 views)
77. 4.3.1 Documented preservation strategies relevant to its holdings‏‎ (2,782 views)
78. 4.2.6.3 PDI is persistently associated with Content Information of AIP‏‎ (2,777 views)
79. 4.1.3 Recognition and parsing of SIPs‏‎ (2,770 views)
80. 4.5.3 Create bi-directional linkages between each AIP and its descriptive information‏‎ (2,768 views)
81. 5.1.2.1 Mechanisms in place to ensure any/multiple copies of digital objects are synchronized‏‎ (2,766 views)
82. 5.2.3 Staff shall have delineated roles, responsibilities, and authorizations related to implementing changes‏‎ (2,764 views)
83. 4.2.4 Convention that generates persistent, unique identifiers for AIPs‏‎ (2,757 views)
84. 4.2.7.1 Processes for testing understandability for Designated Community of the Content Information of AIPs‏‎ (2,755 views)
85. 4.4.2.2 Demonstrate that any actions taken on AIPs were compliant with the specification of those actions‏‎ (2,733 views)
86. 4.1.4 Verify the identity of the Producer‏‎ (2,717 views)
87. 4.1.6 Obtain sufficient control over digital objects‏‎ (2,711 views)
88. 4.1.2 Specify content information at deposit‏‎ (2,704 views)
89. 4.1.5 Verify SIPs for completeness and correctness‏‎ (2,697 views)
90. 4.2.4.1 Uniquely identify each AIP‏‎ (2,692 views)
91. 4.2.6 Documented processes for acquiring PDI for associated Content Information‏‎ (2,665 views)
92. 4.2.4.2 System of reliable linking/resolution services in order to find identified objects‏‎ (2,663 views)
93. 4.2.6.1 Documented processes for acquiring PDI‏‎ (2,646 views)
94. 4.1.7 Provide depositor with responses‏‎ (2,641 views)
95. 5.1.1.1.6 Procedures in place to monitor and receive notifications when software changes are needed‏‎ (2,639 views)
96. 4.1.1 Identify content information and information properties‏‎ (2,618 views)
97. 4.2.4.1.1 Have unique identifiers‏‎ (2,618 views)
98. 5.1.1.6.2 Process for testing and evaluating the effect of changes to the repository's critical processes‏‎ (2,613 views)
99. 5.1.1.1.2 Procedures in place to monitor and receive notifications when hardware technology changes are needed‏‎ (2,608 views)
100. 4.2.6.2 Execute documented processes for acquiring PDI‏‎ (2,607 views)

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