isa - integrated collaborative platform functional ... · pdf file1.2 definitions, acronyms...

Copyright Atos Origin 2010. Tous droits réservés. Reproduction complète ou partielle interdite sans le consentement écrit du propriétaire. Atos, Atos et le poisson, Atos Origin et le poisson, Atos Consulting ainsi que le poisson seul sont des marques déposées d'Atos Origin SA

/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

ISA - Integrated Collaborative Platform

Functional Specifications

Customer : EC DIGIT

Project : ISA-ICP

Reference : ISA-ICP_SPE001

Version : 4.1

Status : REVIEWED

Date : 24/06/2011

Classification : Public

Appendices number : 0

ISA - Integrated Collaborative Platform / Functional Specifications

Public ISA-ICP_SPE001– revision 4.1– REVIEWED– 24/06/2011

Copyright Atos Origin 2011. All rights reserved. Partial or complete copy without written authorization granted by the document owner is forbidden.

/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

Revision history

REVISION DATE CHANGES COMPARED TO PREVIOUS VERSION

(CHAPTERS) WRITTEN BY VERIFIED BY APPROVED

BY

1.0 10/12/2010 Creation of the document LCT

1.1 24/01/2011 Update of the document according to the remarks of SSS and VPS

LCT FMR

2.0 04/02/2011 Add the scope of the product version 2

Modify §1.1, 1.2, 1.3, 2.2, 4.1, 5.2.4.1, 5.7, 8.2, 9.1

Add §5.8, 5.9, 5.10, 6, 8.3, 8.4, 8.10, 8.11, 8.12, 8.13

typo §5.2.1, 5.5.1

LCT

04/02/2011

FMR

04/02/2011

2.1 03/03/2011 Update the document according to the remarks of SSS

LCT

03/03/2011

FMR

2.2 15/03/2011 Update the taxonomies and the open source software fields

§8.3, §9

LCT

15/03/2011

FMR

15/03/2011

2.3 17/03/2011 Modify the classification of the document from “Project Only” to “Public”

Update the document with the comment from SSS §6.11.5.2.

Include the mail templates for the request membership §5.2.4.2 and §6.1.3.2

LCT

17/03/2011

FMR

17/03/2011

SSS

17/03/2011


Modify §1.2, §1.3, §4.1, §5, §6.5.3

Add §5.9, §5.10, §5.11, §5.13, §6.12, §7.1, §7.2, §7.3, §7.4, §8.16, §8.17, §8.18, §8.19, §8.20, §8.21

FMR

22/03/2011

LCT

01/04/2011


§2.2, §4.2.2, §5.9.1, §5.9.3, §5.9.4, §5.10.1, §5.10.3, §5.10.4, §, §5.11.1, §5.12.1, §5.13.1, §5.13.3, §6.4.1, §6.5.1, §6.7.3, §6.8.3, §6.12.1, §7.3.1, §7.4.1, §8.1

Delete of the §4.2.6

FMR 06/05/2011

LCT

12/05/2011


§2.3, §5.12.1, §6.7.3

TBR

17/05/2011

LCT

17/05/2011


§2.4, §4.1, §4.2.1, §4.2.6, §5.1.2, §5.2.2.1, §5.2.4.5, §5.3, §5.8, §6.1.3.5, §8.21

Update some elements

§6.1.3.6, §6.12.1, §8.18,

LCT

13/06/2011

TBR

17/06/2011

4.1 24/06/2011 Update the document according to SSS remarks

§2.4, §5.2.2.1, §5.2.4.5, §6.1.3.5, §8.5, §8.18

LCT

13/06/2011

CSR

13/06/2011




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

TABLE OF CONTENTS

ISA - INTEGRATED COLLABORATIVE PLATFORM ...................................................................................... 1

FUNCTIONAL SPECIFICATIONS ..................................................................................................................... 1

REVISION HISTORY .......................................................................................................................................... 2

TABLE OF CONTENTS ..................................................................................................................................... 4

1. INTRODUCTION ............................................................................................................................... 10

1.1 Aims................................................................................................................................................... 10

1.2 Definitions, acronyms and abbreviations .......................................................................................... 10

1.3 Reserves ........................................................................................................................................... 11

2. THE USERS ...................................................................................................................................... 12

2.1 Type of users ..................................................................................................................................... 12

2.2 The roles ........................................................................................................................................... 12

2.3 The user attributes ............................................................................................................................ 13

2.4 User activity tracking ......................................................................................................................... 14

3. USER MANAGEMENT ..................................................................................................................... 16

3.1 Synopsis ............................................................................................................................................ 16

3.1.1 Create account ................................................................................................................................. 16

3.1.2 Authenticate ..................................................................................................................................... 16

3.1.3 Edit profile ........................................................................................................................................ 17

3.1.4 Manage user .................................................................................................................................... 17

3.1.5 Delete account ................................................................................................................................. 17

3.1.6 Request new password .................................................................................................................... 17

3.2 Management rules ............................................................................................................................. 17

3.3 Workflow ............................................................................................................................................ 18

3.3.1 Create account ................................................................................................................................. 18

3.3.2 Manage user .................................................................................................................................... 18

4. SITE MAP AND PAGE STRUCTURE .............................................................................................. 19

4.1 Site map ............................................................................................................................................ 19

4.2 Presentation of ISA-ICP home page ................................................................................................. 20

4.2.1 The wireframe .................................................................................................................................. 20

4.2.2 The header ....................................................................................................................................... 21

4.2.3 The menu ......................................................................................................................................... 21

4.2.4 The submenu ................................................................................................................................... 21

4.2.5 The content ...................................................................................................................................... 22

4.2.6 The footer ......................................................................................................................................... 22




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

5. “INFORM” LAYER ........................................................................................................................... 24

5.1 General .............................................................................................................................................. 24

5.1.1 Synopsis ........................................................................................................................................... 24

5.1.2 The wireframe of the community home page ................................................................................... 26

5.1.3 Workflow ........................................................................................................................................... 27

5.1.4 Business rules .................................................................................................................................. 31

5.2 COMMUNITIES ................................................................................................................................. 31

5.2.1 Synopsis ........................................................................................................................................... 31

5.2.2 Data model ....................................................................................................................................... 32

5.2.3 Business rules .................................................................................................................................. 33

5.2.4 Workflow ........................................................................................................................................... 34

5.3 News.................................................................................................................................................. 36

5.3.1 Synopsis ........................................................................................................................................... 36

5.3.2 Wireframe of embed news ............................................................................................................... 37

5.3.3 Data model ....................................................................................................................................... 38

5.3.4 Business rules .................................................................................................................................. 38

5.3.5 Workflow ........................................................................................................................................... 38

5.4 Blogs.................................................................................................................................................. 38

5.4.1 Synopsis ........................................................................................................................................... 38

5.4.2 Data model ....................................................................................................................................... 38

5.4.3 Business rules .................................................................................................................................. 38

5.4.4 Workflow ........................................................................................................................................... 38

5.5 Wikis .................................................................................................................................................. 38

5.5.1 Synopsis ........................................................................................................................................... 38

5.5.2 Data model ....................................................................................................................................... 39

5.5.3 Business rules .................................................................................................................................. 39

5.5.4 Workflow ........................................................................................................................................... 39

5.6 Forum topics ...................................................................................................................................... 39

5.6.1 Synopsis ........................................................................................................................................... 39

5.6.2 Data model ....................................................................................................................................... 39

5.6.3 Business rules .................................................................................................................................. 39

5.6.4 Workflow ........................................................................................................................................... 39

5.7 Image gallery ..................................................................................................................................... 39

5.7.1 Synopsis ........................................................................................................................................... 39

5.7.2 Data model ....................................................................................................................................... 39

5.7.3 Business rules .................................................................................................................................. 39

5.8 Web TV ............................................................................................................................................. 40

5.8.1 Synopsis ........................................................................................................................................... 40

5.8.2 Data model ....................................................................................................................................... 40




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

5.8.3 Business rules .................................................................................................................................. 40

5.8.4 Workflow ........................................................................................................................................... 40

5.9 Comments ......................................................................................................................................... 40

5.9.1 Synopsis ........................................................................................................................................... 40

5.9.2 Data Model ....................................................................................................................................... 40

5.9.3 Business rules .................................................................................................................................. 40

5.9.4 Workflow ........................................................................................................................................... 40

5.10 Documents ........................................................................................................................................ 40

5.10.1 Synopsis ........................................................................................................................................... 40

5.10.2 Data Model ....................................................................................................................................... 41

5.10.3 Business rules .................................................................................................................................. 41

5.10.4 Workflow ........................................................................................................................................... 41

5.11 Cases ................................................................................................................................................ 41

5.11.1 Synopsis ........................................................................................................................................... 41

5.11.2 Data Model ....................................................................................................................................... 41

5.11.3 Business rules .................................................................................................................................. 41

5.11.4 Workflow ........................................................................................................................................... 41

5.12 Notifications ....................................................................................................................................... 42

5.12.1 Synopsis ........................................................................................................................................... 42

5.12.2 Data Model ....................................................................................................................................... 42

5.12.3 Business rules .................................................................................................................................. 42

5.12.4 Workflow ........................................................................................................................................... 42

5.13 Surveys ............................................................................................................................................. 42

5.13.1 Synopsis ........................................................................................................................................... 42

5.13.2 Data Model ....................................................................................................................................... 43

5.13.3 Business rules .................................................................................................................................. 43

5.13.4 Workflow ........................................................................................................................................... 43

5.14 Factsheets ......................................................................................................................................... 43

5.14.1 Synopsis ........................................................................................................................................... 43

5.14.2 Data Model ....................................................................................................................................... 43

5.14.3 Business rules .................................................................................................................................. 43

5.14.4 Workflow ........................................................................................................................................... 43

6. “SEED” LAYER ................................................................................................................................ 44

6.1 Projects ............................................................................................................................................. 44

6.1.1 Data Model ....................................................................................................................................... 46

6.1.2 Business rules .................................................................................................................................. 46

6.1.3 Workflow ........................................................................................................................................... 47

6.2 Project Community ............................................................................................................................ 49

6.3 Assets ................................................................................................................................................ 49




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

6.3.1 Synopsis ........................................................................................................................................... 49

6.3.2 Data Model ....................................................................................................................................... 50

6.3.3 Business rules .................................................................................................................................. 50

6.3.4 Workflow ........................................................................................................................................... 50

6.4 Open Source Software ...................................................................................................................... 50

6.4.1 Synopsis ........................................................................................................................................... 50

6.4.2 Wireframe of the Open Source Software list .................................................................................... 51

6.4.3 Data Model ....................................................................................................................................... 52

6.4.4 Business rules .................................................................................................................................. 52

6.5 Issues ................................................................................................................................................ 52

6.5.1 Synopsis ........................................................................................................................................... 52

6.5.2 Data Model ....................................................................................................................................... 52

6.5.3 Business rules .................................................................................................................................. 52

6.5.4 Workflow ........................................................................................................................................... 53

6.6 Mailing lists ........................................................................................................................................ 53

6.6.1 Synopsis ........................................................................................................................................... 53

6.7 Source Code Management ............................................................................................................... 53

6.7.1 Synopsis ........................................................................................................................................... 53

6.7.2 Business rules .................................................................................................................................. 53

