B. Access to DOMS materials

State: Not started

Time used: 0 md.

There is a TaskB Overview page available.

Description

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

• B.1. Summa Cooperation

• B.2. Access to Data.

• B.3. Access Rights.

• B.4. Playback Disseminators.

• B.5. DOMS Interface.

Documentation

• Analysis Document

• Design Document

• System Set-up and Maintenance Document

Parent task

• WBS

Progress history

2008-04-24

Made a round-up of what parts of this task have been made so far and by whom. See details here.

2008-05-26

Task description updated

B.1.Summa Cooperation

State: In progress

Time used: 0 md.

Description

We want to meet with the Summa development team and establish an agreement. The meeting should cover:

• harvest format + procedure
• XSLTs
• Storage Access API?
• localisation?
• rights?

This task has been expanded from a Summa XSLT task to a Summa task. The old description follows:

Summa depends on two XSLTs for its behaviour:

1. An XSLT from the source to an index document
2. An XSLT from the source document to a presentation in HTML

The pre-analysis did a proof-of-concept which can be used to base this tasks solution on.

However, some extra work is required concerning localisation of the presentation and indexing. This will depend on the metadata model.

Note that this task depends on TaskA.2 as well as TaskB.2.

Documentation

• Analysis Document

• Design Document

• System Set-up and Maintenance Document

Parent task

• TaskB

Progress history

2008-05-26

• Task description updated

Analysis of Summa Cooperation

During the pre-analysis phase, a mockup of the Summa access functionality was created, and the two XSLTs from that work exist.

They do not address the internationalisation issues, and especially the presentation XSLT is very bare.

They are attached for reference, together with an example digital object

• digitalObjectBundleToHTML.xslt

• digitalObjectBundleToIndexDocument.xslt

• digitalObjectBundle.xml

Prerequisites and Assumptions

The estimation of the XSLT part of this task is based on these notes, which also should be taken into consideration when implementing the task:

BAM: fremvisning... ved ikke, internationalisering

TE: Nye formater i Summa-sammenhæng

TSH: Præsentations add-on klosterpapir så objekter kan findes

MKE: i18n

KFC: NEEDINFO Tweaking af index-xslt; omskrivning af fremvisnings-XSLT. Fornuftig fremvisning, bemærk internationalisering.

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

• Analysis Document

• Design Document

• System Set-up and Maintenance Document

Parent task

• TaskB

Progress history

2007-12-18

• Actions ActionSummaOnAStick and ActionHarvestDomsToSumma have been created for processing in iteration 7

2008-05-26

• Task description updated

Analysis of Access to DOMS Data

The analysis should be updated to reflect that the task has been expanded from DOMS access through Summa to general DOMS access.

The preanalysis included generation of a digital object bundle, by simply following named references, and concatenating the objects in an XML file with an extra top-level element "digitalObjectBundle". A file is attached with an example of a generated digital object bundle.

digitalObjectBundle.xml

The implementation was done rather quickly, using a jsp-page backed up by a simple java class. Those are attached

• digitalObjectBundle.jsp

• DigitalObjectBundleCreator.java

Also, a Summa storage API was designed on top of the fedora OAI provider plugin.

See SummaStorage for more on this.

When addressing this task, we should consult the following TDR requirements:

• Dissemination must always return correct results, and reject requests otherwise : B5.3-6, R77

See TaskC.1AnalysisDocumentDetails#CorrectDissemination

Prerequisites and Assumptions

The estimation of the 'access through Summa'-part of this task is based on these notes, which also should be taken into consideration when implementing the task:

BAM: F.5.2 + om lang tid? + disseminator

TE: Summa disseminator

TSH: Summa disseminator (pak relevante data sammen), OAI tweaks

MKE: + summa disseminator + i18n + oaistorage update to new API

KFC: Opdatere somma-disseminator; tweake OAI storage w/ my summa.

B.3. Access Rights

State: Not started

Time used: 0 md.

Description

How do we manage access rights through our general DOMS access interface?

And through Summa? Should the following be moved to TaskB.1?

It is desirable that we can make Summa searches where only material available to us is presented. This requires that Summa at some point is updated to be able to handle that, but also that we are able to use that extension when it comes.

This will depend on the metadata described in TaskA.2.3, but we will need to be able to present the rights thus presented to Summa in a meaningful way.

Unknown factors are here, both regarding integration with Summa, since we don't know what model will be used there, but also regarding how we describe rights, which needs to be coordinated with the DK-AAI work.

Documentation

• Analysis Document

• Design Document

• System Set-up and Maintenance Document

Parent task

• TaskB

Progress history

2008-05-26

• Task description updated

Analysis of Access Rights

When addressing this task, we should consult the following TDR requirements:

• Must be possible to document copyrights and restrictions on all digital material in a format that it is possible to act on/Require enforced access rights A5.3, B.5.1, C3.3, C3.4, D3.2, D3.3, R15-17, R18?, R36, R52, R76

See TaskC.1AnalysisDocumentDetails#Rights

Prerequisites and Assumptions

The estimation of this task is based on these notes, which also should be taken into consideration when implementing the task:

BAM: RIGHTS?!?

TE: Ukendte faktorer

TSH: No comments.

MKE: PUNT

KFC: NEEDINFO

B.4 Playback Disseminators

State: Not started

Time used: 0 md.

Description

We wish to have disseminators that are optionally available on all objects, that can give one of four previews of the objects: - Image - Text - Movie - Sound

For instance an audio file might have a sound preview available as 10 seconds of the sound, or an image might have a thumbnail preview.

The idea is that an object does not necessarily need to be an image to be able to present an image preview disseminator. For instance a CD album might present its cover.

The task is to implement the needed disseminators for the default types, and making them available through the presentation XSLT.

Documentation

• Analysis Document

• Design Document

• System Set-up and Maintenance Document

Parent task

• TaskB

Progress history

B.5 DOMS Interface

State: Not started

Time used: 0 md.

Description

Design a general DOMS access interface, which should also be the DOMS access point for the public libraries.

This interface may be the oai-provider given by TaskB.2, in which case what is mostly needed is documentation (TaskD?).

Sub tasks

Documentation

• Analysis Document

• Design Document

• System Set-up and Maintenance Document

Parent task

• TaskB

Progress history

2008-05-26

This task was created after the DOMS-day discussions 2008-05-08.

Analysis of Summa Integration

When addressing this task, we should consult the following TDR requirements:

• Data must be searchable/discoverable: R71
• Access log required: B5.2, C3.2, R36

See TaskC.1AnalysisDocumentDetails#Searchable

See TaskC.1AnalysisDocumentDetails#AccessLog

Prerequisites and Assumptions

Risks and Potential Problems

Round-up of Task B

This page describes the current state of task B as of 24th April 2008. That is, a status of all work performed on this task and its sub-tasks so far, and a overview over the developers whom perforned the work.

Sub-tasks addressed so far: