Task ECM

Title

ECM

State

Not started

Time used

Time estimated

24md

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

1. 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.
2. 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.
3. 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
4. Pid generator. The Pid generator is written and ready. It is a soap webservice. ECM has a pid generator interface, behind which it hides an implementation. This should be the soap client to the pidgenerator webservice. 2B, as we need to add config params to web.xml for the soap client, but otherwise very basic codechange.

Future tasks

1. Bring Validator service into Fedora. RelsInt support estimated at 5C, but there is more to this task.

2. 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

Documentation

• Analysis Document

• Design Document

• System Set-up and Maintenance Document

Progress history