026500

 

BELIEF

Bringing Europe’s eLectronic Infrastructures to Expanding Frontiers

 

 

WP1D5.1 - Bridging Information Consumers & Providers

Ver. 1.2

 

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:

Metaware SpA, 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:

WP1D5.1 - T1.1-T1.2-T1.3 - Bridging Information Consumers & Providers.

 

Contents

 

1...... Summary. 5

2...... Executive Summary. 6

3...... Introduction. 8

3.1.   General Concepts. 8

3.2.   General Characteristics of the Implemented Solution. 11

4...... Requirements Collection and Analysis. 13

4.1.   Adopted Methodology. 13

4.2.   Requirements from DoW... 15

4.2.1.   Bridging Information Consumers (WP1T11) 15

4.2.2.   DL Creation and Maintenance (WP1T12) 16

4.2.3.   Bridging Information Providers (WP1T13) 16

4.2.4.   BELIEF Portal and DL Integration (WP1T14) 17

4.3.   Additional Requirements. 17

4.3.1.   eConcertation Initiative. 17

4.3.2.   Research Infrastructure Unit Initiative. 18

4.4.   Requirements from Consumers and Providers. 19

4.4.1.   Involved Research Infrastructure Projects, Organizations and Initiatives. 19

4.4.2.   Information Source Documents and Metadata. 21

4.5.   Requirements cross-reference. 31

5...... The BELIEF DL. 34

5.1.   General Concepts. 34

5.1.1.   Collections. 36

5.1.2.   Interest Areas. 42

5.2.   Supported Standard Protocols and Formats. 48

5.3.   BELIEF DL Metadata Definition. 48

5.4.   Collecting Documents and Metadata from Information Sources. 54

5.4.1.   Document type cross-reference. 55

5.4.2.   Metadata cross-reference. 57

5.4.3.   Developed Tools for Document and Metadata Harvesting. 59

5.5.   Document Submission and Search. 60

5.5.1.   Models for Document Submission. 60

5.5.2.   Search Types. 61

5.6.   Portal and DL Integration. 62

5.6.1.   Registering as a BELIEF Community Member 62

5.6.2.   Portal and DL integration via APIs. 65

5.6.3.   Accessing the DL via the BELIEF Portal 66

5.6.4.   Direct Access to the DL. 66

5.7.   Basic DL Configuration. 69

5.8.   Managing DL Maintenance. 70

6...... Achieved Results and Conclusions. 71

7...... Planning Brief for Future Releases. 75

7.1.   Entities to be added. 75

7.2.   Harvesting Tools to be implemented. 75

7.3.   Functionalities and Services to be added, enhanced and engineered. 76

8...... References. 77

9...... Appendix A – Questionnaire for Requirements Collection. 78

10.... Appendix B – Savane: a PM Support Tool 82

11.... Appendix C – OpenDLib. 85

 

Log of changes

 

Version N°

Date (dd/mm/yyyy)

Changes

0.1

15/12/2005

None – First draft

0.2

28/12/2005

The following contents have been modified:

·         “General Concepts”

·         “BELIEF Portal and DL integration”

0.3

02/01/2006

The following contents have been added:

·         Requirements cross-reference

0.4

09/02/2006

The following contents have been added:

·         Requirements Analysis

·         SAVANE – A PM Support Tool

The following contents have been modified:

·         Portal and DL Integration

·         Achieved Results and Conclusions

0.5

03/03/2006

The following contents have been added:

·         Additional Requirements for eConcertation requirements

·         “Area of Interest” descriptions for DL’s collections definition

0.6

10/03/2006

The following contents have been added:

·         All relevant info for eConcertation

0.7

21/04/2006

The following contents have been added:

·         Appendix A “Questionnaire for Requirements Collection”

The following contents have been modified:

·         “Expected Results” and “Achieved Results”

·         “Classes of Consumers – General Concepts”

1.0

28/04/2006

The following contents have been added:

·         Deliverable D4.1 full contents

·         Appendix C - “OpenDLib”

The following contents have been modified:

·         Organization (identification, content, etc.) of requirements

·         General structure of the deliverable to be consistent with added contents

1.0.1

10/05/2006

The following contents have been modified:

·         “Document Models”

·         ”Planning Brief for Future Releases”

1.0.2

06/06/2006

The following contents have been added:

·         “Direct Access to the DL – The User Interface”

The following contents have been modified:

·         Collections

·         “Collecting Documents and Metadata from Information Sources”

·         “Portal and DL Integration”

·         ”Planning Brief for Future Releases”

1.0.3

08/06/2006

Content has been updated to reflect last changes on:

·         Collections’ definition

·         Collections’ description

·         Types’ definition

1.0.4

26/06/2006

The following contents have been added:

·         All informations related to “Research Infrastructure Unit Initiative”

1.0

19/07/2006

Final review, the following contents have been modified:

·         Summary, Executive Summary and Introduction

·         Requirements Collection and Analysis – Adopted Methodology

·         Supported Standard Protocols and Formats

·         Information Consumers and Providers contents moved to Introduction and to The BELIEF DL sections

·         Models for Document Submission

·         Portal and DL Integration

·         Achieved results and conclusions

·         Planning Brief for Future Releases

1.1

28/07/2006

Minor typing changes. Version revised by Project Coordinator (MTW).

1.2

09/01/2007

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

 

1.                Summary

This document constitutes the first issue of the D5 deliverable “Bridging Information Consumers & Providers” as reported in the Project Deliverables List of BELIEF Project. Three issues of the D5 deliverable are planned (D5.1-M6, D5.2-M12 and D5.3-M18), basically corresponding to different levels of functional richness of the BELIEF Digital Library and community wideness growth.

This document collates results of activities carried out by CNR-ISTI in WP1 – Communication Platform and Digital Library development, T1.1 - Bridging Information Consumers, T1.2 – Setup and Maintenance of the Digital Library and T1.3 – Bridging Information Providers.

It also deals with topics related to the BELIEF Digital Library (hereinafter DL) design and implementation. The BELIEF DL constitutes the deliverables D4.1-M6, D4.2-M12 and D4.3-M18-24 of WP1 and each release is accompanied by a specific “Release Note” [WP1D4.1.a] and a “User Guide” [WP1D4.1.b].

For other related documents, see Section 8.

Access to the BELIEF Digital Library is available to all registered BELIEF community members from the BELIEF Project Portal at http://www.beliefproject.org/.

 

2.                Executive Summary

BELIEF Project’s aim is to create a platform where eInfrastructure providers and users can collaborate and exchange knowledge, which will help ensure that eInfrastructures are developed and used effectively worldwide – and its Digital Library (DL) is a key part of this project, benefiting eInfrastructures stakeholders everywhere. The BELIEF project originated from the perception that there is a gap separating the Research Infrastructure providers from the users. There was an opportunity to provide a ready and common source of information on eInfrastructures: both for the users wanting to find out the supply, or for the providers wanting to extend user base and develop their systems. The BELIEF DL responds to this demand by supplying to researchers documentation that matches their search criteria precisely, according to their interest and professional profile.

 

In Section 3 the overall WP’s goals and contents are briefly described, focussing on DL related issues and characteristics of the implemented solution.

 

Section 4 deals with all requirements collection and analysis related activities: first the methodology adopted for requirements collection is outlined, then requirements collected from the Description of Work (hereinafter DoW) document [DoW] and from the BELIEF DL potential users are described and analyzed.

Research Infrastructure Entities (Projects, Organizations and Initiatives) selected from the ones supporting BELIEF for the first release (D4.1-M6) of the BELIEF DL are identified and Information Sources([1]) analysed in terms of metadata and documents.

Referring to the activities presented in Section 4, we must bring out that significant effort was spent in:

·        Drawing up a Questionnaire (see Paragraph 4.1 and Section 9) to collect requirements.

·        Identifying proper interfaces within Entities, contacting them, obtaining and discussing requirements.

·        Harmonizing similar requirements coming from different Entities.

·        Verifying metadata quality and harmonizing metadata semantic and use;

·        Verifying documents quality, analyzing the document types used by different Entities with different semantics and harmonizing them.

·        Drawing up a Memorandum of Understanding to be signed with each of the Entities collaborating in subsequent releases to ensure clear, full and effective interaction and collaboration.

 

In Section 5 the implemented BELIEF DL is described. General concepts relevant for the BELIEF DL implementation are first introduced (Paragraph 5.1); these represent the logical link between the basic requirements and the components of the implemented solution. Then supported standard protocols and formats for metadata encoding and harvesting are summarized (Paragraph 5.2).

Even if Information Sources can be accessed via multiple protocols and formats, in the BELIEF DL the use of Dublin Core Qualified encoding has been chosen for metadata definition for interoperability purposes since it allows a better sharing of informations between Information Sources using different coding with no loss of semantics. The metadata structure for BELIEF DL is defined in Paragraph 5.3.

Documents and metadata collected by each selected Information Source are then described (Paragraph 5.4). Two cross-reference tables mapping BELIEF Document Types with Metadata and Document Types and Metadata used by Information Sources are provided and the integration with BELIEF Portal is described. Within this same Paragraph, tools developed for the harvesting of metadata and documents and the feeding of the BELIEF DL are introduced.

In Paragraph 5.5, sets of implemented “models” for the submission and retrieval of documents and metadata to/from the DL via a web-based interface are introduced.

Paragraph 5.6 deals with the integration of the BELIEF Portal with the DL. First, from an end-user perspective, informations logically linking the Portal and the DL are presented then, from a technical perspective, APIs on which the Portal and DL integration relies are briefly outlined.

The two implemented ways of accessing the BELIEF DL are then described:

·        Via the “DL wrapper” supported by the BELIEF Portal (suggested for novice users).

·        Via direct access to the DL (suggested for experienced users).

Paragraph 5.7 describes the hardware and software configuration of the BELIEF DL supporting environment, while Paragraph 5.8, finally, defines both the maintenance activities to be performed on the DL and the supported management functions.

Referring to the activities presented in Section 5, we must bring out that significant effort was spent in:

·        Implementing harvesters supporting even not-always-proper use of standard formats and conventions on Information Sources side (unfortunately, this is a matter of fact). Presently, the following standard protocols and coding formats are supported by the harvesting tools of the BELIEF DL:

o       Metadata encoding protocols: DC, DCQ (recommended), MARC, UNIMARC, MARC21.

o       Metadata harvesting protocols: OAI-PMH - Open Archives Initiative Protocol for Metadata Harvesting (recommended) or any API call returning an XML file containing metadata encoded in one of the above mentioned encoding.

o       File formats: XML (recommended), RSS.

·        Implementing “models” and a web-based interface allowing users to easily submit metadata and documents to the DL.

·        Designing and implementing a user-friendly interaction and a seamingless integration between the User, the Portal and the DL, allowing smooth transition between the outer and the inner level of the system.

·        Implementing a set of APIs to be easily used by programmers to interface basic functions of the DL. The interaction with the BELIEF Portal is supported by means of these APIs.

 

In Section 6 achieved results are punctually reported with respect to requirements expressed in Section 4 and conclusions are summarized and, finally, Section 7 outlines the planning for the future releases of the DL.

 

3.                Introduction

The BELIEF DL has been conceived to serve the needs of eInfrastructure researchers and industrial users that want to keep up to date on existing projects and products and on the latest developments in eInfrastructures.

The DL offers to its user community advanced services to uniformly access multimedia documents such as technical reports, presentations, videos, manuals, on-line tutorials, etc., which present very latest details on eInfrastructure related projects, initiatives and events.

The material maintained in the BELIEF DL is harvested from different sources, like web sites, repositories and databases of eInfrastructure Projects, Initiatives and Organizations. However, the BELIEF DL organizes the harvested information according to the information needs of the user communities rather than according to its physical format, structuring and distribution on the different sources, so that it is capable of providing users with multiple virtual views of the existing documentation. To achieve this, the construction of the DL has been preceded and continuously accompanied by a careful collection and analysis of the requirements of its potential users.

 

3.1.         General Concepts

This section introduces the main concepts that characterize the BELIEF DL as perceived by its end-users. These concepts represent the logical link between the basic requirements and the components of the implemented solution and can be summarized in the following proposition:

Users (according to their Role of Consumer, Provider or Librarian) of the BELIEF DL access DL’s Resources (Content gathered from Information Sources and Services) according to Access Rights on Collections grouped in user-specific Information Spaces. To each User a User Profile is associated recording her/his characteristics in terms of Information Space and Access Rights.

Where:

 

Users                 Are the actors entitled to interact with the DL. Different types of Users can be provided.

The following are the types of Users that the BELIEF DL presently supports:

·        Technician, with subtypes:

o       Administrator

o       Researcher

o       Manager/Executive

·        General Public

 

Role                   A function within the context of an organization (in our case the BELIEF DL) with some associated semantics regarding the authority and responsibility conferred on the user assigned role. Different types of Roles can be provided.

The following are the Roles that the BELIEF DL presently supports:

·        Consumers      Are the Users that access the DL for consuming its Content.

·        Providers         Are the Users that provide new Content to be stored into the DL or update already existing Content.

·        Librarian         i.e. the DL Administrator.

 

DL                      From a high-level perspective a DL is a organization with the capability of collecting, creating, accessing and managing a Content and offering to its Users specialized Services on that Content, according to prescribed Rights.

 

Resources         Are the resources which can be accessed by Users, depending on their Role and Rights. Different types of Resources can be provided.

The following are the types of Resources that the BELIEF DL presently supports:

·        Content            i.e. Information Sheets, News & Events, Training, Deliverables, Presentations, Meetings, User Guides, Technical Reports, Technical Notes, Metadata, etc..

·        Services           i.e. DL Administration, Publisher Administration, Document Submission, Document Approval, Collection Creation, etc..

 

Access Rights   Are the allowed actions on the Resources which can be accessed. (Create, Modify, Delete, Search/Browse, Use/Perform, etc.).

 

Collection          A set of Resources of type Content defined according to some characterization criteria.

Collections represent the mechanism to organise Content and to provide focused views of the Information Space. Thanks to these focused views the DL end-users are entitled to access to thematic parts of the whole Information Space. These focused views can be created by the Librarian in order to keep the DL Content organised and to improve its access and usage; further, they can be created by authorised Users in order to implement their own personal views of the DL Information Space. The definition and identification of the Contents constituting a Collection is based on a set of characterisation criteria. These criteria can range from the enumeration of the Contents belonging to the Collection to membership conditions that specify which are the properties that Contents must satisfy in order to become Collection members.

 

Information Space     Corresponds to set of Collections on the DL that each user can access. Information Spaces can be defined according to different criteria.

The following criteria are presently suggested to be followed in the BELIEF DL Information Spaces definition:

·        Different abstraction levels:

o       By Organization            (Academia, Industry, SME, etc.)

o       By Project                    (EGEE, DANTE, etc.)

o       By Main Topic             (High Parallel Computing, Network Security, etc.)

o       By Keywords               (Certification Authority, Public Key Infrastructure, Security policies, Web services security, etc.)

o       Etc.

·        The most common information needs of the defined Users:

o       “At a glance”                (i.e. Brochure + Presentation, etc.)

o       “General Executive”      (i.e. Project Management Document + Project Management Meeting, etc.)

o       “Developer”                 (i.e. eCourse + Software + Technical Document, etc.)

o       “General Admin”          (copying the actual organization of resources)

o       Etc.

 

User Profile       Contains information about the user. It may be viewed as a set of characteristics with associated values. A profile may store information of different kinds, such as: personal data (e.g., name, address), demographic data (such as marital and economic status), education and training level, group membership, preferences (e.g., look and feel of the user interface, preferred Content and Services of the DL), experience, knowledge, or skills, disabilities (e.g., vision problems), permissions, search history data, navigation history and so forth. Each piece of user information alone and in conjunction with others determines system behaviour towards the user.

The profile is strictly coupled to the informations, preferences and options managed by the BELIEF Portal and expressed by a user on registering to the BELIEF Community trough the BELIEF Portal (see Paragraph 5.6Portal and DL Integration”). Actually, the initial User Profile is created basing on such informations and can be further modified by the user.

 

Information Sources              As mentioned above, this term is used to mean metadata and documents related to/produced by an Entity (Projects, Organizations and Initiatives) and gathered to form the BELIEF DL.

Information Sources are characterized by the type, structure and semantics of the metadata and documents they contain.

 

3.2.         General Characteristics of the Implemented Solution

The BELIEF DL is created as an instance of the OpenDLib system, thus being capable of offering the following services to its users:

 

·        Submission, description, searching, browsing, retrieval, access, preservation and visualization of multimedia documents.

·        Definition of the their personal Information Space which they want to search/browse upon in terms of collections selected from those managed by the DL. Collections can be created interactively defining:

i)         the condition that is satisfied by the members of the collection;

ii)        ii) which archives the documents are to be selected from.

·        Different search/browse options: Google-like or fielded (with fields selected from a variety of known metadata formats), with or without relevance feedback. Users can search/browse any information associated with digital objects and their parts. As result of their search/browse operations, users obtain a set of results pages with the list of digital objects that satisfy their request. By clicking on the object, users can access any of its multiple manifestations. In particular, they can select the one that is compatible with the software installed on the local machine.

 

In the implementation of the BELIEF DL particular effort has been devoted to the following issues:

 

·        Implementation of harvesters supporting standard formats and specific conventions on Information Sources side. Presently, the following standard protocols and coding formats are supported by the harvesting tools of the BELIEF DL:

o       Metadata encoding protocols: DC, DCQ (recommended), MARC, UNIMARC, MARC21.

o       Metadata harvesting protocols: OAI-PMH - Open Archives Initiative Protocol for Metadata Harvesting (recommended) or any API call returning an XML file containing metadata encoded in one of the above mentioned encoding.

o       File formats: XML (recommended), RSS.

·        Implementation of “models” and of a web-based interface allowing users to easily submit metadata and documents to the DL.

·        Design and implementation of a user-friendly interaction and a seamingless integration between the User, the Portal and the DL, allowing smooth transition between the outer and the inner level of the system.

·        Implementation of a set of APIs to be easily used by programmers to interface basic functions of the DL. The interaction with the BELIEF Portal is supported by means of these APIs.

·        Harmonization of concepts (use of metadata, terms and of different types of document) to be benefited by the whole Community in facilitating knowledge communication and document exchange.

·        Factorization of vocabularies used both for metadata and document content description, categorization and search.

·        Implementation of research community oriented services.

The following services are supported by BELIEF and can be offered to any project of the research community willing/needing to benefit from BELIEF:

o       DL Hosting Service

BELIEF can offer 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.

o       DL Extended Access Service

BELIEF can offer an “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.

 

The BELIEF DL will thus cover a double role:

·        by supporting the integration of the produced documentation it will facilitate cross-fertilization and synergies between eInfrastructure performers, and

·        by providing a more friendly access via the availability of advanced services for the definition and navigation of personalized information spaces it will promote pervasive penetration of the state-of-the-art technology in the research infrastructures.

The benefits coming from the use of the BELIEF DL are twofold:

·        On the Information Provider’s side:

o       eInfrastructure projects’ documents can be accessed by a wider users’ community.

o       This wider audience is also a more targeted audience: the DL intelligently provides users with the most accurate selection for their needs, in a way that bridges them directly with the projects’ material.

o       It gives projects’ audience a one-stop-shop to find the precise documentation that they require about the projects, thus it is a valuable target to send inquirers to, should they be searching quickly for projects’ documentation.

o       Documents are accessible via different formats.

o       The DL supports document preservation.

o       Projects can submit their documents directly to the DL: BELIEF offers a submission interface and a document hosting service to host projects’ documents directly on the DL. To ensure that any new documents can be easily collected by the DL a standard method is provided by which to describe them.

·        On the Information Consumer’s side:

o       Directly accessing a website and browsing a project’s material, users get material from that project/website only. Using the DL they get the relevant information from many projects’ sites. This give them a wider range of information on eInfrastructures, how they work, what projects exists and how to use them.

o       User can search documents in a uniform way, accessing via a unique interface documents produced by different providers.

o       This is not like Google which may often come up with nothing or thousands of results or it yields material that is not relevant or up to date.

o       Even documents stored in inner sections of the websites - which are not indexed and accessed by common search engines - are accessed by the DL. The Belief DL knows what material the user is interested in, since this is told by the user itself when signing up to the BELIEF Community by filling in interest and profile criteria. The DL then intelligently provides users with the most accurate selection for their needs, in a way that bridges them directly with the eInfrastructure Providers’ material.

4.                Requirements Collection and Analysis

4.1.         Adopted Methodology

In order to adopt a structured approach to the requirements collection and analysis phase of the project, the following steps have been performed:

1.      Contacts have been established with a group of Entities (Projects which signed the Letter of Support for BELIEF, Organizations and Initiatives) chosen from the most relevant and/or suitable in terms of:

a.       quality of produced material (in terms of the particular significance of the related topic/area);

b.      quantity of produced material (in terms of the number of document types, use scenarios and availability of infos and documents), in order to have a large sample available;

c.       willingness to collaborate.

These Entities have been included in the first release of the DL (D4.1-M6).

2.      A Questionnaire has been produced to lead the requirements collection process and have been sent to the above mentioned Entities. To facilitate the requirements collection process, for some of these Entities requirements were preliminarily proposed by CNR-ISTI and confirmed or amended and improved by the Contact in charge of the interaction with BELIEF for each Entity.

3.      A Savane System instance has been setup and customized in order to comply with the specific needs of our project. The Savane System has been used to register and trace the collected requirements.

4.      Follow-up actions performed via e-mail and phone contact have been logged with Savane (details on contact points and actions can be found in Paragraph 4.4).

In the following, the collected requirements are presented grouped in:

·        Requirements directly expressed in the DoW.

·        Additional requirements emerged during project’s development.

·        Additional requirements deriving from designers’ analysis of the above mentioned requirements and from the interactions with the Contacts.

A cross-reference table listing requirements along with SAVANE items and paragraphs within this document dealing with them is provided in Paragraph 4.5.

In order to allow an easy tracing of the requirements, the following naming structure have been adopted:

RWPxTyz-nnn        where              R         means Requirement

                                                           x          is the Work Package number

                                                           yz         is the Task number (for requirements classified as

“Additional Requirement” this value is “AR”)

                                                           nnn       is a progressive for requirement identification

End of requirement text is determined by another requirement or by a specific marker:

<END OF REQUIREMENT>

The content of the Questionnaire used for collecting basic requirements related to the contents and logical organization of the Information Sources and of the Digital Library is shown in Appendix A.

In Appendix B the Savane System is briefly introduced as a supporting tool for Project Management activities and especially for the requirements collection and management.

 

4.2.         Requirements from DoW

Text of [DoW] is reported herein after and relevant parts making up requirements are identified as mentioned above.

4.2.1.      Bridging Information Consumers (WP1T11)

The BELIEF DL will respond to the pressing demand of many user communities that are approaching the eInfrastructure subject and that find extremely difficult to retrieve relevant documentation following the links spread on the different project Websites. This documentation is not only distributed, but also organised in a way which reflects the specific project activities structure, instead that the user logic, needs, and level of comprehension of the technology. Moreover, a global search facility is often missing.

This task will take care of:

RWP1T11-010      collecting, understanding and analysing the user communities needs in order to provide the guidelines necessary for the creation of a comprehensive multimedia DL. This activity will be based on the observation that, using the OpenDLib framework, the same sources can be virtually organised and structured according to the needs of the user communities audience.

RWP1T11-020      For this reason, for each user community two main different classes of providers: the technicians and general public will be identified.

RWP1T11-021      The technicians mainly include actors involved in the production of new sources related to eInfrastructure subjects and their consumption.

RWP1T11-022      The general public is intended to collect end-users and practitioners that are approaching specific subjects to investigate the potentiality of new technologies.

The former category will be selected from the community of e-Infrastructure projects developers; the latter will be initially recruited among the participants of a restricted number of EU and National projects that use the e-Infrastructure technologies as a basis for their development and, as the project progresses, among the members of the user communities that will participate to the BELIEF organised events.

RWP1T11-030      An appropriate tool, such as SAVANE, must be identified,

RWP1T11-031      then it will be set up by month 2 and

RWP1T11-032      it will made accessible to the identified representatives of the two user classes in order to allow them to continuously express their requirements.

The provision of their requirements and feedback will be a continuous activity that will improve the synergies between the information consumers and the BELIEF project.

This continuous needs gathering process will allow the collection of a wide variety of requirements from a large number of heterogeneous consumer communities.

RWP1T11-033      A specific priority will be assigned to each requirement that will drive our development and adaptation plan. Moreover, each requirement will be managed with a discussion thread that will include the acceptance, the understating, the management, and the final report stages.

<END OF REQUIREMENT>

 

4.2.2.      DL Creation and Maintenance (WP1T12)

RWP1T12-010      This activity will set up an instance of the OpenDLib system…

RWP1T12-020      …that can be interfaced with the selected information providers…

RWP1T12-030      …and satisfies the needs expressed by the information consumers.

RWP1T12-040      This will imply a design of the schema of the document model…

RWP1T12-050      …and of the information space organization,…

RWP1T12-060      …and an appropriate configuration of the OpenDLib services and architecture.

RWP1T12-070      This configuration may be changed during the BELIEF DL lifetime to…

RWP1T12-071      …support emerging requirements…

RWP1T12-072      …and to include new information providers.

RWP1T12-080      In particular, this activity will be also responsible for the management of the requirements expressed by the information consumers when they are consolidated and approved. This means that special actions would be required…

RWP1T12-081      to change the organization of the content sources for specific user communities,…

RWP1T12-082      to arrange a new perception view of the information sources that will be based on…

RWP1T12-083      new transformation of the source metadata,…

RWP1T12-084      to include other query languages,…

RWP1T12-085      etc..

<END OF REQUIREMENT>

 

4.2.3.      Bridging Information Providers (WP1T13)

Each information provider uses its own solution for managing her documents. It may be using software compliant with the Open Archive Initiative Protocol for Metadata Harvesting[2] (OAI-PMH) or not.

RWP1T13-010      In all cases, for each data provider, the BELIEF DL needs to have a specific behaviour, following dedicated processes for harvesting records of interest.

RWP1T13-020      This task therefore requires to implement the harvesting process for each information provider, accordingly to its policy and technology.

RWP1T13-030      Of course, this means recovering all past existing documents but also setting up periodical automated processes that will ensure the completeness of data made available through the BELIEF services.

RWP1T13-040      This software will also be in charge of ensuring semantic interoperability between the harvested information. It will require transformation of the source metadata into the common format of the BELIEF DL, with the constraint that the whole information must be preserved.

RWP1T13-050      Existing harvesting software should be re-used after a thorough comparison, especially for retrieving OAI-PMH compliant archives.

<END OF REQUIREMENT>

 

4.2.4.      BELIEF Portal and DL Integration (WP1T14)

The BELIEF Portal, on the other hand, will support the complete organizational, promotional and dissemination activities. It will incorporate the following features:

1)      A Trans-European database featuring the BELIEF research and industrial community.

2)      Online registration for brainstorming, networking workshops and the international conferences

3)      Automate personalised communications & interaction with registered users:

a.       Acknowledge registration and identify next steps.

b.      Support interaction between the research & industry communities, to facilitate knowledge sharing and community building.

RWP1T14-010

c.       Allow registered uses to interface with others, based on disclosed profiles of the user communities.

RWP1T14-020

d.      Digital rights management – Content Access based on Profile & Identity.

<END OF REQUIREMENT>

e.       Administration & Conference secretariat for brainstorming events, Networking workshops, international conferences.

RWP1T14-030

f.        Community Showcase and access to workshop and conferences presentations through the BELIEF DL functionalities

<END OF REQUIREMENT>

g.      Browsing research & industry profiled showcases by Name, Organization, Type of Organization or Organizational focus, FP6 project.

 

4.3.         Additional Requirements

4.3.1.      eConcertation Initiative

In addition to the above, new requirements were expressed by EC during the last eConcertation Meeting in Bordeaux (December 2005) regarding BELIEF to become a central access point for moderators and facilitators who attend the eConcertation Meetings which hold twice a year.

Discussion on this topic was immediately started and actions were undertaken in order to define support to the following:

·        Discussion forums which may be implemented on the BELIEF Portal.

·        A repository to store the documentation produced at the eConcertation Meetings (which could be the digital library developed in BELIEF).

From the DL point of view, this led to the definition of new requirements for WP1T12:

RWP1TAR-010

Definition of DL structures for implementing eConcertation Workgroups and Workshops requirements.

RWP1TAR-020

Definition of related metadata.

RWP1TAR-030

Definition of rules and procedures to be implemented for the harvesting of metadata and documents and tools for BELIEF DL feeding, distinguishing between the initial “bulk” load ad the following incremental updates.

<END OF REQUIREMENT>

 

4.3.2.      Research Infrastructure Unit Initiative

After the meeting between the Commission and the Project’s Management Board held in Brussels on 08.06.06 an agreement was reached in order to…

RWP1TAR-031

…let BELIEF provide a simple Web-based interface where users are asked to specify very simple information, e.g. author, title, event, and to upload their presentations. All the material submitted in this way will go into an incoming area, where BELIEF “librarian” will check it and make the submission permanent if everything is correct. The same procedure can be applied for any other type of simple documents, like for example, brochures and press releases.

RWP1TAR-032

For the time being, until a better knowledge of user needs shall be acquired, BELIEF librarian will take care of the submission of composite documents, like those related to the Knowledge Infrastructure events (in this case users may either send the link to the Web page where they have been published or e-mail the collected material itself to the BELIEF librarian).

When requirements shall be refined, a solution like the one implemented for requirement RWP1TAR-031 will be adopted.

<END OF REQUIREMENT>

 

4.4.         Requirements from Consumers and Providers

4.4.1.      Involved Research Infrastructure Projects, Organizations and Initiatives

RWP1TAR-040

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:

 

  • EGEE Project

(Enabling Grids for E-sciencE)

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

  • 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

  • SEE-GRID Project

(South Eastern European GRid-enabled eInfrastructure Development)

http://www.see-grid.org

  • e-IRG Organization and e-IRGSP Project

(e-Infrastructure Reflection Group)

http://www.e-irg.org

  • CONDOR Project

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

  • 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)

  • Research Infrastructure Unit Initiative

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

and, obviously,

  • BELIEF Project

(Bringing Europe’s eLectronic Infrastructures to Expanding Frontiers)

http://www.beliefproject.org

<END OF REQUIREMENT>

The rationale for this choice has been outlined in Paragraph 4.1Adopted Methodology”.

For strategic planning purposes, A list of other Entities to be potentially included has been drawn up and each of them has assigned a priority based on the above mentioned rationale. These will be approached three-at-a-time (this is considered the best-effort/dimension compromise for BELIEF project’s planning) and increasingly included in the DL’s releases (D4.2-M12 and D4.3-M18-24).

A Memorandum of Understanding has also been drawn up and will be signed with each of these Entities to ensure they place their data and documentation on the DL.

Basic Requirements related to the contents and logical organization of the Information Sources and of the Digital Library have been collected using the Questionnaire shown in Appendix A.

To facilitate the requirements definition process, for some of these Entities requirements were preliminarily proposed by CNR-ISTI and confirmed or amended and improved by the Contact in charge of the interaction with BELIEF for each Entity.

RWP1TAR-050

Starting from these requirements, a draft classification of Users and Consumers and their needs was produced and preliminarily discussed with MTW in order to adopt a common approach for T1.4, which had to provide Portal and DL integration (see Paragraph 5.6Portal and DL Integration”).

RWP1TAR-060

Harvesting process has to be implemented for the identified Information Sources (see Paragraph 5.4Collecting Documents and Metadata from Information Sources”) for DL feeding.

RWP1TAR-070

Submission interfaces have to be defined (see Paragraph 5.5Document Submission and Search”) for supporting information providers in adding their material to the DL.

<END OF REQUIREMENT>

 

4.4.2.      Information Source Documents and Metadata

RWP1TAR-080

Documents to be collected from each selected Entity are listed in the following together with metadata to be collected from each of them.

RWP1TAR-090

For document type correspondences between BELIEF DL and the Entities, see Paragraph 5.4.1Document type cross-reference”.

RWP1TAR-100

For metadata correspondences between BELIEF DL and the Entities, see Paragraph 5.4.2Metadata cross-reference”.

<END OF REQUIREMENT>

4.4.2.1.            EGEE

RWP1TAR-110

Documents

The material the EGEE project is willing to provide is the following:

Training

