026500

 

BELIEF

Bringing Europe’s eLectronic Infrastructures to Expanding Frontiers

 

 

WP1D4.1.a - BELIEF DL Release Notes – Release 1.0

Ver. 1.0

 

09 January 2007

 

 

Start date: 1 November 2005                                                                             Duration: 24 months

 

The BELIEF Consortium consists of:

1.      Metaware SpA, IT

2.      CNR- ISTI, IT

3.      University of Athens, GR

4.      ERNET, IN

5.      ENGITECH, IE

6.      Escola Politécnica da Universidade de São Paulo, PUSP, BR

7.      Wisconsin-Madison University, US

Responsible Author:

Franco Zoppi - CNR-ISTI, IT

Contributors:

Michele Artini, Federico Biagini, Pasquale Pagano, Manuele Simi - CNR-ISTI, IT

Status:

Confidentiality:

[

[

[

[

 

 

X

]

]

]

]

Draft

To be reviewed

Proposal

Final/Released to CEC

[

[

 

[

 

 

[

X

 

 

 

 

 

 

]

]

 

]

 

 

]

- PU

- PP

 

- RE

 

 

- CO

for PUblic use

restricted to other Programme Participants (including the Commission Service)

REstricted to a group specified by the consortium (including the Commission Service)

COnfidential, only for members of the consortium (including the Commission Service)

Summary / Content:

WP1D4.1.a - T1.2 – Digital Library Release Note – Release 1.0.

 


 

Contents

 

1.     Summary. 4

2.     Implementation Contents. 5

2.1.      DL Contents. 5

2.1.1.       Information Sources. 5

2.1.2.       Supported Standard Protocols and Formats. 6

2.1.3.       BELIEF DL Metadata Definition. 6

2.1.4.       Collecting Documents and Metadata from Information Sources. 11

2.1.4.1.        Document type cross-reference. 12

2.1.4.2.        Metadata cross-reference. 14

2.1.4.3.        Developed Tools for Document and Metadata Harvesting. 16

2.2.      DL Functionalities. 17

2.2.1.       Services. 17

2.2.1.1.        Information Space Management 17

2.2.1.2.        Search Services. 17

2.2.2.       User Interface. 19

2.2.3.       Toolkit APIs. 19

3.     Known Issues and Limitations. 21

4.     Next Implementation Brief 22

4.1.      New DL Contents. 22

4.2.      New DL Functionalities. 22

5.     References. 24

 

 


 

Log of changes

 

Version N°

Date (dd/mm/yyyy)

Changes

D4.1.a V0.1

11/05/2006

None – First draft

D4.1.a V0.2

26/06/2006

The following contents have been modified:

·         Specific contents for the DL First Release (1.0)

D4.1.a V1.0

09/01/2007

Final version following the recommendations of the 1st Annual Review.

 

 

 

 

1.                Summary

This document describes the implementation of the 1.0 Release of the BELIEF Digital Library in terms of:

·        DL Contents

·        DL Functionalities

You will find this “Release Notes” also at http://www.beliefproject.org/.

The BELIEF DL is an instance of OpenDLib. OpenDLib is a digital library management system consisting of a federation of services that can be customized to satisfy the requirements of a target user community. This federation can be expanded at any time by adding other community specific services. The entire set of services can be managed and hosted either by a single or by a multitude of organizations that collaborate on the maintenance of the shared digital library, each according to their own computational and human resources.

For more detailed information on OpenDLib see [OpenDLib].

 

2.                Implementation Contents

2.1.   DL Contents

2.1.1.     Information Sources

Within the Research Infrastructure Entities (Projects which signed the Letter of Support for BELIEF, Organizations and Initiatives), the following Information Sources have been selected for the first release (D4.1-M6) of the BELIEF DL:

  • CONDOR Project

http://www.cs.wisc.edu/condor

  • DANTE Organization, which actually means:
    • DANTE

