026500

 

BELIEF

Bringing Europe’s eLectronic Infrastructures to Expanding Frontiers

 

 

WP1D4.2.a - BELIEF DL Release Notes – Release 2.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.2.a - T1.2 – Digital Library Release Notes – Release 2.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. 7

2.1.3.       BELIEF DL Metadata Definition. 7

2.1.3.1.        DL Metadata list 7

2.1.3.2.        DL Metadata details. 8

2.1.4.       Collecting Documents and Metadata from Information Sources. 13

2.1.4.1.        Document type cross-reference. 14

2.1.4.2.        Metadata cross-reference. 16

2.1.4.3.        Developed Tools for Document and Metadata Harvesting. 18

2.2.      DL Functionalities. 19

2.2.1.       Services. 19

2.2.1.1.        Information Space Management 19

2.2.1.2.        Search Services. 19

2.2.2.       User Interface. 21

2.2.3.       Toolkit APIs. 21

2.2.4.       Added Functionalities. 23

3.     Known Issues and Limitations. 24

4.     Next Implementation Brief 25

4.1.      New DL Contents. 25

4.2.      New DL Functionalities. 26

5.     References. 27

 

 


 

Log of changes

 

Version N°

Date (dd/mm/yyyy)

Changes

D4.1.a V0.1

11/05/2006

None – First draft

D4.1.b V0.2

26/06/2006

The following contents have been modified:

·         Specific contents for the DL First Release (1.0)

D4.2.a V0.1

26/10/2006

The following contents have been modified:

·         Specific contents for the DL Second Release (2.0)

D4.2.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 (hereafter DL) in terms of:

·        DL Contents

·        DL Functionalities

These “Release Notes” are also available at http://www.beliefproject.org/.

The BELIEF DL is an instance of OpenDLib, a digital library management system comprising a federation of services that can be customised to meet 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 organisations collaborating 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

With regard to the Research Infrastructure Entities (Projects which signed the Letter of Support for BELIEF, Organisations 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

The following Information Sources have been selected for the second release (D4.2-M12) of the BELIEF DL:

 

·        BIOINFOGRID

Bioinformatics Grid Application for life science

http://www.bioinfogrid.eu/

·        DRIVER Project

Digital Repository Infrastructure Vision for European Research

http://www.driver-repository.eu/

·        EELA Project

E-Infrastructure shared between Europe and Latin America

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

·        ETICS

eInfrastructure for Testing, Integration and Configuration of Software

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

·        EUChinaGRID

http://www.euchinagrid.org/

·        EUIndiaGRID

http://www.euindiagrid.eu/

·        EUMEDGRID

http://www.eumedgrid.org/

·        Grid@Asia

Advanced Grid Research Workshops through European and Asian Co-operation

http://www.gridatasia.net/

·        GRIDCC

Grid Enabled Remote Instrumentation with Distributed Control and Computation

http://www.gridcc.org/

·        ICEAGE

The International Collaboration to Extend and Advance Grid Education

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

·        ISSeG

Integrated Site Security for Grids

http://isseg.web.cern.ch/ISSeG/

·        LOBSTER

Large-scale Monitoring of Broadband Internet Infrastructures

http://www.ist-lobster.org/

·        MUPBED

Multi Partner European Testbeds for Research Networking

http://www.ist-mupbed.org/

 

2.1.2.     Supported Standard Protocols and Formats

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

Metadata encoding protocols:

·        DC

·        DCQ (recommended)

·        MARC, UNIMARC, MARC21, MARCXML

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 (virtually mandatory):

·        UTF-8 (Unicode Transformation Format-8)

2.1.3.     BELIEF DL Metadata Definition

With OpenDLib, resources can be catalogued with multiple metadata formats. The BELIEF DL uses Dublin Core Qualified (DCQ) encoding for the purpose of interoperability purposes since it enables the enhanced sharing of information between Information Sources adopting different coding with no loss of semantics [DCMI]. Descriptions in the following are extracted from [DCMIMT].

However, BELIEF metadata can be modified (see Paragraph 5.8Managing DL Maintenance”).

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

2.1.3.1.      DL Metadata list

 

1)         (*)       Title (qualified)

2)         (*)       Creator

3)         (*)       Subject

4)         (*)       Description (qualified)

5)         (*)       Publisher

6)           -         Contributor (qualified)

7)         (*)       Date (qualified)

8)         (*)       Type (qualified)

9)           -         Status

10)         -         Format

11)       (*)       Identifier (qualified)

12)         -         Source (qualified)

13)         -         Language

14)         -         Relation (qualified)

15)         -         Coverage (qualified)

16)         -         Rights

17)         -         Provenance

 

The 8 (eight) metadata marked with (*) should be considered mandatory for effective classification in the DL.

 

2.1.3.2.      DL Metadata details

 

1)         Title

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 mainly responsible for creating the resource content.

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

 

3)         Subject

Topic of the resource content.

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

 

4)         Description

An account of the resource content.

