Oldest pages

Jump to: navigation, search

Showing below up to 50 results starting with #1.

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

  1. 3) Organizational Infrastructure‏‎ (00:05, 22 September 2013)
  2. 4) Digital Object Management‏‎ (00:17, 22 September 2013)
  3. 5) Infrastructure and Security Risk Management‏‎ (00:20, 22 September 2013)
  4. 5.1.1 Identify and manage the risks to its preservation operations and goals associated with system infrastructure‏‎ (15:28, 23 September 2013)
  5. 5.1.1.1 Employ technology watches or other technology monitoring notification systems‏‎ (15:29, 23 September 2013)
  6. 5.1.1.1.1 Hardware technologies appropriate to the services it provides to its designated communities‏‎ (15:31, 23 September 2013)
  7. 5.1.1.1.2 Procedures in place to monitor and receive notifications when hardware technology changes are needed‏‎ (15:32, 23 September 2013)
  8. 5.1.1.1.3 Procedures in place to evaluate when changes are needed to current hardware‏‎ (15:33, 23 September 2013)
  9. 5.1.1.1.4 Procedures, commitment and funding to replace hardware when evaluation indicates the need to do so‏‎ (15:34, 23 September 2013)
  10. 5.1.1.1.6 Procedures in place to monitor and receive notifications when software changes are needed‏‎ (15:37, 23 September 2013)
  11. 5.1.1.1.7 Procedures in place to evaluate when changes are needed to current software‏‎ (15:38, 23 September 2013)
  12. 5.1.1.1.8 Procedures, commitment and funding to replace software when evaluation indicates the need to do so‏‎ (15:39, 23 September 2013)
  13. 5.1.1.2 Adequate hardware and software support for backup functionality sufficient for preserving the repository content and tracking repository functions‏‎ (15:42, 23 September 2013)
  14. 5.1.1.3 Effective mechanisms to detect bit corruption or loss‏‎ (15:43, 23 September 2013)
  15. 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‏‎ (15:43, 23 September 2013)
  16. 5.1.1.5 Defined processes for storage media and/or hardware change (e.g., refreshing, migration)‏‎ (15:45, 23 September 2013)
  17. 5.1.1.6 Identified and documented critical processes that affect its ability to comply with its mandatory responsibilities‏‎ (15:46, 23 September 2013)
  18. 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‏‎ (15:47, 23 September 2013)
  19. 5.1.1.6.2 Process for testing and evaluating the effect of changes to the repository's critical processes‏‎ (15:48, 23 September 2013)
  20. 5.1.2.1 Mechanisms in place to ensure any/multiple copies of digital objects are synchronized‏‎ (16:09, 23 September 2013)
  21. 5.2.1 Maintain a systematic analysis of security risk factors associated with data, systems, personnel, and physical plant‏‎ (16:10, 23 September 2013)
  22. 5.2.2 Implemented controls to adequately address each of the defined security risks‏‎ (16:11, 23 September 2013)
  23. 5.2.3 Staff shall have delineated roles, responsibilities, and authorizations related to implementing changes‏‎ (16:12, 23 September 2013)
  24. 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)‏‎ (16:13, 23 September 2013)
  25. 4.1.1 Identify content information and information properties‏‎ (16:16, 23 September 2013)
  26. 4.1.1.1 Procedures for identifying information properties that we will preserve‏‎ (16:19, 23 September 2013)
  27. 4.1.1.2 Record of content information and information properties that we will preserve‏‎ (16:21, 23 September 2013)
  28. 4.1.2 Specify content information at deposit‏‎ (16:21, 23 September 2013)
  29. 4.1.3 Recognition and parsing of SIPs‏‎ (17:33, 23 September 2013)
  30. 4.1.4 Verify the identity of the Producer‏‎ (17:36, 23 September 2013)
  31. 4.1.5 Verify SIPs for completeness and correctness‏‎ (17:37, 23 September 2013)
  32. 4.1.6 Obtain sufficient control over digital objects‏‎ (17:39, 23 September 2013)
  33. 4.1.7 Provide depositor with responses‏‎ (17:40, 23 September 2013)
  34. 4.1.8 Records of actions and processes related to acquisition‏‎ (17:42, 23 September 2013)
  35. 4.2.1 Associated definition for each AIP or class of AIPs‏‎ (17:54, 23 September 2013)
  36. 4.2.1.1 Identify which definition applies to which AIP‏‎ (17:58, 23 September 2013)
  37. 4.2.1.2 Definition of each AIP‏‎ (18:03, 23 September 2013)
  38. 4.2.2 Description of how AIPs are constructed from SIPs‏‎ (18:05, 23 September 2013)
  39. 4.2.3 Document final disposition of all SIPs‏‎ (18:06, 23 September 2013)
  40. 4.2.3.1 Procedures if a SIP is not incorporated or discarded‏‎ (18:07, 23 September 2013)
  41. 4.2.4 Convention that generates persistent, unique identifiers for AIPs‏‎ (18:35, 23 September 2013)
  42. 4.2.4.1 Uniquely identify each AIP‏‎ (18:36, 23 September 2013)
  43. 4.2.4.1.1 Have unique identifiers‏‎ (18:37, 23 September 2013)
  44. 4.2.4.1.2 Assign and maintain persistent identifiers of the AIP and its components‏‎ (18:39, 23 September 2013)
  45. 4.2.4.1.3 Describe any processes for changes to identifiers‏‎ (18:40, 23 September 2013)
  46. 4.2.4.1.4 Provide a list of all identifiers and check for duplications‏‎ (18:41, 23 September 2013)
  47. 4.2.4.1.5 System of identifiers is adequate now and in the future‏‎ (18:42, 23 September 2013)
  48. 4.2.4.2 System of reliable linking/resolution services in order to find identified objects‏‎ (18:43, 23 September 2013)
  49. 4.2.5 Tool and resources to provide authoritative Representation Information for all objects‏‎ (18:45, 23 September 2013)
  50. 4.2.5.1 Tools or methods to identify the file types of all objects‏‎ (18:48, 23 September 2013)

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

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