(Delivery of Advanced Network Technology to Europe)

http://www.dante.net

    • GEANT2 Project

http://www.geant2.net

    • GEANT Project

http://www.geant.net/

    • TEIN2 Project

(Trans-Eurasia Information Network)

http://www.tein2.net

    • EUMEDCONNECT Project

(EUro-MEDiterranean CONNECTion)

http://www.eumedconnect.net

    • ALICE Project

(America Latina Interconectada Con Europa)

http://alice.dante.net

  • DILIGENT Project

(DIgital Library Infrastructure on Grid ENabled Technology)

http://www.diligentproject.org

  • eConcertation Initiative

http://www.geant2.net (as far as the 2nd eConcertation Workshop is concerned)

  • EGEE Project

(Enabling Grids for E-sciencE)

http://www.eu-egee.org/

  • e-IRG Organization and e-IRGSP Project

(e-Infrastructure Reflection Group)

http://www.e-irg.org

  • Research Infrastructure Unit Initiative

http://cordis.europa.eu/infrastructures/home.html

  • SEE-GRID Project

(South Eastern European GRid-enabled eInfrastructure Development)

http://www.see-grid.org

and, obviously,

  • BELIEF Project

(Bringing Europe’s eLectronic Infrastructures to Expanding Frontiers)

http://www.beliefproject.org

2.1.2.     Supported Standard Protocols and Formats

The BELIEF DL supports harvesting of information from Information Source in which metadata are represented using a number of different protocols and formats. Presently, the following metadata are supported by the harvesting tools of the BELIEF DL:

Metadata encoding protocols:

·        DC

·        DCQ (recommended)

·        MARC, UNIMARC, MARC21

Metadata harvesting protocols:

·        OAI-PMH - Open Archives Initiative Protocol for Metadata Harvesting (recommended)

·        Any API call returning an XML file containing metadata encoded in one of the above mentioned encoding

File formats:

·        XML (recommended)

·        RSS

The following character encoding is strongly recommended (nearly mandatory):

·        UTF-8 (Unicode Transformation Format-8)

2.1.3.     BELIEF DL Metadata Definition

In OpenDLib resources can be catalogued with multiple metadata formats. In the BELIEF DL the use of Dublin Core Qualified (DCQ) encoding has been chosen for interoperability purposes since it allows a better sharing of informations between Information Sources using different coding with no loss of semantics [DCMI]. Descriptions in the following are extracted from [DCMIMT].

Modification to Belief metadata can however be implemented (see Paragraph 5.8Managing DL Maintenance”).

The following (17, 9 of which qualified) DCQ metadata are presently supported by BELIEF DL:

 

1)         Title

A name given to the resource.

Typically, Title will be a name by which the resource is formally known.

·        Qualifiers

o       Alternative

Any form of the title used as a substitute or alternative to the formal title of the resource.

This qualifier can include Title abbreviations as well as translations.

 

2)         Creator

An entity primarily responsible for making the content of the resource.

Examples of Creator include a person, an organization, or a service. Typically, the name of a Creator should be used to indicate the entity.

 

3)         Subject

A topic of the content of the resource.

Typically, Subject will be expressed as keywords, key phrases or classification codes that describe a topic of the resource. Recommended best practice is to select a value from a controlled vocabulary or formal classification scheme [WP1D5.1, for the ones used within BELIEF DL].

 

4)         Description

An account of the content of the resource.

Examples of Description include, but is not limited to: an abstract, table of contents, reference to a graphical representation of content or a free-text account of the content.

·        Qualifiers

o       abstract

A summary of the content of the resource.

o       fulltext

A summary of the content of the resource.

o       tableOfContents

A list of subunits of the content of the resource.

 

5)         Publisher

An entity responsible for making the resource available.

Examples of Publisher include a person, an organization, or a service. This should be used to indicate the Information Source (i.e. the name of the Project, Organization or Initiative which owns the resource).

 

6)         Contributor

