## page was renamed from B. Support indexing of all DOMS materials with Summa

##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. Access to DOMS materials =

## 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.
'''Time used:''' 0 md.

There is a [[TaskB Overview]] page available.

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


The plan for making data available in DOMS for the end users, is to make all data available through Summa, and to make a general DOMS access interface, such that DOMS is not dependent on Summa. Plan:

A disseminator on each object will present the object in a fashion suitable for indexing. This may include presenting nothing, if the object is not to be indexed, or presenting a package of this object and other objects that can be packaged together in a meaningful way. The disseminator is available as a webservice. An oai-pmh-provider will be available for harvesting.

For Summa we need an agreement with the Summa development team. We need XSLTs for converting the harvested material to a Summa-indexing-document and for converting to a Summa-presentation-document (HTML). For the Summa indexing and presentation, localisation needs to be taken into consideration where appropriate, depending on the metadata model.

For metadata and data that is not public, we need to consider how rights may be handled. How are rights handled when making metadata available through an oai-provider? How are rights handled, when you have access to the metadata (which hold a URL to the data) but '''not''' to the data. How are rights handled  when using a Summa index?

We also need an access log. How does this work together with an oai-provider?

In the Summa presentation document and elsewhere, we wish to be able to use thumbnails etc. This requires disseminators able to generate that.

Open questions:
 . How do we make DOMS material accessible for public libraries - and others (DOMS Interface)?
 . We have an oai-pmh-provider; what about ORE (Access to Data)?

== Sub tasks ==

 . [[TaskB.1|B.1. Summa Cooperation]]
 . [[TaskB.2|B.2. Access to Data]].
 . [[TaskB.3|B.3. Access Rights]].
 . [[TaskB.4|B.4. Playback Disseminators]].
 . [[TaskB.5|B.5. DOMS Interface]].

##B.1 Support indexing of all DOMS materials with Summa. Summa index and show transformations need fine-tuning.
##B.2 Packing of data
##B.3 Summa rights integration
##B.4 Default disseminators

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

 * [[TaskBAnalysisDocument| Analysis Document]]
 * [[TaskBDesignDocument| Design Document]]
 * [[TaskBSystemMaintenanceDocument| System Set-up and Maintenance Document]]

== Parent task ==
 * [[WBS]]

== Progress history ==

<<PageDicts(Action,Iteration, Time used,Status,Notes,Tasks adressed ~= TaskB)>>

## 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 that are left. Example:
##
##=== 2007-09-13 ===
##Finished the design documentation. A review is needed before this task can is completed.
##
##=== 2007-08-25 ===
##Completed requirement specification. We are now ready for writing the design document.

=== 2008-04-24 ===
Made a round-up of what parts of this task have been made so far and by whom. See details [[RoundUpTaskB2008-04-24|here]].
=== 2008-05-26 ===
Task description updated