026500

 

BELIEF

Bringing Europe’s eLectronic Infrastructures to Expanding Frontiers

 

 

WP1D5.2 - Bridging Information Consumers & Providers

Ver. 0.2.1

 

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.2 - T1.1-T1.2-T1.3 - Bridging Information Consumers & Providers.

 

Contents

 

1...... Summary. 6

2...... Executive Summary. 7

3...... Introduction. 9

3.1.   General Concepts. 9

3.2.   General Characteristics of the Solution Implemented. 12

4...... Requirement Collection and Analysis. 14

4.1.   Adopted Methodology. 14

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

4.3.1.   eConcertation Initiative. 18

4.3.2.   Research Infrastructure Unit Initiative. 18

4.3.3.   Case Study. 19

4.3.4.   Sub Community. 19

4.4.   Requirements from Consumers and Providers. 20

4.4.1.   Involved Research Infrastructure Projects, Organisations and Initiatives. 20

4.4.2.   Information Source Documents and Metadata. 22

4.5.   Requirements cross-reference. 36

5...... The BELIEF DL. 39

5.1.   General Concepts. 39

5.1.1.   Collections. 41

5.1.2.   Interest Areas. 46

5.2.   Supported Standard Protocols and Formats. 52

5.3.   BELIEF DL Metadata Definition. 53

5.3.1.   DL Metadata list 53

5.3.2.   DL Metadata details. 53

5.4.   Collecting Documents and Metadata from Information Sources. 59

5.4.1.   Document type cross-reference. 60

5.4.2.   Metadata cross-reference. 62

5.4.3.   Developed Tools for Document and Metadata Harvesting. 64

5.5.   Document Submission and Search. 66

5.5.1.   Models for Document Submission. 66

5.5.2.   Search Types. 67

5.6.   Portal and DL Integration. 68

5.6.1.   Registering as a BELIEF Community Member 68

5.6.2.   Portal and DL integration via APIs. 71

5.6.3.   Accessing the DL via the BELIEF Portal 72

5.6.4.   Direct Access to the DL. 72

5.7.   Basic DL Configuration. 75

5.8.   Managing DL Maintenance. 76

5.8.1.   Day-by-day activities. 76

5.8.2.   Managing Information Sources. 76

5.8.3.   Harvesters scheduling. 76

5.8.4.   Information filtering. 76

5.8.5.   Managing Collections. 76

5.8.6.   Managing Metadata Changes. 77

5.8.7.   Managing Document Models. 77

5.8.8.   Adding a Sub Community. 77

5.8.9.   Usage Statistics. 78

6...... Achieved Results and Conclusions. 79

7...... Planning Brief for Future Releases. 83

7.1.   Entities to be added. 83

7.2.   Harvesting Tools to be implemented. 84

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

8...... References. 85

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

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

11.... Appendix C – OpenDLib. 93

 

Log of changes

 

Version N°

Date (dd/mm/yyyy)

Changes

D5.1V0.1

15/12/2005

None – First draft

D5.1V0.2

28/12/2005

The following contents have been modified:

·         “General Concepts”

·         “BELIEF Portal and DL integration”

D5.1V0.3

02/01/2006

The following contents have been added:

·         Requirements cross-reference

D5.1V0.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

D5.1V0.5

03/03/2006

The following contents have been added:

·         Additional Requirements for eConcertation requirements

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

D5.1V0.6

10/03/2006

The following contents have been added:

·         All relevant info for eConcertation

D5.1V0.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”

D5.1V1.0

28/04/2006

The following contents have been added:

·         Deliverable D4.1 full contents

·         Appendix C - “OpenDLib”

The following contents have been modified:

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

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

D5.1V1.0.1

10/05/2006

The following contents have been modified:

·         “Document Models”

·         ”Planning Brief for Future Releases”

D5.1V1.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”

D5.1V1.0.3

08/06/2006

Content has been updated to reflect last changes on:

·         Collections’ definition

·         Collections’ description

·         Types’ definition

D5.1V1.0.4

26/06/2006

The following contents have been added:

·         All informations related to “Research Infrastructure Unit Initiative”

