## 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 Summa integration =

## Task title
 Title:: Summa integration

## 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 Summa integration component of DOMS connects Summa with DOMS, thereby allowing Summa to get content for indexing and presentation, and allowing the DOMS GUI an easy way to obtain search result object PIDs.

Summa will receive content for indexing and presentation via an implementation of the Summa Storage API, which we will do.

A call from Summa to getRecordsModifiedAfter in our implementation of the Summa API will result in a call (with time of last request) to the DOMS Client library, which then handles the generation of a bundle of metadata objects for the views that have changed since last request.
A call of getRecord in our Summa API will return a bundled view of objects for displaying a particular record.

For the functionality needed by DOMS GUI to gain search results, the Summa integration component will use the Summa webservice, and return the results conveniently formatted/packaged for DOMS GUI.

The Summa webservice is described somewhere on the Summa wiki: http://wiki.statsbiblioteket.dk/summa/



## 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 ==
<<PageDicts(Tasks/31/\d+$, Title, State, Time used, Time estimated)>>

== 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/31/AnalysisDocument|Analysis Document]]
 * [[Tasks/31/DesignDocument|Design Document]]
 * [[Tasks/31/SystemMaintenanceDocument|System Set-up and Maintenance Document]]

== Progress history ==
<<PageDicts(Actions/,Iteration,Time used,Status,Notes,Tasks adressed,Tasks adressed ~= Tasks/31)>>

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