6.7.3 Workflow ........................................................................................................................................... 54

6.8 Version management and download................................................................................................. 54

6.8.1 Synopsis ........................................................................................................................................... 54

6.8.2 Business rules .................................................................................................................................. 54

6.8.3 Workflow ........................................................................................................................................... 54

6.9 Link between Projects ....................................................................................................................... 54

6.9.1 Synopsis ........................................................................................................................................... 54

6.9.2 Business rules .................................................................................................................................. 54

6.9.3 Workflow ........................................................................................................................................... 54

6.10 Virtual Forges .................................................................................................................................... 55

6.10.1 Synopsis ........................................................................................................................................... 55

6.10.2 Use Cases ........................................................................................................................................ 55

6.10.3 Business rules .................................................................................................................................. 56

6.10.4 Workflow ........................................................................................................................................... 56

6.11 Federated Forges .............................................................................................................................. 56

6.11.1 Synopsis ........................................................................................................................................... 56

6.11.2 Use Cases ........................................................................................................................................ 56

6.11.3 Data Model ....................................................................................................................................... 56

6.11.4 Business rules .................................................................................................................................. 56

6.11.5 Workflow ........................................................................................................................................... 57




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

6.12 Asset assistant .................................................................................................................................. 59

6.12.1 Synopsis ........................................................................................................................................... 59

6.12.2 Data model ....................................................................................................................................... 59

6.12.3 Business rules .................................................................................................................................. 59

6.12.4 Workflow ........................................................................................................................................... 59

7. “MEET” LAYER ................................................................................................................................ 60

7.1 General use cases ............................................................................................................................ 60

7.2 Newsletters ........................................................................................................................................ 60

7.2.1 Synopsis ........................................................................................................................................... 60

7.2.2 Data Model ....................................................................................................................................... 61

7.2.3 Business rules .................................................................................................................................. 61

7.2.4 Workflow ........................................................................................................................................... 61

7.3 Search facility .................................................................................................................................... 61

7.3.1 Synopsis ........................................................................................................................................... 61

7.3.2 Data Model ....................................................................................................................................... 61

7.3.3 Business rules .................................................................................................................................. 62

7.3.4 Workflow ........................................................................................................................................... 62

7.4 Events ............................................................................................................................................... 62

7.4.1 Synopsis ........................................................................................................................................... 62

7.4.2 Data Model ....................................................................................................................................... 62

7.4.3 Business rules .................................................................................................................................. 62

7.4.4 Workflow ........................................................................................................................................... 62

8. ANNEX 1: DATA MODELS .............................................................................................................. 63

8.1 User Profile ........................................................................................................................................ 63

8.2 Community ........................................................................................................................................ 64

8.3 Open Source Software item .............................................................................................................. 64

8.4 Federated forge ................................................................................................................................. 66

8.5 Asset item .......................................................................................................................................... 67

8.6 News item .......................................................................................................................................... 68

8.7 Blogs.................................................................................................................................................. 68

8.8 Wikis .................................................................................................................................................. 69

8.9 Image ................................................................................................................................................ 69

8.10 Forums .............................................................................................................................................. 69

8.11 Comments ......................................................................................................................................... 70

8.12 Component ........................................................................................................................................ 70

8.13 Release ............................................................................................................................................. 71

8.14 Issue .................................................................................................................................................. 71

8.15 Survey ............................................................................................................................................... 72




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

8.16 Case .................................................................................................................................................. 73

8.17 Document .......................................................................................................................................... 75

8.18 Event ................................................................................................................................................. 76

8.19 Newsletter ......................................................................................................................................... 77

8.20 Factsheet ........................................................................................................................................... 78

8.21 Video ................................................................................................................................................. 78

9. ANNEXE 2: TAXONOMIES .............................................................................................................. 79

9.1 Imported taxonomies ......................................................................................................................... 79

END OF THE DOCUMENT .............................................................................................................................. 88




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

1. INTRODUCTION

1.1 Aims

The European Commission has set up several collaborative platforms in the area of eGovernment and ICT in general. The ISA Integrated Collaborative platform is the project aimed to unify the developments of these three web applications: semic.eu, osor.eu and epractice.eu. The services provided by each of these platforms are around the Content Management System (CMS) infrastructure and uses the Web 2.0 communication technology.

The purpose of this document is to define the key functionalities and elements related to the development of the ISA Integrated Collaborative Platform.

This document gathers the key elements used to implement the ISA-ICP project. This document is constituted by the description of:

the functionalities

the users and their roles

the graphical user interface

the rules and workflow for the data management

the data model is attached in annex

Note:

The requirements emitted from the Business Manager have their reference written in bold and underline.

1.2 Definitions, acronyms and abbreviations

Term / acronym Definition

Community A community is a group of user who has access to collaborative tools. We distinguished three different kinds of community:

Community of interest (called simply “community”)

Community for a semantic asset

Community for a software project

GUI Graphical User Interface

ISA-ICP ISA Integrated Collaborative Platform

Moderation Moderation is the process of validating or refusing contents. It is mainly used for news items to make sure that all content published on the site is of interest for the other users or members.

OSS Open Source Software

Post moderation Post moderation is the process of updating or deleting contents after they were published. It is used for communication channels like forums, wikis (and eventually blogs).

Asset An asset is a specific type of project. It is used to describe resources that support the exchange of data in distributed information systems.

Forge A forge is a collaboration platform allowing collaborative software development over the internet. It hosts multiple independent projects.




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

1.3 Reserves

This document is adapted to Product Versions 1 to 3 of the project. The scope of this document includes then:

User management restricted to the product version 1

Communities management

Content management o News o Forum o Blogs o Wikis

Forges o Project management o Virtual forges o Federated forges

Asset management o Project management o Clearing process o Asset assistant

Cases

Documents

Events

Search

Newsletters

Factsheets

Notifications

For each product version, the document will implement a part of the final specifications in order to have a final version of the specification at the end of the product version 4.




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

2. THE USERS

2.1 Type of users

Two kinds of users are represented on the ISA-ICP application:

The anonymous user is considered as a guest, or unregistered user. The capabilities of this user on the site are restricted to viewing public contents and create an account to become a registered user.

The registered user is the user that has created an account using the registration process. A registered user has extended capabilities on the application. Later in the documents, we will use the generic shortcut “user” for referencing the registered users.

2.2 The roles

Roles are created in order to manage permissions for users. According to the role that is given to a user, he will have access to more or less functionalities on the site.

The anonymous role is the default role when the user is not logged in on the application. All other listed roles will then be for users already registered in ISA-ICP.

Role Scope1 Actions

Anonymous General Access to public content

Create an account

Request a new password for an existing account

User General Access to public content

Access to profile

Propose content (news, blogs, …)

Request a new community

Modify its own content (news, blogs)

Edit own information (profile)

Delete account

Join an open community

Request membership to a moderated community

Create / Edit / Delete comment on content (news, blogs)

Create / Comment issues (Project scope)

Create / Comment forum (Project scope)

Clearing Process Manager

General Inherit permissions from the User role

Validate some workflow status of the asset lifecycle

1 The scope of a role is linked to the notion of communities. For example, a user may be a regular user on all

the platform exception to a community in which he is the facilitator and as a consequence has extended privileges.




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

Role Scope1 Actions

Moderator General Inherit permissions from User role

Accept / Modify / Reject content (news, blogs, …)

Accept / Modify / Reject community request

Accept / Modify / Reject project request

Receive notification for comment

Receive notification of new blog entry

Block / Unblock user

Define user‟s role

Define the editor‟s choice

Administrator General Inherit permissions from Moderator role

This user can do everything on the application

Member Community / Project

Propose highlight of content (news, blogs, communities…)

Create / Edit / Delete own content (forum topics)

Create / Edit content (wiki page)

Create / Edit / Delete comment on content (forum topics)

Create / Edit / Delete own content (blogs)

Leave community

Facilitator Community / Project

Inherit permissions from Member role

Create / Reject highlight (Community scope)

Create / Reject link (Project scope)

Edit / Delete content (forum topics, wiki page, blog associated to the community)

Approve / Reject membership requests

Remove member

Invite new member

Define member‟s role

Developer Project Inherit permissions from Member role

Modify source code of the application.

Project Owner Project Inherit permissions from Facilitator role

Inherit permissions from Developer role

Virtual Forge admin

Project Edit the theme of the virtual forge

Is warned of new project created within his virtual forge

2.3 The user attributes

The attributes are the fields that compose the profile of a user; they can be filled by any user asking for registration. The user has the capability to authorise other regular user to accede to its profile information or




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

not. These choices are: Email Visibility. The moderators and the administrators are not affected by these options.

Note:

The fields are described in annex 8.1.

2.4 User activity tracking

Ech time a user is performing a certain kind of activity on the platform, the system logs. This activity tracking is a way to keep the user informed of what happens on the platform and as a consequence to keep the other user up to date. This activity is logged on the platform through different information:

- Timestamp: the time at which the activity has performed - Actor: the user who performed the activity. - Content: the content node on which the activity was performed. - Activity Type: the type of activity that was performed on the content node.

The following table presents the actions that trigger an activity log.

Content type Activity type Derived message

User profile Create account %user% has joined ISA-ICP

Update %user% has updated is profile

Community Creation %user% has created the community %title%

Join %user% has joined the community %title%

Leave %user% has left the community %title%

Software Creation %user% has registered the software %title%

Join %user% has joined the software community %title%

Leave %user% has left the software community%title%

Semantic Asset Creation %user% has registered the semantic asset %title%

Join %user% has joined the semantic asset %title%

Leave %user% has left the semantic asset community %title%

Call for comment %user% has called for comment concerning the asset %title%

End of call for comment %user% has stopped the call for comment concerning the asset %title%




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

Content type Activity type Derived message

Semantic Asset Release Request maturity %user% has requested maturity for the semantic asset release %title%

Approve maturity %user% has approved maturity for the semantic asset release %title%

Reject maturity %user% has rejected maturity for the semantic asset release %title%

Group Content (news, wiki, documents, issue, release)

Create %user% has created the %type% %title%

Update %user% has updated the %type% %title%

Request publication %user% has requested the publication of the %type% %title%

All content Comment %user% has commented the %type% %title%

Highlight %user% has highlighted the %type% %title% in the %group_type% %group_title%

Platform Content (news, blogs, case, video, community, semantic asset, software)

Published2 %user% has published the

%type% %title%

2 It doesn‟t have any sense to manage the status « Propose » and « Rejected » has the regular user will not

have the capabilities to see them and the current user have those elements in his dashboard




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

3. USER MANAGEMENT

3.1 Synopsis

The user management contains all functionalities from the user registration to the user deletion. Several main topics are distinguished:

Create account is the action created by an anonymous user to become a registered user on the platform ;

Edit profile is the action of the user to fill in personal information ;

Manage users is the action of the Moderator to suspend the account of a registered user ;

Delete account is the action of the ISA-ICP Administrator to suppress a registered user ;

Request new password is the action that allows the user to recover its password ;

3.1.1 Create account

The user registration process is initialised by an anonymous user. The user registers directly on the application using a web form, all information concerning a user is stored within the platform. The system sends a notification to the user in order for him to confirm his email address. As soon as the email address is confirmed, the user can navigate through all the public part of the application.