D5.1V1.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

D5.1V1.1

28/07/2006

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

D5.2V0.1

25/10/2006

First release of he second issue.

The following contents have been added:

·         All informations related to the new “Case Study” facility

·         All informations related to the new “Sub Community” facility

·         All informations related to “Managing DL Maintenance”

The following contents have been modified:

·         DANTE harvesting for DCQ compliance

·         EGEE Conferences harvesting for DCQ compliance

·         “Basic DL Configuration”

D5.2V0.2

15/11/2006

Second release of he second issue.

The following contents have been added:

·         All informations related to the new projects:

o        BioinfoGRID

o        DRIVER

o        EELA

o        ETICS

o        EUChinaGRID

o        EUIndiaGRID

o        EUMEDGRID

o        Grid@Asia

o        GridCC

o        ICEAGE

o        ISSeG

o        LOBSTER

o        MUPBED

The following contents have been modified:

·         TBD

D5.2V0.2.1

09/01/2007

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

 

 

1.                Summary

This document is the second issue of the D5 deliverable “Bridging Information Consumers & Providers”, as indicated in the BELIEF Project Deliverables List. Three issues of the D5 deliverable are planned (D5.1-M6, D5.2-M12 and D5.3-M18), corresponding to the scope of functionalities of the BELIEF Digital Library (DL) and the expansion of the BELIEF Community. Each issue of this  Deliverable includes the contents of the earlier issue(s). 

