3.3.3 Documented history of changes

3.3.3 - The repository shall have a documented history of the changes to its operations, procedures, software, and hardware.

The histories of the changes to the various aspects of the CLOCKSS Archive are preserved as follows:

• Operations:
  • Technical operations are documented in CLOCKSS: Box Operations.
  • Business operations are documented in submissions to, and minutes of, the CLOCKSS board.
• Procedures:
  • Technical procedures are documented in:
    • CLOCKSS: Ingest Pipeline
    • CLOCKSS: Box Operations
    • CLOCKSS: Extracting Triggered Content
    • LOCKSS: Software Development Process
    • LOCKSS: Property Server Operations
  • Business procedures are documented in submissions to, and minutes of, the CLOCKSS board, and the history of communications with libraries and publishers the procedures result in is maintained in the RT ticketing system.
• The software inventory is maintained as described in CLOCKSS: Hardware and Software Inventory. Source code control of the LOCKSS software, and thus its history, is provided by SourceForge. As described in LOCKSS: Software Development Process, the process of evolving the software is tracked using the Roundup system.
• The hardware inventory is maintained in CLOCKSS: Hardware and Software Inventory.

Relevant Documents

1. CLOCKSS Board minutes
2. CLOCKSS: Box Operations
3. CLOCKSS: Ingest Pipeline
4. CLOCKSS: Extracting Triggered Content
5. LOCKSS: Software Development Process
6. CLOCKSS: Hardware and Software Inventory
7. LOCKSS: Property Server Operations