An entity responsible for making contributions to the content of the resource.

Examples of Contributor include a person, an organization, or a service. Typically, the name of a Contributor should be used to indicate the entity.

In BELIEF DL this element may be used with the following qualifiers:

·        Qualifiers

o       Coordinator

o       Organizer

o       Participants

 

7)         Date

A date of an event in the lifecycle of the resource.

Typically, Date will be associated with the creation or availability of the resource. Recommended best practice for encoding the date value is defined in a profile of ISO 8601 [W3CDTF] and includes (among others) dates of the form YYYY-MM-DD.

·        Qualifiers

o       Available

Date (often a range) that the resource will become or did become available.

o       Created

Date of creation of the resource.

o       Issued

Date of formal issuance (e.g., publication) of the resource.

o       Modified

Date on which the resource was changed.

o       Valid

Date (often a range) of validity of a resource.

 

8)         Type

The nature or genre of the content of the resource.

Type includes terms describing general categories, functions, genres, or aggregation levels for content. Recommended best practice is to select a value from a controlled vocabulary (for example, the DCM1 Type Vocabulary [DCT1]). To describe the physical or digital manifestation of the resource, use the FORMAT element.

In BELIEF DL this element is used with the set of values provided in [DCT1] plus a new set of new types that may be given as values for this element.

The following are the DCT1 possible values:

Ø      Collection

Ø      Dataset

Ø      Event

Ø      Image

Ø      Interactive resource

Ø      Moving image

Ø      Physical object

Ø      Service

Ø      Software

Ø      Sound

Ø      Still image

Ø      Text

The following are presently the BELIEF specific defined possible values:

Ø      Brochure

Ø      Conference & Meeting

Ø      Deliverable

Ø      eCourse

Ø      Manual & User Guide

Ø      News

Ø      Poster

Ø      Presentation

Ø      Project Management Document

Ø      Project Management Meeting

Ø      Publication

Ø      Software

Ø      Training

Ø      Technical Document

·        Qualifiers

o       Informationsource

The types of the content used in the information source repositories.

In BELIEF the following values are presently accepted:

Ø      Article(s)

Ø      Audio

Ø      Book(s)

Ø      Brochure(s)

Ø      Code Exemplar

Ø      Conference(s)

Ø      Consortium Agreement(s)

Ø      Contract(s)

Ø      Contribution(s)

Ø      Course(s)

Ø      Deliverable(s)

Ø      Discussion Document

Ø      Documentation

Ø      eCourse(s)

Ø      EGEE Document

Ø      EU Deliverable

Ø      Event(s)

Ø      Exercise

Ø      Flyer(s)

Ø      Guideline(s)

Ø      Information Sheet(s)

Ø      Leaflet(s)

Ø      Manual(s)

Ø      Map(s)

Ø      Meeting(s)

Ø      (Meeting) Minute(s)

Ø      Module(s)

Ø      News

Ø      News Releases

Ø      Newsletter(s)

Ø      Paper

Ø      Phone Conference(s)

Ø      Plan(s)

Ø      Poster(s)

Ø      Presentation-Publication

Ø      Presentation(s)

Ø      Press

Ø      Publication(s)

Ø      Quality Plan(s)

Ø      Research Publication(s)

Ø      Series

Ø      Slide Presentation(s)

Ø      Software

Ø      Talk(s)

Ø      Technical Annex(es)

Ø      Technical Document(s)

Ø      Technical Note(s)

Ø      Technical Report(s)

Ø      Training

Ø      Training material

Ø      Tutorial(s)

Ø      User Guide(s)

Ø      Video(s)

Ø      Website(s)

Ø      White Paper(s)

Ø      Workgroup(s)

Ø      Workshop(s)

 

9)         Status

The working status of the content of the resource.

In BELIEF DL this element is presently used with the following values:

Ø      Approved

Ø      In Work

Ø      Obsolete

Ø      Released

Ø      Under Approval

 