This document brings together the results of activities carried out by CNR-ISTI in Work Package 1 (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.

In addition, this document covers topics relating to both the design and implementation of the BELIEF DL. The BELIEF DL is covered in the Deliverables D4.1-M6, D4.2-M12 and D4.3-M18-24 of WP1 and each release is issued with a specific “Release Note” [WP1D4.1.a, WP1D4.2.a], a “User Guide” [WP1D4.1.b, WP1D4.2.b], and a “User Guide At-a-Glance” [WP1D4.2.c].

For other related documents, see Section 8.

Access to the BELIEF DL is available to all Members registered with the BELIEF Community through the BELIEF Project Portal at http://www.beliefproject.org/.

 

2.                Executive Summary

The BELIEF Project aims to create an effective forum where e-Infrastructure providers and users can collaborate and exchange knowledge, ensuring the development and adoption of e-Infrastructures on a worldwide scale. The BELIEF DL plays a key part in the project, bringing a range of benefits to e-Infrastructures stakeholders across the globe by facilitating the exchange of knowledge and experiences through a single and easily accessible tool. The BELIEF Project was developed from an awareness that a gap existed between Research Infrastructure providers and users. In order to bridge this gap, a complete and common source of information on e-Infrastructures was needed, both for users demanding provision,and resources and for providers intending to extend their user base and develop their systems. The BELIEF DL responds to this demand by providing users with research and similar documentation matching their search criteria accurately and according to their interests and professional profile.

 

Section 3 describes the focus and main goals of the WP with particular reference to issues relating to the DL and the features concerning the solutions implemented.

 

Section 4 deals with collection and analysis requirements. The methodology adopted for collection requirements is outlined. The requirements indicated in the Description of Work (DoW) and the BELIEF DL potential users are described and analysed.

Research Infrastructure Entities (Projects, Organisations and Initiatives) selected from Entities 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.

Activities outlined in Section 4 comprise the following:

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

·        Matching similar requirements from diverse Entities.

·        Verifying the quality of the metadata and making the semantics and use of metadata conform;

·        Verifying the quality of documents, analysing the types of documents used by diverse Entities with different semantics and making them conform.

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

 

Section 5 addresses the implementation of the BELIEF DL. General concepts regarding the implementation of the BELIEF DL are outlined (Paragraph 5.1). These general concepts represent the logical link between basic requirements and the components of the solution implemented. Additionally, the standard protocols supported and formats for encoding and harvesting metadata are summarised (Paragraph 5.2).

While Information Sources can be accessed via multiple protocols and formats, the BELIEF DL adopts Dublin Core Qualified [DCQ] encoding to define metadata for the purpose of interoperability, since such encoding enables the enhanced sharing of information between Information Sources using different coding with no loss of semantics. Paragraph 5.3 defines the metadata structure for the BELIEF DL.

Paragraph 5.4 describes the documents and metadata collected by each selected Information Source. Two cross-reference tables map BELIEF Document Types with Metadata and Document Types and Metadata used by Information Sources and describe the integration with the BELIEF Portal. This Paragraph also illustrates the tools developed for harvesting metadata and documents and feeding the BELIEF.

Paragraph 5.5 presents the sets of “models” adopted for submitting and retrieving documents and metadata to/from the DL via a web-based interface.

Paragraph 5.6 deals with the integration of the BELIEF Portal with the DL. The information logically linking the Portal and the DL are explained from an end-user perspective. From a technical perspective, the APIs on which Portal and DL integration relies are briefly described.

This Paragraph also explains the two different ways of accessing the BELIEF DL:

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

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

Paragraph 5.7 describes the hardware and software configuration of the BELIEF DL supporting environment. Paragraph 5.8 defines both the maintenance activities and the management functions supported.

With regard to the activities presented in Section 5, significant efforts have been spent on the following:

·        Implementing harvesters that also support the use of standard formats and conventions on Information Sources that are not always correctly performed (such non-conformities have been known to occur). The following standard protocols and coding formats are currently supported by the BELIEF DL harvesting tools:

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 enabling users to submit metadata and documents to the DL easily.

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

·        Implementing a set of APIs that can be easily adopted by programmers to interface basic DL functions. Interaction with the BELIEF Portal is supported by these APIs.

 

Section 6 presents the results achieved with reference to the requirements outlined in Section 4, together with the conclusions. Section 7 outlines the planning for future releases of the DL.

 

3.                Introduction

The BELIEF DL has been designed to serve the needs of e-Infrastructure research and industrial users that want to keep up to date with existing projects and the latest developments in e-Infrastructures.

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

The material maintained in the BELIEF DL is harvested from different sources, such as web sites, repositories and databases of e-Infrastructure Projects, Initiatives and Organisations. The BELIEF DL organises the harvested information according to the information needs of the user communities rather than according to its physical format, structuring and distribution on diverse  sources, so that it is capable of providing users with multiple virtual views of the existing documentation. To this end, a continuous and meticulous collection and analysis of the requirements of potential users was made before the DL was created.

3.1.         General Concepts

This section introduces the main concepts characterising the BELIEF DL from the perspective of its end-users. These concepts represent the logical link between the basic requirements and the components of the solution implemented, as follows:

Users (according to their Role of Consumer, Provider or Librarian) of the BELIEF DL access the DL’s Resources (Content gathered from Information Sources and Services) according to the Access Rights on Collections grouped in user-specific Information Spaces. A User Profile is associated with each User recording his/her 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 currently supports:

·        Technician, with subtypes:

o       Administrator

o       Researcher

o       Manager/Executive

·        General Public

 

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

The BELIEF DL currently supports the following roles:

·        Consumers      Users that access the DL to utilise its Content.

·        Providers         Users that provide new Content to be stored on the DL or update Content that already exist.

·        Librarian         The DL Administrator.

 

DL                      From a high-level perspective, a DL is an organisation capable of collecting, creating, accessing and managing Content and offering to its Users specialised Services on that Content, according to the Rights prescribed.

 

Resources         The resources that can be accessed by Users, depending on their Role and Rights. Diverse types of Resources can be provided.

The BELIEF DL currently supports the following types of Resources:

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

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

 

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

 

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

Collections represent the mechanism to organise Content and to provide focused views of the Information Space. These focused views entitle DL end-users to access to thematic parts of the whole Information Space. These focused views can be created by the Librarian to keep the DL Content organised and improve its access and usage. Additionally, they can be created by authorised Users to implement their own personal views of the DL Information Space. A set of characterisation criteria defines and identifies the Contents forming a Collection.  These criteria can range from the enumeration of the Contents belonging to the Collection to membership conditions that specify the properties that Contents must meet 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 recommended for defining the BELIEF DL Information Spaces:

·        Different abstraction levels:

o       By Organisation            (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 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 organisation 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 different types of information, 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 information, preferences and options managed by the BELIEF Portal and expressed by a user on registering with the BELIEF Community through the BELIEF Portal (see Paragraph 5.6Portal and DL Integration”). The initial User Profile is created based on such information and can be further modified by the user.

 

Information Sources  This term is used to indicate metadata and documents related to/produced by an Entity (Projects, Organisations and Initiatives), collected to form the BELIEF DL.

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

 

3.2.         General Characteristics of the Solution Implemented

The BELIEF DL is an instance of the OpenDLib system and is therefore capable of offering the following services to its users:

 

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

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

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

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

 

The following issues have been addressed in the design and implementation of the BELIEF DL: 

 

·        Implementation of harvesters supporting standard formats and specific conventions in terms of Information Sources.. The following standard protocols and coding formats are currently supported by the BELIEF DL harvesting tools:

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

o       File formats: XML (recommended), RSS.

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

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

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

·        Organisation of concepts (use of metadata, terms and diverse types of documents) that can benefit the whole Community by facilitating document and knowledge exchange.

·        Factorisation of vocabularies used both for metadata and document content description, categorisation and search.

·        Implementation of research community oriented services.

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

o       DL Hosting Service

BELIEF can offer a DL hosting service (design, implementation and maintenance of a DL) for entities that cannot (or do not want to) afford their own.

o       DL Extended Access Service

BELIEF can offer an “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 by adding transform capabilities.

 

The BELIEF DL therefore plays a dual role:

·        by supporting the integration of documentation produced, it will facilitate cross-fertilisation and synergies between e-Infrastructure performers;

·        by providing more friendly access via the availability of advanced services for defining and navigating personalised information spaces, the BELIEF DL will promote the pervasive penetration of state-of-the-art technology in research infrastructures.

The benefits of using the BELIEF DL include:

·        From the perspective of the Information Provider::

o       E-Infrastructure project documents can be accessed by a wider user community;

o       This wider audience is also a more targeted audience: the DL intelligently provides users with the most accurate selection for their needs, building a bridge between the user and the material generated by diverse projects;

o       This DL provides a one-stop-shop to find the exact documentation about the projects that users require, making it a valuable target for inquirers searching quickly for the  documentation of a range of projects;

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 project documents directly on the DL. A standard method for describing new documents ensures that they can easily be collected by the DL.

·        From the Information Consumer persepctive:

o       The BELIEF DL provides the Consumer with relevant information from the sites of many projects, giving them a wider range of information on e-Infrastructures, how they work, what projects exists and how to use them. This offers a clear advantage over directly accessing a website and browsing project material, which provides from that project/website only;

o       Users can search documents in a uniform way and accessing documents produced by different providers via a single interface;

o       The BELIEF DL provides both relevant and up-to-date information unlike a typical Google-like search that may often come up with nothing or thousands of results or that generates irrelevant material;

o       The BELIEF DL also provides access to documents stored in the inner sections of  websites, which are not indexed and accessible via common search engines. The BELIEF DL knows what material the user is interested in, since this information is provided the users themselves by creating a personal and interest profile when signing up with the BELIEF Community. The DL then intelligently provides users with the most accurate selection for their needs, creating a direct link between users and e-Infrastructure Provider material.

4.                Requirement Collection and Analysis

4.1.         Adopted Methodology

The following measures were adopted to provide a structured approach to the collection requirements and analysis phase of the Project:

1.      Contacts were established with a group of the most pertinent Entities (Projects that signed a Letter of Support for BELIEF, Organisations and Initiatives) in terms of:

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

b.      quantity of material produced (regarding the number of document types, use scenarios and availability of information and documents), in order to make 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 was produced to help define the collection requirement process and  sent to the above-mentioned Entities. To facilitate this process, in some instances, the requirements were preliminarily proposed by CNR-ISTI. The Entities concerned subsequently confirmed, or amended and improved the requirements by the Contact responsible for interacting with BELIEF.

3.      A Savane System instance has been set up and customised to comply with the specific needs of the Project. The Savane System has been used to register and trace the requirements collected.

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

The requirements collected are grouped as follows:

·        Requirements directly expressed in the DoW;

·        Additional requirements that have emerged during Project’s development.

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

Paragraph 4.5 contains a cross-reference table listing requirements along with SAVANE items and paragraphs within the relevant document.

The following symbols have been adopted so that the requirements can be easily traced: 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>

Appendix A shows the layout of the Questionnaire used to collect basic requirements concerning the content and logical organisation of the Information Sources and the DL.

Appendix B presents the Savane System as a supporting tool for Project Management activities, particularly the collection and management of requirements.

4.2.         Requirements from DoW

The exact text of the [DoW] document is reported herein. 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 their 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 conveyed by the EC during the last eConcertation Meeting in Bordeaux (December 2005). According to this requirement, BELIEF should become a central access point for moderators and facilitators attending the eConcertation Meetings held 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 Management Board, held in Brussels on 08.06.06 an agreement was reached in order to…

RWP1TAR-031

…allow BELIEF to 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 the BELIEF “librarian” will check it and make the submission permanent provided everything is correct. The same procedure can be applied for any other type of simple documents, for example, brochures and press releases.

RWP1TAR-032

For the time being, until a better knowledge of user needs has been acquired, the BELIEF librarian will deal with 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 have been refined, a solution like the one implemented for requirement RWP1TAR-031 will be adopted.

<END OF REQUIREMENT>

 

4.3.3.      Case Study

During the PMB Meeting on 24.08.06, in order to emphasise synergies with the objectives of WP3, an agreement was reached to…

RWP1TAR-033

…provide a simple “Submit Case Study” facility with the following flow:

1.      User submits a Case Study to the BELIEF Portal via a new specific form;

2.      BELIEF Portal places the Case Study in the DL (submission will be implemented via a new “Submit” API);

3.      BELIEF Administrator receives and edits the case study and approves it (via DL UI function);

4.      User can search case studies on the BELIEF Portal via a new specific form.

Users do not need to be authorised to use the submission service since this function is performed at Portal-DL integration level.

<END OF REQUIREMENT>

 

4.3.4.      Sub Community

During the PMB Meeting on 24.08.06, following a suggestion from the PUSP Project Partner, an agreement was reached to…

RWP1TAR-034

…provide a “Sub Community” facility allowing to:

·        Create a Sub Community within the BELIEF Community for a particular project.

·        Use the BELIEF DL as a document repository accessible only by this Sub Community.

The overall facility flow will be as follows:

  1. Sub Community members must sign up with the BELIEF Community;
  2. A responsible for the new Sub Community must contact the BELIEF Project asking for 'Project X' to have its own community repository, communicating Sub Community members’ names;
  3. BELIEF DL Administrator arrange for the creation of proper structures creation and assignment of grants;
  4. Project members submit the documents with the correct metadata according to the submission form(s) available from BELIEF UI;
  5. The responsible of the Sub Community approves the submitted documents:
  6. The documents of the Sub Community are placed in a reserved area where only that Sub Community’s members can share it;
  7. Documents that are to be made available to the entire community must be re-submitted (provided this procedure has been properly authorised). The BELIEF DL Administrator is responsible for authorising this procedure.

<END OF REQUIREMENT>

 

4.4.         Requirements from Consumers and Providers

4.4.1.      Involved Research Infrastructure Projects, Organisations and Initiatives

RWP1TAR-040

With regard to the Research Infrastructure Entities (Projects that have 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

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

For this set of Information Sources no requirements needed to be defined in addition to those defined for the first release.

<END OF REQUIREMENT>

The rationale behind this selection is explained in Paragraph 4.1Adopted Methodology”.

For strategic planning purposes, a list of other Entities to be potentially included has been drawn up. Each of these Entities has been assigned a priority based on the above-mentioned rationale. These Entities will be approached three-at-a-time (this is considered the best-effort/dimension compromise for BELIEF Project planning), and will be 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 organisation of the Information Sources and of the DL have been collected using the Questionnaire illustrated in Appendix A.

To facilitate the requirement definition process, these were preliminarily proposed by CNR-ISTI to several of the Entities selected and subsequently confirmed or amended and improved by the Contact responsible for interacting with the             BELIEF Project.

RWP1TAR-050

Based on these requirements, a draft classification of Users and Consumers and their needs was produced and discussed with MTW, in order to adopt a common approach for T1.4, which specifies  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 (for each metadata the DC naming convention is used, despite of its original naming convention).

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 EGEE project is willing to provide the following material:

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://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

 https://edms.cern.ch/cedar/plsql/api_egee.STO$GET_XML_DOC_LIST)

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 thus far for a simple transcoding into OAI-compliant records. The following metadata are available to date:

·        dc:title

·        dc:creator

·        dc:type

·        dc:date

·        dc:status

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

Conferences

Access to Indico’s content is available both via the “Indico Search” service (http://indicosearch.cern.ch/) and via AOI standard protocol. (http://indico.cern.ch/oai.py, starting from 2Q2006, Indico V0.9x). A number of different output formats is also available, including DC.

At presently, the metadata quality obtained via “Indico Search” remains preferable to the AOI quality. Output in MARCXML is more detailed compared with DC output, hence content is harvested via “Indico Search” and the MARCXML output is translated into DCQ by the harvester.

The following metadata are currently available:

·        dc:identifier

·        dc:title

·        dc:description.abstract

·        dc:creator

·        dc:type

·        dc:date

·        dc:coverage.spatial

·        dc:coverage.temporal

Public documents and other information

The Metadata available for the EGEE Public Documents are described below.

The following are accessible via API invocation on EDMS system:

·        dc:identifier (EDMS internal)

·        dc:identifier.URL

·        dc:description.abstract

·        dc:creator

·        dc:status

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

·        dc:title

·        dc:type

·        dc:date

<END OF REQUIREMENT>

 

4.4.2.2.            DANTE

RWP1TAR-120

Documents

DANTE is willing to provide is the following material:

  • Case studies
  • 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 metadata are available (starting from 2Q2006) via API invocation on DANTE repository (http://www.dante.net/resource_xml_export.php):

·        dc:title

·        dc:creator

·        dc:subject

·        dc:description

·        dc:publisher

·        dc:contributor

·        dc:date

·        dc:type

·        dc:format

·        dc:language

·        dc:identifier

·        dc:identifier.URL

Unfortunately, only a few of these metadata have not-null values, namely:

·        dc:title

·        dc:subject

·        dc:description

·        dc:language

·        dc:identifier

·        dc:identifier.URL

The following are thus obtained via some heuristic rules on the content of the previous:

·        dc:publisher

·        dc:type

<END OF REQUIREMENT>

 

4.4.2.3.            SEE-GRID

RWP1TAR-130

Documents

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

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

 

Metadata

All material of the 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 tables below.

The first column in the table shows the fields. The second column provides a brief description for each field and the third column whether this field needs filling in.

There are three cases:

  • Needed: This is a mandatory field to be filled out.
  • Not needed: User does not need to provide information for this field.
  • Automatic: User does not 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

Organiser’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 as follows:

  • 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 CONDOR Project is willing to provide is the following material:

  • Manuals
  • Research Publications
  • Slide Presentations
  • Technical Documents

Metadata

Access to CONDOR’s content is available via AOI standard protocol. Dublin Core Qualified encoding is used. The following metadata are available:

  • dc:title
  • dc:creator
  • dc:subject
  • dc:description.abstract
  • dc:publisher
  • dc:contributor
  • dc:date
  • dc:type

<END OF REQUIREMENT>

 

4.4.2.6.            DILIGENT

RWP1TAR-160

Documents

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

  • 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 (BELIEF and DILIGENT share the same repository). Dublin Core Qualified encoding is used. The following metadata are available:

  • dc:title
  • dc:creator
  • dc:subject
  • dc:description.abstract
  • dc:publisher
  • dc:contributor
  • dc:date
  • dc:type

<END OF REQUIREMENT>

 

4.4.2.7.            eConcertation

RWP1TAR-170

Documents

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

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

Metadata

At present, 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:

  • Workshops, Events and Meetings are described by:
    • Title
    • Organiser
    • 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 implementation 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 Research Infrastructure Unit Initiative is willing to provide is the following material:

  • Presentations

These will be submitted to the BELIEF DL directly through a web interface.

Metadata

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

<END OF REQUIREMENT>

 

 

Research Infrastructure additional requirements impact on the BELIEF DL

The implementation 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.4.2.9.            Case Study

RWP1TAR-176

Documents

Users will provide is the following material:

  • Case Study (free text/documents plus the descriptive information descripted in the following).

Metadata

The proposed submission form fields and their mapping with DC attributes is as follows:

i)          Organisation                è        dc:contributor

The name of the organisation of the user sending the case study.

ii)         Organisation type         è        dc:contributor.organizationtype

Values:

    • Academia
    • EU Funded Project
    • Industry
    • Research
    • RTD (Research and Technological Development)
    • SME (Small and Medium Enterprise)
    • NGO (Non Governative Organisation)
    • Government

iii)       Project type                 è        dc:contributor.projecttype

Values: TBD

iv)       Country                       è        dc:coverage.spatial

v)        Period                         è        dc:coverage.temporal

