##Task ## 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. = B.2. Access to DOMS Data = ## Packaging of Summa Data ## Valid states: "Not started", "In progress" and "Finished" '''State:''' In progress ## The time used is measured in man days and does not include the time spent on any sub-tasks. '''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 [[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 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 == ## 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 == ## . [:TaskX.Y.Z:Add sub task link 1 here] ## . [:TaskX.Y.Z:Add sub task link 2 here] ## . ..[[BR]] ## . ..[[BR]] ## . .. ## . [:TaskX.Y.Z:Add sub task link N here] == 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 "MyTaskPageNameAnalysisDocument" in your created page. ## This should be a proper default, however, it may be changed. * [[TaskB.2AnalysisDocument|Analysis Document]] * [[TaskB.2DesignDocument|Design Document]] * [[TaskB.2SystemMaintenanceDocument|System Set-up and Maintenance Document]] == Parent task == * [[TaskB]] == Progress history == <> === 2007-12-18 === * Actions [[ActionSummaOnAStick]] and ActionHarvestDomsToSumma have been created for processing in [[Iteration7|iteration 7]] === 2008-05-26 === * Task description updated