Examples of Description include, but are 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 resource content.

o       fulltext

A summary of the resource content.

o       tableOfContents

A list of subunits of the resource content.

 

5)         Publisher

An entity responsible for making the resource available.

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

 

6)         Contributor

An entity responsible for making contributions to the resource content.

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

This element may be used with the following qualifiers in the BELIEF DL:

·        Qualifiers

o       Coordinator

o       Organiser

o       Participants

o       Organizationtype

Current BELIEF specific defined possible values are as follows:

Ø      Academia

Ø      EU Funded Project

Ø      Industry

Ø      Research

Ø      RTD (Research and Technological Development)

Ø      SME (Small and Medium Enterprise)

Ø      NGO (Non Governative Organization)

Ø      Government

o       Projecttype

 

7)         Date

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

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 expressed as YYYY-MM-DD.

·        Qualifiers

o       Available

Date (often a range) when the resource will become or became available.

o       Created

Date when the resource was created.

o       Issued

Date when the resource was issued (e.g., publication).

o       Modified

Date when the resource was changed.

o       Valid

Date (often a range) indicating resource validity (period).

 

8)         Type

The type or kind of the resource content.

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]). The FORMAT element is used to describe the physical or digital manifestation of the resource. .

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

DCT1 possible values are as follows:

Ø      Collection

Ø      Dataset

Ø      Event

Ø      Image

Ø      Interactive resource

Ø      Moving image

Ø      Physical object

Ø      Service

Ø      Software

Ø      Sound

Ø      Still image

Ø      Text

Current BELIEF specific defined possible values are as follows:

Ø      Brochure

Ø      Case Study

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

Values currently accepted for BELIEF are as follows:

Ø      Article(s)

Ø      Audio

Ø      Book(s)

Ø      Brochure(s)

Ø      Case Study

Ø      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 resource content.

This element is currently used with the following values in BELIEF:

Ø      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 current resource is derived.

The current 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 resource content..

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 resource content.

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 resource content.

    • Temporal

Temporal characteristics of the intellectual resource content.

 

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 impact on its authenticity, integrity and interpretation.

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

 

 

2.1.4.     Collecting Documents and Metadata from Information Sources

This section outlines document type correspondences between the BELIEF DL and the Information Sources and metadata similarities 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

Case Study

 

Case Study

 

 

 

 

 

 

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

(To be provided in the next release)

CONDOR

1.       Title

Title

Title

Name

-

Title

2.       Creator

Creator

Creator

 

-

Creator

3.       Subject

 

Subject

 

-

Subject

4.       Description

.abstract

.fulltext

.tableOfContents

 

Description.abstract

 

Description

 

Description

 

Programme

-

 

Description.abstract

5.       Publisher

 

Publisher

 

-

Publisher

6.       Contributor

.coordinator

.organiser

.participants

.organisationtype

.projecttype

 

Contributor

 

 

Organiser, Contact

Participants

-

Contributor

7.       Date

Date

Date

Date

-

Date

8.       Type

.informationsource

Type

Type

 

-

Type

9.       Status

status

 

 

 

 

10.    Format

 

Format

 

-

 

11.    Identifier

.URL

Identifier

Identifier.URL

Identifier

Identifier.URL

 

Link

-

 

12.    Source

.Activity

.Event

 

 

 

-

 

13.    Language

 

Language

 

-

 

14.    Relation

 

 

 

-

 

15.    Coverage

.Spatial

.Temporal

 

 

 

-

 

16.    Rights

 

 

 

-

 

17.    Provenance

 

 

 

-

 

Metadata cross-reference (1/2)

 

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

.Organiser

.Participants

Contributor

 

 

Organiser

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

At present, the automatic harvesting process has been implemented for the following Information Sources:

·        EGEE

·        DANTE and related projects:

o       ALICE

o       EUMEDCONNECT

o       GEANT2

o       GEANT

o       TEIN2

·        DILIGENT

·        SEE-GRID

Documents are collected also from the following repositories, although automatic harvesting has not yet been implemented on these:

·        CONDOR

·        e-IRGSP

Finally, the following Entities directly submit their documents to the DL:

·        eConcertation

·        Research Infrastructure

 

The table below shows how the documents and metadata are collected from each Project selected, highlighting specific actions to be performed either by individual Projects or BELIEF as appropriate.

 

 

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

Proprietary, MARCXML
(alternatively OAI, DC)

None

API invocation

Specific Harvester

EGEE Public

Proprietary, XML

None

API invocation

Specific Harvester

DANTE

Proprietary, XML

None

API invocation

Specific Harvester

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

None – Hosting of the DL on BELIEF

None – Direct submission

None – Native support

Models for submission

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 visualisation of documents.

The BELIEF DL search service offers diverse 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 customised according to several dimensions, such as, metadata formats, controlled vocabularies, and browsable fields. Other DL specific functionalities are also provided, such as the control of access policies to 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 provided to support the preservation of documents, document reviewing process, introduction of new collections, and handling of users and user group profiles.

