## page was renamed from C.1. Call meetings with Planets(Lars)/DPE(Colin)
##Task
## If any of the below links or sections are not applicable to your page, then please comment them out rather than deleting
## as they may become relevant later on.
= C.1. Identify TDR Requirements =
## Valid states: "Not started", "In progress" and "Finished"
'''State:''' In progress

## The time used is measured in man days and does not include the time spent on any sub-tasks.
'''Time used:''' 1 3/4 md. Note: Time spent before iteration 3 not registered.; iteration 11: 1 md

== Description ==
## Add a high level task (goals / sub-goals) description here, sufficiently detailed to provide a background for creation of action descriptions.
## Any available (technical) details goes into the below documentation pages.
 * Meet with CSR about [[http://www.digitalpreservationeurope.eu/|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 [[TaskC.1AnalysisDocument|Analysis Document]].
 * Meet with LC about [[http://www.planets-project.eu/|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]].
##== Sub tasks ==
## . Identify requirements from Planets in order to perform preservation planning.
## . Identify requirements regarding logging of DOMS usage and access control.
== Documentation ==
## The documentation section links to the documentation relevant to this task and its sub-tasks (if any).
##
## The below links will automatically be expanded to page names like "MyTaskPageNameAnalysisDocument" in your created page.
## This should be a proper default, however, it may be changed.
 * [[TaskC.1AnalysisDocument|Analysis Document]]
== Parent task ==
 * [[TaskC]]
== Progress history ==
<<PageDicts(Action,Iteration, Time used,Status,Notes,Tasks adressed ~= TaskC.1)>>

## Add information about about the current state of the task here. That is, information about what has been completed so far and
## what outstanding issues that are left. Example:
##
##=== 2007-09-13 ===
##Finished the design documentation. A review is needed before this task can is completed.
##
##=== 2007-08-25 ===
##Completed requirement specification. We are now ready for writing the design document.
=== 2007-09-24 ===
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.

=== 2008-08-28 ===
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.