Each user should have a unique username and a unique email address across the application. The username is used for authenticating the user but his not aimed to appear in the other part of the application where the user appear with his real first name and last name.

3.1.2 Authenticate

An anonymous user who holds an account can authenticate him by entering his credential on the authentication form. If the credentials are incorrect, the user is not recognized as a “user” by the application. In case of three bad credentials, if the username exists, the user account associated to it is automatically blocked.

Anonymous

Moderator

Create account

Delete account

Manage users

ISA

Edit profile Define role

«extends»

Block / Unblock

user

«extends»Request new

password

User

«extends»

Reauthoring

«uses»

«extends»

«extends»

Authenticate

«uses»




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

The authentication system can save the settings on the application side during 90 minutes.

3.1.3 Edit profile

Any user on the application may edit his personal data. These data corresponds to the profile of the user.

3.1.4 Manage user

The moderators have the ability to interact with the user to block or unblock a user who doesn‟t respect a code of conduct on the platform (like spamming).

The moderators can define the role on the general scope of a user. A user can then become a moderator. The administrator role cannot be defined by a moderator, only the administrators can create a new administrator.

The moderators can also create user accounts without any validation of the email address of the user and define on the fly the future role of the user. In that particular case, the user will not be blocked even if the email address has not been validated.

The moderators have access to all content across the platform and it includes the personal data of the user. If the user hides their personal data, the moderators can access to them.

3.1.5 Delete account

Every user has the ability to delete his account without any interference by the ISA-ICP team. The account deletion cannot be undone due to the European legislation.

Each contents created by the user, each contributions will be automatically re-authored to “Former user”.

An account can be deleted by an administrator or a moderator.

3.1.6 Request new password

If a user lost his password, the system may generate a new password and sent it to his email. The old password is deleted from the system. The user may use the new password to connect once in order to change his credentials.

3.2 Management rules

R_ISA-ICP_FUN_Meet_Profile_001 : The application shall support the management of user profiles.




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

3.3 Workflow

3.3.1 Create account

After the creation of an account, the user receives an email address he entered in the registration form.

Dear <Firstname>, Thank you for registering ISA-ICP platform. You may now log in to http://<website address>/user using the following username and password: Username: <username> Password: <password> You must confirm you registration by clicking on this link or copying and pasting it in your browser: http://<URL> This is a one-time login, so it can be used only once. After logging in, you will be redirected to http://<website address>/user/ so you can change your password. ISA-ICP Team

3.3.2 Manage user

At any time, the moderator has the possibility to reactivate an account. A notification will be sent to the user

Dear <Firstname>, Your account has been reactivated. You are now able to connect again to the ISA-ICP platform. ISA-ICP Team

In case of blocking of an account, the associated user will receive the following notification:

Dear <Firstname>, Your account has been blocked. In case of error, you can contact us thanks to the address <Email>. ISA-ICP Team




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

4. SITE MAP AND PAGE STRUCTURE

4.1 Site map

The following schema describes the organization of the main components for the ISA-ICP application.

From homepage, access to SEED, INFORM and MEET layers is possible via the menu.

The SEED layer proposed in this document will then allow access to:

Semantic Assets.

Software.

The INFORM layer proposed in this document will then allow access to:

News items ;

Blogs ;

Communities ;

Wikis ;

Forum topics ;

eLibrary (documents, cases, factsheets, video).

The MEET layer proposed in this document will then allow access to:

Events ;

Newsletters ;

Search facilities.




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

4.2 Presentation of ISA-ICP home page

4.2.1 The wireframe




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

4.2.2 The header

The header is aimed to directly distinguish in the application that the user is logged on, and offer some basic information and quick launch.

This information comprises:

A logo of the application which is a link to the home page ;

Search to a new page for advanced search ;

A login information part contains either the form to quickly connect to the application or the connection information with:

o The name of the connected user ; o A log out link to disconnect from the application ; o Access to profile information “My Account”.

4.2.3 The menu

It is composed by the 3 layers which are just aimed to help the user understanding the concept of the application: SEED, INFORM and MEET.

SEED represents the ability for the user to have a dedicated space to help him leaving grow his ideas and have concretisation through a project or an asset.

INFORM gives to the user the tools necessary to help in communicating with other user thanks to communities that are aimed to emulate people around topics.

MEET offers then the mean to meet people on real life thanks to a directory, workshop organisation, online or real meeting…

Under each of one of these layers, some elements are useful to access a primary menu in order to get contextual information.

4.2.4 The submenu

The submenu is the headband of the site and offers a unique chance to push elements in each page that needs a high interest in the page.




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

On the home page, this element is the editor‟s choice while on the news page, we push the “Add a news” button to help the user to contribute to the application.

4.2.5 The content

The content of the home page is cut into blocks. Blocks are piece of information aimed to quickly access to the latest information the user is interested in. Each block is cut into a user and information characterized at least by a title and a short description of the element.

By providing several simple blocks, the user can accede easily to the information and may also get more information by clicking on the element to access to it.

The “view all” button redirects the user to a dedicated web page showing more elements than the one presented on these blocks.

4.2.6 The footer

The footer of the application contains several links to help the user getting other resources. It helps the user having more information on the application.

From this footer, the available links are:

- Help - FAQ - Contact - Legal notices - About us - Sitemap - Partners - RSS

From the footer, clicking on the links opens in popup windows to avoid redirecting the user to another page.

4.2.6.1 About us

The “About us” section is a static page that explains the target of the application.

4.2.6.2 Legal notices

“Legal notices” is a static page that explains the code of conducts, and legal aspects associated to the registration on the ISA-ICP platform.

In order to register themselves, a semantic asset or a software, the users need to accept the legal notices.

4.2.6.3 Partners

“Partners” is a static page that references all the partners of the site.




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

4.2.6.4 Glossary

The glossary is a static page that references all the keywords useful to know when you navigate within the ISA-ICP platform.

This glossary allows the user to navigate through the first letter of the words on the top of the page. Clicking on a letter redirects you to the anchor set in the text.

4.2.6.5 Help

The help link on the bottom of the page redirects the user to the global help of the application. It means that on the contrary to the contextual help on the top of the page, this button links the user to the index of the online help.

4.2.6.6 FAQ

The FAQ link on the bottom of the page redirects the user to the global FAQ of the application. Two different types of FAQ are used on the platform. The first one is generic to the platform and deals with several standard subjects (connection, kudos, target of the application…). The second one is embedded within the legal corner and is dedicated only to legal question, about licenses etc.

4.2.6.7 Contact

The contact feature redirects the user to a form in which he has the capability to enter a question which will be transmitted to the support of the platform.

The fields of this form are:

- Firstname (mandatory) - Lastname (mandatory) - Organisation / Company (not mandatory): The organisation of the sender - Email Address (mandatory): The email address of the sender. - Message (mandatory): The message the user wants to send to the support - Captcha (mandatory): A captcha is an image that represents a text in order to avoid or limit email

spam from robots.

If the user is logged in, the elements firstname, lastname, email address are automatically filled by the system according to the user profile. If so, then the user cannot modified them (the boxes are deactivated).

The message is then sent to an email provided by the European Commission. The message is treated by the support.




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

5. “INFORM” LAYER

The “INFORM” layer is dedicated to share information around the themes of the application.

Information channels that will be described in this document are:

News items to publish articles that can be viewable inside a community or in the public area ;

Blogs to create individual commentaries, events descriptions or any other contents to a community of users ;

Wikis to create web pages, the content of the page can contain formatted texts and links to images or documents shared on external applications ;

Forum topics to share information with the group members, as for the wiki pages, the forum post can only contain formatted texts and links to external resources ;

Highlights to push an element coming from the public part of the application but outside of the community in the front end of it ;

E-Library contents as documents, cases and factsheets to share documentation or experiences with users of the platform ;

Surveys to question users about specific subjects.

5.1 General

5.1.1 Synopsis

For any new content (belonging to a community or not), user or member can do following actions:

Propose a content ;

Modify its own content ;

Propose deletion of content ;

Add/modify/delete a comment ;

Propose a highlight.




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

Moderator

User

Publish Wiki Page

Create Community Publish Blog

ISA – Product Version 1

Propose News Publish Forum Topic

Browse News

Browse Wikis

Browse Communities

Browse Forums

Highlight Content

in Community

Leave Comment

Anonymous

«uses»

«uses»

Facilitator

Moderate Content

Member

«uses»

Browse Blogs

«uses»




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

5.1.2 The wireframe of the community home page




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

5.1.3 Workflow

All content created by simple user within the application is aimed to be moderated. We distinguished two kinds of moderations, the first one is the direct moderation (called in the following “moderation”) and the second is the post-moderation.

Roughly speaking, the moderation consists in validating the content before its publication on the contrary to the post-moderation which consists in being notified for each new content and remove it afterwards.

The both following schema depict the differences between both workflows. In each case, it is possible for the moderator to be helped by a third party system for tagging the content (like Open Calais

3, a text mining tool).

5.1.3.1 Moderated content

3 http://www.opencalais.com/

http://www.opencalais.com/




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

5.1.3.2 Post moderated content

5.1.3.3 Propose a content

Content can only be proposed by a registered user. The moderation is only included in the creation process. In case of modification, the post-moderation workflow will be used.

It requires moderator‟s validation. The publication will only take place once the moderator has validated its content.

The type of content which implied the moderation:

News

Community




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

In this case, each moderator receives the following notification:

Dear <Firstname>, User <User firstname and surname> has proposed the following content. <values of the creation form field set> The publication of this content requires your validation. Please click on the link below to reach the validation or denial form. <HYPERLINK> ISA-ICP Team

Another notification is sent to the author, informing him that his content has been submitted:

Dear <Firstname>, Your content (title <Title>) has been submitted. It requires the validation from site moderator, before it will be visible on the ISA-ICP site. You will receive another message when the content is accepted and published. In case it has been refused, you will be notified about the reasons, and eventually the possibility to submit your content again, after some updates. Thank you for sharing information on the ISA-ICP site. ISA-ICP Team

If the content is refused, the notification contains:

Dear <Firstname>, Your content has been refused for the following reason: <reason> ISA-ICP Team

Finally, if the content is published, the original user receives:

Dear <Firstname>, Your content (title <Title>) has been accepted and published. It is now visible for any users on the ISA-ICP site. Thank you for sharing information on the ISA-ICP site. ISA-ICP Team

5.1.3.4 Modify own content

Any user can modify the content he has created. The post-moderation workflow is then applied.

5.1.3.5 Propose deletion of a content

Any user can propose the deletion of a content he has created.

The process is similar to content proposal. Moderator needs to validate the deletion of the content. Deletion is completed only after moderator‟s approval.




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

5.1.3.6 Add/modify/delete a comment

Any user can add, modify or delete a comment on any content without any approval from site moderator.

Moderator just gets notified of any comment made on content.

5.1.3.7 Highlight a content

A highlighted content is a content existing in the public area of the ISA-ICP platform that has been linked to a community.

Any member of a community can propose to highlight content so that it appears in the community area. The content will then be easily viewable by any other member of the community or by any user if the community is public.

Any member can propose a highlight. The post-moderation workflow is applied for this process.

