• Tasks
• 30

Task DOMS Client

Title

DOMS Client

State

Not started

Time used

Time estimated

Description

The DOMS Client java library will be utilized by (for now) four other components of DOMS:

• Summa integration
• DOMS GUI
• Mass ingest
• OAI-PMH

So the features of the DOMS Client library should atleast facilitate whatever these four components need from the lower levels of DOMS. A brainstorm on interactions with these four "users" of the DOMS Client can be found in the Analysis Document below.

Most of the functions of the DOMS Client can be implemented as methods on java objects which represent their Fedora object counterparts. This will allow the DOMS Client users to juggle DOMS contents in a convenient object oriented way. These methods manipulate object graphs in Fedora and deal with views, collections, relations, content models, datastreams, object status, and so on. These are mainly used by DOMS GUI and Mass Ingest. A few methods needed in the DOMS Client will not belong on Fedora object representations - these instead "slice the Fedora contents by time", generating bundles of objects modified since a certain date/time, for use by Summa integration and for providing OAI-PMH access.

The complexity of most methods mentioned in the analysis is low to medium, with a few methods with higher complexity (like generating recent-change bundles and compound content models).

The methods mentioned in the analysis are from a quick brainstorm, and we should expect that at the time the DOMS Client is mature enough to support its four clients, there would have been implemented an estimated 10-40% more methods in addition to the ones mentioned.

Sub tasks

Documentation

• Analysis Document

• Design Document

• System Set-up and Maintenance Document

Progress history