Functionalities offered to users to exploit the DL services are introduced here below.

2.2.1.1.      Information Space Management

Users can define the information space they want to search/browse..

This information space comprises all collections the user has selected from the BELIEF DL. Where no information space is defined, user operations are carried out on all “Public collections”.

Information Space Selection

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

Creation of New Collections

A collection consists of a set of documents selected from the archives of the DL publishing institutions or from pre-existing collections. Users wanting to create a collection interactively defines i) which conditions the document metadata should meet 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 their own private collections.

2.2.1.2.      Search Services

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

·        Query Mediator

·        Index

·        Browse

·        User Interface

These services enable users to access the digital objects maintained in the DL that they are using. Users can search any information associated with digital objects and their parts, namely:

·        Content representation (metadata)

·        References to other objects

·        Textual content of digital objects

Users can refine search results with both additional search operations and feed-back operations. Search operations enable users to signal which documents retrieved are relevant to their interests.  Accordingly, the DL uses the signalled documents to repeat search operations that produce results as close as possible to the user’s relevance feedback.

Search results are presented as a list of references to the documents meeting the user search query. References comprise information extracted from one or more metadata elements of the related documents and are customisable by the user. These references enable users to obtain document previews so that they can request access specifically to documents of interest, thus avoiding the search of irrelevant documents.

Simple Search

The simple search operation enables users to specify one or more words to be searched in all the 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 frequency in these documents.

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

Advanced Search

The advanced search operation enables users to specify a complex query in which the 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 enables users to set up structured queries but is recommended for users with at least a minimum knowledge of document metadata formats. Such queries are very similar to those possible with the “where” clause of a SQL query in a relational database. However, the BELIEF DL offers the additional option to use Boolean operators, or probabilistic operators, or a combination of both.

Query Mediator

This dispatches queries to Index service instances, according to availability.

Index

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

Browse

Users 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 used as a pre-search operation. It visualises a portion of any indexed information while arranging its items in alphabetical order. Users can select the information they are interested in (whether personal names, or subjects, titles, publication dates, etc.) and define the portion of the alphabetical order they want to browse. Users can also customise the visualisation  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 listing those documents that meet their request. The DL manages digital objects that are compliant with the OpenDLib DoMDL model and visualises them as a graphical rendering of this model. The visualisation of these objects is more complex than the visualisation of a simple file. Two visualisation modes are available to users: tab page and top level. With the tab page visualisation, 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, depending on their preferences and the type of digital objects selected for visualisation.

In both modes, a tree representing the structure of the retrieved digital object appears on the left of the first visualisation 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 users accessing them in the same mode.

According to the DoMDL specifications, a digital object is composed of 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 view 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 enables interaction with the DL in two different modes: a human-to-application interaction and an application-to-application interaction. The human-to-application interaction is obtained through the OpenDLib UI Service that comes with the OpenDLib Toolkit. The application-to-application interaction is implemented by a set of APIs enabling interaction 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 when the project was implemented 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 have been implemented and included in the OpenDLib Toolkit:

·        Browse

·        BrowseInfo

·        BrowseStandard

·        GetDocumentsPerTerm

·        ListCollections

·        Submit

 

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.

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

Submit                    to perform document submission.

 

 

2.2.4.     Added Functionalities

The following functionalities and services have been added in the current release:

 

·        DL On-Line-Help Functionality

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

 

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

 

 

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 Sources are planned:

·        DEISA Organization

(Distributed European Infrastructure for Supercomputing Applications)

http://www.deisa.org/

·        GARUDA Initiative

(National Grid Computing Initiative)

http://www.garudaindia.in/

·        BalticGrid

http://www.balticgrid.org/

·        EuQoS

End-to-end Quality of Service support over heterogeneous networks

http://www.euqos.org/

·        EuroLabs

European Distributed NGN Laboratories

http://www.ist-eurolabs.org/

·        6DISS

IPv6DISSemination and Exploitation

http://www.6diss.org/

·        OMII-Europe

http://www.omii-europe.org/

·        CYCLOPS

CYber infrastucture for CiviL protection Operative ProcedureS

http://www.cyclops-project.eu/

·        EXPReS

Express Production Real-Time e-VLBI Service

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

·        Int.eu.grid

Interactive European Grid

http://dissemination.interactive-grid.eu/

·        ITHANET

eInfrastructure for Thalassaemia Research Network

http://www.ithanet.eu/

·        SEEFIRE

South-East Europe Fibre Infrastructure for Research and Education

http://www.seefire.org/

·        SEEREN2

South Eastern European Research & Education Network

http://www.seeren.org/

·        DSpace System based Libraries

 

4.2.   New DL Functionalities

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

 

·        DL Hosting Service

BELIEF already implements a “DL Hosting Service” (design, implementation and maintenance of a DL) for entities that cannot (or do not want to) afford their own service.

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 that want to maintain ownership on their DL environment (HW + SW + data). This “extended access service” enables DL users to access DL 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