In the following picture, the concept of the highlight is represented by the content which is whatever created within the melting pot of content or within a community “β” but is represented in the community “λ” thanks to symbolic links. The conditions to modify an item are the same if there is a link or not. The link doesn‟t give particular rights to the member of a community.

All contents on the platform can be highlighted (it means news, community, project, video…).

COMMUNITY βCOMMUNITY λ

NEWSNEWS

NEWSNEWS

BLOGSBLOGS

BLOGSBLOGS

BLOGSBLOGS

WIKIWIKI

FORUMFORUM

BLOGSBLOGS

WIKIWIKI

WIKIFORUM

FORUM

FORUM

NEWS




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

5.1.4 Business rules

R_ISA-ICP_FUN_Content_Creation_001: Any user shall be able to contribute new content

R_ISA-ICP_FUN_Content_Moderation_001: In case of new community content, it shall be published only after approval by a facilitator

R_ISA-ICP_FUN_Content_Moderation_002: In case of new public content, it shall be published only after approval by a moderator

R_ISA-ICP_FUN_Content_Moderation_003: In case of modification or comment to community content, the facilitator is notified

R_ISA-ICP_FUN_Content_Moderation_004: In case of modification or comment to public content, the moderator is notified

R_ISA-ICP_FUN_Content_Moderation_005: In case of community content, the facilitator can edit, modify, delete any content

R_ISA-ICP_FUN_Content_Moderation_006: In case of public content, the moderator can edit, modify, delete any content

R_ISA-ICP_FUN_Content_Moderation_007: The moderators shall be notified of new content.

R_ISA-ICP_FUN_Content_Moderation_008: Any new content shall be moderated.

5.2 COMMUNITIES

5.2.1 Synopsis

A community is a shared communication channel dedicated to some members. Each community can have its own information channel (blogs, wikis and forums).

A community is managed by an administrator (a user that has facilitator role in the context of a community). His role is to manage the community member list and all included content. Regarding content management, the facilitator can make modifications or suppress content within the community, and can also report any abusive behaviour to the moderators.

The members are only able to publish content. However, they can delete any of their own contributions without impacting on other users' modifications.

Any user can leave a community as long as at least one community facilitator remains.

The visibility of a community depends on the membership system. For an opened community, all the content is PUBLIC, for other kind of communities, the content is PRIVATE.




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

5.2.2 Data model

See annex 8.2.

Moderator

Propose community

Modify community

Moderate

Join community

Leave community

Member

Manager community

usersDefine role

«extends»

Approve membership«extends»

ISA

Create / Edit own

forum thread

Create / Edit wiki

page

Invite Members

«extends»

Facilitator

Comment forum

thread

Moderate

Notify

«uses»

«uses»

«uses»

Propose deletion

of content«uses»

User

«uses»

Notify

«uses»




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

5.2.2.1 Manage the communication channels

In the edition form of a community (creation or update), the user has the capability to choose to activate or deactivate the creation of several content:

- News - Forum - Wiki - Documents

It consists in making possible to create or not any of this kind of content. If an element is not checked (by default all the elements are checked), then the associated link on the action bar (on the right menu) is not visible.

At any time, an administrator, owner or facilitator can activate or deactivate the capability to create an element by checking or not the type of content.

As any member of the community still has the capability to highlight an element which is in the type that has not been activated, the views (left menu) is still accessible for any user, but it will not be possible to create any new elements. As an example, if the user deactivates the news, it is impossible to create a news embed in the community but, the members can highlight elements from other communities.


R_ISA-ICP_FUN_Inform_Community_001.Tools: Each community shall be able to use one or more of the collaborative tools (wiki, blog, forum).

R_ISA-ICP_FUN_Inform_Community_002: The application shall be able to manage open (public) and closed (private) communities.

R_ISA-ICP_FUN_Inform_Community_003: Open communities shall have all information available for all users, subscription shall be automatically accepted for all registered users.

R_ISA-ICP_FUN_Inform_Community_004: Closed communities shall have all information (except for a generic description of the community) available only for the community members.

R_ISA-ICP_FUN_Inform_Community_005: A registered user shall be able to request the registration of a new community.

R_ISA-ICP_FUN_Inform_Community_006: Any registered user shall be able to request to be the member of a community.

R_ISA-ICP_FUN_Inform_Community_007: A community facilitator shall be able to invite people to the community, approve or reject registration request for closed community.

R_ISA-ICP_FUN_Inform_Community_008: Any member of a community shall be able to propose to highlight any public content.

R_ISA-ICP_FUN_Inform_Community_009: Any member of a community shall be able to propose new content.

R_ISA-ICP_FUN_Inform_Community_010: Any member of the community shall be able to get notified on any new content in a community.

R_ISA-ICP_FUN_Inform_Community_011: Any member of a community shall be able to propose to link a community to another one.




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

5.2.4 Workflow

5.2.4.1 Propose community

Any registered user can propose (or start) a community.

The process answers to moderation workflow (See §5.1.3.1).

The moderators receive the following first notification:

Dear moderator, A new user wants to start a new community. The user enters the following information for the community: Title: <Title> Description: <Description> Domains: <List of domains> Languages: <List of languages> Community Privacy: <Public or private> The start of the community requires your validation. Please click on the link below to reach the validation or denial form. <HYPERLINK> ISA-ICP Team

If the moderator refuses, the user receives this notification:

Dear <Firstname>, You community has been refused by an administrator for the following reason: <Refusal Comment> ISA-ICP Team

If the moderator accepts, the user receives this notification:

Dear <Firstname>, Your proposal for a new community has been approved. Community <Title> has been started. From now, you have the facilitator role for the community <Title>. You can now invite registered users to join the community. As the facilitator of this community, you can delegate this role to other members. From now, you can add contents to the community (highlight public contents, complete wiki pages, create forum topics...). ISA-ICP Team

5.2.4.2 Join a community

Any registered user has the possibility to join an open community, for the closed community, the user can request membership to the facilitator.

In case of closed community, for a membership request, the facilitators receives the following email: Dear <Firstname>,




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

A user has requested membership on the community <Name>. Please click on following link to approve/deny membership: <HYPERLINK> ISA-ICP Team

After the approval of the request, the user become a member and receives the following notification:

Dear <Firstname>, You are now member of the community <Title>. Community <Title> has been added to your personal settings under “My communities” list. As member of this community, you have now access and participate to all contents inside this community. ISA-ICP Team

5.2.4.3 Modify community

This action is only possible for a community facilitator.

5.2.4.4 Manage community users

This action is only possible for a community facilitator.

5.2.4.5 Invite a new user

From the “Members list” page, it is possible to invite an external user to join the community. Any member of the community has the capability to fill a form indicating the recipient and a specific message to invite him to the community.

The form that needs to be filled by the user contains the following fields:

- Recipient’s email address (mandatory): the email address of the people who is invited. - Message (mandatory, at least 15 characters): an message that will be associated to the email sent

by the platform in order to explain the recipient why it is recommended for him to join - Captcha (mandatory): A captcha is an image that represents a text in order to avoid or limit email

spam from robots.

The recipient and the authenticated user (in copy) will then receive the following message.




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

<Firstname> <Lastname> has invited you to join the community <Name> on ISA-ICP. <Firstname> enclosed the following message for your intention: <Message> About the community <Title>: <Abstract>. To join this community click on the following link <Link To Community> As a member, you will be able to participate actively in the activities of this community. You will be able to create and highlight content, such as blogs, news items, events, useful software or semantic asset and participate in the discussion forums and wikis of the community. You will be automatically notified of any activities and new content. For a complete list of advantages of membership, click here <Link To About Us>. You want to report a spam? You can send us an email to <site email address>. ISA-ICP Team

If the recipient‟s email address doesn‟t exist, no warning is sent to the sender.

5.2.4.6 Leave a community

Members of a community can choose to leave a community, by filling the appropriate form. Form just asks for confirmation and an optional field inviting the member to give a reason.

This action doesn‟t require approval from community facilitator.

The user receives a notification informing him that his request has been completed.

Dear <Firstname> Your request to leave community <Title> has been completed. From now, you are no more member of this community. ISA-ICP Team

5.3 News

5.3.1 Synopsis

A news item is a content published on the site. It can be published either in the melting pot of information (from the root of the website) or directly within a community. When the news is created within a community, its visibility depends on the visibility of the community.

This kind of content can both be visible in the public area of the ISA-ICP platform or highlighted inside a community.




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

5.3.2 Wireframe of embed news




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

5.3.3 Data model

See annex 8.6.


R_ISA-ICP_FUN_Content_Type_007.News: The application shall be able to manage news items

5.3.5 Workflow

A news item is considered as moderated.

5.4 Blogs

5.4.1 Synopsis

A blog is a webpage owned by a user.

The aim of this kind of content is to publish news inside this personal area, viewable by any other users.

Users have the possibility to add comments and share more information. Contents are generally sorted chronologically.

5.4.2 Data model

See annex 8.7.


R_ISA-ICP_FUN_Content_Type_001.Blogs: The application shall be able to manage blogs items

5.4.4 Workflow

A blog is considered as post moderated.

5.5 Wikis

5.5.1 Synopsis

A wiki is a webpage owned by a user, whose content can be updated by any other user (after it has been approved by wiki owner).

A wiki is created by a user who wants to share information with any other users of the platform. The content shall evolve and any user can propose updated or additional information.

Any user may edit the wiki but only the facilitator can go back to a previous version.

Note:

The wiki cannot be commented.




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

5.5.2 Data model

See annex 8.8.


R_ISA-ICP_FUN_Content_Type_010.Wikis: The application shall be able to manage wikis items

5.5.4 Workflow

A wiki is considered as post moderated.

5.6 Forum topics

5.6.1 Synopsis

A forum is a communication channel based on discussions around a theme.

Any member of a community can propose a forum, the creation of it requires the validation of the facilitator.

5.6.2 Data model

See annex 8.10.


R_ISA-ICP_FUN_Content_Type_006.Forums: The application shall be able to manage forum items

5.6.4 Workflow

A forum topic is considered as post moderated.

5.7 Image gallery

5.7.1 Synopsis

An image gallery is composed of images uploaded on the application. The size of an image is restricted to 2Mb.

The image gallery is accessed by an AJAX system.

5.7.2 Data model

See annex 8.9.


No dedicated business rules




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

5.8 Web TV

5.8.1 Synopsis

The web TV embeds all the contents created by the editorial team (the moderators). These videos are accessible from the e-Library menu.

5.8.2 Data model

See annex 8.21.


No dedicated business rules

5.8.4 Workflow

No workflow, only the moderator can create a video.

5.9 Comments

5.9.1 Synopsis

A comment is a possibility for any user on the ISA-ICP platform to react after viewing any kind of content (news, blog, and forum). It is a feedback for the owner of the content.

5.9.2 Data Model

See annex 8.11.


No business rule.

5.9.4 Workflow

A comment is considered as post moderated.

5.10 Documents

5.10.1 Synopsis

A document is part of the e-library.

Two kinds of documents are managed by the system: generic documents created directly from the common area and community specific documents. The generic documents are moderated whereas the community‟s documents are post-moderated.

Any user on the ISA-ICP platform can propose a document to share more information on the site.




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

5.10.2 Data Model

See annex 8.17.


A document can be created in the frame of a community, a project or directly in the common area.

A document can be commented, and highlighted to communities or projects (softwares and assets).

Document‟s accessibility depends on where it is published (if it is created in a private community, only members will have access to it).

5.10.4 Workflow

A document is considered as moderated if it is a generic document (not belonging to a community or a project). Any user can propose a document but it needs to be approved by the moderator.

A document is considered as post-moderated in case it belongs to a community. Any user can propose a document item. The document is published and available for other users. A facilitator (depending on where the document is published – in a community, project or in the common ISA-ICP area) can unpublished it.

5.11 Cases

5.11.1 Synopsis

A case is part of the e-library.

.

A case is a structure set of text describing a best practice in the area of semantic asset, policy, open source, etc.

In order to share practical experience, any user can create a case. This will provide a platform for showcasing success stories highlighting results of initiatives undertaken by a project, a community, a company.

5.11.2 Data Model

See annex 8.16.


A case is not created in the frame of a community or a project. It is necessarily created in the common area, and is visible by any user of the ISA-ICP platform.

A case can be highlighted for a community, software or asset.

A case can be commented by any user of the ISA-ICP platform.

5.11.4 Workflow

A case is moderated.

Any user can propose a case. The moderator needs to approve it to be available on the ISA-ICP platform.




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

5.12 Notifications

5.12.1 Synopsis

Two different types of notifications will be managed:

- Automatic notifications on contents related to a user (e.g. when a comment is left on such a content); it means that a user can subscribe to each update made on a content. These notifications are sent automatically after the modification of the contents.

- Automatic notifications on a content type. The user chooses the type of content he is interested in and the frequency (every hour, day or week). He will then receive a digest with the element that has changed since the last email. The email contains only elements that are part of the group on which the user is member of. The highlights are not taken into account.

Notifications can be managed directly by the user, they belong to user profile.

5.12.2 Data Model

No data model.


R_ISA-ICP_FUN_UserFocalization_Notification_000: Community member shall be able to ask for notification on any new content in the community.

5.12.4 Workflow

No workflow.

5.13 Surveys

5.13.1 Synopsis

In order to get feedback from the users, the system automatically sends a survey 10 days (by default, this value is modifiable by the administrator) after a user downloaded a release of a project (asset or software). The survey is unique over the platform for all the projects.

The survey is modifiable by the moderators, depending on the type of modification; the existing results may be impacted.

Ten days after their download, the users receive the following email.

Dear <Firstname> Thanks for downloading the project <Project Title>. In order to improve the quality of our product we would like to have your feedback on our projects. The link below will redirect you to an online survey. <URL> Thank you, ISA-ICP Team




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

It is possible to consult the result of the survey through two ways. The first one is site wide in the “Service / Metrics” menu. The second is dedicated to the project in the “Global metrics” part.

5.13.2 Data Model

See annex 8.15.


R_ISA-ICP_FUN_Seed_Tools_009: The application shall support tools for voting and decision making

R_ISA-ICP_FUN_Seed_Tools_010: The application shall support tools for surveying

R_ISA-ICP_FUN_Seed_Tools_021: The application shall support the monitoring of downloader and the "afterlife" of a downloaded asset / project (e.g. with surveys).

5.13.4 Workflow

A survey is considered as post moderated.

5.14 Factsheets

5.14.1 Synopsis

A factsheet is part of the e-library.

A (country) factsheet is a possibility to publish a document specific to a country, and a factsheet topic (to categorize its content using taxonomies, tags...).

5.14.2 Data Model

See annex 8.20.


A factsheet is necessarily created in the common area, it is describing an overall picture of the situation and progress for a country.

Upload facilities to moderators, and download possibilities to users are available.

Only the moderator can create factsheets.

A factsheet can be commented, highlighted in communities, projects or assets, and rated.

5.14.4 Workflow

No workflow.




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

6. “SEED” LAYER

The “SEED” layer is dedicated to offer a place to grow for the projects hosted by the application. We distinguished two main types of projects within this layer. The first type of project is the interoperability assets (called “assets” later in the document) and the second type of project are the open source software.

The following paragraph deals with projects which are concepts. Indeed the projects don‟t exist as content types but the behaviour is the same for the OSS and the assets. The functioning of these both data types are then explained in the paragraph 6.1. In the paragraph 6.3 and 6.4 we explained the dedicated behaviour of the assets (6.3) and the OSS (6.4).

6.1 Projects

A project is a shared communication channel and a set of tools dedicated to some members. Each project can have its own information channel (blogs, wikis, forums, documents). Each project has also its own development “framework” (source code repository, binaries repository, issue management, release management).

The community is managed by administrators (a user who has either the “project owner” or “facilitator” role in the context of a project). His role is to manage the community member list and all included content. Regarding content management, the facilitator can make modifications or suppress the content concerning the information channel. The management of the development “framework” is done by the project owner.

The projects are moderated communities; it means that any user can request membership. The validation of the request may be done either by the project owner or the facilitators.

The visibility of a project is PUBLIC.

The project page is only available in English.

The following use cases show the capabilities of those projects.




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

ISA – Browse Project (PV2)

Anonymous

Browse Projects

Browse Wikis

Browse Forums

Leave Comment

«uses»

Browse Blogs

«uses»

«uses»«uses»

«uses»

«uses»

Browse Releases

Browse Source Code

Browse OSS

Browse Assets

«extends»

«extends»

Browse Issues

«uses»

«uses»

«uses»

Browse File

Rate ProjectPublish Forum Topic

«uses»

User




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

6.1.1 Data Model

See annex 8.3 for the Open Source Software Data Model.


R_ISA-ICP_FUN_Seed_Tools_001: The platform shall provide software versioning tool for project developers

R_ISA-ICP_FUN_Seed_Tools_005: The platform shall provide collaboration tools for asset and software repositories. It includes wikis, blogs and forum.

R_ISA-ICP_FUN_Seed_Tools_013: The application shall support hosting of asset / oss source code on third party repositories.

R_ISA-ICP_FUN_Seed_Tools_018: The application shall provide information (description, tags, activity, and metrics) related to OSS projects and assets.

R_ISA-ICP_FUN_Seed_Tools_019: The application shall provide download facility for asset and projects.

R_ISA-ICP_FUN_Seed_Tools_020: The application shall monitor the number of downloads of any asset and projects.

ISA – Participate to Projects (PV2)

Project Owner

Developer

Moderate Content

«extends»

«extends»

«extends»

«uses»

Assign IssuePublish Content Edit Source Code

Close Issue

Manage Project

Edit Project

Manage Release

Publish Issue

User

Publish Forum Topic

Manage Users

«extends»

«extends»

«extends»

«extends»

Advisor

Clearing Process Manager

Modify / Validate

Status

System

Link To Other

Project

«extends»

Answer To Poll

«extends»

Generate The Change

History Artefact

Facilitator

Highlight Content

«extends»

Member




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

6.1.3 Workflow

6.1.3.1 Propose project

A project is considered as moderated (See §5.1.3.1).

Any registered user can propose a project.

The moderators receive the following first notification:

Dear moderator, A new user wants to start a new project. The user enters the following information for the project: Name: <Name> Description: <Description> Type: <Type> Domains: <List of domains> Languages: <List of languages> The start of the project requires your validation. Please click on the link below to reach the validation or denial form. <HYPERLINK> ISA-ICP Team

If the moderator refuses, the user receives this notification:

Dear <Firstname>, You project has been refused by an administrator for the following reason: <Refusal Comment> ISA-ICP Team

If the moderator accepts, the user receives this notification:

Dear <Firstname>, Your proposal for a new project has been approved. Project <Title> has been started. From now, you have the project owner role for the project <Name>. You can now invite registered users to join the project. As the project owner of this project, you can delegate the facilitator, contributor and developer roles to other members. From now, you can add contents to the project (public contents, complete wiki pages, create forum topics...)., the repository has been created for your project. You will find more information on the homepage of your project. ISA-ICP Team

6.1.3.2 Request membership to a project

Any registered user has the possibility to request membership to any project, the validation of the membership is done by the facilitators or the owner.




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

The facilitators and the owner receive the following email:

Dear <Firstname>, A user has requested membership on the project <Name>. Please click on following link to approve/deny membership: <HYPERLINK> ISA-ICP Team

After the approval of the request, the user become a member and receives the following notification:

Dear <Firstname>, You are now member of the project <Name>. Project <Name> has been added to your personal settings under “My Projects” list. As member of this project, you have now access to all contents inside this project. ISA-ICP Team

6.1.3.3 Modify project

The modification of a project consists in updating the description of it. It doesn‟t include the content embed within it.

This action is only possible for a facilitator or the project owner.

6.1.3.4 Manage project users

This action is only possible for a facilitator or the project owner.

6.1.3.5 Invite new users

From the “Members list” page, it is possible to invite an external user to join the project (semantic asset or software). Any member of the group has the capability to fill a form indicating the recipient and a specific message to invite him to the community.

The form that needs to be filled by the user contains the following fields:

- Recipient’s email addresses (mandatory): the email addresses of the people who are invited (separated by a coma).

- Message (mandatory, at least 15 characters): an message that will be associated to the email sent by the platform in order to explain the recipient why it is recommended for him to join

- Captcha (mandatory): A captcha is an image that represents a text in order to avoid or limit email spam from robots.

The recipient and the authenticated user (in copy) will then receive the following message.




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

<Firstname> <Lastname> has invited you to join the team of the project <Name> on ISA-ICP. <Firstname> enclosed the following message for your intention: <Message> About the <Group type> <Title>: <Abstract>. To join this community click on the following link <Link To Community> As a member, you will be able to participate actively in the activities of this community. You will be able to create and highlight content, such as blogs, news items, events, useful software or semantic asset and participate in the discussion forums and wikis of the community. You will be automatically notified of any activities and new content. For a complete list of advantages of membership, click here <Link To About Us>. You want to report a spam? You can send us an email to <site email address>. ISA-ICP Team

If the recipient‟s email address doesn‟t exist, no warning is sent to the sender.

6.1.3.6 Leave a project

Members of a project can choose to leave it by filling the appropriate form. Form just asks for confirmation.

This action doesn‟t require approval from facilitator or project owner.

The user receives a notification informing him that his request has been completed.

Dear <Firstname> Your request to leave the project <Name> has been completed. From now, you are no more member of this project. ISA-ICP Team

6.2 Project Community

The projects are extended communities; they can use the same tools as the information communities (blogs, forums, wiki…). Those tools are detailed in the §5.

6.3 Assets

6.3.1 Synopsis

The assets describe resources that support the exchange of data in distributed information systems. Several kind of semantic assets are available through ISA-ICP, syntactic, semantic and meta assets:

Syntactic assets define common data structures, e.g. XML schema.

Semantic assets, on the other hand, deliver a central terminology to ensure that data elements are interpreted in the same way (e.g. taxonomies or code lists).




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

Meta-assets are not like the two others, the meta-assets consist in documenting technical specifications, good practices, methodologies, and process descriptions. Those are a precondition in order to produce adequate semantic interoperability assets.

6.3.2 Data Model

See annex 8.5.

Note: The assets don‟t hold any automatic image representation of the asset.


R_ISA-ICP_FUN_Content_Type_009.SemanticAssets: The application shall be able to manage semantic assets items.

R_ISA-ICP_FUN_Seed_Tools_007: The application shall support collaborative clearing process workflow.

