Differences between revisions 2 and 3
Revision 2 as of 2010-05-30 21:12:52
Size: 3505
Editor: jrg
Comment:
Revision 3 as of 2010-05-31 13:12:54
Size: 3647
Editor: jrg
Comment:
Deletions are marked like this. Additions are marked like this.
Line 28: Line 28:
The last option appears to be the most convenient for our use. (arguments?) The last option appears to be the most convenient for our use. Reason: The first would require more development on our part than the last. And the second is less convenient for Summa that the last. So, the last it is.

Task Summa integration

Title
Summa integration

State
Not started

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.

There are three ways in which Summa can receive content for indexing (and presentation)

  • By the DOMS side calling an ssh-script to deliver a zip file of contents to Summa
  • By the Summa side requesting latest changed objects via OAI-PMH
  • By the DOMS side implementing the Summa API, through which Summa can request latest changes

The last option appears to be the most convenient for our use. Reason: The first would require more development on our part than the last. And the second is less convenient for Summa that the last. So, the last it is.

A request from Summa to 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. The metadata should comprise enough information for Summa to index, and enough information to be able to access the files that are needed for presentation.

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/

Sub tasks

Title State Time used Time estimated

Documentation

Progress history

Iteration Time used Status Notes Tasks adressed

Tasks/31 (last edited 2010-06-07 09:36:32 by jrg)