10)       Format

The physical or digital manifestation of the resource.

Typically, Format may include the media-type or dimensions of the resource. Format may be used to identify the software, hardware, or other equipment needed to display or operate the resource. Examples of dimensions include size and duration. Recommended best practice is to select a value from a controlled vocabulary (for example, the list of Internet Media Types [MIME] defining computer media formats).

 

11)       Identifier

An unambiguous reference to the resource within a given context.

Recommended best practice is to identify the resource by means of a string or number conforming to a formal identification system. Formal identification systems include but are not limited to the Uniform Resource Identifier (URI) (including the Uniform Resource Locator (URL)), the Digital Object Identifier (DOI) and the International Standard Book Number (ISBN).

  • Qualifiers
    • URL

The Uniform Resource Locator.

 

12)       Source

A Reference to a resource from which the present resource is derived.

The present resource may be derived from the Source resource in whole or in part. Recommended best practice is to identify the referenced resource by means of a string or number conforming to a formal identification system.

  • Qualifiers
    • Activity

A value from a controlled vocabulary (RTD Innovation, Training, Demonstration, Management, Functional Design, Architectural Design, Implementation, Test, Dissemination, Exploitation, Project Management, etc.).

    • Event

A value from a controlled vocabulary (Meeting, Review, Conference, etc.).

 

13)       Language

A language of the intellectual content of the resource.

Recommended best practice is to use RFC 3066 [RFC3066] which, in conjunction with ISO639 [ISO639]), defines two- and three-letter primary language tags with optional subtags. Examples include "en" or "eng" for English, "akk" for Akkadian", and "en-GB" for English used in the United Kingdom.

 

14)       Relation

A reference to a related resource.

Recommended best practice is to identify the referenced resource by means of a string or number conforming to a formal identification system.

  • Qualifiers
    • isPartOf

The described resource is a physical or logical part of the referenced resource.

 

15)       Coverage

The extent or scope of the content of the resource.

Typically, Coverage will include spatial location (a place name or geographic coordinates), temporal period (a period label, date, or date range) or jurisdiction (such as a named administrative entity). Recommended best practice is to select a value from a controlled vocabulary (for example, the Thesaurus of Geographic Names [TGN]) and to use, where appropriate, named places or time periods in preference to numeric identifiers such as sets of coordinates or date ranges.

  • Qualifiers
    • Spatial

Spatial characteristics of the intellectual content of the resource.

    • Temporal

Temporal characteristics of the intellectual content of the resource.

 

16)       Rights

Information about rights held in and over the resource.

Typically, Rights will contain a rights management statement for the resource, or reference a service providing such information. Rights information often encompasses Intellectual Property Rights (IPR), Copyright, and various Property Rights. If the Rights element is absent, no assumptions may be made about any rights held in or over the resource.

 

17)       Provenance

A statement of any changes in ownership and custody of the resource since its creation that are significant for its authenticity, integrity and interpretation.

The statement may include a description of any changes successive custodians made to the resource.

 

 

2.1.4.     Collecting Documents and Metadata from Information Sources

This section summarizes document type correspondences between BELIEF DL and the Information Sources and metadata correspondences and differences with respect to BELIEF DL Metadata Definition.

 

 


2.1.4.1.      Document type cross-reference

 

BELIEF

EGEE

DANTE

SEE-GRID

e-IRGSP

CONDOR

DILIGENT

eConcertation

Research Infrastructure

Conference & Meeting

Conference(s),

Event(s),

Meeting(s)

 

Events

Meetings

 

Events & Meeting

Events,

Meetings,

Workshops,

Workgroups

 

Deliverable

EU Deliverable,

Deliverable(s),

Deliverables

Deliverables

 

 

Deliverable

Deliverables

 

Manual & User Guide

User Guides

 

 

 

Manuals

Manuals & User Guides

 

 

Presentation

Audio,

Presentation,

Presentation-Publication,