R_ISA-ICP_FUN_Seed_Tools_008: The application shall support asset lifecycle management.

6.3.4 Workflow

The conformance process is depicted in the document “Vision of the Clearing Process” (ref: ISA-ICP_EXT003).

6.4 Open Source Software

6.4.1 Synopsis

An Open-source software (OSS) is a computer software that is available in source code form for which the source code and certain other rights normally reserved for copyright holders are provided under a software license that permits users to study, change, improve and at times also to distribute the software.

Only authenticated users can download an OSS.




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

6.4.2 Wireframe of the Open Source Software list




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

6.4.3 Data Model

See annex 8.3.


R_ISA-ICP_FUN_Seed_Tools_012: The application shall support the linking of a logo.

6.5 Issues

6.5.1 Synopsis

The issue is the global functionalities allowing managing:

The anomalies

The improvements

The milestones

The tasks

When the issue is created, it is unassigned.

Each member of a project can take an issue (auto-assign it) if the issue is unassigned.

Users with „developer‟ or „project owner‟ role can assign an issue to any other members.

An issue can be modified by „developer‟, „project owner‟ or any user assigned to the issue. In that case, any change made will be traced. Modifying an issue is done by adding a comment to it.

6.5.2 Data Model

See annex 8.14.


R_ISA-ICP_FUN_Seed_Tools_003: The application shall provide integrated bug tracking / issue management tool

R_ISA-ICP_FUN_Seed_Tools_004: The application shall provide integrated task management tools including milestones, tasks assignation and reporting




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

6.5.4 Workflow

The workflow used for managing the issues is available for all type of issues. Any ISA-ICP user may open a new issue; any member of the project may start working on it and solve it. Only the administrator can close or reopen an issue.

6.6 Mailing lists

6.6.1 Synopsis

Each project offers the capability of having a mailing list. The user can then speak between them by registering to the list and discussing through emails. Those emails are all stored within the project. It is then possible to look for the email sent.

6.7 Source Code Management

6.7.1 Synopsis

ISA-ICP offers the capability for the projects to store their source code within a source code management system (also called source code repository). Developers can use the repository to maintain current and historical versions of files such as source code, web pages, and documentation.


R_ISA-ICP_FUN_Seed_Tools_001 The application shall provide software versioning tool for project developers

R_ISA-ICP_FUN_Seed_Tools_011: The application shall provide adequate storing space for the source code and related documentation of projects and assets.

Open

In Progress

Resolved

Reopened Closed

Any User AdminMember




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

6.7.3 Workflow

At the end of the creation step, when the project is validated by the moderators, a repository for the source code is created and the access rights are given to the owner and the developers of the projects.

It‟s not possible to rename a repository after project creation. If required, project owner has to contact ISA administrator.

6.8 Version management and download

6.8.1 Synopsis

The application allows the owner to manage versions of software from the project. For each version, it is possible to add a file as attachment. Every registered user can then access to the download section of the project. It is mandatory to be a user to be able to download a project file.

When a user is downloading a release, the system must track this download in order to know how many people downloaded the product. The number of download for each release should be available on the release page.


R_ISA-ICP_FUN_Seed_Tools_018: The application shall provide information (description, tags, activity, and metrics) related to OSS projects and assets

6.8.3 Workflow

Only the owner (or facilitator) can create a release and attach files to it.

Only the owner (or facilitator) can delete a release.

6.9 Link between Projects

6.9.1 Synopsis

By the same process of the Highlight (see §5.1.3.7), A member can define another project as an “used” project. For example, if a project is using a library registered within the platform, it is possible for user to declare it. Both projects will then have a reference each other.


R_ISA-ICP_FUN_Seed_AssetLink_001: The application shall support the concept of atomic and complex semantic assets.

6.9.3 Workflow

Any member can propose a highlight. The post-moderation workflow is applied for this process.




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

6.10 Virtual Forges

6.10.1 Synopsis

The virtual forges are websites that provides a view of projects coming from the ISA-ICP repository. The virtual forges are views of the existing repository in order to retrieve only the open source software. Because the virtual forge is a view of the ISA-ICP repository, all the rules and regulations of the platform will apply also to the virtual forge projects.

The virtual forges are a way for the European Administration to have their own forges without having another tool than the one given by ISA-ICP.

The virtual forges are technically administered by the ISA-ICP team but the moderation is given to the requesters in the condition that he is a member of a European Public Administration or a FLOSS community.

The virtual forges possess their own graphical charts which are configurable by the moderators. They are also a sub domain of ISA-ICP which allows linking a domain name dedicated to the forge (e.g. myforge.com redirects to myforge.isa.eu).

A project can be registered by several virtual forges. During the registration on a virtual forge, open source software is automatically added to the ISA-ICP repository and the current virtual forge. It is also possible on demand to ask to a moderator of ISA-ICP to add or remove project from the virtual forge.

The registration of a project within the virtual forge has exactly the same validation workflow as on the regular ISA-ICP interface, only the moderators are modified.

6.10.2 Use Cases

ISA – Virtual & Federated Forges (PV2)

Moderator

Create Virtual

Forge (VF)

Browse Virtual

Projects

Anonymous

User

Propose Project

Add Project Within

Virtual Forge

System

Choose Language

Add Project To

Global Forge

Update VF CSS

Update VF Front

Page

«uses»

«uses»

«uses»

«uses»

«uses»

Moderate

If the user is in the scope of

a virtual forge,

he automatically add the

project to this virtual forge

(if the project is accepted)

Import XML File

Create Federated

Project

Translate

«uses»

External Translation Service

Create Federated

Forge

«uses» «uses»




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

In addition, virtual forges are managed by users having the specific “Virtual Forge admin” role. This role lets them have the possibility to modify the virtual forge theme and all contents inside the virtual forge.

A virtual forge administrator has not the possibility to validate projects when created, but they receive notifications about validated or rejected projects.


R_ISA-ICP_FUN_Seed_Tools_022: The application shall support the creation of "virtual forges".

6.10.4 Workflow

The creation of a virtual forge is a technical administration workflow. By the intermediary of a user, a European Administration asks for a new Virtual Forge through the contact form.

6.11 Federated Forges

6.11.1 Synopsis

The federated forge consists in making links from existing European forge within ISA-ICP. The moderator can create and update a federated forge. It consists in uploading on the application an XML file through a dedicated interface.

The integration of federated projects is done in several steps:

Register the federated forge.

Get the list of project and choose the one you are interested in.

Register the project on ISA-ICP

Those federated projects are not aimed to have the same tools as the other projects. It is only a description of the project with the link to the real forge. The description may be tagged and categorized by the moderators. The categorization must answer to the same elements as the other projects.

6.11.2 Use Cases

See §6.10.2.

6.11.3 Data Model

We distinguished two different kind of data model within this concept of federated forges. The first data model is the definition of a federated forge (see §8.4)

The data model for the federated project is the same as for the other open source software (see §8.3)


R_ISA-ICP_FUN_Seed_Tools_016: The application shall provide tool for federating information (description, tags, activity) related to OSS projects hosted by partner national forge.

R_ISA-ICP_FUN_Seed_Tools_017: The application shall make possible to exclude projects from federation of partner national forge.




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

6.11.5 Workflow

6.11.5.1 Registering a federated forge

This workflow consists in registering an external forge on the platform. This creation can only be done by a moderator. It only consists in registering the form. On the following night, during the nightly update, all projects from the forge will be created and will need to be validated by a moderator before being




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

6.11.5.2 Automatic update of the federated forge

The automatic update is launched every day during the night.

A second phase of this automatic update is for the moderators to get the report and apply manually those following actions:

System

Extract the list

of projects

Third Party System

Upload the

description file

End

Propose

English translation

Launch

automatic update

[YES]

[NO]

Update

the project

Does the project

exist or is it in the

banned list ?

Get the project name

Partial

End

Notify moderators

with a report

Propose the project

Does the

description been

modified ?

[NO]

Get the description

[YES]




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

For newly federated projects: approve, postpone or deny federation, categorize the project and enhance the description.

For projects with changed description: see the changes made and perform changes on the newly proposed english description.

6.12 Asset assistant

6.12.1 Synopsis

The asset assistant is a set of issue that the owner of a semantic asset can generate through the interface. This is a help for the asset owner in order to help him having a correct asset. These issues are managed in two different phases.

1. The first phase consists in choosing what kind of issue, the asset owner needs 2. In a second step, the system generates a set of issue depending on the answer of the first step.

By clicking on a button from the semantic asset homepage, the user is generating a form (through AJAX). This form must be filled depending on the issue already generated. At first use, all the boxes are unchecked. If the issues are deleted manually by the owner, they cannot be regenerated.

6.12.2 Data model

No Data model


No business rules

6.12.4 Workflow

No workflow.




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

7. “MEET” LAYER

The “MEET” layer is dedicated to offer a place to exchange information about the real life.

This part of the document details tools like newsletters, search engine and calendar/events.

7.1 General use cases

7.2 Newsletters

7.2.1 Synopsis

A newsletter is a regularly distributed publication generally about one main topic that is of interest to its subscribers.

Register To

Newsletter

«extends»

«extends»

ISA – Newsletter, Search and Event content

types (PV3 & PV4)

Anonymous

Browse Content

Browse Cases

Browse Events

Browse eLibrary

«extends»

«extends»

«uses»

«uses»

User

System

Send Newsletter Moderator

Prepare Newsletter

Search For Content

Browse Glossary

«extends»

Publish Video

Content

Send Message

(Contact)




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

Any user can define whether or not he wants to receive a newsletter. For this, he can check an option in its profile.

Newsletters are managed by the moderators.

On the one hand, the moderators can create simple newsletter and define editorial content. On the other hand, the moderator will also have the possibility to create automated newsletters and define:

- How frequently the system will send newsletters to subscribers (days/weeks/month) - Which content type or taxonomy to send - What week day and time of the day the newsletter should be sent out - How to format the newsletter (labels, header, footer, style…)

Newsletters are archived after sending.

7.2.2 Data Model

See annex 8.19.


R_ISA-ICP_FUN_Content_Newsletter_001: The application shall support the preparation and the distribution of newsletters

7.2.4 Workflow

No workflow.

7.3 Search facility

7.3.1 Synopsis

A search allows users to find contents matching specific criteria.

It can be generic (searching one or more words in the contents) or with more advanced criteria (based on taxonomies e.g. domains, languages, countries or content types e.g. assets, projects, users, news...).

It is possible to search inside attached documents to contents.

Search facility consists of providing an advanced search allowing user to select filters:

- any words or phrase ; - based on taxonomies ; - a global search (on the whole content of the platform) - a localized search (within a community)

Note:

It is important to distinguish the search with the filters. The search federates different contents whereas the filter is attached to an existing list of content.

7.3.2 Data Model

No data model is available yet.




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A


R_ISA-ICP_FUN_Content_Search_001: The application shall support the presentation of tailored content based on user preferences

R_ISA-ICP_FUN_Content_Search_002: User shall able to search for all content he has access to

R_ISA-ICP_FUN_Content_Search_001: The application shall support semantic search

7.3.4 Workflow

No workflow.

7.4 Events

7.4.1 Synopsis

An event informs users about a specific subject happening on a specific date and time.