vi)       Author                         è        dc:creator

User sending the case study

vii)     Submitter                     è        dc:publisher

The person in charge of submission/approval to the DL

viii)    Date                            è        dc:date

Date of submission

ix)       Title                             è        dc:title

x)        Abstract                      è        dc:description

xi)       Keywords                   è        dc:subject

xii)     Rights                          è        dc:rights

xiii)    Language                     è        dc:language

xiv)   Document                    è        N/A

<END OF REQUIREMENT>

 

 

Case Study additional requirements impact on the BELIEF Portal

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

RWP1TAR-177

·        Creation of two forms for submission and search of “Case Study”. The fields have been specified above.

RWP1TAR-178

·        Integration with the DL via “Submit” API.

The Case Study will be submitted to the DL by the Portal at system level using a new API.

<END OF REQUIREMENT>

 

 

Case Study additional requirements impact on the BELIEF DL

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

RWP1TAR-179

·        Definition of DL structures.

A specific collection has to be defined for “Case Study”.

RWP1TAR-180

·        Definition of metadata.

A specific dc:type has to be defined for “Case Study”.

RWP1TAR-181

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

A new “Submit” API has to be implemented.

<END OF REQUIREMENT>

 

4.4.2.10.        Sub Community

RWP1TAR-182

Documents

