Differences between revisions 5 and 7 (spanning 2 versions)

Task ECM

Title: ECM

State: Not started

Time used

Time estimated: 22md

Description

ECM is both the better content model system, and a webservice for performing certain tasks on fedora.

It is to be moved into Fedora. For the purposes of DOMS, we do not allocate ressources for this work, but only for the things that are directly relevant for DOMS.

State: A rest based webservice, that uses Fedora client to speak with Fedora. Design of ECM is close to final.

Outstanding tasks

Finalise design of ECM, and bring it into Fedora 3.4
1. Schema location bug. Schemas that import each other need an absolute URL. 7C, as this bug has been with us for some time. We have a design, but if that fails we knows not what to do. There are workarounds, that can be used just for DOMS, through.
2. Name-spaces. We need to agree on the ECM (and DOMS) name-spaces. This involves a meeting, updating all docs marked as current, and updating the ECM webservice. Combined, this is 5B, as we know quite well what should be done, and ECM is quick to update, but the meeting might take time, and the docs can be nasty.
3. DS-COMPOSITE-MODEL. Little change with the roll-in to Fedora, which necessitates a change to the webservice. 1A. RelsInt support postponed.
4. Ontology syntax. The final decision on how to designate relations (with # and so on) in the ontologies. Not done yet, despite much work, so not easy. 3D.
Add collection based operations. All collection based operations are queries. As such, they are easy to implement, as ECM has a good query framework. But many operations, and review, so 4B.
Update View system to take date as a parameter. This is needed by the Update tracking stuff, where you need to get the object view bundle as it looked at a certain date (when it was published). Fedora already takes date as a param for most stuff, so this should just be propagated upwards. 2B

Future tasks

Bring Validator service into Fedora. RelsInt support estimated at 5C, but there is more to this task.
To use a better way of speaking to Fedora. Fedora releases a new java Client in 3.4. Migrate ECM to use this. 3C, as new tech, but the client code is isolated in ECM.

Sub tasks

Title

State

Time used

Time estimated

Documentation

Progress history

Iteration

Time used

Status

Notes

Tasks adressed

-  ⇤ ← Revision 5 as of 2010-06-03 11:51:54 → 
  Size: 2933
  Editor: abr
  Comment:
+   ← Revision 7 as of 2010-06-09 09:25:42 → ⇥
  Size: 4259
  Editor: abr
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 Line 17:
- Time estimated::
+ Time estimated:: 22md
-Line 26:
+Line 27:
+It is to be moved into Fedora. For the purposes of DOMS, we do not allocate ressources for this work, but only for the things that are directly relevant for DOMS.
-Line 30:
+Line 33:
-. Finalize design of ECM, and bring it into Fedora 3.4
  1. Schema location bug
  1. Namespaces
  1. DS-COMPOSITE-MODEL
  1. Ontology syntax
 1. Rework backend of the webservice:
  1. To use the correct schema and so on
 1. Add collection based operations.
 1. Update View system to take date as a parameter. This is needed by the Update tracking stuff, where you need to get the object view bundle as it looked at a certain date (when it was published)
+. Finalise design of ECM, and bring it into Fedora 3.4
  1. Schema location bug. Schemas that import each other need an absolute URL. 7C, as this bug has been with us for some time. We have a design, but if that fails we knows not what to do. There are workarounds, that can be used just for DOMS, through.
  1. Name-spaces. We need to agree on the ECM (and DOMS) name-spaces. This involves a meeting, updating all docs marked as current, and updating the ECM webservice. Combined, this is 5B, as we know quite well what should be done, and ECM is quick to update, but the meeting might take time, and the docs can be nasty.
  1. DS-COMPOSITE-MODEL. Little change with the roll-in to Fedora, which necessitates a change to the webservice. 1A. RelsInt support postponed.
  1. Ontology syntax. The final decision on how to designate relations (with # and so on) in the ontologies. Not done yet, despite much work, so not easy. 3D.
 1. Add collection based operations. All collection based operations are queries. As such, they are easy to implement, as ECM has a good query framework. But many operations, and review, so 4B.
 1. Update View system to take date as a parameter. This is needed by the Update tracking stuff, where you need to get the object view bundle as it looked at a certain date (when it was published). Fedora already takes date as a param for most stuff, so this should just be propagated upwards. 2B
-Line 41:
+Line 42:
-. Bring Validator service into Fedora
 1. To use a better way of speaking to Fedora.
+. Bring Validator service into Fedora. RelsInt support estimated at 5C, but there is more to this task.
 1. To use a better way of speaking to Fedora. Fedora releases a new java Client in 3.4. Migrate ECM to use this. 3C, as new tech, but the client code is isolated in ECM.