Differences between revisions 1 and 2
Revision 1 as of 2008-02-19 14:45:02
Size: 1790
Comment:
Revision 2 as of 2008-06-26 12:26:09
Size: 2242
Editor: kfc
Comment: Created by the PackagePages action.
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
## page was renamed from Milestones
Line 9: Line 10:
||<10% style="text-align: center;">3 ||<style="text-align: left;">[:Milestone3:Running Fedora with ingest module - only Fedora-tool-access] ||<15% style="text-align: center;">Summer 2008 ||
||<10% style="text-align: center;">4 ||<style="text-align: left;">[:Milestone4:Summa Integration, including disseminator and XSLTs] ||<15% style="text-align: center;"> Late autummn 2008||
||<10% style="text-align: center;">5 ||<style="text-align: left;">[:Milestone5:Production system, reevaluated datamodel, 1. iteration collection manual] ||<15% style="text-align: center;"> Winter 2008/2009||
||<10% style="text-align: center;">6 ||<style="text-align: left;">[:Milestone6:Metadata manager] ||<15% style="text-align: center;">Spring 2009 ||
||<10% style="text-align: center;">7 ||<style="text-align: left;">[:Milestone7:TDR] ||<15% style="text-align: center;">Summer 2009 ||
||<10% style="text-align: center;">8 ||<style="text-align: left;">[:Milestone8:Final touches, rights] ||<15% style="text-align: center;">Autumn 2009 ||
||<10% style="text-align: center;">3 ||<style="text-align: left;">[:Milestone3:Get mjølner started] ||<15% style="text-align: center;">Late June 2008 ||

More milestones to be defined.

'''Milestone revision notes:'''

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'?

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]

Late June 2008

More milestones to be defined.

Milestone revision notes:'

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'?

Milestones (last edited 2010-03-17 13:09:34 by localhost)