Popular pages

Jump to: navigation, search

Showing below up to 100 results starting with #1.

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

  1. Main Page‏‎ (150,127 views)
  2. Definition of AIP‏‎ (30,764 views)
  3. CLOCKSS: Extracting Triggered Content‏‎ (28,692 views)
  4. LOCKSS: Format Migration‏‎ (26,809 views)
  5. CLOCKSS: Ingest Pipeline‏‎ (26,654 views)
  6. CLOCKSS: Box Operations‏‎ (26,402 views)
  7. LOCKSS: Polling and Repair Protocol‏‎ (25,900 views)
  8. LOCKSS: Software Development Process‏‎ (17,136 views)
  9. CLOCKSS: Logging and Records‏‎ (16,419 views)
  10. LOCKSS: Basic Concepts‏‎ (16,238 views)
  11. LOCKSS: Extracting Bibliographic Metadata‏‎ (15,526 views)
  12. LOCKSS: Property Server Operations‏‎ (14,316 views)
  13. CLOCKSS: Threats and Mitigations‏‎ (12,741 views)
  14. Definition of SIP‏‎ (12,222 views)
  15. LOCKSS: Metadata Database‏‎ (9,723 views)
  16. 3) Organizational Infrastructure‏‎ (9,307 views)
  17. CLOCKSS: Succession Plan‏‎ (7,283 views)
  18. CLOCKSS: Hardware and Software Inventory‏‎ (7,115 views)
  19. CLOCKSS: Business Plan Overview‏‎ (6,783 views)
  20. Definition of DIP‏‎ (6,776 views)
  21. CLOCKSS: Business History‏‎ (6,532 views)
  22. 3.3.3 Documented history of changes‏‎ (6,031 views)
  23. CLOCKSS: Preservation Strategy‏‎ (5,746 views)
  24. CLOCKSS: Governance and Organization‏‎ (5,498 views)
  25. CLOCKSS: Designated Community‏‎ (5,257 views)
  26. CLOCKSS: Collection Development‏‎ (5,220 views)
  27. 4) Digital Object Management‏‎ (5,169 views)
  28. CLOCKSS: Budget and Planning Process‏‎ (5,109 views)
  29. CLOCKSS: Access Policy‏‎ (5,095 views)
  30. 5) Infrastructure and Security Risk Management‏‎ (5,018 views)
  31. CLOCKSS: Mandatory Responsibilities‏‎ (4,998 views)
  32. 3.5.1.3 Policies about preservation responsibility‏‎ (4,732 views)
  33. 4.2.7 Content Information is understandable for Designated Community at the time of AIP creation‏‎ (3,846 views)
  34. CLOCKSS: Mission Statement‏‎ (3,719 views)
  35. 3.3.5 Information integrity measurements‏‎ (3,588 views)
  36. 5.1.2 Manage the number and location of copies of all digital objects‏‎ (3,413 views)
  37. 3.1.1 Mission statement‏‎ (3,343 views)
  38. 3.5.2 Track and manage property rights/restrictions‏‎ (3,327 views)
  39. 3.3.2 Preservation policies‏‎ (3,321 views)
  40. 3.5.1.4 Policies about liability and rights challenges‏‎ (3,306 views)
  41. 3.3.4 Commit to transparency‏‎ (3,304 views)
  42. 3.4.3 Risk, benefit, investment, expenditure‏‎ (3,294 views)
  43. 4.2.1.2 Definition of each AIP‏‎ (3,291 views)
  44. 3.4.1 Business planning processes‏‎ (3,270 views)
  45. 3.1.2 Preservation strategic plan‏‎ (3,269 views)
  46. 3.1.2.1 Succession, contigency, escrow plans‏‎ (3,259 views)
  47. 3.4.2 Financial transparency, compliance, and audits‏‎ (3,249 views)
  48. 3.1.3 Collection policy‏‎ (3,246 views)
  49. 3.3.1 Designated community‏‎ (3,236 views)
  50. 3.2.1.2 Appropriate number of staff‏‎ (3,220 views)
  51. 3.2.1.1 Identified and established duties‏‎ (3,219 views)
  52. 3.3.6 Self-assessment and external certification‏‎ (3,198 views)
  53. 3.2.1 Identified duties and appointed staff‏‎ (3,195 views)
  54. 3.2.1.3 Professional development program‏‎ (3,173 views)
  55. 3.5.1 Contracts or deposit agreements for content‏‎ (3,172 views)
  56. 5.1.1.1.5 Software technologies appropriate to the services it provides to its designated communities‏‎ (3,158 views)
  57. 4.2.5.1 Tools or methods to identify the file types of all objects‏‎ (3,156 views)
  58. 3.3.2.1 Review and update preservation policies‏‎ (3,140 views)
  59. 3.1.2.2 Monitor environment for time to deploy succession, contingency, escrow‏‎ (3,130 views)
  60. 5.1.1.4 Process to record and react to the availability of new security updates based on a risk-benefit assessment‏‎ (3,122 views)
  61. 4.3.4 Provide evidence of the effectiveness of its preservation activities‏‎ (3,105 views)
  62. 3.5.1.2 Completeness of agreements with depositors‏‎ (3,090 views)
  63. 3.5.1.1 Contracts or deposit agreements for preservation rights‏‎ (3,080 views)
  64. 5.1.1.1.1 Hardware technologies appropriate to the services it provides to its designated communities‏‎ (3,042 views)
  65. 4.6.1 Comply with Access Policies‏‎ (3,034 views)
  66. 5.1.1.5 Defined processes for storage media and/or hardware change (e.g., refreshing, migration)‏‎ (2,225 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,160 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,155 views)
  69. 4.2.9 Independent mechanism for verifying the integrity of the content‏‎ (2,092 views)
  70. 5.1.1.3 Effective mechanisms to detect bit corruption or loss‏‎ (2,089 views)
  71. 4.4.1.1 Preserve the Content Information of AIPs‏‎ (2,055 views)
  72. 5.1.2.1 Mechanisms in place to ensure any/multiple copies of digital objects are synchronized‏‎ (2,050 views)
  73. 4.4.2.1 Procedures for all actions taken on AIPs‏‎ (2,041 views)
  74. 5.2.3 Staff shall have delineated roles, responsibilities, and authorizations related to implementing changes‏‎ (2,038 views)
  75. 4.2.7.1 Processes for testing understandability for Designated Community of the Content Information of AIPs‏‎ (2,031 views)
  76. 4.4.1.2 Actively monitor the integrity of AIPs‏‎ (2,008 views)
  77. 4.3.1 Documented preservation strategies relevant to its holdings‏‎ (2,002 views)
  78. 4.2.3 Document final disposition of all SIPs‏‎ (1,937 views)
  79. 4.2.1.1 Identify which definition applies to which AIP‏‎ (1,924 views)
  80. 4.1.5 Verify SIPs for completeness and correctness‏‎ (1,923 views)
  81. 4.2.4.2 System of reliable linking/resolution services in order to find identified objects‏‎ (1,921 views)
  82. 4.4.2.2 Demonstrate that any actions taken on AIPs were compliant with the specification of those actions‏‎ (1,915 views)
  83. 4.1.7 Provide depositor with responses‏‎ (1,901 views)
  84. 4.1.3 Recognition and parsing of SIPs‏‎ (1,896 views)
  85. 4.1.2 Specify content information at deposit‏‎ (1,892 views)
  86. 4.2.4.1 Uniquely identify each AIP‏‎ (1,887 views)
  87. 4.1.4 Verify the identity of the Producer‏‎ (1,886 views)
  88. 4.5.3 Create bi-directional linkages between each AIP and its descriptive information‏‎ (1,880 views)
  89. 4.2.4 Convention that generates persistent, unique identifiers for AIPs‏‎ (1,872 views)
  90. 4.2.6.1 Documented processes for acquiring PDI‏‎ (1,872 views)
  91. 4.2.6.3 PDI is persistently associated with Content Information of AIP‏‎ (1,862 views)
  92. 4.1.1 Identify content information and information properties‏‎ (1,860 views)
  93. 5.1.1.1.2 Procedures in place to monitor and receive notifications when hardware technology changes are needed‏‎ (1,857 views)
  94. 4.2.4.1.5 System of identifiers is adequate now and in the future‏‎ (1,855 views)
  95. 4.2.6 Documented processes for acquiring PDI for associated Content Information‏‎ (1,855 views)
  96. 5.1.1.6 Identified and documented critical processes that affect its ability to comply with its mandatory responsibilities‏‎ (1,853 views)
  97. 5.1.1.1 Employ technology watches or other technology monitoring notification systems‏‎ (1,853 views)
  98. 4.2.5.2 Tools or methods to determine what Representation Information is necessary for understandability‏‎ (1,850 views)
  99. 4.2.3.1 Procedures if a SIP is not incorporated or discarded‏‎ (1,848 views)
  100. 4.2.7.2 Execute testing process of Content Information of AIPs‏‎ (1,845 views)

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

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