Contribution(s),

Talk(s)

Presentations

 

 

Slide Presentations

Presentation

 

Presentations,

Talks

Presentations

Brochure

Information Sheets

Brochures,

Leaflets

Brochures

Information Sheets

 

Flyers

Brochures

 

Poster

 

Maps,

Posters

 

 

 

 

 

 

News

News,

News Releases

News Releases

Press,

Newsletters

 

 

 

News

 

 

Project Management Document

(Meeting) Minute(s)

 

 

Meeting Minutes

 

Project Management Document

 

 

Project Management Meeting

 

 

 

 

 

Project Management Meeting

 

 

Publication

Article,

Book

 

Articles

eInfrastructures Roadmap,

Opportunities List,

White Papers

Research Publications

Publication

 

 

Software

Code Exemplar

 

 

 

 

Software

 

 

Technical Document

EGEE Document,

Technical Document,

Technical Note(s),

Technical Report(s)

 

 

 

Technical Documents

Technical Document

 

 

Training

Course,

EGEE Training Resource,

Exercise,

Module,

Series,

Tutorial,

Video,

Website

 

 

 

 

eCourse,

Presentations,

Training,

Tutorials

Tutorials

 

Document type cross-reference (1/1)

 

2.1.4.2.      Metadata cross-reference

 

BELIEF

EGEE

DANTE (*)

SEE-GRID

e-IRGSP (*)

CONDOR

1.       Title

Title

-

Name

-

Title

2.       Creator

Creator

-

 

-

Creator

3.       Subject

 

-

 

-

Subject

4.       Description

.abstract

.fulltext

.tableOfContents

 

Description.abstract

-

 

Description

 

Programme

-

 

Description.abstract

5.       Publisher

 

-

 

-

Publisher

6.       Contributor

.Coordinator

.Organizer

.Participants

 

-

 

 

Organizer, Contact

Participants

-

Contributor

7.       Date

Date

-

Date

-

Date

8.       Type

.informationsource

Type

-

 

-

Type

9.       Status

status

-

 

 

 

10.    Format

 

-

 

-

 

11.    Identifier

.URL

Identifier

Identifier.URL

-

 

Link

-

 

12.    Source

.Activity

.Event

 

-

 

-

 

13.    Language

 

-

 

-

 

14.    Relation

 

-

 

-

 

15.    Coverage

.Spatial

.Temporal

 

-

 

-

 

16.    Rights

 

-

 

-

 

17.    Provenance

 

-

 

-

 

Metadata cross-reference (1/2)

 

(*)           To be provided in the next release.

 

BELIEF

DILIGENT

eConcertation Workshops

eConcertation Workgroups

eConcertation
Other documents

Research Infrastructure

1.       Title

Title

Title

Title

Title

Title

2.       Creator

Creator

 

 

Author

Creator

3.       Subject

Subject

Subject

Subject

Keywords

Subject

4.       Description

.abstract

.fulltext

.tableOfContents

 

Description.abstract

 

Description

 

Agenda

 

Description

 

Description

 

Description.abstract

5.       Publisher

Publisher

 

 

 

Publisher

6.       Contributor

.Coordinator

.Organizer

.Participants

Contributor

 

 

Organizer

Attendees

 

Coordinator

 

Members

 

 

7.       Date

.Created

.Issued

.Modified

Date

 

 

 

Date Creation

 

Date Modification

 

Date Creation

Date Publication

 

8.       Type

.informationsource

Type

 

 

Type

Type

9.       Status

 

 

 

 

Status

10.    Format

 

 

 

 

 

11.    Identifier

 

 

 

 

 

12.    Source

.Activity

.Event

 

 

 

 

Related Workgroup

Related Workshop

 

13.    Language

 

 

 

 

Language

14.    Relation

 

 

 

 

Event

15.    Coverage

.Spatial

.Temporal

 

 

Venue

Data

 

 

 

Event Place

Event Period

