Differences between revisions 2 and 3
Revision 2 as of 2008-08-20 08:04:11
Size: 2888
Editor: abr
Comment:
Revision 3 as of 2010-03-17 13:12:31
Size: 2894
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 13: Line 13:
The intention is that we have a disseminator and a disseminator web-service that nicely packages up data for indexing, and an OAI-PMH-provider (using the Fedora plugin) which is also an implementation of the [http://hera/cgi-bin/viewcvs.cgi/Summa/MetadataStorage/src/dk/statsbiblioteket/summa/storage/io/AccessRead.java?rev=HEAD&content-type=text/vnd.viewcvs-markup Summa metadata storage API]. The intention is that we have a disseminator and a disseminator web-service that nicely packages up data for indexing, and an OAI-PMH-provider (using the Fedora plugin) which is also an implementation of the [[http://hera/cgi-bin/viewcvs.cgi/Summa/MetadataStorage/src/dk/statsbiblioteket/summa/storage/io/AccessRead.java?rev=HEAD&content-type=text/vnd.viewcvs-markup|Summa metadata storage API]].
Line 45: Line 45:
 * [:TaskB.2AnalysisDocument:Analysis Document]
 * [:TaskB.2DesignDocument:Design Document]
 * [:TaskB.2SystemMaintenanceDocument:System Set-up and Maintenance Document]
 * [[TaskB.2AnalysisDocument|Analysis Document]]
 * [[TaskB.2DesignDocument|Design Document]]
 * [[TaskB.2SystemMaintenanceDocument|System Set-up and Maintenance Document]]
Line 50: Line 50:
 * ["TaskB"]  * [[TaskB]]
Line 54: Line 54:
[[PageDicts(Action,Iteration, Time used,Status,Notes,Tasks adressed ~= TaskB.2)]] <<PageDicts(Action,Iteration, Time used,Status,Notes,Tasks adressed ~= TaskB.2)>>
Line 57: Line 57:
 * Actions [:ActionSummaOnAStick:] and ActionHarvestDomsToSumma have been created for processing in [:Iteration7:iteration 7]  * Actions [[ActionSummaOnAStick]] and ActionHarvestDomsToSumma have been created for processing in [[Iteration7|iteration 7]]

B.2. Access to DOMS Data

State: In progress

Time used: 0 md.

The intention is that we have a disseminator and a disseminator web-service that nicely packages up data for indexing, and an OAI-PMH-provider (using the Fedora plugin) which is also an implementation of the Summa metadata storage API.

The pre-analysis project provides a simple proof-of-concept implementation, that simply packages up data related by some certain named relations, in a list of FoxML documents wrapped in a top-level XML-tag. It also provides a complete SummaAPI of good quality.

This implementation of the disseminator needs to be brought to production quality.

Furthermore, the Summa-storage API will change in the version of Summa we wish to use, and this may require some updating to the summa storage API implementation based on the OAI provider.

We also should consider whether we would like a OAI-ORE-provider?

Open question: Is an oai-provider sufficient access to DOMS? Or do we need a "local DOMS search engine", e.g. for federated search?

Description

Documentation

Parent task

Progress history

Iteration Time used Status Notes
ActionTrueSearch 15 0md In progress
ActionTrueSearchContinued 16 0md In progress
ActionViewDatastream 13 0md Described, lacks review

2007-12-18

2008-05-26

  • Task description updated

TaskB.2 (last edited 2010-03-17 13:12:31 by localhost)