C.1. Identify TDR Requirements
State: In progress
Time used: 1 3/4 md. Note: Time spent before iteration 3 not registered.; iteration 11: 1 md
Meet with CSR about DPE and any standards or checklists that can be used to identify requirements for trusted digital repositories. This meeting was held on July 5th (2007). The next step is looking through the found requirements and determining which apply and how they apply to the DOMS project (including requirements to logging and access control). This should help us identify and plan for any necessary changes. All notes and links can be found in the Analysis Document.
Meet with LC about Planets which might offer practical digital preservation services and tools and probably more requirements. Also, it should be determined if any TDR functionality can be inherited from the Planets project to avoid redundant implementations. How any general requirements apply to the DOMS is a part of this tasks.
Completing this task may result in more open questions, thus, more sub-tasks must be added to TaskC.
The analysis document has been updated with all requirements, and tasks have been identified that should address these requirements. We have also had to introduce some new tasks.
Please see the analysis document for more information.
In connection with ActionDataModelTDRRequirements, we discovered that all references to 'RLG/NARA audit checklist' in the analysis document was to an 'old' version (and the link to this version was dead). The analysis document has now been updated with links to both old and new version. We should take time to go through the revised TRAC: Criteria and Checklist. We could also take a look at the Platter checklist.