16.    Rights

 

 

 

 

Availability

17.    Provenance

 

 

 

 

 

Metadata cross-reference (2/2)

 


2.1.4.3.      Developed Tools for Document and Metadata Harvesting

So far the harvesting process has been implemented for the following Information Sources:

·        EGEE

·        SEE-GRID

·        CONDOR

·        DILIGENT

Moreover, documents are collected also from e-IRGSP, although no automatic harvesting is implementable on that repository yet, and the harvesting process has been designed for DANTE and will be available in the next release.

Way of collecting documents and metadata from each selected Project is summarized in the table below. For each of them specific actions to be performed by the Project or by BELIEF are highlighted (if any).

Technical characteristics of automated tools developed for the harvesting of metadata and documents and their submission to DL are described (to be provided in the next release).

 

 

Provider

Harvesting protocols and coding formats

Actions to be performed

Tools developed by BELIEF

On Provider side

On BELIEF side

EGEE Training

OAI, DC

None

WS invocation

Specific Harvester

EGEE Conferences

MARCXML

None

API invocation

Specific Harvester

EGEE Public

XML

None

API invocation

Specific Harvester

DANTE

Next Release

Next Release

Next Release

Next Release

SEE-GRID

RSS, XML

None

RSS access

Specific Harvester

e-IRGSP

None

None

Temporarily manually performed by DL Administrator

Next Release

CONDOR

OAI, DCQ

None

Temporarily manually performed by DL Administrator

Next Release

DILIGENT

OAI, DCQ

None

Direct access

None

eConcertation

Next Release

Next Release

Temporarily manually performed by DL Administrator

Next Release

Research Infrastructure

None – Hosting of the DL on BELIEF

None – Direct submission

None – Native support

Models for submission

 

 

2.2.   DL Functionalities

2.2.1.     Services

This release of the BELIEF DL provides services to support the submission, description, indexing, search, browsing, retrieval, access, preservation and visualization of documents.

The search service offers different search options: Google-like or fielded (with fields selected from a variety of known metadata formats). Documents retrieved can be navigated across all their editions, versions, structure, metadata and documents formats. All the above services can be customized according to several dimensions such as, for example, metadata formats, controlled vocabularies, and browsable fields. Other DL specific functionality are also provided, such as the control of access policies on documents, and the management of “user-shelves” able to maintain document versions, result-sets, session results, and other information, etc..

In addition, a number of administration functions are also given to support preservation of documents, document reviewing process, introduction of new collections, and handling of users and user group profiles.

Functionalities offered to the users to exploit the DL services are introduced in the following.

2.2.1.1.      Information Space Management

Any user can define the information space which s/he want to search/browse upon.

This information space is composed of all collections the user has selected from those managed by the DL. If no information space is defined, user operations are carried out on all “Public collections”.

Information Space Selection

The user can choose the collections to be included in her/his information space by means of system menu options. The user can view her/his private collections and/or public collections and insert one or more collections into her/his information space; s/he can also view her/his current information space and update it by removing collections or insert new ones.

Creation of New Collections

A collection consists in a set of documents selected from the archives of the DL publishing institutions or from pre-existing collections. The user who wants to create a collection interactively defines i) which conditions the document metadata have to satisfy in order to be selected; ii) which archives documents are to be selected from. Collections are defined as publicly or privately accessible. Public collections can only be created by the library administrator while any registered user can create her/his private collections.

2.2.1.2.      Search Services

The DL provides a set of dedicated advanced services (referred to as “Search Services”) for discover operations on DL content. These services include:

·        Query Mediator

·        Index

·        Browse

·        and, of course, User Interface

Thanks to these services, a user can access the digital objects maintained in the DL that they are using. The user can search any information associated with digital objects and their parts, namely:

·        Content representation (metadata)

·        References to other objects

·        Textual content of digital objects