An event can be linked (highlighted) for communities, projects or assets. It means that the events are site wide objects.

A list of the upcoming and latest events is displayed to site homepage.

Event‟s list will also be available in a calendar view.

7.4.2 Data Model

See annex 8.18.


No business rules

7.4.4 Workflow

An event is considered as moderated. Any user can propose an event but it needs the approval from moderator to be published on the ISA-ICP site.




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

8. ANNEX 1: DATA MODELS

8.1 User Profile

Profile Field Type Mandatory Multiple Comments

Account Information

Username Short text yes no

Password Short text yes no

Email Email yes no

Role List* yes no "Moderator" or ""

Personal Data

First name Short text yes no

Name Short text yes no Surname or Last name

Photo Image no no

Country List yes no European countries (Albania… United Kingdom), Other countries (…Pan European… Oceania)

CV File no no A file for the Curriculum Vitae of the user.

Organization / Company

Name Short text yes no

Type List yes no Public, Private (large enterprise), Private (SME or independent), Non-profit, Academia

Scope List yes no Worldwide, European, National, Regional, Local

My Preferences

My Domains List no yes List of categories based on the fixed categories available on the web site

My Keywords

List no yes List of keyword (tags)

My Languages

List no yes Bosnian, Bulgarian, …, Turkish, Other

Privacy Settings

Email Visibility

checkbox yes no Registered users can see email

Profile Visibility

checkbox yes no Registered users can see My Languages, My Domains




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

8.2 Community

Community Field Type Mandatory Multiple Comment

Community Information


Abstract Short text yes no Limited to 150 characters

Description Long text yes no

Email Contact Email yes no

Logo Image no no

Sponsor Logo Image no no

Categories

Domains List yes yes

List of categories based on the fixed categories available on the web site

Keywords List no yes A list of free tags managed by the moderators

Languages List yes yes Bosnian, Bulgarian, …, Turkish, Other

Goals and Background

Expectations Long text yes no

Estimated members at launch

Short text yes no Default value is 1

Estimated members after 1 year

Short text yes no Default value is 1

Existing URL on the Internet

Short text no no

Privacy Settings Community Privacy Checkbox yes no Public or private (default value for public)

Rating Rating Mark no no

Anybody can rate an asset (even the member of a community)

8.3 Open Source Software item

Field Field Type Mandatory Multiple Comment

Software Information




Features Long text no no

Future Plans Long text no no

Get Involved Long text no no




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A


Public Administration Reference

Long text no no


Logo Image no no

Sponsor Logo Image no no

Project Resources

Homepage URL no no

More Links URL no yes

This is a set of URL + title, it means for example that a project can register “Issue Management” http://XXXX

Source repository URL no no

Generated by the project at the creation but modifiable afterwards.

Categories

Development Status List yes no


Intended Audience List no yes List of categories based on the fixed categories available on the web site

Licence List no yes List of categories based on the fixed categories available on the web site

Natural Language List no yes Refers to the “Languages” category

Operating System List no yes List of categories based on the fixed categories available on the web site

Programming Language List no yes List of categories based on the fixed categories available on the web site





http://xxxx/




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A


Related Projects

Using List no yes List of other projects used by this project.

Used By List no yes

List of other projects on the platform which are using this one. This list is inherited from the other project “Using” list.

Rating Rating Mark no no

Anybody can rate an asset (even the member of a software community)

8.4 Federated forge


Forge Information



Language List yes no

Choose the language from which the translation will be done into English

Get Involved Long text no no


Logo Image no no

Forge resources

Homepage URL yes no Reference the original web site

XML File URL yes no Reference the XML file to be retrieved.

Associated Projects List no yes List of projects associated to this federated forge

Categories








/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

8.5 Asset item


Asset Information





Logo Image no no

Asset Owner Long text yes no The asset owner is the legal owner of the asset.

Represented Countries List yes yes


Categories

Asset Status List yes no


Licence List no yes


Natural Language List no yes






Related Projects

Using List no yes List of other projects used by this project.

Used By List no yes

List of other projects on the platform which are using this one. This list is inherited from the other project “Using” list.

Rating Rating Mark no no Anybody can rate an asset (even the member of an asset




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

community)

8.6 News item

News Field Type Mandatory Multiple Comment

News Information

Title Short text yes no



City Short text no no

Source URL URL no no

Documentations Files no yes

Categories

Country List no no List of countries

Domains List yes yes List of categories based on the fixed categories available on the web site



Revision

Author Short text yes no Automatic

Created Date yes no Automatic

Last Edited Date yes no Automatic

Rating Rating Mark no no The owner can’t rate his own content

8.7 Blogs

Blog Field Type Mandatory Multiple Comment

Blog Information



Categories





Revision



Last Updated

Date yes no Automatic

Rating Rating Mark no no The owner can’t rate his own blog




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

8.8 Wikis

Wikis Field Type Mandatory Multiple Comment

Wiki Information



Categories




Revision

Author Short text yes no Invisible


Last Updated


Last Updated By

Short text yes no Automatic

Rating Rating Mark no no The owner can’t rate his own wiki

8.9 Image

Forums Field Type Mandatory Multiple Comment

Image Information


Image File yes no

Categories




8.10 Forums

Forums Field Type Mandatory Multiple Comment

Forum Information



Categories




Revision Author Short text yes no Automatic




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A


Last Updated


Rating Rating Mark no no The owner can’t rate his own forum

8.11 Comments

Comments Field Type Mandatory Multiple Comment

Main Information Title Short text yes no


Revision Author Short text yes no


8.12 Component

Component Field Type Mandatory Multiple Comment

Main Information Name Short text yes no







/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

8.13 Release

Release Field Type Mandatory Multiple Comment

Main Information

Number Short text yes no


Files File no yes

Release Information

Models List yes yes Just available for the assets See list declared in taxonomy “Models”

Syntactical Specification

List yes yes Just available for the assets See list declared in taxonomy “Syntactical specification”

Semantical Specification

List yes yes Just available for the assets See list declared in taxonomy “Semantical specification”

Abstract Specification

List yes yes Just available for the assets See list declared in taxonomy “Abstract specification”



8.14 Issue

Issue Field Type Mandatory Multiple Comment

Main Information Title Short text yes no


Project Information

Project name

Short text yes no

Version List yes no

Component List yes no

Issue Information

Category List yes no See list declared in taxonomy “Issue type”

Priority List yes no See list declared in taxonomy “Issue severity”

Assigned List no no List of users

Status List no no

Files File no yes






/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

8.15 Survey

Survey Field Type Mandatory Multiple Comment

Main Information Question Short text yes no


Decision Choices Short text yes yes

Settings

Maximum choices

Integer no no

Opening date

Date no no

Closing date

Date no no

Electoral list

Boolean yes no Restrict voting to electoral list

Individual vote

Boolean yes no Show individual votes. Users with the appropriate permissions will be able to see how each person voted

Randomise Boolean yes no Display answers in a random order each time the poll is displayed

Quorum Integer no no These settings allow for a decision to be valid only if a certain number of eligible voters have cast their ballot






/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

8.16 Case

Case Field Type Mandatory Multiple Comment

Case Information


Acronym Short text no no

Presentation URL URL yes no

Logo Image no no

Website URL URL yes no

City/Region Short text no no

Start date Date yes no

End date Date yes no

Operational date Date no no Date on which case become operational

Abstract Long text yes no

Policy context Long text no no

Target users Long text yes no

Description of target users and groups

Long text no no

Description of the way to implement the initiative

Long text no no

Technology solution

Long text no no

Main results, benefits and impacts

Long text no no

Return on investment description

Long text no no

Track record of sharing

Long text no no

Lessons learnt Long text no no

Categories


Type of initiative List yes yes List based on taxonomy

Domains List yes yes List based on taxonomy


Scope List yes yes List based on taxonomy “Scope”

Status List no no List based on taxonomy “Case status”

Type of service List yes no List based on taxonomy

Overall implementation

List yes no List based on taxonomy




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

approach

Technology choice

List yes yes List based on taxonomy

Funding source List no no List based on taxonomy

Implementation cost

List no no List based on taxonomy

Yearly cost List no no List based on taxonomy

Return on investment

List no No List based on taxonomy


Revision








/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

8.17 Document

Document Field Type Mandatory Multiple Comment

Document Information



Publication date Date yes no

Publisher Short text no no

ISBN Number Short text no no

Description of license

Short text no no

Additional documentation description

Short text no yes

Additional documentation file

File no yes List of documents (max 6MB) Allowed : ppt, pdf, doc, zip

Original URL URL yes no

Email contact Short text yes no

Categories

Nature of documentation


Domains List yes yes List based on taxonomy


License of document


Country List yes no List of countries

Languages List yes yes List based on taxonomy

Revision








/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

8.18 Event

Event Field Type Mandatory Multiple Comment

Event Information



Logo File no no

Start date Date yes no

End date Date yes no

City Short text yes no

Venue Long text no no

Address/Location Long text no no

GMAP location Map no no Link to Google Map

Organiser Short text yes no

Website URL no no

Contact email Short text no no

Agenda Long text no no

Expected participants

Long text yes no

Fees description Long text yes no

Categories

Starred contents List no yes List of content types (cases, news, blog, event or home)

Country List yes no List based on taxonomy

Scope List yes no List based on taxonomy

Languages List yes yes List based on taxonomy

Domain List yes no List based on taxonomy


Topic List yes yes List based on taxonomy

Videos List no no List based on taxonomy

Free event List yes no Yes, participant has no cost No, participants have to pay a fee

Open event List yes no

Yes, event with unrestricted attendance No, restricted event, only by invitation

Revision








/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

8.19 Newsletter

Newsletter Field Type Mandatory Multiple Comment

Newsletter Information


Description Long text no no

Categories Domain List yes no

Revision








/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

8.20 Factsheet

Factsheet Field Type Mandatory Multiple Comment

Factsheet Information



Upload file File yes yes Allowed formats (pdf, html)

Categories Country List yes no List based on taxonomy

Factsheet Topic List yes no List based on taxonomy

Revision





8.21 Video

Factsheet Field Type Mandatory Multiple Comment

Video Information



Link to the video Embed link

yes No Link to video coming from Youtube or dailymotion.

Categories Domain List yes no List based on taxonomy


Revision







/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

9. ANNEXE 2: TAXONOMIES

9.1 Imported taxonomies

The three applications (semic.eu, osor.eu and epractice.eu) already host taxonomies that will simply be imported to ISA-ICP platform as they will still be useful. However, in order to improve the conformance regarding existing norms, some of these taxonomies have been modified to take advantages of the tree structure offered by Drupal:

“Development Status” from osor.eu merges the status “Conform” from semic.eu

“Operating Systems” is using the Wikipedia tree structure

“Categories” is replacing the taxonomies “Environment” and “Topic” from osor.eu by a taxonomy coming from sourceforge.net

4

The merging of the domains of these both platforms results in the table below.

Note: These taxonomies are aimed to be available at the beginning of the project but this list may be adapted online, it means that during the life of the project if there is a need to adapt a taxonomy, the system will provide interfaces to do it.

Level 1 Level 2 Level 3

Development Status

Planning (empty)

Pre-Alpha (empty)

Alpha (empty)

Beta (empty)

Production/Stable (empty)

Mature (empty)