Users will provide is the following material:

  • Any type of document supported by BELIEF.

Metadata

Metadata will be specified at submission time according to the document model provided by BELIEF for each document type.

<END OF REQUIREMENT>

 

 

Sub Community additional requirements impact on the BELIEF Portal

None.

 

 

Sub Community additional requirements impact on the BELIEF DL

The implementation of this requirement led to the definition of the following further requirement:

RWP1TAR-183

·        Definition of DL structures.

i)       A specific Authority has to be defined for each “Project X”.

ii)      A specific Private Set has to be defined for each “Project X”.

iii)    A specific Collection has to be defined for each “Project X”.

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

SR157

Paragraph 5.4Collecting Documents and Metadata from Information Sources

Paragraph 5.6Portal and DL Integration

RWP1TAR-034

SR164

Paragraph 5.5Document Submission and Search

Paragraph 5.8Managing DL Maintenance

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

RWP1TAR-176

SR157

Paragraph 5.4Collecting Documents and Metadata from Information Sources

Paragraph 5.6Portal and DL Integration

RWP1TAR-177

SR157

Paragraph 5.4Collecting Documents and Metadata from Information Sources

Paragraph 5.6Portal and DL Integration

RWP1TAR-178

SR157

Paragraph 5.4Collecting Documents and Metadata from Information Sources