The user can refine search results by means of both additional search operations and feed-back operations. The latter function allows the user to signal which of the retrieved documents s/he judges as being relevant to her/his interests. Accordingly, the DL uses the signalled documents to repeat its search operations which will produce results very much influenced by the user’s relevance feedback.

Search results are presented as a list of references to the documents satisfying the user search query. References consist of information extracted from one or more metadata elements of the related documents and are customisable by the user. References allow the users to get document previews so that they can request to access a document only if it is of interest. In this way  they don’t lose any time in looking at less relevant documents.

Simple Search

With the simple search operation the user can specify one or more words and let them be searched in all indexed pieces of information. No operator is allowed among words. The system finds all the documents containing those words and orders the search results according to the word frequencies in such documents.

The simple search operation will allow users to search by a “phrase”, i.e. to specify that the set of words they have entered is a “phrase”. This search type, that usually produces more precise results, is currently made available by the DL as an option of the advanced search operation; however this option is exploitable only by users with, at least, a minimum knowledge of the indexed metadata formats.

Advanced Search

With the advanced search operation the user can specify a complex query in which search terms, matching operators between search fields and search terms (such as “contains”, “equal to”, etc), and relation operators between simple queries (such as “boolean-and”, “and-not” etc.) may have to be entered.

This search type requires users have at least a minimum knowledge of documents metadata formats, but allows them to set up structured queries. Such queries are very similar to those permitted by the “where” clause of a SQL query in a relational database, but the DL offers the additional option to use Boolean operators, or probabilistic operators, or a combination of them.

Query Mediator

Dispatches queries to Index service instances, according to availability.

Index

Accepts queries and returns documents matching those queries. The Index function is parametric with respect to the metadata formats, to the set of indexed fields, to the set of result sets formats and the language of the terms.

Browse

The user can browse any information associated with digital objects and their parts, namely:

·        Content representation (metadata)

·        References to other objects

·        Textual content of digital objects

Browsing can also be seen as a pre-search operation. It visualizes a portion of any indexed information while arranging its items in alphabetical order. The user can select the information s/he is interested in (whether personal names, or subjects, titles, publication dates, etc.) and define the portion of the alphabetical order s/he want to browse; s/he can also customize the visualization  format. The ordered list of references is shown by the system accordingly.

2.2.2.     User Interface

As result of their search or browse operations, users obtain a set of results pages with the list of documents that satisfy their request. The DL manages digital objects that are compliant with the OpenDLib DoMDL model and visualizes them as a graphical rendering of this model. The visualization of these objects is more complex than the visualization of simple file. Two visualization modes are available to the users: tab page and top level. With the tab page visualization, all object manifestations are displayed in the same window; with the top level mode, each manifestation is displayed in a new window. Users can choose either mode, according to their preferences and to the type of digital objects to be visualized.

In both modes, a tree representing the structure of the retrieved digital object appears on the left of the first visualization page. Although object data can be maintained in very different ways (stored locally or remotely, or as a reference to other data), this is transparent to the users who access them in the same manner.

According to the DoMDL specifications, a digital object is composed by a number of views and manifestations. By navigating the tree and clicking on the object manifestations, users can access the object data. The DL is able to manage every type of manifestation, regardless of the nature or dimension. Multiple physical manifestations of the same view make it possible to select the one that is compatible with the software installed on the local machine. This is useful when no specific viewer for a given format (e.g., Microsoft Word) is available, but a suitable one (e.g., Acrobat Reader) is installed.

 

2.2.3.     Toolkit APIs

An OpenDLib based system allows to interact with the DL in two different modes: a human to application interaction and an application to application interaction. The former is obtained through the OpenDLib UI Service that comes with the OpenDLib Toolkit while the latter is implemented by means of a set of APIs which let an application to interact with an instance of OpenDLib. The APIs are also provided as part of the UI Service since usually this is the only service exposed to public access. Typically other services are protected by a firewall and they are not directly accessible.

