## Please put instances of this task in the subfolder Tasks/ with name for the number, and subfolders as approproate, e.g. Tasks/X/Y ## If any of the below links or sections are not applicable to your page, then please comment them out rather than deleting ## as they may become relevant later on. ## Headline like "Task Implement Backup" = Task DOMS Server = ## Task title Title:: DOMS Server ## Valid states: "Not started", "In progress" and "Finished" State:: Not started ## The time used is measured in man days and does not include the time spent on any sub-tasks. As a rule of thumb, time should always be allocated to subtasks, rather than parent tasks. Format: Xmd Time used:: ## As 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 operations can be found here: [[DOMS Server API]]. A brainstorm list of DOMS Client functionality, which suggests what should be supported 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. ## Add a high level task (goals / sub-goals) description here, sufficiently detailed to provide a background for creation of action descriptions. ## Any available (technical) details goes into the below documentation pages. == Sub tasks == <> == Documentation == ## The documentation section links to the documentation relevant to this task and its sub-tasks (if any). ## ## The below links will automatically be expanded to page names like "Tasks/X/Y/AnalysisDocument" in your created page. ## This should be a proper default. ## ## DO NOT comment out these links. * [[Tasks/28/AnalysisDocument|Analysis Document]] * [[Tasks/28/DesignDocument|Design Document]] * [[Tasks/28/SystemMaintenanceDocument|System Set-up and Maintenance Document]] == Progress history == <> ## Add information about about the current state of the task here. That is, information about what has been completed so far and ## what outstanding issues are left. Example: ## ##=== 2007-09-13 === ##Finished the design documentation. A review is needed before this task is completed. ## ##=== 2007-08-25 === ##Completed requirement specification. We are now ready for writing the design document.