Diff for "Milestones"

Differences between revisions 4 and 5

Milestones

The below table contains all planned and completed milestones for this project.

Number	Title	Due date
1	[:Milestone1:Planning, infrastructure and project setup]	2007-10-16
2	[:Milestone2:Early ingest and trivial search - Temporary production system]	Early 2008
3	[:Milestone3:Get Mjølner started]	September 12, 2008
4	[:Milestone4:Complete datamodel and DOMS interface]	October 17, 2008
5	[:Milestone5:Data Model Validation]	November 7, 2008
6	[:Milestone6:Production System]	December 1, 2008
7	[:Milestone7:To be defined]	??

More milestones to be defined. Outstanding issues are at least all access, and rights management!

Milestone revision notes:'

-  ⇤ ← Revision 4 as of 2008-08-25 14:14:37 → 
  Size: 2870
  Editor: kfc
  Comment:
+   ← Revision 5 as of 2008-08-25 14:15:39 → ⇥
  Size: 2992
  Editor: kfc
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 Line 16:
-More milestones to be defined.
+More milestones to be defined. Outstanding issues are at least all access, and rights management!
-Line 21:
+Line 20:
-See OldMilestones

 * Get Mjøner started. I.e. deliver data model language definition, examples of collection data models, functional specification for API/GUI and test interfaces/data if needed?
 * DOMS is Fedora 3 compliant. (Finish definition of type system/base types? Ingester (pre-ingester?), disseminators modified)
 * Access control for ingest/meta data manipulation.
 * Audit trail implemented for ingest and meta data manipulation. Registration of who did what to what and when....
 * (RIFF) validation at ingest and by modifications of objects.
 * Active integrity check (RIFF validation, format validation (e.g. of JPG files)) of repository.
 * Successful integration test with Mjølner admin. interface. Demonstate that metadata can be edited from the GUI.
 * Access control for dissemination.
 * Audit trail for dissemination.
 * Summa integration. Default disseminators and XSLTs.


Other "tanks"....

 * Kan man se DOMS status, altså om der er noget galt? F.eks. hvis et objekt bliver "krøllet".
 * Skal vi levere fine tools til at rette op på ting i DOMS, der er gået i stykker?
 * Hvad med tools til styring af adgangskontrol mv.? Findes de, eller skal vi gør' det sel'?
+## See OldMilestones
## 
##  * Get Mjøner started. I.e. deliver data model language definition, examples of collection data models, functional specification for API/GUI and test interfaces/data if needed?
##  * DOMS is Fedora 3 compliant. (Finish definition of type system/base types? Ingester (pre-ingester?), disseminators modified)
##  * Access control for ingest/meta data manipulation.
##  * Audit trail implemented for ingest and meta data manipulation. Registration of who did what to what and when....
##  * (RIFF) validation at ingest and by modifications of objects.
##  * Active integrity check (RIFF validation, format validation (e.g. of JPG files)) of repository.
##  * Successful integration test with Mjølner admin. interface. Demonstate that metadata can be edited from the GUI.
##  * Access control for dissemination.
##  * Audit trail for dissemination.
##  * Summa integration. Default disseminators and XSLTs.
## 
## 
## Other "tanks"....
## 
##  * Kan man se DOMS status, altså om der er noget galt? F.eks. hvis et objekt bliver "krøllet".
##  * Skal vi levere fine tools til at rette op på ting i DOMS, der er gået i stykker?
##  * Hvad med tools til styring af adgangskontrol mv.? Findes de, eller skal vi gør' det sel'?