Paragraph 5.6Portal and DL Integration

RWP1TAR-179

SR157

Paragraph 5.4Collecting Documents and Metadata from Information Sources

Paragraph 5.6Portal and DL Integration

RWP1TAR-180

SR157

Paragraph 5.4Collecting Documents and Metadata from Information Sources

Paragraph 5.6Portal and DL Integration

RWP1TAR-181

SR157

Paragraph 5.4Collecting Documents and Metadata from Information Sources

Paragraph 5.6Portal and DL Integration

RWP1TAR-182

SR164

Paragraph 5.5Document Submission and Search

Paragraph 5.8Managing DL Maintenance

RWP1TAR-183

SR164

Paragraph 5.5Document Submission and Search

Paragraph 5.8Managing DL Maintenance

 

5.                The BELIEF DL

This Section explains the implementation of the BELIEF DL, starting with pertinent general concepts (Paragraph 5.1). Supported standard protocols and formats for metadata encoding and harvesting are summarised in Paragraph 5.2.

Although Information Sources can be accessed via multiple protocols and formats, Dublin Core Qualified [DCQ] encoding is used to define metadata definition for interoperability purposes, since DCQ enables the enhanced sharing of information between Information Sources adopting different coding with no loss of semantics. The metadata structure for BELIEF DL is defined in Paragraph 5.3.