Accessible via a Fedora Repository
(http://129.215.30.186:20100/egeelearning/describeDatabase.jsp

 http://egee.lib.ed.ac.uk/)

o       Article

o       Audio

o       Book

o       Code Exemplar

o       Course

o       Event

o       Exercise

o       Module

o       Presentation

o       Series

o       Tutorial

o       Video

o       Website

Conferences

Accessible via Indico System, developed on CDSware System
(
http://indico.cern.ch/index.py
 
http://indico.cern.ch/categoryDisplay.py?categId=415

 http://cdsware.cern.ch/)

o       Contributions

o       Events

o       Presentations

o       Talks

Public documents and other informations

Accessible via EDMS System
(
https://edms.cern.ch/cedar/plsql/cedarw.site_home

 https://edms.cern.ch/cedar/plsql/cedarw.home?cookie=4520646&project=EGEE)

o       Deliverables

o       Information Sheets

o       Events

o       Meetings

o       (Meeting) Minute(s)

o       News Releases

o       Technical Reports

o       Technical Notes

o       User Guides

 

Metadata

Training

Content is available via OAI harvesting service. Dublin Core (pure) encoding has been chosen up to now for a simple transcoding into OAI-compliant records. The following metadata are available up to now (DC format is shown):

·        Title

·        Creator

·        Type

·        Date

·        Status

In the next future a new metadata profile will be available including new DC terms and OpenURL identifiers.

Conferences

Content is available via Indico Search service (http://indicosearch.cern.ch/). MARCXML output encoding has been chosen up to now. The following metadata are available (DC format is shown):

·        Identifier

·        Title

·        Description.abstract

·        Creator

·        Type

·        Date

·        Coverage.spatial

·        Coverage.temporal

Public documents and other informations

The Metadata available for the EGEE Public Documents are described below (DC format is shown).

The following are accessible via API invocation on EDMS system:

·        Identifier

·        Description.abstract

·        Creator

·        Identifier.URL

·        Status

The following are obtained parsing the html page accessed via “Identifier.URL”:

·        Title

·        Type

·        Date

<END OF REQUIREMENT>

 

4.4.2.2.            DANTE

RWP1TAR-120

Documents

The material the DANTE Organization is willing to provide is the following:

  • Formal Project Deliverables for public circulation
  • Presentations
  • Publicity Brochures and Leaflets
  • Maps and Posters

This applies for each of the following Entities, when available:

  • DANTE itself
  • GEANT2
  • GEANT
  • TEIN2
  • EUMEDCONNECT
  • ALICE

 

Metadata

The following have been agreed with DANTE (Beale and Pauley) up to now:

  • Since BELIEF use DC Qualified encoding (see description in this document), DANTE will provide at least (DC format is shown):
    • Title
    • Creator
    • Subject
    • Description
    • Date
    • Type
    • Identifier
    • Identifier.URL
  • BELIEF is ready to accept even more Type.document values than the initially agreed ones.
  • DANTE will provide a PHP to be invoked to get metadata in RDF format.

Implementation will be available in next release.

<END OF REQUIREMENT>

 

4.4.2.3.            SEE-GRID

RWP1TAR-130

Documents

The material the SEE-GRID project is willing to provide is the following:

  • Public Deliverables
  • Events
  • News
    • Articles
    • News
    • Newsletters
    • Press
  • Brochures

 

Metadata

All material of SEE-GRID project is available on:

http://www.see-grid.org/index.php?
op=modload&modname=Sitemap&action=sitemapviewpage&pageid=67

It is encoded in RSS format and provided via 6 different files:

  • events.rdf describes the events (RSS 1.0 have been used because it contains the event module)
  • deliverables.xml describes the public deliverables (RSS 2.0)
  • press.xml describes the press releases uploaded in the project site (RSS 2.0)
  • newsletter.xml describes the project newsletters (RSS 2.0)
  • news.xml describes the articles written for the project (RSS 2.0)
  • brochures.xml describes brochures of the project (RSS 2.0)

The Metadata stored for the SEE-GRID material are described in the following tables.

The first column of the array describes the table’s fields. The second column provides a small description for each field and the third column if this field is necessary to be filled or not. There are three cases:

  • Needed: This is an obligatory field to be filled out.
  • Not needed: User doesn’t need to provide information for this field.
  • Automatic: User doesn’t have to provide any information for this field.

 

Pubic Deliverables

Name

The deliverable title

Needed

Link

The deliverable file

Needed

Description

Description of the deliverable

Not needed

Size of the file

The file’s size

Automatic

Events

Events

Title

The event’s title

Needed

Date

The event’s date

Needed

Description/Objectives

The event’s description

Not needed

Programme

The event’s program

Not needed

Organizer’s

A description for the organizing committee

Not needed

Participants

A description for those who should attend the event

Not needed

Contact

Contact details for the event

Not needed

News

Press

Name

The press release’s title

Needed

Link

The press release’s file

Needed

Description

Description of the press release

Not needed

Size of the file

The file’s size

Automatic

 

Newsletter

Name

The newsletter’s title

Needed

Link

The newsletter’s file

Needed

Description

Description of the newsletter

Not needed

Size of the file

The file’s size

Automatic

 

Articles

Title

The article’s title

Needed

Link

The article’s online link

Needed

Date

The date the articles has been published

Needed

Description

A small description for the article

Needed

Brochures

Title

The brochure’s title

Needed

Link

The brochure’s file

Needed

Description

A small description for the brochure

Not Needed

Size of the file

Size of the brochure’s file

Automatic

<END OF REQUIREMENT>

 

4.4.2.4.            e-IRGSP

RWP1TAR-140

Documents

The material that e-IRG/e-IRGSP is willing to provide is the following:

  • Information Sheets
  • Meetings
  • Publications
    • Opportunities List
    • e-Infrastructures Roadmap
    • White Papers
  • Meeting Minutes

No access is provided in an automated way.

For the BELIEF current release, documents have been inserted by BELIEF DL Administrator.

 

Metadata

No metadata is provided in an automated way.

For the BELIEF current release, metadata have been inserted by BELIEF DL Administrator.

<END OF REQUIREMENT>

 

 

4.4.2.5.            CONDOR

RWP1TAR-150

Documents

The material the CONDOR Project is willing to provide is the following:

  • Manuals
  • Research Publications
  • Slide Presentations
  • Technical Documents

Metadata

Content is directly available to the harvesting service. Dublin Core Qualified encoding is used.

The following metadata are available (DC format is shown):

  • Title
  • Creator
  • Subject
  • Description.abstract
  • Publisher
  • Contributor
  • Date
  • Type

<END OF REQUIREMENT>

 

4.4.2.6.            DILIGENT

RWP1TAR-160

Documents

The material the DILIGENT Project is willing to provide is the following:

  • Deliverable
  • eCourse
  • Events & Meetings
  • Manuals & User Guides
  • Presentations
  • Project Management Document
  • Project Management Meeting
  • Software
  • Technical Document
  • Training
  • Tutorials

Metadata

Content is directly available to the harvesting service. Dublin Core Qualified encoding is used.

The following metadata are available (DC format is shown):

  • Title
  • Creator
  • Subject
  • Description.abstract
  • Publisher
  • Contributor
  • Date
  • Type

<END OF REQUIREMENT>

 

4.4.2.7.            eConcertation

RWP1TAR-170

Documents

The material the eConcertation Initiative is willing to provide is the following:

  • Presentations
  • Talks
  • Tutorials
  • Deliverables
  • Events
  • Meetings
  • Workshops
  • Workgroups
  • News
  • Brochures
  • Etc. (generally any public material)

Metadata

Up to now, metadata cannot be extracted automatically from any repository.

Thus, the following elements have been identified to be supported as entities described by metadata within the overall context of eConcertation Workgroups and Workshops (DC format is shown):

  • Workshops, Events and Meetings are described by:
    • Title
    • Organizer
    • Subject
    • Description
    • Data
    • Venue
    • Attendees
    • Agenda
  • Workgroups are described by:
    • Title
    • Subject
    • Description
    • Coordinator
    • Members
  • Other documents are described by
    • Title
    • Author
    • Keywords
    • Description
    • Date (creation, modification)
    • Type (Presentation, Talk, Tutorial, etc.)
    • Related Workgroup
    • Related Workshop

<END OF REQUIREMENT>

 

 

eConcertation additional requirements impact on the BELIEF DL

The introduction of this requirement led to the definition of the following further requirements:

RWP1TAR-171

·        Definition of DL structures.

o       A specific Collection needs to be defined for this Initiative.

o       Specific Discussion Interest Areas need to be defined related to the workgroups’ themes:

      • Monitoring & Performance Enhancement
      • Resource Management and Allocation
      • Security and AAI
      • Interoperability and Interface

RWP1TAR-172

·        Definition of metadata.

Consistency of defined BELIEF Metadata was checked against eConcertation needs and properly cross-referenced. No further element needs to be defined.

RWP1TAR-173

·        Definition of rules, procedures and tools for the harvesting of metadata and documents.

<To be implemented in the next release>

<END OF REQUIREMENT>

 

 

4.4.2.8.            Research Infrastructure Unit Initiative

RWP1TAR-174

Documents

The material the Research Infrastructure Unit Initiative is willing to provide is the following:

  • Presentations

These will be submitted to the BELIEF DL directly by means of a web interface.

Metadata

Metadata will be specified at submission time accordingly to the document model provided by BELIEF.

<END OF REQUIREMENT>

 

 

Research Infrastructure additional requirements impact on the BELIEF DL

The introduction of this requirement led to the definition of the following further requirements:

RWP1TAR-175

·        Definition of DL structures.

o       A specific Collection needs to be defined for this Initiative.

·        Definition of metadata.

Consistency of defined BELIEF Metadata was checked against Research Infrastructure needs and properly cross-referenced. No further element needs to be defined.

<END OF REQUIREMENT>

 

 

4.5.         Requirements cross-reference

 

 

Requirement

SAVANE Item

Treated in

Bridging information consumers (WP1T11)

RWP1T11-010

SR106

Section 4Requirements Collection and Analysis

RWP1T11-020

SR106

Section 3.1General Concepts

RWP1T11-021

SR106

Section 3.1General Concepts

RWP1T11-022

SR106

Section 3.1General Concepts

RWP1T11-030

SR120

Paragraph 4.1Adopted Methodology

RWP1T11-031

SR120

Paragraph 4.1Adopted Methodology

RWP1T11-032

SR120

Paragraph 4.1Adopted Methodology

RWP1T11-033

SR120

Paragraph 4.1Adopted Methodology

DL creation and maintenance (WP1T12)

RWP1T12-010

SR121

Paragraph 5.6.4Direct Access to the DL

RWP1T12-020

SR118, SR119, SR122, SR123, SR124, SR125, SR126, SR127, SR128, SR130

Section 4Requirements Collection and Analysis

Paragraph 5.3BELIEF DL Metadata Definition

Paragraph 5.4Collecting Documents and Metadata from Information Sources

RWP1T12-030

SR113, SR119

Section 4Requirements Collection and Analysis

Paragraph 5.3BELIEF DL Metadata Definition

Paragraph 5.4Collecting Documents and Metadata from Information Sources

RWP1T12-040

SR119

Paragraph 5.5Document Submission and Search

RWP1T12-050

SR119

Paragraph 5.1.1Collections

RWP1T12-060

SR119, SR121

Paragraph 5.6.4Direct Access to the DL

RWP1T12-070

SR117, SR121

Paragraph 5.8Managing DL Maintenance

RWP1T12-071

SR117, SR121

Paragraph 5.8Managing DL Maintenance

RWP1T12-072

SR117, SR121

Paragraph 5.8Managing DL Maintenance

RWP1T12-080

SR121

Paragraph 5.8Managing DL Maintenance

RWP1T12-081

SR121

Paragraph 5.8Managing DL Maintenance

RWP1T12-082

SR121

Paragraph 5.8Managing DL Maintenance

RWP1T12-083

SR121

Paragraph 5.8Managing DL Maintenance

RWP1T12-084

SR121

Paragraph 5.8Managing DL Maintenance

RWP1T12-085

SR121

Paragraph 5.8Managing DL Maintenance

Bridging information providers (WP1T13)

RWP1T13-010

SR131

Section 3.1General Concepts

RWP1T13-020

SR131

Section 3.1General Concepts

RWP1T13-030

SR131

Section 3.1General Concepts

RWP1T13-040

SR131

Section 3.1General Concepts

RWP1T13-050

SR131

Section 3.1General Concepts

BELIEF Portal and DL integration (WP1T14)

RWP1T14-010

SR132

Paragraph 5.6Portal and DL Integration

RWP1T14-020

SR132

Paragraph 5.6Portal and DL Integration

RWP1T14-030

SR132

Paragraph 5.6Portal and DL Integration

Additional Requirements

RWP1TAR-010

SR129

Section 4Requirements Collection and Analysis

Paragraph 5.4Collecting Documents and Metadata from Information Sources

RWP1TAR-020

SR129

Section 4Requirements Collection and Analysis

Paragraph 5.3BELIEF DL Metadata Definition

RWP1TAR-030

SR129

Paragraph 5.4Collecting Documents and Metadata from Information Sources

RWP1TAR-031

SR134

Paragraph 5.4Collecting Documents and Metadata from Information Sources

RWP1TAR-032

SR124

Paragraph 5.4Collecting Documents and Metadata from Information Sources

RWP1TAR-040

SR122

Paragraph 5.4Collecting Documents and Metadata from Information Sources

RWP1TAR-050

SR119

Paragraph 5.6Portal and DL Integration

RWP1TAR-060

SR122

Paragraph 5.5Document Submission and Search

RWP1TAR-070

SR122

Paragraph 5.5Document Submission and Search

RWP1TAR-080

SR122

Paragraph 5.4Collecting Documents and Metadata from Information Sources

RWP1TAR-090

SR122

Paragraph 5.4.1Document type cross-reference

RWP1TAR-100

SR122

Paragraph 5.4.2Metadata cross-reference

RWP1TAR-110

SR123, SR127, SR130

Paragraph 5.4Collecting Documents and Metadata from Information Sources

RWP1TAR-120

SR124

Paragraph 5.4Collecting Documents and Metadata from Information Sources

RWP1TAR-130

SR125

Paragraph 5.4Collecting Documents and Metadata from Information Sources

RWP1TAR-140

SR128

Paragraph 5.4Collecting Documents and Metadata from Information Sources

RWP1TAR-150

SR126

Paragraph 5.4Collecting Documents and Metadata from Information Sources

RWP1TAR-160

SR122

Paragraph 5.4Collecting Documents and Metadata from Information Sources

RWP1TAR-170

SR129

Paragraph 5.4Collecting Documents and Metadata from Information Sources

RWP1TAR-171

SR129

Paragraph 5.4Collecting Documents and Metadata from Information Sources

RWP1TAR-172

SR129

Paragraph 5.4Collecting Documents and Metadata from Information Sources

RWP1TAR-173

SR129

Paragraph 5.4Collecting Documents and Metadata from Information Sources

RWP1TAR-174

SR134

Paragraph 5.4Collecting Documents and Metadata from Information Sources

RWP1TAR-175

SR134

Paragraph 5.4Collecting Documents and Metadata from Information Sources

 

5.                The BELIEF DL

In this Section the implemented BELIEF DL is described. General concepts relevant for the BELIEF DL implementation are first introduced (Paragraph 5.1).

Then supported standard protocols and formats for metadata encoding and harvesting are summarized (Paragraph 5.2).

Even if Information Sources can be accessed via multiple protocols and formats, in the BELIEF DL the use of Dublin Core Qualified encoding has been chosen for metadata definition for interoperability purposes since it allows a better sharing of informations between Information Sources using different coding with no loss of semantics. The metadata structure for BELIEF DL is defined in Paragraph 5.3.

Documents and metadata collected by each selected Information Source are then described (Paragraph 5.4). Two cross-reference tables mapping BELIEF Document Types with Metadata and Document Types and Metadata used by Information Sources are provided and the integration with BELIEF Portal is described. Within this same Paragraph, tools developed for the harvesting of metadata and documents and the feeding of the BELIEF DL are introduced.

In Paragraph 5.5, sets of implemented document models for the submission and retrieval of documents and info to/from the DL via a web-based interface are introduced.

Paragraph 5.6 deals with the integration of the BELIEF Portal with the DL. Designing and implementing a user-friendly interaction and integration between the User, the Portal and the DL, allowing seamingless transition between the outer and the inner level of the system was a primary goal of the project.

First, from an end-user perspective, informations logically linking the Portal and the DL are presented then, from a technical perspective, APIs on which the Portal and DL integration relies are briefly outlined.

The two implemented ways of accessing the BELIEF DL are then described:

·        Via the “DL wrapper” supported by the BELIEF Portal (suggested for novice users).

·        Via direct access to the DL (suggested for experienced users).

Paragraph 5.7 describes the hardware and software configuration of BELIEF DL supporting environment, while Paragraph 5.8, finally, defines both the maintenance activities to be performed on the DL and the supported management functions.

5.1.         General Concepts

The BELIEF DL is created as an instance of OpenDLib. OpenDLib is a Digital Library Management System (DLMS) 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.

The main services offered by a OpenDLib based system are:

·        Submission, description, searching, browsing, retrieval, access, preservation and visualization of multimedia documents.

·        Definition of user-specific Information Space on which searching/browsing upon in terms of collections selected from those managed by the DL. Collections can be created interactively.

·        Different search/browse options: Google-like or fielded (with fields selected from a variety of known metadata formats), with or without relevance feedback.

For more detailed information on OpenDLib see Appendix C.

Two methods for feeding the DL with new metadata and documents are supported:

·        Via harvesting from existing Information Sources.

·        Via direct submission to the DL.

These methods described respectively in Paragraphs 5.4 and 5.5.

Presently, BELIEF characterize the DL Collections in terms of:

·        Document Types

·        Projects, Organizations and Initiatives

·        Interest Areas (Available in the next release):

o       Applications

o       Discussion Topics

While Projects, Organizations and Initiatives are a continuously increasing set, the following Document Types are presently provided by BELIEF DL:

·        Brochure

·        Conference & Meeting

·        Deliverable

·        eCourse

·        Manual & User Guide

·        News

·        Poster

·        Presentation

·        Project Management Document

·        Project Management Meeting

·        Publication

·        Software

·        Training

·        Technical Document

Mapping between these DL Document Types and Document Types used by Information Sources is provided in 5.4.1Document type cross-reference”.

The two following paragraphs define respectively:

·        Collections (and Sub-collections) and related details which have been so far created within the DL, in terms of:

o       Document Types

o       Projects, Organizations and Initiatives

·        Interest Areas, i.e. a suggestion for the subjects to be proposed to BELIEF Community members as “Area of Application Interest” and “Area of Topic Discussion Interest” for which corresponding Collections could be defined.

Presently these subjects are proposed on BELIEF Portal at registration time to collect Community members’ interests; their description defines the semantic domain of collections to be implemented. Subjects and their descriptions can be enriched and/or modified basing on Community members’ suggestions collected through the Portal, to direct actual implementation.

 

5.1.1.      Collections

 

Collections & sub-collections

Details

 

·         Document Types

Name

Document Types

 

Image/Logo

<BELIEF Project Logo>

 

Description

This collection contains all public documents produced by collaborating Entities (Projects, Organizations and Initiatives) which will be accessible through the BELIEF DL.

This collection is further organized in sub-collections, one for each document type.

 

Sub-collections

Brochure

Conferences & Meetings

Deliverables

Manuals & User Guides

Outreach

Presentations

Project Management

Publications

Software

Technical Documents

Training

 

Metadata Format

 

 

Access Rights

 

o        Conferences & Meetings

Name

Events & Meetings

 

Image/Logo

<BELIEF Project Logo>

 

Description

This collection contains all information related to events and meetings of interest hosted by or signalled by collaborating Entities

 

Values from Information Sources:

Conferences

Events

Meetings

Workgroups

Workshops

 

Metadata Format

 

 

Access Rights

 

o        Deliverables

Name

Deliverables

 

Image/Logo

<BELIEF Project Logo>

 

Values from Information Sources

This collection contains all public deliverables produced by collaborating Entities.

 

Subject

Deliverables

 

Metadata Format

 

 

Access Rights

 

o        Manuals & User Guides

Name

Manuals & User Guides

 

Image/Logo

<BELIEF Project Logo>

 

Description

This collection contains all official use documentation produced by collaborating Entities

 

Values from Information Sources

Documentation

Guidelines

Manuals

User Guides

 

Metadata Format

 

 

Access Rights

 

o        Outreach

Name

Outreach

 

Image/Logo

<BELIEF Project Logo>

 

Description

This collection contains all official information and dissemination materials produced by collaborating projects

 

Values from Information Sources

Brochures

Flyers

Information Sheets

Leaflets

Maps

News

Newsletters

Posters

Press

 

Metadata Format

 

 

Access Rights

 

o        Presentations

Name

Presentations

 

Image/Logo

<BELIEF Project Logo>

 

Description

This collection contains all public presentations produced by collaborating Entities.

 

Values from Information Sources

Contributions

Presentations

Talks

 

Metadata Format

 

 

Access Rights

 

o        Project Management

Name

Project Management

 

Image/Logo

<BELIEF Project Logo>

 

Description

This collection contains all documents related to the managements of the contributing Entities.

 

Values from Information Sources

Consortium Agreements

Contracts

Meetings

Minutes

Plans

Quality Plans

Technical Annexes

 

Metadata Format

 

 

Access Rights

 

o        Publications

Name

Publications

 

Image/Logo

<BELIEF Project Logo>

 

Description

This collection contains all official documents produced by researcher involved on various relevant topics with respect to the goals of the communities.

 

Values from Information Sources

Articles

Books

Publications

White Papers

 

Metadata Format

 

 

Access Rights

 

o        Software

Name

Software

 

Image/Logo

<BELIEF Project Logo>

 

Description

This collection contains software produced by researcher involved on various relevant topics with respect to the goals of the communities.

 

Values from Information Sources

Software

 

Metadata Format

 

 

Access Rights

 

o        Technical Documents

Name

Technical Documents

 

Image/Logo

<BELIEF Project Logo>

 

Description

This collection contains all documents (not formally published) produced by researcher involved on various relevant topics with respect to the goals of the communities.

 

Values from Information Sources

Technical Documents

Technical Notes

Technical Reports

 

Metadata Format

 

 

Access Rights

 

o        Training

Name

Training

 

Image/Logo

<BELIEF Project Logo>

 

Description

This collection contains all available public training documents produced by collaborating Entities

 

Values from Information Sources

eCourses

Modules

Presentations

Training

Tutorials

Videos

 

Metadata Format

 

 

Access Rights

 

·         Projects, Organizations and Initiatives

Name

Projects, Organizations and Initiatives

 

Image/Logo

<BELIEF Project Logo>

 

Description

This collection contains all public documents produced by collaborating Entities (Projects, Organizations and Initiatives) which will be accessible through the BELIEF DL.

This collection is further organized in sub-collections, one for each collaborating Entity.

 

Sub-collections

·         EGEE

·         DANTE

·         GEANT2

·         GEANT

·         TEIN2

·         EUMEDCONNECT

·         ALICE,

·         SEE-GRID

·         e-IRGSP

·         CONDOR

·         DILIGENT

·         eConcertation

·         Research Infrastructure

 

Metadata Format

 

 

Access Rights

 

o        (for each Entity)

Name

<Entity’s Name>

 

Image/Logo

< Entity’s official Logo>

 

Description

<short description>

 

Web Site

< Entity’s web site>

 

Metadata Format

 

 

Access Rights

 

·         Application Areas

Name

Application Areas

 

Description

This collection contains the application areas which DL contents belong to.

Each application area is in turn qualified by a set of specific subjects.

 

Sub-collections

·         Astrophysics

·         Business

·         Bioinformatics

·         Biophysics

·         Chemistry

·         Digital Libraries

·         Earth Science

·         Financial

·         Geophysics

·         Mathematical and computer methods in mechanics

·         Material processing & Sciences

·         Medicine & Biology

·         Physics

 

Metadata Format

 

 

Access Rights

 

o        Application Areas
(for each)

Name

<Application Area Name>

 

Description

<short description>

 

Subject

<main topics>

 

Metadata Format

 

 

Access Rights

 

·         Discussion Topic Areas

Name

Discussion Topic Areas

 

Description

This collection contains the discussion topic areas which DL contents belong to.

Each discussion topic area is in turn qualified by a set of specific subjects.

 

Sub-collections

GRID/Middleware:

·         AAI (Authentication and Authorization Infrastructure)

·         Applications of parallel/distributed/GRID computing

·         Data Management

·         Dependable networks & middleware

·         GRID & eInfrastructure in Industry

·         Grid Access

·         GRID On Demand

·         Information & Monitoring

·         Interoperability & Interfaces

·         Methods and tools for dependable distributed systems

·         Metrics for trustworthiness

·         Middleware Security

·         Performance Monitoring, Analysis & Prediction

·         Resources Management & Allocation

·         Scheduling, mapping, load balancing

·         Virtual Organization(s)

·         Workload Management

 

Networking:

·         Advanced Network Monitoring

·         Bandwidth on Demand

·         End to End Service Provision

·         IPV6

·         Layer 2 VPN

·         Multicast

·         Network Security

·         Performance Measurement and Monitoring

·         Quality of Service

·         Testbed, technology testing

 

Metadata Format

 

 

Access Rights

 

o        Discussion Topic Areas (for each)

Name

<Discussion Topic Area Name>

 

Description

<short description>

 

Subject

<main topics>

 

Metadata Format

 

 

Access Rights

 

 

 

5.1.2.      Interest Areas

 

Subject

Description