|
⇤ ← Revision 1 as of 2010-05-28 11:17:39
Size: 2136
Comment:
|
Size: 3067
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 20: | Line 20: |
The DOMS Server is the point of access through which systems that communicate with DOMS can utilize the features of the system. Features that are taken care of by the different engine parts in DOMS, and which the DOMS Server gathers in an interface accessible for example through the DOMS Client java library. While DOMS Client provides a higher level object oriented abstraction, the DOMS Server API lists a multitude of more basic operations which allow for manipulating objects in Fedora in detail. A work-in-progress list of suggested operation can be found here: [[DOMS Server API]]. A brainstorm list of DOMS Client functionality, which suggests support by DOMS Server operations, can be found here: [[Tasks/30/AnalysisDocument]] The DOMS Server implements its operations with calls to high-level bitstorage, ECM and Fedora, as well as using the update tracker for time-data needed for search functionality. |
Task DOMS Server
- Title
- DOMS Server
- State
- Not started
- Time used
- Time estimated
Description
The DOMS Server is the point of access through which systems that communicate with DOMS can utilize the features of the system. Features that are taken care of by the different engine parts in DOMS, and which the DOMS Server gathers in an interface accessible for example through the DOMS Client java library. While DOMS Client provides a higher level object oriented abstraction, the DOMS Server API lists a multitude of more basic operations which allow for manipulating objects in Fedora in detail.
A work-in-progress list of suggested operation can be found here: DOMS Server API.
A brainstorm list of DOMS Client functionality, which suggests support by DOMS Server operations, can be found here: Tasks/30/AnalysisDocument
The DOMS Server implements its operations with calls to high-level bitstorage, ECM and Fedora, as well as using the update tracker for time-data needed for search functionality.
Sub tasks
| Title | State | Time used | Time estimated |
Documentation
Progress history
| Iteration | Time used | Status | Notes | Tasks adressed |