Paragraph 5.4 describes the documents and metadata collected by each selected Information Source. Two cross-reference tables map BELIEF Document Types with Metadata and Document Types and Metadata used by Information Sources. Integration with the BELIEF Portal is also explained. In addition, details of the tools developed for harvesting metadata and documents and feeding the BELIEF DL are given.

Paragraph 5.5 focuses on sets of implemented document models for submitting and retrieving documents and information to/from the DL via a web-based interface.

Paragraph 5.6 deals with the integration of the BELIEF Portal with the DL. One of the primary goals of the Project was to design and implement user-friendly interaction and integration between the User, the Portal and the DL, enabling the seamless transition between the outer and the inner level of the system. Information logically linking the Portal and DL are presented from an end-user perspective, and an overview of the APIs on which the Portal-DL integration relies is given from a technical perspective.  The two ways of accessing the BELIEF DL are also described:

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

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

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

5.1.         General Concepts

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

The main services offered by a OpenDLib based system are:

·        Submission, description, searching, browsing, retrieval, access, preservation and visualisation of multimedia documents;

·        Definition of user-specific Information Space for searching/browsing 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 are described in Paragraphs 5.4 and 5.5 respectively.

BELIEF classifies the DL Collections in terms of:

·        Document Types

·        Projects, Organisations and Initiatives