Conform (empty)

Categories

Clustering (empty)

Communications Internet Phone, Email, Fax, Telephony, BBS, Ham Radio, Conferencing, Chat, FIDO, Streaming, Usenet News, File , haring, Synchronization, RSS Feed Readers

Database Front-Ends, Database Engines/Servers

Desktop Environment K Desktop Environment (KDE), Window Managers, Gnome, Fonts, Screen Savers

Education Testing, Computer Aided Instruction (CAI), Administration, Languages, Library

Formats and Protocols Data Formats, Protocols

Internet File Transfer Protocol (FTP), Log Analysis, Finger, Name Service (DNS), SSH (Secure SHell), WWW/HTTP, WAP, Other file transfer protocol

Mobile (empty)

Multimedia Home Theater PC, Cataloguing, Sound/Audio, Video, DVD, Graphics

4 http://sourceforge.net




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

Office/Business

Enterprise, Report Generators, Desktop Publishing, To-Do Lists, Project Management, Office Suites, Insurance, Scheduling, E-Commerce / Shopping, Knowledge Management, Time Tracking, Modelling, Financial

Printing (empty)

Scientific/Engineering

Physics, Mechanical and Civil Engineering, Electronic Design Automation (EDA), Bio-Informatics, Ecosystem Sciences, Simulations, Artificial Intelligence, Molecular Science, Earth Sciences, Mathematics, Quantum Computing, Mapping, Test and Measurement, Linguistics, Chemistry, Interface Engine/Protocol Translator, Astronomy, Molecular Mechanics, Building Automation, Human Machine Interfaces, Medical Science Apps., Information Analysis, Medical Physics, Visualization, Robotics, SCADA

Security Anti-Spam, Anti-Malware, Anti-Virus, Cryptography, Password manager

Social Sciences Genealogy, Psychology, Voting, History, Politics

Software Development

Collaborative development tools, Compilers, Profiling, Source code browsing, Agile development tools, Binary editors, Virtual Machines, ORM (Object-relational mapping), Version Control, Cross Compilers, Application Servers, Algorithms, User Interfaces, Templates, Source code analysis, Modeling, Testing, Assemblers, Design, Code Generators, Documentation, Usability, Build Tools, Quality Assurance, Interpreters, Object Oriented, Object Brokering, Debuggers, Libraries, CASE, Source code review, I18N (Internationalization), L10N (Localization), Frameworks

System

System Shells, Installation/Setup, Power (UPS), Clustering, Distributed Computing, Cron and scheduling, Systems Administration, OS distribution, Hardware, Networking, Benchmark, Software Distribution, Embedded systems, Storage, Home Automation, Boot, Search, Filesystems, Logging, Operating System Kernels, Emulators

Terminals Telnet, Serial, Terminal Emulators/X Terminals

Text Editors

Computer Aided Translation (CAT), Word Processors, Documentation, Integrated Development Environments (IDE), Emacs, Vi/Vim, Text Processing

Other/Nonlisted Topic (empty)

Country

European Countries Albania, Austria, Belgium, Bosnia and Herzegovina....,

Sweden, Switzerland, Turkey, United Kingdom

Other Countries Other European Countries, Pan European, EU Institutions, Internal Organizations, Africa, Asia, Central and South America, North America, Oceania

Domains Culture Architecture, Languages, Library Science, Multilingualism, Religion, Culture (other)




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

Economy Accounting, Agriculture, Customs, Energy, Enterprise, Employment, Fisheries and Maritime Affairs, Internal Market, Procurement, Taxation, Trade, Economy (other)

EU Affairs Budget, External Relations, Foreign and Security Policy, Regional Policy, EU Affairs (other)

Environment Biodiversity, Pollution, Waste, Water, Environment (other)

Health Diseases, Food Safety, eHealth, Pharmaceutics, Health (other)

Information Society Audiovisual and Media, Communications, Internet, Information Society (other)

Justice Crime, Internal Security, Law, Justice (other)

Research and Innovation Biology, Chemistry, Engineering, Geography, Social Sciences, Research and Innovation (other)

Social Affairs Consumers, Development, Education, eInclusion, Employment, Youth, Social Affairs (other)

Other (empty)

Intended Audience

Developers (empty)

End Users/Desktop (empty)

Other Audience (empty)

System Administrators (empty)

Issue Severity

Blocker (empty)

Critical (empty)

Major (empty)

Normal (empty)

Minor (empty)

Trivial (empty)

Issue Type

Bug (empty)

Improvement (empty)

New Feature (empty)

Support (empty)

Task (empty)

Languages

Bosnian, Bulgarian, ...

French, German, Greek, ...

Turkish, Other

(empty)

Licenses

European Union Public License (EUPL)

(empty)

Apache Software License 2.0

(empty)

Artistic License (Perl) (empty)




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

BSD License 2.0 (empty)

GNU General Public License (GPL)

(empty)

GNU General Public License (GPL) 2.0

(empty)

GNU General Public License (GPL) 3.0

(empty)

GNU Lesser General Public License (LGPL) 2.1

(empty)

MIT License (empty)

Mozilla Public License (MPL) 1.1

(empty)

Public Domain (empty)

Other Licenses

OSI Approved, IBM Public License, Intel Open Source License, Jabber Open Source License, MITRE Collaborative Virtual Workspace License (CVW), MIT/X Consortium License, Mozilla Public License (MPL), Mozilla Public License (MPL) 1.0, Nethack General Public License, Nokia Open Source License, Python License, QT Public License (QPL), Ricoh Source Code Public License, Sleepycat License, Sun Internet Standards Source License, Vovida Software License, zlib/libpng License, Other

Operating Systems

Other Apple, Inc. Mac OS X, Mac OS X Server , Other Apple, Inc.

DOS DR-DOS, FreeDOS, MS-DOS, Other DOS

IBM AIX, MVS, OS/400

Microsoft Windows 3.x, 95 / 98 / Me, NT / 2000, XP, 2003, Vista, 2008, 7

POSIX / UNIX BSD, GNU, GNU / Linux, Other POSIX / UNIX

Mobile Android, BlackBerry OS, Cisco IOS, Palm OS, Windows Mobile, Other Mobile

Other Environment (empty)

Programming Language

C (empty)

C# (empty)

Java (empty)

JavaScript (empty)

Perl (empty)

PHP (empty)

PL/SQL (empty)

Python (empty)

Ruby (empty)

Zope (empty)




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

Other ASP, ASP .NET, Ada, APL, Assembly, C++, Cold Fusion, Delphi/Kylix, Eiffel, Erlang, Euler, Euphoria, Forth, Fortran, Lisp, Logo, ML, Modula, Objective C, Object Pascal, Pascal, Pike, Progress 4GL, Prolog, REBOL, Rexx, Scheme, Simula, Smalltalk, Tcl, Unix Shell, Visual Basic, Visual Basic .NET, XBasic

Nature of documentation

Annual report of activities (empty)

Article (empty)

Audit/Parlamentary reports and evaluations

(empty)

Book (empty)

Booklet (empty)

Conference-seminar-meeting proceeding

(empty)

Guide (empty)

Independent reports and studies

(empty)

Legal document (empty)

Manual (technical documentation)

(empty)

Official reports and studies (empty)

Other (empty)

Package (didactic kit, software, CD-Rom…)

(empty)

Policy/Strategy papers (empty)

Standard (empty)

Statement (empty)

Surveys (empty)

Technical report (empty)

Thesis (empty)

Unpublished work (empty)

Document license

Copyright (empty)

Copyleft (empty)

Creative commons (empty)

GPL (empty)

Other (empty)




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

Type of initiative

Project or service (empty)

Network (empty)

Strategic initiative (empty)

Award scheme (empty)

Promotion/awareness campaign

(empty)

Other (empty)

Scope

Cross-border (empty)

International (empty)

Local (city or municipality) (empty)

National (empty)

European (empty)

Pan-European (empty)

Regional (sub-national) (empty)

Case status

Not applicable / Not available

(empty)

Research (empty)

Pilot (empty)

Implementation (empty)

Operation (empty)

On hold (not operating) (empty)

Ended (empty)

Type of service


(empty)

Awareness-raising information

(empty)

Training and education (empty)

Content provision (empty)

IT Infrastructures and products

(empty)

Participation (empty)

Inclusive services of general interest

(empty)

Other (empty)

Overall Public administration (empty)




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

implementation approach Private sector (empty)

Non-profit sector (empty)

Partnerships between administration and/or private sector and/or non-profit sector

(empty)

Technology choice

Proprietary technology (empty)

Standards-based technology

(empty)

Mainly (or only) open standards

(empty)

Accessibility-compliant (minimum WAI AA)

(empty)

Open source software (empty)


(empty)

Funding source

Public funding EU (empty)

Public funding national (empty)

Public funding regional (empty)

Public funding local (empty)

Private sector (empty)

Charity, voluntary contributions

(empty)

Implementation cost


(empty)

€1-5,000 (empty)

€5-15,000 (empty)

€15-49,000 (empty)

€49-299,000 (empty)

€300-499,000 (empty)

€500-999,000 (empty)

€1,000,000-5,000,000 (empty)

€5,000,000-10,000,000 (empty)

Larger than €10,000,000 (empty)

Yearly cost Not applicable / Not available

(empty)




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

€1-49,000 (empty)

€49-299,000 (empty)

€300-499,000 (empty)

€500-999,000 (empty)

€1,000,000-5,000,000 (empty)

€5,000,000-10,000,000 (empty)


Return on investment


(empty)

€1-5,000 (empty)

€5-15,000 (empty)

€15-49,000 (empty)

€49-299,000 (empty)

€300-499,000 (empty)

€500-999,000 (empty)

€1,000,000-5,000,000 (empty)

€5,000,000-10,000,000 (empty)


Factsheet topic

Actors (empty)

Areas (empty)

The Future of eInclusion (empty)

eServices for Administration

(empty)

Country profile (empty)

Digital Literacy and Competences

(empty)

e-Accessibility (empty)

e-Inclusion Challenges (empty)

e-Inclusion and Cultural Diversity

(empty)

eServices for Businesses (empty)

eServices for citizens (empty)

Geographic digital divide (empty)

History (empty)




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

Inclusive eGovernment (empty)

ICT & Ageing (empty)

Infrastructure (empty)

Internal Services (empty)

Legal Framework (empty)

National infrastructure (empty)

Research in Practice (empty)

Society (empty)

Strategy (empty)

Who is who (empty)

Asset assistant chapters

Requirements Analysis (empty)

Concept & Specification (empty)

Reusing existing assets (empty)

Development of a new asset

(empty)

Avoiding Semantic Conflicts (empty)

Prototype (empty)

Asset status Unpublished (empty)

Development (empty)

Models

UML (empty)

UMM (empty)

BPMN (empty)

FMC (empty)

Other (empty)

Syntactical specification

XML Schema (empty)

Relax NG (empty)

Schematron (empty)

WSDL (empty)

ebXML Process Def. (empty)

Other (empty)

Semantical specification

Codelists (empty)

Mappings (empty)

Taxonomy (empty)




/ 88

MD

-11-0

4-S

M-2

6-E

N R

ev A

Ontology (empty)

Other (empty)

Abstract specification

Core Components (empty)

Other (empty)

END OF THE DOCUMENT