Since the BELIEF DL was created as an instance of OpenDLib, the implementation of the integration between the BELIEF Portal and the DL is based on the use of the APIs. Part of these APIs were available at project’s implementation time as part of the of the OpenDLib Toolkit [OpenDLib]. Nevertheless, in order to cope with new requirements and/or suggestions coming from the project the following new APIs were implemented and included in the OpenDLib Toolkit:

·        Browse

·        BrowseInfo

·        BrowseStandard

·        GetDocumentsPerTerm

·        ListCollections

 

The following APIs are thus now available:

AdvancedQuery    to perform an advanced (fielded) query.

Browse

BrowseInfo

BrowseStandard

CreateSession       to create a new user session.

CreateUser

DeleteUser

DescribeVerb

DisplayUserInfo

Disseminate           to retrieve a manifestation of a given document.

GetDocument        to retrieve the document structure and the associated metadata.

GetDocumentsPerTerm

Identify

ListCollections      to retrieve the information space (in terms of collection IDs) in which the current user can perform its queries. The returned collection IDs can be used in the AdvancedQuery to restrict the information space where the queries are executed in.

ListVerbs

Load

Main

ModifyUser

Navigate                to navigate a result set create by the system after a SimpleQuery or an AdvancedQuery invocation.

SimpleQuery          to perform a simple query. A simple query is a string-based query that asks to the system to retrieve all documents that contain the specified term1 term2 etc..

 

 

 

3.                Known Issues and Limitations

 

None.

4.                Next Implementation Brief

4.1.   New DL Contents

More Information Sources will be included in the DL. The following are foreseen to be added up to now:

·        DEISA Organization

(Distributed European Infrastructure for Supercomputing Applications)

http://www.deisa.org/

·        DRIVER Project

(Digital Repository Infrastructure Vision for European Research)

[website to be created]

·        EELA Project

(E-Infrastructure shared between Europe and Latin America)

http://www.eu-eela.org/

·        ETICS Project

(eInfrastructure for Testing, Integration and Configuration of Software)

http://etics.web.cern.ch/etics/

·        Grid@Asia

(Advanced Grid Research Workshops through European and Asian Co-operation)

http://www.gridatasia.net/

·        GARUDA Initiative

(National Grid Computing Initiative)

http://www.garudaindia.in/

·        DSpace System based Libraries

 

 

4.2.   New DL Functionalities

The following functionalities and services are planned to be part of next releases:

 

·        DL On-Line-Help Functionality

The On-Line-Help functionality will be engineered to offer a more immediate, effective and user-friendly aid.

 

·        DL Administration Service

BELIEF already implements a “DL Administration Service”; this service will be enhanced by:

o       Adding new functionalities to facilitate administrators’ tasks.

o       Engineering both the interface and the man-machine interaction to offer a more user-friendly environment.

 

·        DL Hosting Service

BELIEF already implements a “DL Hosting Service” (design, implementation and maintenance of a DL) for entities which cannot (or do not want to) afford this matter by its own.

This service will be enhanced by:

o       Adding new models to facilitate the submission of new content.

 

·        DL Extended Access Service

BELIEF already implements a “DL Extended Access Service” for entities which want to maintain ownership on their DL environment (HW + SW + data). The “extended access service” allows DL users to access DL’s content via manifestations not currently supported by the original DL, adding transform capabilities.

This service will be enhanced by:

o       Supporting new formats (based on specific requests and needs) for Information Sources’ metadata compatibility.

 

 

 

 

 

5.                References

 

[DCMI]                The Dublin Core Metadata Initiative Open Forum

http://www.dublincore.org/

[DCMIMT]          DCMI Metadata Terms

http://dublincore.org/documents/dcmi-terms/

[DES97]               “The role of classification schemes in Internet resources description and discovery” - DESIRE Project Deliverable 3.2.3, 19 Feb 1997, M. Day et al., UKOLN, University of Bath, UK.

[OpenDLib]          http://www.opendlib.com