·        Interest Areas (Available in the next release):

o       Applications

o       Discussion Topics

While Projects, Organisations and Initiatives are continuously increasing, the following Document Types are currently provided by BELIEF DL:

·        Brochure

·        Case Study

·        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 given in 5.4.1Document type cross-reference”.

The following two paragraphs define respectively:

·        Collections (and Sub-collections) and related details created at the present time within the DL, in terms of:

o       Document Types

o       Projects, Organisations and Initiatives

·        Interest Areas, i.e. a suggestion for areas of interest or applications 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.

At present, these areas of interest and applications are included in the on-line Community registration form. The areas selected define the semantic domain of collections to be implemented. These areas and related descriptions can be extended and/or modified based on the suggestions made by Community member through the Portal.

 

 

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, Organisations and Initiatives) which will be accessible through the BELIEF DL.

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

 

Sub-collections

Brochure

Case Study

Conferences & Meetings

Deliverables

Manuals & User Guides

Outreach

Presentations

Project Management

Publications

Software

Technical Documents

Training

 

Metadata Format

 

 

Access Rights

 

o        Case Studies

Name

Case Studies

 

Image/Logo

<BELIEF Project Logo>

 

Description

This is a collection of e-Infrastructures case studies submitted freely by BELIEF members  registered through the portal. This represents a 'best practice' collection, a window onto the pioneering e-Infrastructures activities of researchers and businesses worldwide.

 

Values from Information Sources:

Case Study

 

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 researchers involved in a variety of topics related 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 researchers involved in a variety of topics related 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 researchers involved in a variety of topics related 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, Organisations and Initiatives) which will be accessible through the BELIEF DL.

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

 

Sub-collections