Difference between revisions of "5.1.1.1.5 Software technologies appropriate to the services it provides to its designated communities"
From CLOCKSS Trusted Digital Repository Documents
(Created page with "== 5.1.1.1.4 - The repository shall have procedures, commitment and funding to replace hardware when evaluation indicates the need to do so. == The procedures for purchasing ...") |
(Fix cut/paste error) |
||
Line 1: | Line 1: | ||
− | == 5.1.1.1. | + | == 5.1.1.1.5 - The repository shall have software technologies appropriate to the services it provides to its designated communities. == |
− | The | + | The CLOCKSS archive performs its [[CLOCKSS: Mandatory Responsibilities|Mandatory Responsibilities]] to its [[CLOCKSS: Designated Community|Designated Community]] using a range of software. It is all either developed by the LOCKSS team, or free, open source software supported by the open source community: |
+ | * The inventory of the software in use and how it is maintained is described in [[CLOCKSS: Hardware and Software Inventory#Software|CLOCKSS: Hardware and Software Inventory]]. | ||
+ | * The risks involved are described in the Software Obsolescence section of [[CLOCKSS: Threats and Mitigations#Software Obsolescence|CLOCKSS: Threats and Mitigations]]. | ||
+ | * The process by which the LOCKSS software evolves in response to the experience of using it is described in [[LOCKSS: Software Development Process]]. | ||
− | + | === Relevant Documents === | |
− | + | # [[CLOCKSS: Designated Community]] | |
− | + | # [[CLOCKSS: Mandatory Responsibilities]] | |
+ | # [[CLOCKSS: Hardware and Software Inventory]] | ||
+ | # [[CLOCKSS: Threats and Mitigations]] | ||
+ | # [[LOCKSS: Software Development Process]] | ||
=== Relevant Documents === | === Relevant Documents === |
Latest revision as of 03:33, 8 October 2013
5.1.1.1.5 - The repository shall have software technologies appropriate to the services it provides to its designated communities.
The CLOCKSS archive performs its Mandatory Responsibilities to its Designated Community using a range of software. It is all either developed by the LOCKSS team, or free, open source software supported by the open source community:
- The inventory of the software in use and how it is maintained is described in CLOCKSS: Hardware and Software Inventory.
- The risks involved are described in the Software Obsolescence section of CLOCKSS: Threats and Mitigations.
- The process by which the LOCKSS software evolves in response to the experience of using it is described in LOCKSS: Software Development Process.
Relevant Documents
- CLOCKSS: Designated Community
- CLOCKSS: Mandatory Responsibilities
- CLOCKSS: Hardware and Software Inventory
- CLOCKSS: Threats and Mitigations
- LOCKSS: Software Development Process