Long pages

Showing below up to 50 results starting with #1.

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

1. (hist) ‎CLOCKSS: Threats and Mitigations ‎[35,990 bytes]
2. (hist) ‎CLOCKSS: Ingest Pipeline ‎[28,307 bytes]
3. (hist) ‎CLOCKSS: Box Operations ‎[25,176 bytes]
4. (hist) ‎Definition of AIP ‎[24,328 bytes]
5. (hist) ‎LOCKSS: Software Development Process ‎[20,160 bytes]
6. (hist) ‎CLOCKSS: Extracting Triggered Content ‎[20,101 bytes]
7. (hist) ‎LOCKSS: Polling and Repair Protocol ‎[19,561 bytes]
8. (hist) ‎LOCKSS: Extracting Bibliographic Metadata ‎[18,193 bytes]
9. (hist) ‎Definition of SIP ‎[16,581 bytes]
10. (hist) ‎LOCKSS: Format Migration ‎[14,701 bytes]
11. (hist) ‎CLOCKSS: Logging and Records ‎[13,619 bytes]
12. (hist) ‎4) Digital Object Management ‎[12,313 bytes]
13. (hist) ‎LOCKSS: Basic Concepts ‎[10,245 bytes]
14. (hist) ‎CLOCKSS: Designated Community ‎[9,165 bytes]
15. (hist) ‎LOCKSS: Property Server Operations ‎[7,850 bytes]
16. (hist) ‎5) Infrastructure and Security Risk Management ‎[6,351 bytes]
17. (hist) ‎CLOCKSS: Preservation Strategy ‎[6,261 bytes]
18. (hist) ‎Definition of DIP ‎[6,110 bytes]
19. (hist) ‎LOCKSS: Metadata Database ‎[5,923 bytes]
20. (hist) ‎3) Organizational Infrastructure ‎[5,608 bytes]
21. (hist) ‎CLOCKSS: Mandatory Responsibilities ‎[5,163 bytes]
22. (hist) ‎Main Page ‎[4,923 bytes]
23. (hist) ‎CLOCKSS: Governance and Organization ‎[4,760 bytes]
24. (hist) ‎CLOCKSS: Business Plan Overview ‎[4,130 bytes]
25. (hist) ‎4.4.2.2 Demonstrate that any actions taken on AIPs were compliant with the specification of those actions ‎[2,635 bytes]
26. (hist) ‎CLOCKSS: Hardware and Software Inventory ‎[2,542 bytes]
27. (hist) ‎CLOCKSS: Budget and Planning Process ‎[2,463 bytes]
28. (hist) ‎4.2.4.1.5 System of identifiers is adequate now and in the future ‎[2,093 bytes]
29. (hist) ‎4.2.4 Convention that generates persistent, unique identifiers for AIPs ‎[2,063 bytes]
30. (hist) ‎CLOCKSS: Business History ‎[2,015 bytes]
31. (hist) ‎4.2.1.1 Identify which definition applies to which AIP ‎[1,954 bytes]
32. (hist) ‎4.1.6 Obtain sufficient control over digital objects ‎[1,749 bytes]
33. (hist) ‎3.3.3 Documented history of changes ‎[1,683 bytes]
34. (hist) ‎4.5.1 Specify minimum information requirements to enable the Designated Community to discover and identify material ‎[1,649 bytes]
35. (hist) ‎4.2.1.2 Definition of each AIP ‎[1,633 bytes]
36. (hist) ‎CLOCKSS: Access Policy ‎[1,597 bytes]
37. (hist) ‎4.2.5.1 Tools or methods to identify the file types of all objects ‎[1,533 bytes]
38. (hist) ‎4.3.3 Mechanisms to change preservation plans as a result of its monitoring activities ‎[1,500 bytes]
39. (hist) ‎4.3.4 Provide evidence of the effectiveness of its preservation activities ‎[1,457 bytes]
40. (hist) ‎5.1.1.1.1 Hardware technologies appropriate to the services it provides to its designated communities ‎[1,412 bytes]
41. (hist) ‎3.3.6 Self-assessment and external certification ‎[1,380 bytes]
42. (hist) ‎5.1.1.1.2 Procedures in place to monitor and receive notifications when hardware technology changes are needed ‎[1,352 bytes]
43. (hist) ‎3.2.1 Identified duties and appointed staff ‎[1,342 bytes]
44. (hist) ‎3.3.4 Commit to transparency ‎[1,333 bytes]
45. (hist) ‎5.1.1.1.5 Software technologies appropriate to the services it provides to its designated communities ‎[1,314 bytes]
46. (hist) ‎4.1.3 Recognition and parsing of SIPs ‎[1,293 bytes]
47. (hist) ‎5.2.3 Staff shall have delineated roles, responsibilities, and authorizations related to implementing changes ‎[1,282 bytes]
48. (hist) ‎5.1.1.1.8 Procedures, commitment and funding to replace software when evaluation indicates the need to do so ‎[1,252 bytes]
49. (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]
50. (hist) ‎5.1.1.6.2 Process for testing and evaluating the effect of changes to the repository's critical processes ‎[1,169 bytes]

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