Publications Office Portal 2012 - Functional Requirements
Publications Office Portal
Functional Requirements definition
Version 1.3
|Date: |13 June 2012 |
|Version: |1.3 |
|Reference Number: |Publications Office Portal 2012 - Functional Requirements |
Other applicable or related documents
|Doc Date |Doc Version |What |
|1/03/2012 |3.1 |Technical environment and standard operating procedures of the Publications Office |
|13/06/2012 |1.1 |PORTAL2012-BUSINESS-PROCESS-MODELS |
|14/02/2012 |1.0.6 |DLV0006 CELLAR Dissemination Interface |
|17/03/2010 |4.0 |ATTO - Architecture Schema overview[pic] |
|25/03/2011 |1.0 |Search Layer Software Architecture Document |
Table of Contents
Introduction 6
Purpose 6
Document Scope 6
Key Stakeholders 6
Vision & Scope 7
Business perspective 8
Business objectives 10
Business metrics 12
Business services 15
Business processes 18
BP1 – Search 19
BP2 –Display or Download 22
BP3 - Browse by subject 26
BP4 - Wide accessibility 29
BP5 – Order publications 31
BP6 – Notifications 34
BP7 – Semantic Search 40
BP8 – Error handling 44
BP9 – User Profile Management 46
BP10 - Personalization 48
BP11 – User identification 50
BP12 – User authentication 52
BP13 – Application Store management 54
User perspective 55
User profiles and audiences 55
User features 59
Browsing & Navigation 61
Search 63
Browse by subject 66
Content Display 69
Permanent links 70
Web Content Management 71
Multi-site, Multi-tenant 75
Multilingual aspect 76
Publishing workflow 77
User feedback 77
Social sharing - ShareThis 77
Bookmarks 78
Annotations 78
Survey / Quiz 78
Profiling - personalization / customization 79
Mash-ups / widgets 90
Authorization - access rights 92
Single Sign On 92
Notifications 93
Linked Open Data - Use of public data 94
Direct access to search index 96
Statistics and reporting 97
Error handling 100
Mobile View 100
Page mock-ups 101
Home page 101
Search results 102
Advanced search 103
Page details 104
ShareThis feature 107
Permanent Links 108
Browse by subject 109
page templates & widget areas 110
Mobile Homepage(search center) 110
Mobile search autosuggest feature 111
Mobile Browse by subject 112
Mobile search results list and publications details 112
Solution requirements 113
Business requirements 113
Scalability 113
Reliability 113
System requirements 114
Architecture 114
Interoperability and standards 136
Electronic Publishing 136
Operational requirements 137
Security 137
Search Engine Optimization (SEO) 137
Availability 138
Performance 138
Manageability & Maintainability 139
Installation & Deployments 140
Ownership 140
Traceability 140
Technical environment of the Publications Office 140
Legal & regulatory requirements 141
The publications office mission statement 141
Data protection legal framework 141
EU Commission security legal framework 141
User requirements 142
Wide accessibility 142
Usability 144
Extensibility 146
Integration 147
Search layer 147
CELLAR 147
Translation systems (ATTO) 147
EUROVOC 147
Metadata register - Authority tables 148
Web-analytics, Statistics and reporting – Webtrends system 148
Other systems 150
Annexes 151
Annex I – Mobile Web Usability guidelines 151
Annex II – Detailed schemas of business processes used by 153
Table of Figures
Figure 1 - Business Interaction Model of the Content Management business domain 8
Figure 2 - Publications Office online dissemination services 15
Figure 3 – OP Online Dissemination Services - General Access Services (to be provided by Portal-2012) 16
Figure 4 – OP Online Dissemination Services – Support and Management Services (detailed those to be provided by Portal-2012) – provide support services for General Access Services and Specialized Access Services 18
Figure 5 - OP Common User profile & preferences 57
Figure 6 - Common shared features and functionalities to be supported by 59
Figure 8 - Specialized features and functionalities (to be supported by specialized websites/services) 60
Figure 9 - Using widgets 90
Figure 10 - Mockup of the home page 101
Figure 11 - Mockup of the search results page 102
Figure 12 - Mockup of the advanced search page 103
Figure 13 - Mockup of an EU law details page 104
Figure 14 - Mockup of a general publication details page 105
Figure 15 - Mockup of a business opportunity publication details page 106
Figure 16 - MockUp of the ShareThis feature as presented in the EU Commission IPG 107
Figure 17 - Mock-up of Permanent link for a publication 108
Figure 18 - Mockup Browse by subject 109
Figure 19 - Mobile homepage mock-up 110
Figure 20 - Mobile search mock-up 111
Figure 21 - Mobile Browse by subject mock-up 112
Figure 22 - Mobile search results mock-up 112
Figure 23 - Target architecture of the Transformation Program 115
Figure 24 - Portal Sitemap 117
Figure 25 - Single point of entry to web resources and services 118
Figure 26 - Integration / aggregation of multiple services and applications 119
Figure 27 - Role based content presentation. Display different data depending on a user's role 120
Figure 28 - Widgets and mashup capabilities 121
Figure 29 - Multilingual content and navigation - a method to simplify the development and management of pages for each language 122
Figure 30 - Login 123
Figure 31 - CELLAR system overview 125
Figure 32 - PO-USER-PROFILING-SERVICE 130
Figure 33 - PO-CENTRAL-AUTHENTICATION-SYSTEM 134
Figure 34 - PO User identity 135
Introduction
Purpose
The is a strategic component of the Publications Office Transformation program. It will implement the "web" layer of the target architecture foreseen by the Transformation program and it will enable any Internet user to access any content and any metadata stored in CELLAR and managed by the Office. stands for the internal OP name of the project and its project management needs.
Document Scope
The purpose of this document is to define the business and user needs and features of the proposed information system. It focuses on the capabilities needed by the stakeholders and the target users. Detailed descriptions of how the information system fulfills these needs are presented in the business services and processes chapters.
This document proposes a complete view on including the following elements:
• A detailed definition of the strategic orientation of the new dissemination tool which is ;
• A detailed description of the user and system functional requirements, including how the user should interact with the system as well as system inputs and outputs.
• A proposal for the functional architecture of the system with an brief description of its functionalities;
• Guidelines for the implementation of the system.
Key Stakeholders
Project stakeholders are those entities within or outside an organization which sponsor the project or have an interest or a gain upon a successful completion of a project or may have a positive or negative influence in the project completion. For the Project, the key stakeholders are:
• The Management Committee (Comité de direction)
• The Publication Office senior management
• The business owners of the OP specialized sites: EUR-Lex, EU Bookshop, TED
• The CELLAR Business Owner (OP Unit Enterprise Architecture)
• The OP Index & Search layer business Owner
• OP Units infrastructure, OP IT Projects Unit
• The Publications Office LISO and DPO
• User representatives
• Compliance with governance issues is assured by:
o IT Steering Committee (SI2) in the Publications Office
o European Commission Information Systems Project Management Board
Vision & Scope
The main goal of will be to provide the general public with simple and easy access to all EU Law and publications stored in CELLAR through a unique and easy to use online access point. Users must be able to easily find content by performing a simple search (single-field), an advanced search (more search options)) or simply navigating by subject or topic. The user should be presented with relevant content in the form of a search results list, grouped by facets (by topic, author, etc.) allowing him to refine the proposed results. The system should propose relevant content based on the user interaction.
Other horizontal services will be available through the web portal (e.g. notifications, fragment publishing, personalization, applications integration, identification, etc.) providing a strong added value to the final user. Horizontal services will be used as well throughout the OP specialized websites (e.g. EUR-Lex, EU Bookshop, TED, CORDIS).
The web portal should be user centric offering high accessibility to the entire content for both human and machine users. It should also allow all end-users to re-use or enhance the content according to their needs. Ultimately, the portal should provide citizens and professionals with an extensive, efficient, secure and easy-to-use suite of online services related to access to EU law and publications on European Union.
should be supported by a solid, flexible, robust, integrated and scalable infrastructure and technology ensuring rapid and constant evolution of its user services as well high accessibility from most web reading devices.
Easy to find, easy to reuse: It is important that the becomes a well-known single point where people can find all EU Law and publications.
Business perspective
The Publications Office of the European Union (Publications Office) publishes Law and general publications for the institutions and other bodies of the European Union as stated in the Treaties. In other words it acts as the publishing house of the EU institutions, producing and distributing all official European Union publications, on paper and in digital form. The figure below represents the interactions between the various actors in the three main domains covered by the Publications Office activities: Production, Storage/Archiving and Dissemination.
[pic]
Figure 1 - Business Interaction Model of the Content Management business domain
Definitions of the above business interaction model:
|Domain Element |Description |
|Archive (System) |Long term preservation archive to store content and metadata in an authenticated manner, in order to |
| |guarantee availability of trustworthy contents and metadata. Archiving tasks are currently performed by|
| |the EUDOR system. |
|Common Index & Search (System) |Common search is accessible via standardized interface to formulate queries that are independent from a|
| |particular search engine. The request will be translated and executed by an appropriate search engine. |
| |Responding to complex queries, by combining different search methods is possible. The search builds on |
| |a common set of indexes that are generated on the basis of content and metadata. |
|CCR (System) |Common content repository for any content published in electronic format managed by the Publications |
| |Office. |
| |CCR has the following functions: |
| |Receives content from production and post production chains; |
| |Transforms content (if needed) into strategic format; |
| |Reference and stores content for dissemination; |
| |Expose content to indexing services; |
| |Monitors the access to content from external systems to prevent degradation of service caused by |
| |external access (generally access is permitted without restrictions). |
|Common Metadata Repository (CMR)|Common Metadata Repository stores instance metadata related to publications being produced, |
|(System) |multilingual thesaurus metadata, translation metadata and metadata of references. There are |
| |synchronized read-only instances of the master CMR database. It enables access to data for indexing |
| |service and data retrieval for record queries. (*A subscription mechanism would be useful to deliver |
| |subscribed queries just in time. Therefore some subscriptions management has to be considered here.) |
| |Common metadata repository has following major functionalities: |
| |Receives metadata from production and post production chains; |
| |Stores metadata according to the storage scheme; |
| |Expose decoded metadata to indexing services; |
| |Makes metadata accessible for queries (receive query, extract metadata, deliver metadata); |
| |Ensures archiving of metadata, i.e. ingestion of metadata into the long-term preservation component. |
|Portal2012 |The web portal the general public with simple and easy access to all EU Law and publications stored in |
| |CELLAR (CMR+CCR) through a unique and easy to use online access point. It also allows all end-users to |
| |re-use or enhance the content according to their needs. |
|Production Systems (System) |Different production chains that prepare publications for production. Production is generally |
| |outsourced. The results (content, metadata) are delivered to post-production (validation, metadata, |
| |production/enrichment), storing and dissemination. |
|Search engine (System) |Internet search engines (e.g. Bing, Google, Yahoo, etc) |
|Validation systems (System) |Systems that validate publications received from production (CERES/ CERES2012). Validation systems are |
| |part of the Post production layer of the new architecture (out of the scope of this call for tender). |
|Author (Role) |Originators of publications delivering their content intended to be managed by OP for the further |
| |production and dissemination. Author is a client for OP and this type of actor represents mainly |
| |institutions and agencies of the EU. |
|Citizen (Role) |Publications Office target group – Citizens, general public |
|Information broker (Role) |Publications Office target group – Person or business that researches information for clients. Common |
| |uses for information brokers can include practically any type of information research & re-use. |
|Institution (Role) |Publications Office target group – European Institutions, Public Administrations, political |
| |Organizations |
|Professional (Role) |Publications Office target group – re-users (legal information services etc.), lawyers, librarians, |
| |knowledge managers, information brokers, and consultants that researches information for clients. |
|Automated application (System) |External application pulling-in content or using horizontal services/features from Portal 2012 (e.g. a |
| |professional/social network, other web portal, etc.) |
Business objectives
Currently, the public sites of the Publications Office are rather structured on a pillar type model despite the predominantly similar services, similar layouts and behavior. Each site was historically the result of ideas launched to support diverse political initiatives at various times, hence little coherence in technical project development. The resulting sites are therefore technically different, based on different management contracts, different hosts and heterogeneous presentation. However analysis confirms that two-thirds of services are common to all the websites with fewer than expected services specific to a particular site. Considering the implementation of a common repository for all official publications (CELLAR) and of the common index and search layer, the Publications Office Portal should represent an effective improvement to the current situation and fulfill the following objectives:
|Objective |Description |
|Efficient access to information: |Easy & rapid access to content: |
| |Users should be able to find information quickly and easily throughout the |
| |portal. |
| |Access services like search and browsing as well as all user interfaces must |
| |be intuitive and straightforward. |
| |User must spend very little or no effort in accessing any document and |
| |metadata stored in the CELLAR. |
|Advanced search services |User is able to limit his search or to refine search results using pertinent |
| |automatically proposed category or a specific section. |
|User centric access |User centric system, which: |
| |Presents content related to users’ interests and behavior. |
| |Recommend other interesting content related to users’ interests and previous |
| |behavior |
| |Allows the user to be in control with consistent set of actions in every |
| |context and all over the portal areas. The set of actions proposed to the |
| |user is dynamically adapted based on the user’s context. |
|Wide accessibility |Cross browser and cross device optimized accessibility |
|Personalization |The goal of personalization is to provide rapid access to relevant content |
| |and services to portal users. Users could decide what they want to view |
| |(explicit personalization) or the system personalizes the content based on |
| |rules or on users’ clickstream analysis (implicit personalization). It is a |
| |widely used method to prevent information overload of the online user. |
| |Personalization is based on the information known about the user and this is |
| |contained in a user profile. |
|Semantic Web |In addition to the classic “Web of documents” it helps building a technology |
| |stack to support a “Web of data”, in order to maximize reusability and value |
| |added services innovation. The ultimate goal of the “Web of data” is to |
| |enable computers to do more useful work and to develop systems that can |
| |support trusted interactions over the network. |
|Homogeneous and standardized presentation |User must have a unique and consistent browsing & content access experience |
| |throughout the portal areas and services; |
|Facilitate corporate image |Improve and harmonize corporate image and services. |
|Fast and quick reaction to changes/corrections. |Easy and rapid updates of editorial content, communication, functional |
| |modules, design and usability. |
|Designed for reusability |Easily discoverable content and indexed by other Internet search engines |
| |Allow for easy reuse of content in other external applications |
| |Allow direct access to our search index which will massively contribute to |
| |increase our dissemination capacity and the presence of EU law and |
| |publications in public access bibliographic databases, public access |
| |Web-based library catalogues (OPACs), web-based search engines like |
| |Bing/Google and/or open-access, government-operated or corporate data |
| |collections. |
|Designed for easy integration |Be able to pull in content or services from other applications/sources |
| |quickly with little or no additional coding. |
|Common horizontal service provider |Easy re-use of existing functionality, which is available as components out |
| |of the box |
| |Provide pre-built components. |
| |Easy extension of services and components with customization or configuration|
| |and without important coding efforts |
| |Easy integration of content coming from different sources. |
| |Provide a single platform ready for electronic dissemination services. |
|Is secure |The system must ensure that the following (predefined) criteria will be met: |
| |The integrity and availability of the services. |
| |Authenticity and reliability of information provided |
| |Confidentiality of personal information |
| |Non-repudiation (e.g. for all notifications) |
Business metrics
The following business metrics are types/methods of measurement used to quantify the performance of the business services (see Business services chapter) in terms of achieving the objectives proposed and described above in this document. This list is by no means exhaustive and the contractor is welcome to complement the existing business metrics with new proposals.
|Business Indicator |Definition |
|Number of visits |Total number of visits to the portal (with advanced data |
| |segmentation (breakdown) and details: origin, geographical split, |
| |language, browsers, time of visit, pages visited, unique visitors &|
| |new visitors for a given period) |
|Number of direct accesses to publications |Total number of publications, in any of the available formats (EU |
| |law or general publications), accessed from web or a mobile device |
| |(human access). This should include segmentation by format, type, |
| |language, and author (core metadata). |
|Number of publications accessed per visit (average) |Number of publications accessed per visit by user. |
|Time to directly access a publication for portal visitors (average)|Average time spent by a (human) user to directly access a |
| |publication, in any of the available formats (EU law or general |
| |publications) during its visit on the portal, accessed from web or a|
| |mobile device (human access) |
|Number of visits from mobile devices |Total number of visits to the portal from a mobile devices |
|Number of applicative accesses to publications (reused content or |Total number of publications, in any of the available formats (EU |
|external references) |law or general publications), accessed from external |
| |applications/services/web sites/widgets (machine access). (data |
| |segmentation by access type) |
|Number of subscribed email alerts (on content update) |Total number of email notifications subscribed for search results |
| |updates or browse by subject results update. |
|System availability |Percentage of total time of service in one year. |
|Number of registered users |Total number of registered users and percentage of visitors |
| |(conversion rate) |
|Number of connected users (logged-in) |Total number of connected users (users who logged-in to the system |
| |in the given period) |
|No of support inquiries |Total number of inquiries regarding content or functionality (email,|
| |HelpDeks, etc.). |
|No of commented publications |Number of publications receiving at least one user comment |
|Number of self-created publications (phase II) |Number of publications created by the users using the service |
| |“creates your own book”. |
|Number of print-on-demand inquiries |Number of inquiries for print-on-demand publications. |
|Searched terms |List of search expressions |
|Time to perform a simple search (average) |Time elapsed from the moment when a user submits his search query to|
| |the moment when the results are displayed on the screen. (this must |
| |take into consideration time required by the system to display the |
| |related pages) |
|Time to perform an advanced search (average) |Time elapsed from the moment when a user submits his search query to|
| |the moment when the results are displayed on the screen. (this must |
| |take into consideration time required by the system to display the |
| |related pages) |
|Number of simple search queries launched (total) |Number of simple search queries launched by the users |
|Number of advanced search queries launched (total) |Number of simple search queries launched by the users |
|Number of search queries with no results |Number of search queries with zero results returned to the user. |
|Number of search queries with no click through (total) |Number of search queries which provided results but the user did not|
| |click on any of the results to check for details. |
|Number of browse by subject queries launched (total, multiple |Number of times the Browse by subject page is displayed for |
|numbers) |subjects, subject matters and terms filtering. |
|Time to refine the list of publications in browse by subject |Time elapsed from the moment when a user choses a filter (subjects, |
| |subject matters and terms) to the moment when the list of |
| |publications results is displayed on the screen according to the |
| |filter. (this must take into consideration time required by the |
| |system to display the related lists as subject matters are dependent|
| |on the chosen subject and the terms are dependent on the subject |
| |matter) |
|Number of web-services available (total) |Total number of available web services through |
| |(independent of the authentication method) |
|Number of accesses to available web-services (total) |Number of accesses to available web-services. |
|Number of RSS calls (total) |Number of RSS called by users (manually, from or from |
| |an external application) |
|Number of application services managed by reused in |Number of application services managed by reused in |
|other systems (total) |other systems |
|Number of search engines using our index (federated search) |How many external search engines use directly our own index. |
|Number of downloaded RDF files (total) |Number of downloaded RDF files (total) |
|Number of SPARQL queries launched via the graphical interface |Number of SPARQL queries launched via the graphical interface. |
|(total) | |
|Number of SPARQL queries launched via web-services (total) |Number of SPARQL queries launched via provided web-services. |
|Time to perform a SPARQL query (average) |Time elapsed from the moment a user submits his SPARQL query and the|
| |moment the results are displayed on the screen. (this must take into|
| |consideration time required by the system to display the related |
| |pages including the probable XSLT transformation) |
|Number of portal pages (total) |Number of pages generated in the web content management. (to be |
| |combined with the usage statistics) |
|Sticky pages and bouncing pages |Pages where users spend a considerable amount of time and pages from|
| |where users bounce off (and percentages) |
|Non bouncing visitors versus bouncing visitors |User who stayed on the site until they directly accessed a |
| |publication versus users who quit the site before accessing a |
| |publication. |
|Number of user errors and timeouts |Number of times user errors or timeouts were handled (user displayed|
| |the error message, including for login or single sign-on reasons) |
It must be possible to present all these metrics on various time scales: daily, weekly, monthly, yearly as well as by relative percentage increase/decrease in the average of a period compared to the previous period. These business metrics include some of the common indicators (a minimum set of indicators applied to all web portals in the Publications Office) defined by the Publications Office. For details please check the table of common indicators for Publications Office site in sub-chapter Web-analytics, Statistics and reporting – Webtrends system
Business services
A service is composing and orchestrating the appropriate level of resources, skills and experience in order to provide customers and consumers with specific benefits or value. The figure below presents the mission of the Publication Office strictly related to the online dissemination services.
[pic]
Figure 2 - Publications Office online dissemination services
|Domain of services |Description |
|General Access Services |User services providing citizens and professionals with an |
| |efficient, secure and easy-to-use suite of online services for : |
| |Access to EU law and publications on European Union which are |
| |reliable, accurate and authentic. |
| |Re-use or enhance EU law and publications in order to create rich or|
| |value added business services. |
|Specialized Access Services |User services providing citizens and professionals with an |
| |efficient, secure and advanced access and re-usability features in |
| |regards to EU Law and publications. These services provide added |
| |business value for specific sectorial or professional needs. |
|Support and Management Services |Common services and utilities supporting the General Access Services|
| |or the Specialized Access Services or being used by the users. |
[pic]
Figure 3 – OP Online Dissemination Services - General Access Services (to be provided by Portal-2012)
|Domain of services |Description |
|Access Service |Provide efficient, secure and easy-to-use suite of online services |
| |for direct access to EU law and publications on European Union |
|Reuse Service |Provide reliable, accurate and authentic information for reuse, |
| |enhance and rich services creation. |
|Search |User is able to search in all EU laws or publications stored in |
| |CELLAR (full text + metadata) |
|Display or Download |User is able to display or download a selected EU law or publication|
| |stored in CELLAR. |
|Browse by subject |User is able to navigate and filter/drill down by subject matter all|
| |EU law and publications stored in CELLAR. |
|Wide accessibility |Portal respects high accessibility standards. Portal is optimized |
| |for both classic web and mobile devices access. |
|Order Publications |The user is able to order a printed copy of any kind of publication:|
| |an existing publication on stock or out of stock (print on demand) |
| |or a self-created publication. |
|Notifications |A service that supports registering user alerts on updates of |
| |specific parts of the content stored in CELLAR. User can choose to |
| |be notified on specific search results updates or on content updates|
| |(by subject). |
|Provide Linked Open Data |Direct access to publications RDF data stored in CELLAR. Advanced |
| |users or automated applications/services are able to query CELLAR |
| |data using SPARQL. External Search engines are capable of better |
| |indexing the root of the information on a publication no matter how |
| |many formats and languages are available. |
|Provide Integration Services |Ability to pull in content or services from other application or to |
| |let other applications plug in easily and reuse existing content and|
| |services. |
|Personalization/ Customization |Personalization provides portal users with rapid access to relevant |
| |content and services. Users could decide what they want to view |
| |(explicit personalization) or the system personalizes content based |
| |on rules or on users’ clickstream analysis (implicit |
| |personalization). |
|Create your own book |Enables readers to create their own customized publication (e.g. |
| |PDFs), based on existing content or parts of publications. (Fragment|
| |publishing) – the implementation of this service is out of the scope|
| |of direct services provided in this call for tender. |
|Print on demand |The user is able to order a printed copy of a selected EU |
| |law/publication – the implementation of this service is out of the |
| |scope of direct services provided in this call for tender. |
[pic]
Figure 4 – OP Online Dissemination Services – Support and Management Services (detailed those to be provided by Portal-2012) – provide support services for General Access Services and Specialized Access Services
|Domain of services |Description |
|Authentication |This service centralizes user authentication and/or identification |
| |upon request by a client application. Authentication is accepting |
| |proof of identity given by a credible person which has evidence on |
| |the said identity or on the originator and the object under |
| |assessment as his artifact respectively |
|Single Sign On |A service which allows the user to be identified and access multiple|
| |applications (e.g. PORTAL-2012, EURLEX-2012, etc.) while providing |
| |their credentials only once (e.g. userid and password) |
|User Profile Management |The system can store and manage user profile details and |
| |preferences. |
Business processes
A business process is a collection of structured activities or tasks that produce or support a specific service. Each business service described in the previous section of this document is supported by one or more specific business processes. This section provides a detailed presentation of each business process with its inputs, outputs, supporting IT Applications and interactions with other processes. Schemas of modeled business processes can be found in A3 format in Annex II – Detailed schemas of business processes used by . IT Application and systems supporting activities in the business processes models below are described further in System requirements chapter, Architecture section (a brief description and a schema of its capabilities and interfaces to other IT applications and/or Systems).
All business processes presented below are indicative and by no means exhaustive. They are in a continuous process of evolution and adaptation.
BP1 – Search
[pic]
Overview of BP1- Search process
| | | | |
|Start event(s) |Portal Home page displayed, Portal page displayed |
|End event(s) |Portal page displayed, User Session Ended, Error or time out |
|IT systems |PORTAL-2012, SEARCH SERVICE, CELLAR-2012, PO-USER-PROFILING-SERVICE |
|Input |Search terms, Sort Order: Pertinence, Publication Date, Author Popularity (no of downloads), Alphabetically |
|Output |Electronic document, List of results (XML), List of results (HTML), Facets (XML), RSS feed |
|Superior processes |directly supporting Portal 2012 Search Service |
|Assigned processes |Portal 2012 Notifications, Portal-2012 DISPLAY or DOWNLOAD, Portal-2012 Error handling, Portal-2012 Personalization |
Details
|Activity |Entity |Input |Output |IT System supporting activity |
|Browse results pages |Citizen |Search results page displayed | |PORTAL-2012, SEARCH SERVICE |
|Browse to advanced Search |Citizen | |Advanced Search page displayed |PORTAL-2012 |
|Change sort order |Citizen |Search query including new sort order: |List of results (XML) |PORTAL-2012, SEARCH SERVICE |
| | |Pertinence or Publication Date or Author or | | |
| | |Popularity (no of downloads) or | | |
| | |Alphabetically | | |
|Display publication details page (detailed |Citizen |Unique publication identifier (URI) |Electronic document, publication’s core metadata (XML) + |PORTAL-2012, CELLAR-2012, |
|in BP2) | | |publications available formats and language + display |PO-USER-PROFILING-SERVICE |
| | | |considering eventual user preferences (if registered and | |
| | | |identified) | |
|Display RSS feed for search performed |Citizen |List of results |RSS feed |PORTAL-2012, SEARCH SERVICE |
|Display Search Results |System |List of results (XML) |List of results (HTML) + display considering eventual user |PORTAL-2012 |
| | | |preferences (if registered and identified) | |
|Download publication |Citizen |Unique publication identifier (URI) |Electronic document |PORTAL-2012, |
| | | | |CELLAR-2012 |
|Handle Error |System | |Friendly error message |PORTAL-2012 |
|Launch Search |Citizen, System |Search terms |Search query |PORTAL-2012 |
|Refine Search Results (facets) |Citizen |Search query |Facets (XML), List of results (XML) |PORTAL-2012, SEARCH SERVICE |
|Returns Search Results | |Search query |Facets (XML), List of results (XML) |SEARCH SERVICE |
|Select advanced search options |Citizen | |Search query |PORTAL-2012 |
|Set email notification for selected domains |Citizen | |Search query |PORTAL-2012, SEARCH SERVICE |
|Type text to search |Citizen | |Search terms |PORTAL-2012 |
Entities
|Name |Description |
|Citizen |Citizens, general public |
|System |On or more involved IT Systems to support the action(s). |
Data
|Name |Description |
|Sort Order: Pertinence or Publication Date or Author or Popularity (no of downloads) or Alphabetically | |
|Electronic document | |
|Facets (XML) | |
|List of results (XML) | |
|Search terms | |
|Unique publication identifier (URI) |Unique resource identifier |
BP2 –Display or Download
[pic]
Detailed from activity: “Display publication details page” (in BP4 – Wide accessibility)
Overview of BP2- Display and download
| | | | |
|Start event(s) |URI requested (HTTP/HTTPS) |
|End event(s) |Publication downloaded, Publications details page displayed, Portal page displayed, User Session Ended, Error or time out |
|IT systems |PORTAL-2012, CELLAR-2012, PO-USER-PROFILING-SERVICE |
|Input |Unique publication identifier |
|Output |Electronic document(any format), Publication’s core metadata (XML), Electronic document in RDF, Widget (code) |
|Superior processes |directly supporting Portal 2012 Search Service |
|Assigned processes |Portal-2012 Wide accessibility, Portal-2012 Error handling, Portal-2012 Personalization |
Details
|Activity |Entity |Input |Output |IT System supporting |
| | | | |activity |
|Handle Error |System | |Friendly error message |PORTAL-2012 |
|Request to CELLAR specific format of a document |System |Unique publication identifier|Unique publication identifier (URI) |PORTAL-2012 |
| | |(URI) | | |
|Request to CELLAR core metadata for the publication |System |Unique publication identifier|Unique publication identifier (URI) |PORTAL-2012 |
| | |(URI) | | |
|Request to CELLAR document in any available format |System |Unique publication identifier|Unique publication identifier (URI) |PORTAL-2012 |
| | |(URI) | | |
|Request user ratings for the publication |System |Unique publication identifier|Unique publication identifier (URI) |PORTAL-2012 |
| | |(URI) | | |
|Request user comments for the publication |System |Unique publication identifier|Unique publication identifier (URI) |PORTAL-2012 |
| | |(URI) | | |
|Returns requested file to portal |System |Unique publication identifier|Electronic document in specific available |CELLAR-2012 |
| | |(URI) |format + Electronic document in RDF | |
|Returns core metadata for the publication |System |Unique publication identifier|Publication’s core metadata (XML) |CELLAR-2012 |
| | |(URI) | | |
|Returns user ratings for the publication |System |Unique publication identifier|User comments |PORTAL-2012 module for |
| | |(URI) | |user rating (could be a |
| | | | |separate independent |
| | | | |service) |
|Returns comments ratings for the publication |System |Unique publication identifier|User rating |PORTAL-2012 module for |
| | |(URI) | |user rating (could be a |
| | | | |separate independent |
| | | | |service) |
|HTML Widget for reuse |System, Citizen |Unique publication identifier|Widget (HTML+javascript) |PORTAL-2012 |
| | |(URI), Code | | |
|Download or open file |Citizen |Unique publication identifier|Electronic document(any format), |PORTAL-2012 |
| | |(URI) | | |
|Display publication details page |Citizen |Unique publication identifier|Electronic document(any format), publication’s |PORTAL-2012 |
| | |(URI) |core metadata (XML), Electronic document in RDF,| |
| | | |Page (HTML) + display considering eventual user | |
| | | |preferences (if registered and identified) | |
|Request related applications |System |Unique publication identifier|Unique publication identifier (URI) |PORTAL-2012 |
| | |(URI) | | |
|Returns related applications details |System |Unique publication identifier|Application details (metadata) |PORTAL-2012 |
| | |(URI) | | |
Entities
|Name |Description |
|Citizen |Citizens, general public |
|System |On or more involved IT Systems to support the action(s). |
Data
|Name |Description |
|Unique publication identifier (URI) |Unique resource identifier |
|Electronic document | |
|Publication’s core metadata (XML) | |
|Electronic document (RDF) |Publication details in RDF format |
|HTML Widget |Code that can be reused in any web page in order to display the publications details and directly |
| |access it from there. |
|User comments | |
|User rating | |
|Page (HTML) | |
|Application details (metadata) |Application details: title, description, author, version , platform, download link, etc. |
BP3 - Browse by subject
[pic]
| | | | |
|Overview of BP3- Browse by subject | | | |
|Start event(s) |Portal Browse by subject page requested |
|End event(s) |Portal page displayed, User Session Ended |
|IT systems |CELLAR-2012, PORTAL-2012, PO-USER-PROFILING-SERVICE |
|Output |Electronic document, List of results (HTML), List of results (XML) |
|Superior processes |Portal-2012 BROWSE by subject EU law or publication |
|Assigned processes |Portal 2012 Notifications, Portal-2012 DISPLAY or DOWNLOAD, Portal-2012 Error handling, Portal-2012 Personalization |
Details
|Activity |Organization |Input |Output |IT System supporting activity |
|Change sort order |Citizen |new sort order: Pertinence or Publication Date or Author or |List of results (XML) |PORTAL-2012 |
| | |Popularity (no of downloads) or Alphabetically | | |
|Choose language(s) |Citizen |Language choice |List of results (XML) |PORTAL-2012 |
|Choose subject |Citizen |EUROVOC subject |EUROVOC subject matter list (XML) + List |CELLAR-2012, PORTAL-2012 |
| | | |of results (XML) | |
|Choose subject matter |Citizen |EUROVOC subject + EUROVOC subject matter |EUROVOC term (XML) + List of results (XML)|CELLAR-2012, PORTAL-2012 |
|Choose term |Citizen |EUROVOC subject + EUROVOC subject matter + EUROVOC term |List of results (XML) |CELLAR-2012, PORTAL-2012 |
|Chose publications domain (EU Law, EU |Citizen |Publications Domain |List of results (XML) | |
|Publications, EU Business Opportunities) | | | | |
|Display portal page |System | |See BP4 – Wide accessibility |PORTAL-2012 |
|Display publication details page |Citizen |Unique publication identifier |See BP2 – Display or Download |PORTAL-2012 |
|Display RSS feed for search performed |Citizen |List of results |RSS feed |PORTAL-2012, SEARCH SERVICE |
|Display Search Results |System |List of results (XML) |List of results (HTML) + display |PORTAL-2012, PO-USER-PROFILING-SERVICE |
| | | |considering eventual user preferences (if | |
| | | |registered and identified) | |
|Download publication |Citizen |Unique publication identifier |See BP2 – Display or Download |PORTAL-2012 |
|Get Eurovoc Subjects |System | |EUROVOC subject list (XML) |CELLAR-2012, PORTAL-2012 |
|Returns Search Results |System |SPARQL search query |List of results (XML) |CELLAR-2012 |
|Send SPARQL Query |System | |SPARQL search query |PORTAL-2012 |
|Set email notification for selected |Citizen |Personal email |Alert notification. See BP5 - |CELLAR-2012, PORTAL-2012 |
|domains | | |Notifications | |
Entities
|Name |Description |
|Citizen |Citizens, general public |
|System |On or more involved IT Systems to support the action(s). |
Data
|Name |Description |
|Unique publication identifier | |
|Electronic document | |
|SPARQL search query | |
|List of results (HTML) | |
|List of results (XML) | |
|EUROVOC subject list (XML) | |
|EUROVOC subject matter list (XML) | |
|EUROVOC term (XML) | |
BP4 - Wide accessibility
[pic]
Overview of BP4- Wide accessibility
| | | | |
|Start event(s) |Request for a portal page (HTTP/HTTPS) |
|End event(s) |Portal page displayed |
|IT systems |PORTAL-2012, PO-USER-PROFILING-SERVICE |
|Superior processes |Portal-2012 BROWSE by subject EU law or publication, Portal-2012 DISPLAY or DOWNLOAD, Portal-2012 Wide ACCESSIBILITY Web & Mobile devices |
|Assigned processes |Portal-2012 Wide ACCESSIBILITY Web & Mobile devices |
Details
|Activity |Organization |Input |Output |IT System supporting activity |
|Detect request origin device |System |HTTP header |User device type/category |PORTAL-2012/External System |
|Display requested page mobile device |System |Mobile Device characteristics + |Web page optimized for mobile device |PORTAL-2012, PO-USER-PROFILING-SERVICE |
|optimized | |accessibility requirements |considering eventual user preferences (if | |
| | | |registered and identified) | |
|Display requested page web optimized |System |accessibility requirements |Web page considering eventual user |PORTAL-2012, PO-USER-PROFILING-SERVICE |
| | | |preferences (if registered and identified)| |
|Verify accessibility compliance |System |User device type/category |Mobile Device characteristics + |PORTAL-2012/External System |
| | | |accessibility requirements | |
Entities
|Name |Description |
|Citizen |Citizens, general public |
|System |On or more involved IT Systems to support the action(s). |
IT System supporting activity (other than those described in Architecture section)
|Name |Description |
|External system |Could be a specific external service (e.g. reverse proxy solution for mobile devices). |
BP5 – Order publications
[pic]
Overview of BP5- Order publications
| | | | |
|Start event(s) |Publication details page displayed, Search results displayed |
|End event(s) |Portal page displayed, Publication details page displayed in EUBookshop |
|IT systems |EUBOOKSHOP-2010, PORTAL-2012 |
|Output |User session context (URI of the specific publication, User, browsing language) |
|Process interfaces |Checkout management, Shopping basket management |
|Superior processes |Portal 2012 ORDER Publications, Portal-2012 DISPLAY or DOWNLOAD |
|Assigned processes |Portal 2012 ORDER Publications |
Details for phase I
|Activity |Organization |Input |Output |IT System supporting activity |
|Click on basket |Citizen | |Launch Forward to EUB activity |PORTAL-2012 |
|Forward To EUB |System |User context, Publication Identifier |User ready to checkout the EUB basket |PORTAL-2012, EUBOOKSHOP-2010 |
| | | |containing his selected publication. | |
Details for phase II
|Activity |Organization |Input |Output |IT System supporting activity |
|Click on basket |Citizen | |Launch Forward to EUB activity |PORTAL-2012 |
|Checkout management |System, Citizen |User context, User basket |Order |PORTAL-2012, EUBOOKSHOP-2010 |
|Shopping basket management |System, Citizen |User context |User Basket |PORTAL-2012, EUBOOKSHOP-2010 |
Entities
|Name |Description |
|Citizen |Citizens, general public |
|System |On or more involved IT Systems to support the action(s). |
Data
|Name |Description |
|User Context |URI of the specific publication, User, browsing language, etc. |
|Publication identifier | |
BP6 – Notifications
[pic]
[pic]
[pic]
Overview of BP6- Notifications
| | | | |
|Start event(s) |Notification request on search results, Notification request on browse by subject, Timer job event, Request for notification update |
|End event(s) |Notification registered, Notification sent |
|IT systems |PORTAL-2012 |
|Output |List of updates, confirmations of notification registration |
|Superior processes |Portal 2012 Notifications |
|Assigned processes |Portal-2012 Error handling |
Details for notification registration sub process
|Activity |Organization |Input |Output |IT System supporting activity |
|Identify user (phase II) |System, Citizen |Username, password, SSO ticket |User is identified by the system |PORTAL-2012 |
|Register user details (phase II) |System, Citizen |User profile details |User profile details registered |PORTAL-2012 |
|Register user email (phase II) |System, Citizen |User email |User email registered |PORTAL-2012 |
|Register notification options |System, Citizen |User options |Notification registered (search or SPARQL |PORTAL-2012 |
| | | |query) with specific options for the | |
| | | |identified user email (phase I) or user | |
| | | |profile (phase II) | |
|Register notification task |System |Notification registered with specific |Task registered |PORTAL-2012 |
| | |options for the identified user email | | |
| | |(phase I) or user profile (phase II) | | |
|Send user confirmation |System |Notification registered, user email |Notification registration confirmation |PORTAL-2012 |
| | | |sent (email) | |
Details for notification sending sub process
|Activity |Organization |Input |Output |IT System supporting activity |
|Identify notifications to be sent |System |Timer job |Notification identified (search query |PORTAL-2012 |
| | | |registered), user email | |
|Launch search |System |Registered search query |Search query sent |PORTAL-2012 |
|Returns search results |System | |Facets (XML), List of results (XML) |CELLAR-2012, SEARCH SERVICE |
|Send SPARQL Query |System |Registered SPARQL query |Search query sent |PORTAL-2012 |
|Create output notification |System |List of results (XML) |List of updates (XML) (updates since last |PORTAL-2012 |
| | | |run) | |
|Send user notification |System | |Notification sent (email) |PORTAL-2012 |
Details for notification update sub process
|Activity |Organization |Input |Output |IT System supporting activity |
|Identify user |System, Citizen | | |PORTAL-2012 |
|Identify notification | | | |PORTAL-2012 |
|Verify user email |System, Citizen | | |PORTAL-2012 |
|Register notification options |System, Citizen |User options |Notification registered (search or SPARQL |PORTAL-2012 |
| | | |query) with specific options for the | |
| | | |identified user email (phase I) or user | |
| | | |profile (phase II) | |
|Register notification task |System |Notification registered with specific |Task registered |PORTAL-2012 |
| | |options for the identified user email | | |
| | |(phase I) or user profile (phase II) | | |
|Delete notification |System |Notification registered, user email |Notification deleted, confirmation sent |PORTAL-2012 |
| | | |(email) | |
|Send user confirmation |System |Notification registered, user email |Notification registration confirmation |PORTAL-2012 |
| | | |sent (email) | |
Entities
|Name |Description |
|Citizen |Citizens, general public |
|System |On or more involved IT Systems to support the action(s). |
Data
|Name |Description |
|List of results (XML) | |
|Facets | |
|User profile details | |
|User email | |
|Notification |Specific options for the identified user email or user profile (phase II) |
BP7 – Semantic Search
[pic]
Overview of BP7- Semantic Search
| | | | |
|Start event(s) |Semantic services page displayed, Semantic Web service call |
|End event(s) |Portal page displayed, User Session Ended, Error or time out, Web Session Ended |
|IT systems |CELLAR-2012, PORTAL-2012, PO-USER-PROFILING-SERVICE |
|Output |Electronic document(any format), List of results (XML), List of results (HTML), Facets (XML), RSS feed (XML), Electronic document in RDF, HTML Widget |
|Superior processes |Directly supporting PORTAL-2012 – Provide Open Linked Data |
|Assigned processes |Portal-2012 DISPLAY or DOWNLOAD, Portal-2012 Error handling, Portal-2012 Personalization |
Details
|Activity |Organization |Input |Output |IT System supporting activity |
|Type text to search |Citizen | |Search terms |PORTAL-2012 |
|Launch Search |Citizen, System |Search terms |SPARQL search query |PORTAL-2012 |
|Returns Search Results |System |SPARQL search query |Facets (XML), List of results (XML) |CELLAR-2012 |
|Display Search Results |System |List of results (XML) |List of results (HTML) + display |PORTAL-2012, PO-USER-PROFILING-SERVICE |
| | | |considering eventual user preferences (if | |
| | | |registered and identified) | |
| | | | | |
|HTML Widget for reuse |System, Citizen |Unique publication identifier (URI) |HTML Widget |PORTAL-2012 |
|Download publication |Citizen | |Electronic document(any format) |PORTAL-2012, |
| | | | |CELLAR-2012 |
|Display publication details page (detailed |Citizen |Unique publication identifier (URI) |Electronic document(any format), |PORTAL-2012, CELLAR-2012 |
|in BP2) | | |publication’s core metadata (XML) + | |
| | | |publications available formats and | |
| | | |language | |
|Refine Search Results (facets) |Citizen |SPARQL Search query |Facets (XML), List of results (XML) |PORTAL-2012, CELLAR-2012 |
|Change sort order |Citizen |SPARQL Search query including new sort |List of results (XML) |PORTAL-2012, CELLAR-2012 |
| | |order: Pertinence or Publication Date or | | |
| | |Author or Popularity (no of downloads) or | | |
| | |Alphabetically | | |
|Display RSS feed for search performed |Citizen, System |List of results |RSS feed (XML) |PORTAL-2012, SEARCH SERVICE |
|Results in RDF |Citizen |Unique publication identifier (URI) |Electronic document in RDF |PORTAL-2012, SEARCH SERVICE |
|Handle Error |System | |Friendly error message |PORTAL-2012 |
Entities
|Name |Description |
|Citizen |Citizens, general public |
|System |On or more involved IT Systems to support the action(s). |
Data
|Name |Description |
|Electronic document (RDF) |Publication details in RDF format |
|HTML Widget |Code that can be reused in any web page in order to display the publications details and directly |
| |access it from there. It might contain HTML preformatting and JavaScript actions. |
|Search terms | |
|Facets (XML) | |
|Unique publication identifier (URI), | |
|RSS feed (XML) | |
|List of results (XML) | |
|Electronic document(any format) | |
|Publication’s core metadata (XML) | |
|SPARQL search query | |
|Sort Order: Pertinence or Publication Date or Author or Popularity (no of downloads) or Alphabetically | |
BP8 – Error handling
[pic]
Overview of BP8 – Error handling
| | | | |
|Start event(s) |Error or Time Out |
|End event(s) |Portal page displayed, User Session Ended |
|IT systems |PORTAL-2012 |
|Output |Friendly error message (HTML), Suggested actions or related publications (HTML) |
|Superior processes |Directly supporting PORTAL-2012 – Error Handling |
|Assigned processes | |
Details
|Activity |Organization |Input |Output |IT System supporting activity |
|Display personalized error page |System |Error or time-out |Friendly error message (HTML) |PORTAL-2012 |
|Suggest other actions or related |System | |Suggested actions or related publications |PORTAL-2012 |
|publications | | |(HTML) | |
Entities
|Name |Description |
|Citizen |Citizens, general public |
|System |On or more involved IT Systems to support the action(s). |
Data
|Name |Description |
|Friendly error message (HTML) |Error message presenting the user with an easy to understand error explanation. |
|Suggested actions or related publications (HTML) |List of actions and/or publications related to its previous actions performed on the portal or pertinent in the context of the just |
| |occurred error. |
BP9 – User Profile Management
Graphic model
[pic]
Overview
| | | | |
|Start event(s) |Custom Application access, Web site browsing |
|End event(s) |User profile registration confirmation sent |
|IT systems |DISTRIBUTION APPLICATIONS, PO-CENTRAL-AUTHENTICATION-SYSTEM, PO-USER-PROFILING-SERVICE, PORTAL-2012 |
|Output |Registered User profile, Registered User preferences |
|Superior processes |Directly supporting Profile&Personalization Service in Support & Management Services for OP Online Dissemination Services |
|Assigned processes |Portal-2012 User Identification, Portal-2012 User Profile Management |
Details
|Activity |Organization |Input |Output |IT System supporting activity |
|Identify user |Citizen, Publications Office |Call of the identification |User security ticket, User GUID |PO-CENTRAL-AUTHENTICATION-SYSTEM, PORTAL-2012 |
| | |service | | |
|Display user profiles & preferences data |System |User security ticket, User GUID |User attributes/preferences displayed |DISTRIBUTION APPLICATIONS, |
| | | | |PO-USER-PROFILING-SERVICE |
|Register user profile & preferences |System | |Registered user profile, Registered |PO-USER-PROFILING-SERVICE |
| | | |user preferences | |
|Send user profile registration confirmation |System | |Email confirmation sent to the user |PO-USER-PROFILING-SERVICE |
|User profile & preferences data checks |System |User attributes/preferences |OK, NOK |DISTRIBUTION APPLICATIONS (e.g. PORTAL-2012, |
| | | | |EURLEX-2012, etc.) |
|User profile & preferences data Collection |Citizen, Publications Office | |User attributes/preferences |DISTRIBUTION APPLICATIONS (e.g. PORTAL-2012, |
| | | | |EURLEX-2012, etc.) |
|Validate user profile & preferences data |System |User attributes/preferences |OK, NOK |PO-USER-PROFILING-SERVICE |
Entities
|Name |Description |
|Citizen |Citizens, general public |
|System |On or more involved IT Systems to support the action(s). |
|Publications Office |Staff of the Publications Office responsible for a specific task |
Data
|Name |Description |
|OK, NOK |Acknowledgments messages between systems |
|Registered user profile |List of profile attributes registered in the system for a specific user |
|Registered user preferences |List of user preferences (including customization rules) registered in the system for a specific user |
|User security ticket |User security ticket obtained by the application for the user from the central authentication system. |
|User attributes/preferences |Collection of attributes and/or preferences stored in the User Profile. |
|User GUID |User profile global unique identifier |
BP10 - Personalization
[pic]
Overview
| | | | |
|Start event(s) |Request for a portal page rendering (HTTP/HTTPS) |
|End event(s) |Portal page displayed |
|IT systems |PO-CENTRAL-AUTHENTICATION-SYSTEM, PO-USER-PROFILING-SERVICE, PORTAL-2012 |
|Output |Registered user preferences |
|Superior processes |Directly supporting Personalization/Customization Service , Portal-2012 BROWSE by subject EU law or publication, Portal-2012 DISPLAY or DOWNLOAD, Portal-2012 |
| |Personalization, Portal-2012 User Identification |
|Assigned processes |Portal-2012 Personalization, Portal-2012 User Identification, Portal-2012 Wide ACCESSIBILITY Web & Mobile devices |
Details
Detailed information is available via the hyperlinks.
|Activity |Organization |Input |Output |IT System supporting activity |
|Identify user |Citizen, Publications Office |Call of the identification |User security ticket, User GUID |PO-CENTRAL-AUTHENTICATION-SYSTEM, PORTAL-2012 |
| | |service | | |
|Prepare page considering user preferences |System |Registered user preferences |Page structure and content |PORTAL-2012 |
|Provide user preferences data |System |User security ticket, User GUID |Registered user preferences |PO-USER-PROFILING-SERVICE |
|Render requested page |System |Page structure and content |Page (HTML) |PORTAL-2012 |
|Request user preferences data |System |User security ticket, User GUID |User security ticket, User GUID |PORTAL-2012 |
Entities
|Name |Description |
|Citizen |Citizens, general public |
|System |On or more involved IT Systems to support the action(s). |
|Publications Office |Staff of the Publications Office responsible for a specific task |
Data
|Name |Description |
|Registered user preferences |List of user preferences (including customization rules) registered in the system for a specific user |
|User security ticket |User security ticket obtained by the application for the user from the central authentication system. |
|User attributes/preferences |Collection of attributes and/or preferences stored in the User Profile. |
|User GUID |User profile global unique identifier |
BP11 – User identification
[pic]
Overview
| | | | |
|Start event(s) |Secure web page accessed, User requests login |
|End event(s) |User identified, User not identified/rejected |
|IT systems |PO-CENTRAL-AUTHENTICATION-SYSTEM, PO-USER-PROFILING-SERVICE, PORTAL-2012 |
|Output |Registered user profile |
|Superior processes |Portal-2012 Notifications, Portal-2012 Personalization, Portal-2012 User Profile Management |
|Assigned processes |Portal-2012 Personalization, Portal-2012 User Authentication |
Details
Detailed information is available via the hyperlinks.
|Activity |Organization |Input |Output |IT System supporting activity |
|Authenticate User |Citizen, Publications Office |User identity username or user |User security ticket |PO-CENTRAL-AUTHENTICATION-SYSTEM, PORTAL-2012 |
| | |identity email, password | | |
|Provide user profile data |System |User security ticket, User GUID |Registered user profile |PO-USER-PROFILING-SERVICE |
|Receive security ticket for the user |System | |User security ticket |PORTAL-2012 |
|Request user profile data |System |User security ticket, User GUID |User security ticket, User GUID |PORTAL-2012 |
|Retrieve user profile |System |Registered user profile |Registered user profile |PORTAL-2012 |
|Verification if user is authenticated (Does |System |User security ticket |OK/NOK |PO-CENTRAL-AUTHENTICATION-SYSTEM, PORTAL-2012 |
|application has a valid user security ticket?) | | | | |
Entities
|Name |Description |
|Citizen |Citizens, general public |
|System |On or more involved IT Systems to support the action(s). |
|Publications Office |Staff of the Publications Office responsible for a specific task |
Data
|Name |Description |
|Registered user profile |List of profile attributes registered in the system for a specific user |
|User security ticket |User security ticket obtained by the application for the user from the central authentication system. |
|User attributes/preferences |Collection of attributes and/or preferences stored in the User Profile. |
|OK, NOK |Acknowledgments messages between systems |
BP12 – User authentication
[pic]
Overview
| | | | |
|Start event(s) |User authentication call from a specific application |
|End event(s) |User authenticated, User not identified/rejected |
|IT systems |PORTAL-2012, PO-CENTRAL-AUTHENTICATION-SYSTEM, IDENTITY PROVIDER 3rd PARTY |
|Output |User security ticket |
|Superior processes |Portal-2012 User Identification |
|Assigned processes | |
Details
Detailed information is available via the hyperlinks.
|Activity |Organization |Input |Output |IT System supporting activity |
|User enters credentials and submits form |Citizen, Publications Office |User identity username or user |User identity username or user identity|PO-CENTRAL-AUTHENTICATION-SYSTEM, PORTAL-2012 |
| | |identity email, password |email, password | |
|Check for errors |System |User identity username or user |OK/NOK |PO-CENTRAL-AUTHENTICATION-SYSTEM |
| | |identity email, password | | |
|Security ticket for the user is sent to the calling |System | |User security ticket |PO-CENTRAL-AUTHENTICATION-SYSTEM |
|application | | | | |
|User redirected on the login page |System | |Login page displayed |PO-CENTRAL-AUTHENTICATION-SYSTEM, PORTAL-2012 |
|Validates user credentials | |User identity username or user |User security ticket |IDENTITY PROVIDER 3rd PARTY, |
| | |identity email, password | |PO-CENTRAL-AUTHENTICATION-SYSTEM |
Entities
|Name |Description |
|Citizen |Citizens, general public |
|System |On or more involved IT Systems to support the action(s). |
Data
|Name |Description |
|User identity username or user identity email, |Credentials provided by the user in the login scenario. |
|password | |
|User security ticket |User security ticket obtained by the application for the user from the central authentication system. |
|OK, NOK |Acknowledgments messages between systems |
BP13 – Application Store management
An application is considered in this context to be any computer, web or mobile device application bringing an added value to the user by treating a particular EU law or publication or a set of EU Law or publications stored in CELLAR. These applications are to be presented to the user on the related EU law or publication detail page as well as in an application catalog directly accessible from the main menu.
This service brings added value and increased visibility of our publications for the EU citizens as well as for our authors. It will improve at the same time our own portal and specifically the related EU laws or publications findability as particularly the mobile applications referenced in our application store will have to be available for download in big application stores (e.g. Apple Store, Android Market, Windows Phone store, etc.). Indexing of our portal should benefit from cross linking reference and the Contractor shall put all effort in optimizing and facilitating this indexing.
The Publications Office could later register a corporate account with major application Stores (e.g. Apple Store, Android Market, Windows Phone store) and thus be able to sub-delegate rights to service providers (when building applications for us) to publish an application on our behalf in the respective app store. The Publications Office will be positioned and recognized as a digital application publisher for the other EU Institutions and citizens.
An application for related EU law or publication could be identified by the following details. These details could be mapped as metadata:
o Name of the Application,
o Description of the Application,
o Author of the Application
o Date of publication (availability)
o Platforms on which the Application runs (e.g Web based, iOS, Android, Windows, Mac, Windows phone, etc.)
o Link(s) for download of the application
o Linked EU laws or publications (for which is built)
o Identifier: DOI could be assigned for each Application like for any digital publication (with multiple values if there are different versions of the application e.g. mobile in App Store, Android Store or Windows phone store
Storage of application details: An application details (metadata notice) will be stored and managed in CELLAR like any other general publication.
Management of applications: Application details (metadata notice) will be managed (produced and updated) by an internal PO team as it is the case for the general publications.
User perspective
Latest big survey targeting users of all our major public websites of the Publications Office was conducted recently. Based on this survey and on our web sites usage statistics analysis, generally, it can be concluded with regard to the users of the Publications Office public websites that:
• They have a wide range of backgrounds.
• They are mostly interested in law and publications.
• They actually use more then one of the Office websites to look for content. (EUR-Lex, EU Bookshop, TED, etc.)
• They are recurrent users: they use the Office websites mostly daily or once a week (over half of survey respondents)
• They tend to overwhelmingly use simple search and browsing
• They want improved search and browsing functions, as well as a better organization and presentation of the content. The new Portal should allow in their view for preferences set-up capabilities.
User profiles and audiences
The actual users of the main Publications Office websites (EUR-Lex, EU Bookshop, TED, CORDIS, Prelex, NLex, EUROVOC, EU Whoiswho) could be summarized as follows:
• They are very divers concerning their background
• They are mostly interested in law and publications
• They use more then one of the Publications Office websites
• There is a big number of recurrent users: over 50% use the Publications Office websites on a regular basis - mostly daily or once a week
• They are especially trying to use simple search and browsing in order to find the needed publications.
• They want improved search and browsing functions, as well as a better organization and presentation of the content. The new Portal should allow in their view for preferences set-up capabilities.
Our users are predominantly interested in Law (73%) and publications (44%) followed by European business opportunities (25%) content.
Most of our target users fall into one of these user categories (audiences):
• Citizen
• Economic operator
• Academic
• National authorities
• EU institutions staff
• Information multipliers (relay)
• Administrative users
We estimate that the great majority of these users will access all the content stored in the CELLAR without being registered or identified. However frequent users must able to benefit of advanced content and functionality personalization and the system must be able to understand and record their preferences for later easy reuse. Personalization is the use of relevant and available content aligned with user’s requirements. Personalization is based on the information we known about the user and is contained in a user profile. This information could mostly be used in order to avoid entering the same type of information every time the user accesses the website. To do so, users will need to be registered and identified by the system.
Therefore we distinguish two types of users for the :
• Unregistered users : they may access and reuse all content and features, without being identified by the system
• Registered users: they access all unrestricted content and features and benefit from advanced content and functionality personalization offered by the system. These users will have to be registered and authenticated in order to access this personalization service or be able to update their preferences.
Front Office users can be unregistered or registered users while Back Office (managing system administration tools and services) users must be registered users. Front Office users are consuming published content (readers) while Back Office users have mainly editorial and system administration roles in the system. The following roles can at this moment be foreseen (non exhaustive list):
• Readers: Content consumer; it is allowed to give feedback or rate content.
• System administrator : Management of the system’s services and features
• User and identity administration: Management of user profiles
• Search administration : Management and configuration of search services and features
• Search management: Management of search quality issues
• Editor : Creates/Updates content
• Publisher : Publishes/Validates content
• Translator : Translates created content (attention to the use and integration of ATTO)
• Designer: Management of page layouts, templates and various graphical elements
The registered user profile is composed of relevant information which describes the characteristics of an individual user as well as its preferences as described in the figure below (Figure 5 - OP Common User profile & preferences). When a user registers through the portal, it does not only register within the portal but it registers within the Publications Office thus it will be recognized by all our public facing applications.
should propose a system called “PO-PROFILING SERVICE” for registered users, manage their profile and preferences. The proposed architecture of this service is presented in the chapter Architecture.
[pic]
Figure 5 - OP Common User profile & preferences
In the conceptual data model above:
• A user profile has a list of attributes by default (check above). They are not compulsory (to be input) except the User GUID, User email or User identifier (one of them).
• The default list of attributes can be extended with specific attributes for each application.
• Some attributes such as preferred language or Country are coming from the Publications Office authority tables (see subchapter Metadata register - Authority tables)
• A registered user can have one or more addresses (imagine he inputs his address, orders for delivery to a different address and billing to another one).
• User roles are out of the scope of this model. User roles and corresponding authorization are to be managed at the application level.
• A registered user can be authenticated as a physical person or for a specific role. Authentication is done by a separate service (“PO-AUTHENTICATION-SYSTEM” or ECAS). Nevertheless a certain number of attributes need to be synchronized.
• A user has a list of preferences (attributes or lists e.g. orders or saved queries)
• The default list of attributes and preferences can be extended with specific attributes for each application.
• The user profile data and preferences are managed under strict compliance to EU Commission data protection rules
User features
This section of the document presents the features that the should display to the final user (both anonymous and registered). By combining these features must build and maintain the horizontal business services for the portal users as described in the previous chapter (see chapter Business services).
[pic]
Figure 6 - Common shared features and functionalities to be supported by
Features classified as "specialized by domain" are for the moment out of the scope of and they must typically be supported by specialized Publications Office sites (EUR-Lex, EU Bookshop, etc.):
[pic]
Figure 7 - Specialized features and functionalities (to be supported by specialized websites/services)
Browsing & Navigation
Navigation
The navigation must support display of multi-level menus generated automatically from the page/site hierarchy defined through the web content management system. The menus must be automatically updated when pages are added, updated and removed and they should offer additional configuration options (graphical display, hide, manual intervention, etc.). A specific authorized user should be able to decide at which level the menu should start and how many sub-menu levels to include, or build the menu bottom-up over any number of menu levels for the currently viewed web page. A specific authorized user should be able to select the formatting and style of the menu so that it can match the design of the menu with the design of the entire website.
The web site main navigation should be persistent and consistent on all web pages. The mobile site navigation should respect state of the art mobile usability best practices.
Each and every page of the portal shall display (at least) a navigation item allowing the user to:
• Reach the homepage directly.
• Reach the mobile version of the site and vice-versa.
• Log-in/out
• Register with the Publications Office.
• Display his/her own profile data and preferences (My Portal)
• Reach any specialized site as on the homepage.
• Change the browsing language.
Breadcrumb
Any page of the portal should display a bread crumb trail for the currently viewed web page's position in the website structure defined through the web content management system. The bread crumb trails can be formatted as required and links are automatically included to each page in the bread crumb trail.
The root of the bread crumb will be Europa portal followed by the homepage of the .
Header
The header should identify the portal across each web page and give direct access to common functionalities such as:
• Home page,
• User profile data and preferences
• MyPortal + Log-in/out
• Registration with Publications Office
• Language selection (Users can easily change the browsing language on any website page)
• FAQ
• Contact page
• Help page
• Other public web sites of the Publications Office
• Europa portal ()
The header must give direct access to the search feature. Search box must be present on the right side of the header on all pages (except the home page) allowing the user to perform a search in one click. A link to the advanced search feature takes the user to the advanced search page where it can choose various search options.
The header should enforce the corporate image of the Publications Office across all pages and websites.
Footer
The footer should present specific tasks and information across each web page and give direct access to common functionalities such as:
• Tools and manuals (Interinstitutional style guide, Thesaurus EUROVOC)
• Help on user tasks such as search, sharing, etc.
• Legal information (legal notice, disclaimer, copyright, personal data protection, etc.)
Homepage
On the home page, the user should have a good overview of the website content and functionalities.
The home page should give user one click access to the Search service and provide direct access to browse by subject or application store services.
The home page must help the user to efficiently accomplish the top tasks which are easy access or reuse of any EU law or publications. The home page should be kept clean of any links and content which could distract the user from the top tasks.
A mock-up of the home page is presented in the following sub-chapter (Figure 9 - Mockup of the home page)
Search
Search feature is by far the most important one to be offered for user in the scope of this project. User must be able to easy and intuitively search in all EU laws or publications stored in CELLAR (full text + metadata).
Any portal page must ensure that the user is able to perform a search at any time with only one click. The search box and button must be directly available on the home page and on the right side of the header on all other pages of the portal.
The search scope includes all content of CELLAR namely EU Law, EU general publications and EU business opportunities in all existing languages. Nevertheless, one publication will be displayed only once in the search results list (and count as one result), preferably the one in the browsing language (otherwise the falling language order settings must be considered). The search must be performed by default on the entire content of CELLAR. Search index used by the search service must include all core metadata and full text available for each of these publications.
On the home page only, all search sub-scopes (EU Law, EU general publications and EU business opportunities) are checked by default. The user can nevertheless choose to restrict the search scope only to one or more specific categories of content. The user can do this by checking or unchecking the domains listed on the home page under the search box: EU Law, EU general publications or EU business opportunities.
User must be able to perform a search by typing any text expression in the search box and validate by clicking a "search" button or typing “Enter”. The search system, using the indexed content from CELLAR, will retrieve for the user:
• A list of results with the relevant content found. For each result there should be the title of the publication, the author(s), the EUROVOC subjects for the publication, the publication date, the index context description for the publication and the links to available formats for the given publication.
• Facets helping the user to refine the results list with a number of results for each facet.
• Options for sorting the list of results
• Information on the performed search: number of results returned, time spent of search
• If any, misspellings or suggested similarities with respect to the searched expression: “did you mean” feature.
Search box (on both web and mobile version) shall have an autocomplete (or autosuggest/incremental) configurable feature. Autocomplete involves predicting a word or phrase that the user wants to type in without the user actually typing it in completely.
The search box should limit search expression to a maximum of 255 characters input.
Users shall be protected by the system against any misuse of the search feature. All known security risks related to search box scenarios should be mitigated by the system. (See Security sub-chapter)
A mock-up of the home page containing the search box is presented in the following sub-chapter Page mock-ups (Figure 9 - Mockup of the home page)
Once the searched performed and the results list displayed, the user must be able to:
• Sort results on: Pertinence, Publication Date , Author, Popularity (no of downloads/rating), Alphabetically
• Re-launch the search on the “did you mean” suggested corrections - "Did you mean: (more common spelling)" will be displayed at the top of your search results page in case misspellings or similarities are detected against common spellings of each word in the expression.
• Refine the results on proposed facets. Once refined, the chosen facet will be displayed on top of the search results. Users can choose to deselect it Facets will be regrouped by :
o Domain (EU Law, EU Publications, EU tenders)
o Subject (all subjects come from EUROVOC. Check EUROVOC sub-chapter for details)
o Document type (document content types of each domain)
o Author (corporate authors. Check corporate authors authority table)
o Publication date (adjustable time line filter)
o Micro search: find text expression inside search results
• Save the search query in his profile preferences (if registered and logged-in)
• Create an RSS feed on this query
• Create an alert on this search results update (by mail)
• Save the permanent link to a specific publication from the results list (and the reusability widget – see the permanent link feature for details)
• Access the publications details page (clicking on the publication title displayed)
• Access a specific format of a specific publication in the results list
• Browse search results displayed in pages (no of results per page to be listed as a preference in the user profile – if registered and logged-in). The paging control should be present at the end of the search results list to allow the user launches the search immediately without scrolling the page upwards.
• Optional service (a separate quotation is needed from the contractor for this implementation) Direct preview of the publication details: On the search results list, if the mouse is on top of a specific result (title, context or other well defined region of the result), the mouse-over effect could display a superior layer of specific information (e.g. the full indexed context which contains the searched keywords + icon of the publication if any available). In case of touch-screen devices, long touch is to be detected instead of mouse-over event.
A mock-up of the search results page is presented in the following sub-chapter Page mock-ups
(Figure 10 - Mockup of the search results page)
The search box should always be displayed together with links leading to the advanced search. The advanced search must enable users to perform a multiple criteria search. When navigating from the “simple” search to the advanced search, the expression used in the “simple” search box should be kept visible. The advanced search form should include besides the search box and the search button on top of it the following supplementary criteria:
• Restrictions on search expression interpretation:
o All of these words
o The exact phrase
o Any of these words
• Domains (EU Law, EU Publications, EU business opportunity)
• Languages to search in (by default search is performed in all languages and all content)
• Authors (all corporate authors from the authority table of authors. For details see subchapter Metadata register - Authority tables)
• Publication date:
o Anytime
o Past 24hours
o Past week
o Past month
o Past 6 months
o Past year
The search button should also be displayed at the end of the advanced criteria listing to allow the user launches the search immediately without scrolling the page upwards.
A mock-up of the advanced search results page is presented in the following sub-chapter Page mock-ups (
Figure 11 - Mockup of the advanced search page
)
All search interfaces should be OpenSearch standard compatible.
Important notice: Any adaptation or configuration needed to be performed on the SEARCH SERVICE (see sub-chapter Search layer) is out of the scope of this contract. Nevertheless, all configurations and adaptation of the portal interfaces, eventual requirements for adaptation of the SEARCH SERVICE along with the follow up of the respective implementation and the overall responsibility of delivering this service (search feature and service described above) are fully in the scope of this tender. The Contractor should include all necessary provisions in its proposal.
Browse by subject
With the browse by subject feature, user must be able to access any of the EU laws and publications only using navigation controls and without necessarily typing a text in the interface. The system must propose the user a way of browsing and filtering the entire collection of EU laws and publications stored in the CELLAR. One of the existing options could be to exploit the existence of the core metadata (see
CELLAR System overview ) of the publications stored in CELLAR namely the EUROVOC tags. Users could iteratively filter the entire collection of publications by selecting EUROVOC subjects, their relative subject matters and/or eventually their respective terms.
After each filtering,
• the system will reduce the list of publications displayed in the lower part of the screen and display the user with the following information for each of the publications in the list:
o The title of the publication,
o The author(s),
o The publication date,
o The links of available formats for the given publication.
o The thumbnail (if it has)
• The user will have options for sorting the list of results (Publication Date , Author, Popularity (rating/no of downloads) , Alphabetically)
• The user will see information on the performed filter: number of publications in the list, time spent of search
• The user will be able to save the query (this filtering) in his profile preferences (if registered and logged-in)
• The user will be able to create an RSS feed on this query
• The user will be able to create an alert on this list results update (by mail) based on the filter.
• Save the permanent link to a specific publication from the results list (and the reusability widget – see the permanent link feature for details)
• Access the publications details page (clicking on the publication title displayed)
• Access a specific format of a specific publication in the results list
• Browse results displayed on pages (number of results per page to be listed as a preference in the user profile – if registered and logged-in). The paging control should be present at the end of the results list to allow the user launches the search immediately without scrolling the page upwards. The list of publications will be paginated at any time and the user will be able to display any of the pages.
Additionally, a text input case must be as well foreseen so that the user could furthermore refine the list on a text expression (Micro search: same behavior as in the previous
Search sub-chapter).
A mock-up of the home page containing the search box is presented in the following sub-chapter Page mock-ups (Figure 17 - Mockup Browse by subject)
Content Display
Users must be able to directly access publications content in their available format or core metadata using navigation, search or browse by subject features. Direct access to content is an essential service provided to the user through . One of the most important business metrics of this project is the average time spent by a user to directly access a publication, in any of the available formats during his/her visit on the portal, accessed from web or a mobile device. The portal must ensure at any time that this top task is accomplished in the shortest time possible.
On the publication details page the user must be able to:
• View the core metadata of a publication stored in CELLAR (for details check the core metadata in and for the CELLAR data model (see sub-chapter CELLAR):
o Title
o Author
o Publication Year
o Identifiers (ISBN, ISSN; DOI; Catalogue number(s) ; etc.). (identifiers should be displayed discretely)
• Graphical icon of the physical publication image (if available . e.g. General publications or JO)
• Links to formats available in the browsing language for the publication
• Other available formats for each of the other available languages displayed in a highly usable way (usability proofed)
• Share the publications permanent link on social networks (ShareThis)
• Directly download the RDF file for the publication
• To see the most relevant publications on the same subject from the search results list (answering the same search criteria)
• Print the current publication (from the displayed format)
• Save the permanent link and reusability widget. (see the permanent link feature for details)
• User comments related to this publication
• User rating of this publication/popularity
• Display the content of the publication directly on the screen. On the detail page of a publication the portal should display directly the publication (e.g. the pdf in a page-integrated pdf viewer, or the xHTML view, etc.). A falling order of formats is defined by the CELLAR (e.g. if the publication has an xml version, the text will be automatically displayed, if not the pdf, or the tiff, etc.). A mock-up of the publication details page (a publications example from each of the domains) is presented in the following sub-chapter Page mock-ups ( Page details). Big size publications may take long to load on client side thus a special mechanism must to be put in place to mitigate the loading time (e.g. infinite page principle) so that the user does not need to wait long to load the whole publication, etc.).
Permanent links
If users find an interesting publication that they like, they must be able to bookmark it in one click and go back to it later or share it with somebody else. This link might be different than the URL in the address bar which is often dynamically generated based on search criteria or which may only work for the duration of the web session. The permanent link must be in line with CELLAR’s URI scheme.
The permanent link must be unique, user friendly (readability) and technology independent (no dependence of the portal URLs specific to the implementation technology).
Permanent links should be proposed at least on search results page next to each publication and on the publications detail page.
Along with the Permanent Link, the system should propose the following options:
• Link/direct download of the RDF file of the publication
• Direct link to the respective publication in RSS format
• A JavaScript widget which the user can place on any HTML page of any other web site and allow direct access to the publication. The widget should include information of the core metadata of the selected publication.
A mock-up of the Permanent Link feature is presented in the following sub-chapter Page mock-ups (Figure 16 - Mock-up of Permanent link for a publication)
Web Content Management
Authorized users from the Publications Office or their contractors need to manage the publication of rich content, use publications workflow, and manage different versions of the same content or multilingual content (23 languages) and navigation.
Web Content management including versioning, publishing workflow and presentation control is an essential feature of the Portal which has the main mission to aggregate information and services.
This feature must ensure that it is easy and/or intuitive for authorizes users:
• To create, edit and publish content on a website. It should allow non-technical authors and editors to easily and quickly publish their content while reducing their need for specific training. It should support the publication of all sorts of content such as text, files (pdf, txt, tiff, xml, xhtml, doc, xls, see also the list of formats available in CELLAR), links, images, videos (rich media), ebooks, etc.
• To manage content creation, edit and publication.
• To define publishing processes and allocate specific publishing rights to various individuals.
• To reduce time-to-publish, allowing you to get content published fast.
• To allows for the design of common and consistent information architecture (metadata, classification, navigation, page structures, layout and design).
• To allow for the consistent management of metadata through content template structures (content types).
• To allow for efficient organization of content in the context of increasing content volume.
• To facilitate information security policies (availability, authenticity and confidentiality where needed). It should control who is allowed to publish on the website, and who is allowed to see what content.
• To ensure visual and corporate image consistency through a series of controlled page and site templates. These templates should be based on widget areas allowing for easy organization (drag and drop) of content and navigational elements (like facets and menus). A certain number of widgets should be available (see
Mash-ups / widgets sub-chapter). An authorized user should be able to determine which widgets are available for a specific page or page template. Users having designer role should be able to create new page templates with customized widget areas.
• To quantify the success of the publishing efforts. It is possible to track who is publishing what, how fast content is getting published, whether the publication schedule is being adhered to, whether out-of-date content is being removed fast enough, etc.
• Ensure its own service levels even when many authors and editors, based at multiple locations, publishing substantial quantities of content continuously.
• To allow multilingual editorial content management (see more on “
Multilingual aspect”)
• To allow authorized users (e.g. administrator) to set preferred display formats in the website preferences (falling order for formats coming from CELLAR)
• To allow integration with a Publications Office internal translation repository system (see Translation systems (ATTO) sub-chapter) for specific content such as labels, navigation and other interface messages.
• To allow integration with a Publications Office internal taxonomy management system/repository (obs: EUROVOC publishes its taxonomy to CELLAR repository).
• To provide an essential audit trail of what was published when, where, by whom, and on what authority.
• To reduce the effort associated with recreating an older version of the site for regulatory or legal reasons.
• To allow aggregation and component management: To combine and publish discrete chunks of content that may originate from a variety of sources (CELLAR, Search and Index layer, ATTO, other Publications Office web sites, etc.)
• To allow specific deployment path: To publish to standard Internet platforms (development, stage/testing, production)
• To provide caching and replication: to ensure high performance in public environments characterized by spikes in demand
• To allow browsing in 23 languages with a default language falling mechanism.
• To allow automatic update of the navigation and sitemap (eg. trough widgets)
• To allow for broken links monitoring and reporting
• To allow authorized users for the creation/publication of RSS feeds based on various configured content sources (e.g. CELLAR, Search and Index)
• To publish WAI compliant pages (see Wide accessibility sub chapter).
• To allow in parallel creation/editing/publication and management of content for mobile version of sites.
• To allow connectivity with social media by being able to push selected content to different social media websites (by the authorized users) and/or by pulling content from there and integrating it into the portal (e.g. comments).
• To allow and support micro-applications which provide basic interactivity to a website such as wikis, blogging, and user-driven tagging (folksonomies).
• Ensure compliance with Authoring Tool Accessibility Guidelines (ATAG) 2.0
In the chapter “User profiles and audiences” we identified a series of roles for users. Some of these roles are directly concerned by the web content management feature as follows:
• Editor : Creates/Updates content
• Publisher : Publishes/Validates contents
• Translator : Translates created content
• Designer: Management of page layouts, templates and various graphical elements
These roles should be easily accommodated by the publishing processes of the proposed web content management.
Authoring tools such as those available in OP workstation are welcome to be used for editing purposes and they should be promoted/integrated. See sub-chapter “Authoring tools” for more details.
The current OP Internet site () must be integrated in the About US section (see Sitemap). This task is part of the requirements and in the scope of this tender. Current pages and structure must be reviewed by the Publications office editorial team based on the Contractor’s proposal.
Multi-site, Multi-tenant
the portal must provide citizens and professionals with an extensive, efficient, secure and easy-to-use suite of online services related to access to EU law and publications on European Union. It is intended to become the unified platform for the Publications Office electronic dissemination services. To achieve this objective, the portal must be supported by a solid, flexible, robust, integrated and scalable infrastructure and technology ensuring rapid and constant evolution of its user services as well as high accessibility from most web reading devices, promoting as much as possible out of the box technology features reuse.
In order to simplify management and upgrading of various sites the system must handle the multi-site feature. Multi-site allows one to share a single platform installation (including core code, modules, features, themes, etc.) among several web sites. Each site could have its own defined title, url, management and security rules but all of them will share the multitude of user features presented in this document. A specifically designed user role must be able to create a new site based on a site template or template site definition, delete or modify or relocate an existing site in the multi-site structure. The multi-site capability should provide a way to standardize and share data, features and business rules/practices between different websites while keeping other types of data, custom features unique or business rules to a particular site (e.g. specific widgets). The multisite capability can also selectively give users access to data on different web sites.
The technology used must also support logically partitioned sites so that each tenant has access and manages rights to their own set of tenant-specific site/collection of sites completely independent from other tenants on the platform.
Multilingual aspect
The system must support content editing, display and browsing in all 23 official languages of the European Union, plus for international character sets such as Croatian, Turkish, Japanese and Arabic.
Website visitors must be able to select at any moment their browsing language. When users select the language link all content subsequently displayed will match the selected linguistic version/language.
A registered identified user shall be able to set a preferred version/language for browsing and for search. When a preferred version/language has been set the preferred content version/language will automatically be displayed or downloaded if it is available. Otherwise the default language/version of the website content will be displayed or downloaded. Given that some content (e.g. logo, template or style sheet) is the same for each version the system should allow defining a default/master version, which will then always be displayed.
Publications Office has its own repository for messages and labels translation called ATTO. must consider tight integration with ATTO in order to use it as a referential for navigation labels and user messages in all 23 languages. It could be also used for some parts of the editorial content.
The management of the linguistic versions of the documents (publications)
• Use of UNICODE in order to handle the different character sets of the official documents
• 23 official languages plus possible further languages (Croatian, Turkish, Japanese).
• Display of a default linguistic version if the wanted version of a document doesn’t exist,
• Similar behavior in the site for the different linguistic versions of a document
The multilingualism of navigation:
• Equal rendition of the website whatever the language is (and if the documents exists). This includes the ability to perform searches in each language and access to return linguistic versions in this language. Extended functionalities may be proposed; even in they are not supported equally for all UE languages.
• Equal search results when a user performs a query among the different linguistic versions of the site. )
For non registered/identified users, the system should remember (e.g. in a cookie) what languages the users used previously and to set the same languages for the next visit. This feature must concern all elements of the user interface which can be set as preferences.
Publishing workflow
Publishing workflow (Creation/Editing, Revision and Publishing) is how content gets modified and approved through a set of interdependent tasks that often occur in a specific sequence. The publishing process must consider Publications Office’s staging requirements (development, stage/testing, production) and eventually authoring tools already available (see Authoring tools sub-chapter). The workflow process can hence ensure systemic stability and reliability by allowing authorized users to align content paths with the Publications Office editorial rules.
User feedback
should allow and especially encourage users to give their feedback publications in a form of surveys, comments or ratings/popularity.
The objective of the user feedback would be:
• To offer a valuable tool to the Publications Office for collecting user feedback on the publications vis-à-vis other DGs and European Institutions.
• To address any problems encountered with the publications
• To help users learn how publications are used
• To continuously understand user needs;
User feedback must be directly associated with a specific publication and should be interactive on the detail page of the publication. The user feedback consists mainly of the ability to rate content. This could be an interactive user rating displayed on the details page of the publication. The user should be able to give a rating (1 to 5) to that content or a combination of rating values, each of them interactive (e.g: Usefulness ****, Easy to use *****).
To do this, the user does not have to be logged-in.
The Portal must present to users the possibility of sorting search results by popularity.
This information (e.g. ratings) must not be stored in CELLAR. (e.g. a separate and independent service shall be foreseen).
Social sharing - ShareThis
The Social bookmarking and networking allows users to share web pages and publications (e.g. publications URIs). Contents are shared using socials networks or e-mails. It must be easy for visitors to bookmark and share content to their favorite social destinations. This service (JavaScript widget) is multilingual and it must be integrated on any portal page. This feature is described more in details in the guidelines from the Information Providers Guide (IPG) of the European Commission. These guidelines are regularly updated and available at the following address:
A mock-up of the ShareThis feature is presented in the following sub-chapter ( ShareThis feature)
Displayed on a publications details page, it will allow the user to the share the permanent link of that publication.
Bookmarks
The portal shall allow the bookmarking of any particular publication or page. The bookmarking functionality shall also allow registered and identified users to organize, add, modify and delete saved bookmarks in the MyPortal space.
Annotations
The portal shall allow the adding of contextual personal notes to the content of a publication and save them. The saved notes shall also be accessible within the MyPortal space for a registered and identified user. If the user is accessing a publication page which has one or more annotations, this should be visible (highlighted text, notes displayed in a separate page layer, etc.). The annotation functionality shall also allow users to easily organize (also using user tags), add, modify and delete any saved notes.
Survey / Quiz
The system should allow collecting user opinions using web published user surveys and quizzes. It should be a web site component that enables users to respond to a set of questions specified by the creator of the survey (an authorized registered user). Surveys should support a wide variety of response types from simple Yes/No answers to free-form text basic question branching logic allowing you to dynamically present users with different questions based on their previous responses. Surveys could be created and published on the portal in all 23 official languages.
Survey results must able to be exported as a text, csv or Microsoft Excel file allowing for further analysis.
Profiling - personalization / customization
The goal of personalization is to let users rapidly access relevant content and services. Users could decide what they want to view (explicit personalization) or the system personalizes based on rules or on users’ clickstream analysis (implicit personalization). Personalization is based on the information known about the user and this is contained in a user profile and preferences. Figure 5 - OP Common User profile & preferences in the chapter called “User profiles and audiences” describes the user profile and preferences attributes.
Based on the above mentioned reference model, a user profile has at least the following preferences (should not be limited to):
• Individual homepage
• Preferred browsing language
• Preferred search language
• Preferred notification type (instant/digest)
• Preferred notification format (text/html)
• Highlight text patterns in search results (yes/no)
• Number of search results displayed per page
• Preferred export format (pdf, xps, xls, xml, csv, etc.)
• Saved search queries
• Saved publications links (permanent links)
• Saved RSS queries
• Saved notifications
• Annotations
• Bookmarks
Various related features and services (e.g. search, notifications, etc.) should consider these preferences when displaying pages/results to the final user. User preference value must prevail over default value for any given display option.
A registered and authenticated user should be able to easily customize portal pages view, select, deselect, add or customized predefined composites/portlets/widgets in predefined areas of any page of the portal. The system must propose the user a series of predefined composites/portlets/widgets. A possible list can be found in subchapter
Mash-ups / widgets“.
To increase the popularity of Portal services and to encourage the re-use of CELLAR data, a special "take away" widget will be proposed on the Permanent link screen of a publication (see Figure 16 - Mock-up of Permanent link for a publication) allowing any user to place it on any HTML page of any other web site and allow direct access to the related publication. The widget should include information on the core metadata of the selected publication.
For non registered/identified users, the system should remember (e.g. in a cookie) previous user selections and set the same selection for the next visit (e.g. languages of browsing). This feature must concern all elements of the user interface which can be set as preferences.
Registering in the portal
In order to benefit from the personalization features, a user should register with the Publications Office (see PO-USER-PROFILING-SERVICES sub-chapter) and be identified (see
PO-CENTRAL-AUTHENTICATION-SYSTEM).
When registering a user should be asked the following information:
• E-mail address (Mandatory – Text input) (will serve as user-ID)
• Password (Mandatory – Text input)
• Password - confirmation (Mandatory – Text input)
• Reproduce security reinforced image CAPTCHA (Mandatory – Image / Text input) or similar security control. (A random image containing a deformed code is displayed and the user has to reproduce the code to prove that he/she is not a robot). It must be based on the latest available technology in order to avoid any spam or automatic registration.
• Title (Optional – Text input)
• Organization (Optional – Text input)
• Function (Optional – Text input)
• Address (Optional – Text input) with a specification explaining to the user that his/her address is important if he/she wishes to order printed publications
These elements should be recorded and some of them synchronized by PO-USER-PROFILING-SERVICES and
PO-CENTRAL-AUTHENTICATION-SYSTEM for their respective needs.
Once the user accomplished the registration process through the portal, he should be signed-in by default (and avoid asking him to log again).
User Sign-in
The sign-in option will present the user with two possible tasks:
• Sign-in (description below)
• Forgotten password (An email with password reset will be sent to the user)
• Register (see previous sub-chapter)
In order to be identified, the user will have to provide:
• User E-Mail addresses (Mandatory – Text input).
• Password (Mandatory – Text input).
Two possible generic roles will be available to a user during the sign-in process. The user must be able to choose one of them: private or corporate: private for his own use or corporate when the user is represents his organization (e.g. European staff member who could log-in to perform tasks on behalf of their DG). Various functions/features of the portal could then be available only for corporate users (e.g. web services, SPARQL query interface, system administration services, etc.). The user details and preferences will be, in a first phase, the same no matter which generic role the user chooses.
Once the user is identified by the
PO-CENTRAL-AUTHENTICATION-SYSTEM a security ticket is handled to and the user is recognized by the system. The personalized welcome page should be displayed or the user preferences applied, the log-out button should appear in the header and given access to the personalization features (MyPortal)
Single-Sign On:
If the user:
• asks for identification
• tries to access a specific feature which requires identification
• access the coming from another web site
It might be that he was already identified by the
PO-CENTRAL-AUTHENTICATION-SYSTEM on another Publications Office or European Commission (by ECAS) web site and in this case the portal will not ask the user to identify themselves again but it will use the same security ticket (single sign on feature of
PO-CENTRAL-AUTHENTICATION-SYSTEM )
Sign-In button will be displayed in the header of all portal pages (as long as the user is not singed-in)
MyPortal
In order to improve the users experience all personalization features and attributes will by easily accessible from one place called MyPortal which must be visible on each page of the portal in the header. Only registered and authenticated users have access to MyPortal feature.
My Portal should allow one click access to the user to:
• Access and Manage his preferences (see
Profiling - personalization / customization above)
• Access and manage his saved content (notifications on the portal, links (shortcuts), search queries, RSS, document links, etc.) – he should be able to add or modify his specific content (e.g notifications or links)
• Access to Personal page
• Sign-out
• Modify password
• Personalize the current page.
MyPortal feature should be easily customizable and extensible with:
• Other preferences (attributes or saved content)
• Other links to services and tasks on the portal
The Contractor is required to provide creative and highly usable screens in MyPortal feature.
Personal user page
One page in the portal is particularly foreseen for users selected content. The user alone can define what he wants to see on his page and choose the available widgets to display the desired content. This page could be available to the user through MyPortal feature. It could also be defined as the homepage of the user if he chooses to do so in its preferences.
The user should also be capable of choosing the page template allowing him various widget placements order on the page (widget placed on specific areas of the page). Drag & drop as well as collapse & expand type of methods should be intuitively available to the user on this page.
More details on Mash-ups and widgets can be found in the subchapter “
Mash-ups / widgets”.
Mash-ups / widgets
In order to support high personalization capabilities for our users, must be able to handle widgets (components or “composites” or “gadgets” or “portlets” or “web parts” depending which technology will be used). For simplification in this document we will refer to these modules as widgets.
Mash-up technique provides a framework that allows a web page or the application itself that uses and combines data, presentation or functionality from two or more sources to create new services. The portal platform must make it easy for users to build web pages and websites by assembling widgets onto a portal page. Portal administrators/webmasters should be able to build pages without coding by reusing existing widgets.
A portal authorized user (e.g. administrator) should be able to enable/disable any widget area for certain page templates (search masks, search results, editorial pages, etc.) or separate pages. This user should be able to easily show or hide different widgets (eg. show or hide certain facet containers) and move widgets from one area to another, or sort them within one area via drag & drop interface.
There should also be an easy way to create and publish new widgets (authorized users w.g. webmaster)
End users and administrators must be able to put widgets onto a page and re-arrange them on the page, and customize their behaviors based on global settings that impact all users in the case of administrators as well as personal settings that only impact that one user. A user should be able to easily customize his/her web page view, select, deselect, add or customized predefined composites/portlets/widgets in predefined areas of any page of the portal (as allowed by the administrator through page templates) like in the figure below:
[pic]
Figure 8 - Using widgets
Foreseen widget types are:
• Navigation related (e.g. menus, quick menus, banners)
• Search related
• SPARQL query related
• User's personal space related
• Content related (editorial content, XML, PDF, RSS, etc.)
The system must propose a series of predefined composites/portlets/widgets like:
• Sign-in widget
• Register widget
• Search box (used to perform search + the link to advanced search)
• Search results (displaying search results and properties associated to them)
• Search results paging (displaying the links for navigating pages containing search results; provide option to automatically display the results of a specific search queries)
• Search facets (displaying the facets available for a search results list used to intuitively refine the results list)
• Search summary (displaying “did you mean” keywords)
• Search results statistics (displaying the search statistics such as the number of results shown on the current page, total number of results, time that took to perform the search, etc.)
• Search best bets/high confidence results (displaying special terms and high confidence or predefined results)
• Search bread crumbs (used to display the search criteria and selected facets)
• Search federated results (displaying federated results from configured location)
• Recommended publications (displaying a certain number of publications related to the selected publication subject, subject matter and term)
• SPARQL query editor (providing a graphical interface to intuitively edit a SPARQL query – to be sent to CELLAR)
• SPARQL query results (displaying SPARQL search results (XML) and properties associated to them; provide option to automatically display the results of a specific SPARQL search query; provide option to modify the XSLT used for display of XML formatted results)
• SPARQL query results paging (displaying the links for navigating pages containing SPARQL search results)
• SPARQL query results statistics (displaying the SPARQL query search statistics such as the number of results shown on the current page, total number of results, time to search, etc.)
• Table of contents aggregator (displays navigation hierarchy of the sites or a list of sites/pages of your choice with associated properties; quick launch, etc.)
• RSS viewer (renders RSS feeds inside a web page. E.g. RSS feeds from external sites)
• PDF viewer (renders a PDF page + its own toolbar inside a web page)
• Image viewer (renders a TIFF/JPEG/GIF image + its own toolbar inside a web page)
• XML viewer (used to display XML file from any source(local or web based) and XSL transformation of that xml)
• Page viewer (use to display linked content, such as files, folders or web pages. The linked content is isolated from the other content on the page)
• Image viewer (displays a selected picture/image)
• Image slideshow viewer (dynamically displays a slideshow of pictures selected from a location)
• Content Editor (allows the use of formatted text, images, tables, etc.)
• WSRP consumer (display other widgets/composites/portlets from websites using WSRP 1.1
• Redirection widget (used to redirect to another page)
• Contact details (used to display details about a contact for the page or for the site. Details about the person could come from any LDAP or from the PO-PROFILING-SERVICE)
• Summary links (displays links that can be grouped, styled and organized by dragging and dropping)
• User profile data (displays user profile data and related actions)
• User preferences data (displays user preferences and related actions)
• User registration (allows registration with Publications Office)
• ShareThis (allowing sharing of the page/publication with various social networks)
• ATTO label widget (displays a label or a configurable set of labels in a given language)
• ATTO message widget (displays one or more specific messages in a given language)
Widgets must be able to pass information/context to other widgets, and they can also consume context/information from other components/widgets on the page.
Authorization - access rights
The portal must be able to manage access policies to all and each of the resources, services, features or applications it aggregates and presents. Access policies and user roles should be easily managed by authorized users.
The following roles can at this moment be foreseen (non exhaustive list):
• Readers: Content consumer; it is allowed to give feedback or rate content.
• System administrator : Management of the system’s services and features
• User and identity administration: Management of user profiles
• Search administration : Management and configuration of search services and features
• Search management: Management of search quality issues
• Editor : Creates/Updates content
• Publisher : Publishes/Validates contents
• Translator : Translates created content
• Designer: Management of page layouts, templates and various graphical elements
Two possible generic roles will be available to a user during the sign-in process, the user must be able to choose one of them: private or corporate: private for his own use or corporate when the user is representing his organization (e.g. European staff member who could log-in to perform tasks on behalf of his DG). Various functions/features of the portal could then be available only for corporate users (e.g. web services, SPARQL query interface, system administration services, etc.). The user details and preferences will be the same no matter which generic role the user chooses.
Single Sign On
A Single Sign on service must allows the user to be identified and access multiple applications (e.g. PORTAL-2012, EURLEX-2012, TED, eTendering, etc.) while providing their credentials only once (e.g. userid and password).
Single Sign On must reduce user frustration of multiple log-on events and forgotten passwords. Users only have one password to remember and update, and only one set of password rules to remember. Their initial login provides them with access to all resources, typically for the entire day.
If a user already authenticated in another Publications Office public web site (e.g. PORTAL-2012, EURLEX-2012, TED, eTendering, etc.) or European Commission web site (by ECAS) it shall be recognized automatically when he access the (with the condition of a certain period of time of activity on the web sites ensured by a security policy) and vice-versa.
This service is also supported by the implementation of the common service PO-USER-PROFILING-SERVICE (see PO-USER-PROFILING-SERVICES sub-chapter): when a user registers through a public web site of the Publications Office, it does not only register within the application but it registers within the Publications Office thus it will be recognized by all our applications.
Notifications
Notifications and alerts on updates and content change is one of the most important features our users expect from the Portal. Users must have the possibility to choose to be regularly informed or alerted of new publications or updates matching a specific query. The notification delivery format might be RSS or e-mail (HTML/TEXT).
Unregistered users as well as identified ones must be able to set alerts/notifications on:
• Search results update (updates matching a specific search query)
• Browse by subject results update (updates matching filtering on a specific subject, subject matter and/or term and/or micro search)
• Existing publications (updates on the core metadata, formats available or content itself)
• Updates on editorial content update (pages or specific sections of pages e.g. Procurement in AboutUS section)
When setting an email alert/notification, the user must be able to choose:
• It’s format: HTML or TEXT (this can be also a preferences set by the user in MyPortal in which case this preference will be selected by default for notifications)
• It’s frequency:
o Immediate
o Daily (with hour schedule)
o Weekly (with day schedule and hour schedule)
Each notification sent by the system should contain:
• Title and description of the alert
• Link to where the user can manage this alert/notification (its frequency, query or the filter applied, delete the notification, etc.)
• List of updates with clear distinction of added items, deleted items or modified items and the modifier properties/metadata (e.g. propose code colors, strikethrough fonts for deleted items, etc.). By item we understand publications with their respective core metadata.
If the user is not identified (registered and authenticated) the system may invite him to sign-in (the sign-in form foresee registration if the user is not registered) in order to benefit from further advantages on notifications but the portal should also propose the user to set an alert/notification only by providing his email address. In this case a confirmation from the user must be demanded in order to authorize setting up a notification on this address. (e.g. user could be sent a specific email with a unique link to click and confirm that he accepts the notifications and agrees with the general conditions which have to be clearly specified).
If the user is identified, creating a notification will automatically save it also to his MyPortal. In MyPortal a section should be dedicated to MyNotifications. In this section the user must be able to change delete or modify notifications like for example change the format or the time schedule.
Once a notification was set by the user, the system will send to the user email a confirmation with all the details of the notifications (title and description of the alert, frequency, description of the content targeted and the query or the filter applied) and a specific link to where the user can modify or delete the notification. For registered users, the link will point to MyNotifications section in MyPortal feature. For unregistered users, the link should bring the user on a portal page where he must input the email address (for verification purposes) in order to update any details in a user friendly and intuitive interface.
From a security perspective, the system shall be effective and reliable and it shall ensure the non-repudiation aspect of sent notifications.
Linked Open Data - Use of public data
Resource Description Framework (RDF) is used in CELLAR to store our publications and their data. RDF provides the foundation for publishing and linking these data. Various technologies allow today to embed these data in documents (RDFa, GRDDL) or make it available as RDF files.
However, just as relational databases the Semantic Web, typically represented using RDF as a data format, needs its own, RDF-specific query language and facilities. This is provided by the SPARQL query language and the accompanying protocols. SPARQL makes it possible to send queries and receive results, e.g., through HTTP or SOAP.
In the Semantic Web, vocabularies define the concepts and relationships (also referred to as “terms”) used to describe and represent the various area of concern. Vocabularies are used to classify the terms that can be used in a particular application, characterize possible relationships, and define possible constraints on using those terms. These vocabularies are called ontologies.
must propose interfaces for human users as well as for automated processes to exploit and reuse the linked open data stored in CELLAR. is the only gateway for CELLAR from the Internet (unique point of entry). To achieve this objective, the portal must propose:
• A series of web services mapped on CELLAR API access services (CELLAR dissemination interface see sub-chapter CELLAR)
• These services will allow direct access to one ore more publications stored in the CELLAR (Consumer model) – PORTAL2012 might act as a reverse proxy for CELLAR access
• A graphical interface which allows any user to query the CELLAR content. This graphical interface should:
o Propose a friendly and intuitive way of writing/editing SPARQL queries
o Propose recommended predefined intuitive design blocks equivalent for SPARQL commands and options allowing user to build SPARQL queries without typing (mouse clicks). (e.g. looking for publications, a specific format from a list of formats, with publishing date from a range, containing a specific string, for a specific author to select from a list, etc.)
o Propose to save SPARQL queries in user preferences (for registered identified users)
o Retrieve results from CELLAR once a SPARQL query is submitted.
o Paginate retrieve results
o Retrieve statistics on SPARQL queries (time of query, number of results, etc.)
o Widgets for each of the above mentioned operations. (see
Mash-ups / widgets also sub-chapter for more widget listing). These particular widgets are very important for the current chapter:
▪ SPARQL query results (displaying SPARQL search results (XML) and properties associated to them; provide option to automatically display the results of a specific SPARQL search query; provide option to modify the XSLT used for display of XML formatted results)
▪ XML viewer (used to display XML file from any source(local or web based) and XSL transformation of that xml)
▪ SPARQL query editor (providing a graphical interface to edit a SPARQL query – to be sent to CELLAR)
▪ SPARQL query results paging (displaying the links for navigating pages containing SPARQL search results)
▪ SPARQL query results statistics (displaying the SPARQL query search statistics such as the number of results shown on the current page, total number of results, time that took to perform the search, etc.)
• Direct access to RDF file of a publication on the publication details pages, search results list and permanent link window.
All SPARQL queries to CELLAR must go through the CELLAR SPARQL End-point service. (See sub-chapter CELLAR) for more details.
For more details on RDF please consult W3C recommendations on RDF: .
For more details on CELLAR structure and interfaces and on the Publications Office ontology please check see sub-chapter CELLAR
The Contractor is required to provide creative and highly usable screens in this feature.
Direct access to search index
One of the key objectives of the is to be designed for and reusability meaning that is easily discoverable and indexed by other Internet search engines and it is easy to reuse content in other external applications. It is particularly important for the portal to be indexed by other Internet search engines as easy and as exhaustive as possible but it is equally important to allow other applications or services to directly reuse our index of EU Law and publications without downloading our entire content and re-indexing. This can be achieved efficiently by the mechanism of search federation.
As it represents the single point of entry from Internet, must ensure through its interfaces (and implicitly those exposed by the SEARCH SERVICE) that search federation is possible from other Internet sites and search engines under defined conditions (the Contractor should define the framework, conditions, governance and security rules of access). The portal should ensure optimization and security control of the access to our index (index exposed by the SEARCH SERVICE).
It is vital though that search interfaces are fully compliant with OpenSearch standard.
Remark: indexing the content stored in CELLAR is a high time and resource consuming operation. Indexing the full content of CELLAR might suppose a certain number of performance and completeness challenges. Details should be managed during the contract with the team in charge of CELLAR development and maintenance.
Federated search is an information retrieval technology that allows the simultaneous search of multiple searchable resources. A user makes a single query request which is distributed to the search engines participating in the federation. The federated search then aggregates the results that are received from the search engines for presentation to the user.
Offering direct access to our search index will massively contribute to increase our dissemination capacity and the presence of EU law and publications in public access bibliographic databases, public access Web-based library catalogues (OPACs), web-based search engines like Google and/or open-access, government-operated or corporate data collections.
Important notice: Any adaptation or configuration needed to be performed on the SEARCH SERVICE (see sub-chapter Search layer) is out of the scope of this contract. Nevertheless, all configurations and adaptation of the portal interfaces, eventual requirements for adaptation of the SEARCH SERVICE along with the follow up of the respective implementation and the overall responsibility of delivering this service (to allow and optimize search federation from other web search indexes) are fully in the scope of this tender. The Contractor should include all necessary provisions in its proposal.
Statistics and reporting
must provide the capacity of generating and managing statistics and reports by creating personalized dashboards or using the predefined ones in order to monitor the system and asses business impacts of portal services and features. The current environment and infrastructure of the Publications Office makes it necessary to have monitoring and reporting mainly for business deciders, the editorial team, administration, infrastructure and maintenance. must provide the appropriate tools to measure and report the business metrics defined earlier in this document (see chapter
Business metrics). To do so the portal must integrate the existing web-analytics & reporting and capabilities existing at the Publications Office (see Web-analytics, Statistics and reporting – Webtrends system and/or statistics provided by the CELLAR or SEARCH SERVICE).
should also allow for easy integration of the current Publications Office administrative and infrastructure monitoring systems (see “Other systems”) and present an authorized user (possibly system administrators) with system physical and logical resources usage, performance and availability statistics.
must be able to present all business metrics (see chapter
Business metrics) and system usage statistics on various time scales: daily, weekly, monthly, yearly as well as or by relative percentage increase/decrease in the average of a period compared to the previous period.
The portal shall be able to present all these business metrics to authorized users in an intuitive unified interface fully integrated with the rest of the system. Authorized users (others than the system administrators) must be able to perform in this interface the following actions:
• Visualize predefined dashboards with above defined business metrics
• Export data relative to the above defined business metrics
• Customize/create dashboards intuitively without very specific training or programming/custom coding
• Modify selection and filtering criteria for each of the defined business metrics intuitively without very specific training or programming/custom coding.
• Modify data segmentation
• Emphasize most important data segments (frequently consulted contents/documents/pages) using filtering values.
• Modify data export formats to be used.
The system should not assume that data used for producing statistics and reports are coming only from logs and tracks fed by hosting/operating environment but shall rely especially on user actions and traces.
Error handling
must handle with care all possible errors and timeouts. User must feel that the site is addressing him and following his actions. In case of an error or a timeout, the portal must gently explain him the reasons and absolutely propose him pertinent recommended actions or publications.
No error or timeout should be let untreated and unexplained to the user.
All messages related to errors or timeouts must be displayed in the current browsing language.
Moreover, the following guidelines concerning error handling should be strictly followed:
• Simplify error messages so that users can understand them.
• Make the error messages informative and operational: tell users what they are supposed to do next.
• Tell users where the error is coming from.
• Place error messages next to the error.
• Do not use alerts to report errors.
• Use progress indicators to show how long users have to wait. Prefer progress bars for tasks that take more than 2s. Avoid making people wait for more than 15s.
• If an error occurs, return to the state before the error. Preserve all the values that the user has already entered.
Mobile View
Portal users must be able to use mobile devices in an optimal way in order to browse the portal and complete use of its services (applied to Front Office user features). The portal must have a mobile version of each public page and users must be able to use and complete any portal service described above in this document by just using the mobile version of the site.
Mobile version of the portal has to be referenced on the web site and vice versa: each site page should carry a distinctive link to the mobile version and vice-versa.
Usability guidelines of the mobile version of the site are presented in detail in the Annex I – Mobile Web Usability guidelines and they must be strictly followed. Deliverables of the project will be rejected if best practices mentioned in this annex will not be respected.
Page mock-ups
Mockups allow users to visualize an application that hasn't yet been constructed. Prototypes help users get an idea of what the system will look like, and make it easier for users to make design decisions without waiting for the system to be built. These are by no means definitive screen shots. It is up to the Contactor to come with proposals for each screen/page and validate them with the Publications Office.
Home page
[pic]
Figure 9 - Mockup of the home page
Search results
[pic]
Figure 10 - Mockup of the search results page
Advanced search
[pic]
Figure 11 - Mockup of the advanced search page
Page details
[pic]
Figure 12 - Mockup of an EU law details page
[pic]
Figure 13 - Mockup of a general publication details page
[pic]
Figure 14 - Mockup of a business opportunity publication details page
ShareThis feature
[pic]
Figure 15 - MockUp of the ShareThis feature as presented in the EU Commission IPG
Permanent Links
[pic]
Figure 16 - Mock-up of Permanent link for a publication
Browse by subject
[pic]
Figure 17 - Mockup Browse by subject
page templates & widget areas
Widget areas on page templates should be designed in the portal using the web content management features. Below there is a proposal for such a page template and widget areas.
|Header |
|Widget area 1 |
|Widget area 2 |Widget area 3 |Widget area 4 |Widget area 5 |
| |Content area | | |
|Widget area 6 |
|Footer |
Area 1 – Could be used for main navigation & bread crumb
Area 2 – Could be used for local menus
Area 3 – Could be used for very important message or banner to be populated through pages
Area 4 – Could be used for related info, supplementary menus
Area 5 – Could be used for related info, supplementary menus
Area 6 – Could be used for footer menus (can be menus of different websites-parts of the portal)
Mobile Homepage(search center)
[pic]
Figure 18 - Mobile homepage mock-up
Mobile search autosuggest feature
[pic]
Figure 19 - Mobile search mock-up
Mobile Browse by subject
[pic]
Figure 20 - Mobile Browse by subject mock-up
Mobile search results list and publications details
[pic]
Figure 21 - Mobile search results mock-up
Solution requirements
Business requirements
Scalability
The Publications Office promotes the implementation of a multi-tier architecture, using thin or web clients, application servers and databases for reasons of performance, scalability and flexibility.
The following considerations shall be followed by the Contractor:
• A portal process should never wait longer than necessary. Synchronous and asynchronous processes/actions should be combined for best efficiency and performance.
• Manage resources appropriately. Do not let processes or users to fight for resources. Adapt the out of the box configurations to the Publications Office infrastructure realities. Provide effort and proof of effort for optimization of resource management in the context of the Portal (memory, processor cycles, bandwidth, separation of traffic by protocol, avoid probable bottlenecks, specific usage of resources in virtual environments if the case, database connections optimizations, temporary files configuration, defragmentation, etc.). Avoid resource contention.
• Design for Commutability: Two or more operations are said to be commutative if they can be applied in any order and still obtain the same result. Typically, operations that you can perform in the absence of transaction are likely candidates.
• Design for reusability and interchangeability. Often, resource pooling schemes take advantage of interchangeable resources
• Separate or partition activities and resources. Minimize relationships between resources and activities thus minimizing the risk of creating bottlenecks. Ease the load that you place on high cost resources (e.g. use SSL only for pages that need or require increased security)
• Plan and provide capacity planning as well as load and performance testing
Failing to follow this consideration by the Contractor, it might result in rejecting the deliveries of the project.
Reliability
The Portal system and all its related components shall perform their required functions in the European Commission environment and under particularly conditions given by this document for the entire period of the contract. The portal shall:
• Continuously perform as required under given performances (specific to the functional requirements).
• Be designed to resist to failures.
• Manage errors and failures if occur
The Contractor must ensure reliability through design and implementation of its solution.
System requirements
is intended to be a web-based interface which provides unified and integrated access to EU law and publications as well as enterprise web applications and services (see Business services and Business processes chapters). The portal must be able to aggregate a collection of loosely-integrated features and services (described above in this document) and offer them to all types of users within an integrated, consistent and intuitive web interface.
Architecture
The key mission of the Office is to provide access to law and publications. The Transformation Program is a collection of aligned projects that together deliver the desired results to reach the objectives. Alignment is ensured through governance organization and procedures. Major decisions are taken by the steering group headed by the director general and supported by an enterprise architecture board. This Transformation Program aims to leverage and consolidate existing and projected initiatives to further enhance and innovate the access capabilities (Portal, Search and Content) of the Publications Office.
The target transformation architecture is intended to enable the harmonization of archiving, cataloguing, and electronic dissemination processes of the Publications Office. The horizontal layering enables the Publications Office to respond easily and swiftly to changes in the demands of the environment and to provide continuous improvement of access to law and publications. Horizontal layering (in short: ‘Portal’, ‘Search’ and ‘Content’) enables independent change per layer. This means e.g. that content formats and storage can be changed without affecting the search and portal layers other than enhanced functionality and services. Also, this architecture allows for multiple portals and multiple search engines and multiple content storage facilities to co-exist, thus enabling controlled, incremental and risk-averse migration.
Business Services of and processes described in the chapter Business perspective will be supported by a multitude of processes and IT Applications and systems, some of them already existing in the Publications Office some of them to be built. architecture and technology must support and ensure:
• Smooth integration with loosely coupling of all necessary services and applications
• Single point of entry for all kinds of users (registered or unregistered) to all services in an integrated and intuitive interface. (e.g. public access to EU Law and publications, support, management & reporting for authorized users, etc.)
• Security of services in all its aspects including availability, integrity, confidentiality
• Easy extension of the interface and of services by configuration and customization with very limited programming efforts.
• Easy integration of content coming from different sources
Below there is a list of IT Applications and Services relevant to this project. For each application, there is a brief description of what it does and a schema of its capabilities and interfaces to other applications (in the figure below, Common Portal refers to ).
[pic]
Figure 22 - Target architecture of the Transformation Program
PORTAL 2012
The portal of the Publications Office provides the general public with simple and easy access to all EU Law and publications stored in CELLAR-2012 through a unique and easy to use online access point. It also allows all end-users to re-use or enhance the content according to their needs.
The enterprise portal environment itself should actually entail multiple levels of services. The portal technology/software must be able to provide and facilitate or expose different services at the same time:
• The top level, the “presentation services”, should manage the presentation (rendering and display of pages, personalization, etc.), and thus provides access to multiple applications from a single point: becoming a de facto online desktop for users.
• The middle level, the “application services”, entails various functional services such as identity management, profile management, content management, navigation, publication process, analytic reporting services, and various specialized business logic or application services.
• The bottom level, “Data Services”, providing connectivity to where content is stored (“CELLAR” for most of the time, Index and Search layer)
[pic]
Sitemap
[pic]
Figure 23 - Portal Sitemap
NB: The current OP Internet site () must be completely reviewed and integrated in the About US section (see above site map)
Technology
A portal is generally defined as a software platform for building websites and web applications with multiple aggregation features that make them the best choice for web applications integration. Below there are the main features the portal technology chosen for implementation should offer out of the box:
[pic]
Figure 24 - Single point of entry to web resources and services
[pic]
Figure 25 - Integration / aggregation of multiple services and applications
[pic]
Figure 26 - Role based content presentation. Display different data depending on a user's role
[pic]
Figure 27 - Widgets and mashup capabilities
Portal platforms make it easy for users to build web pages and websites by assembling portlets or gadgets onto a portal page. Portal websites combine a theme (header/footer and common look and feel), a set of pages, navigation (menu bar, etc.), and a set of portlets and gadgets. Administrators can build pages without coding by reusing existing portlets and gadgets.
[pic]
Figure 28 - Multilingual content and navigation - a method to simplify the development and management of pages for each language
[pic]
Figure 29 - Login
Portal technologies make it easy to build websites that show different content depending on whether or not the person is logged in.
SEARCH SERVICE
The Publications Office common search service is accessible via standardized interface. The search builds on a common set of indexes that are generated on the basis of content and metadata stored in the Publications Office common content & metadata repository (CELLAR-2012).
The search and index layer must be seen as a horizontal service based on Autonomy technology (at the moment it is built used by EUR-LEX2012 only) with standard interfaces, optimal and scalable indexing for all types of content stored in CELLAR (general publications, tenderings and EU Whoiswho).
Important notice: Any adaptation or configuration needed to be performed on the SEARCH SERVICE (see sub-chapter Search layer) is out of the scope of this contract. Nevertheless, all configurations and adaptation of the portal interfaces, eventual requirements for adaptation of the SEARCH SERVICE along with the follow up of the respective implementation and the overall responsibility of delivering this service (to allow and optimize search federation from other web search indexes) are fully in the scope of this tender. The Contractor should include all necessary provisions in its proposal.
For details please see Annex 18 of the present call for tender specifications (Annex 18 SEARCH AND INDEX LAYER INTERFACE DEFINITIONS)
CELLAR
Common content & metadata repository for any content published in electronic format managed by the Publications Office.
System overview
The CELLAR system has two subsystems:
• The Common Content Repository (CCR),
• The Common Metadata Repository (CMR).
These subsystems rely on a Common Layer that takes care of the common processing and provides communication services between components.
[pic]
Figure 30 - CELLAR system overview
The common layer is the part of CELLAR that is providing access to metadata and content to external systems. It also plays the role of a coordinator for operations that involve the CCR and CMR.
For details please see Annex 17 of the present call for tender specifications which provides all necessary information for interactions with CELLAR through the dissemination interface (Annex 17 CELLAR DISSEMINATION INTERFACE). Table of contents of this document addresses particularly in detail the following issues:
• List of Services
• Resource Identification
• Service Specification
• Data exchange formats
• Configuration
• Disclaimer Notes
• Annexes with Examples
The Publications Office created and uses its own defined ontology which provides the CELLAR datamodel. This document will be available for the Contractor at the beginning of the contract.
CELLAR also contains information about the languages falling order as well as format falling order.
Core metadata and publications formats
The list of CELLAR « core metadata » is based on Dublin Core metadata elements set used in the digital world (and for Europa). The following standards were used in this context:
• Dublin Core element set,
• FRBR (Functional Requirements for Bibliographic Record - data model),
• CIDOC/CRM (temporal data),
• XML / FORMEX,
• RDF / OWL,
• RDA (Resource Description Access),
• METS (Metadata Encoding and Transmission Standard).
|No. |DC Element |OP Element |
|amz |Amazon Kindle eBook format |application/vnd.amazon.ebook |
|doc |Microsoft Word document |application/msword |
|docx |Office Open XML |application/vnd.openxmlformats-officedocument.wor|
| | |dprocessingml.document.main+xml |
|epub |Electronic Publication (open e-book standard) |application/epub+zip |
|fmx2 |Formex V2 |application/xml;type=fmx2, text/sgml;type=fmx2 |
|fmx3 |Formex V3 |application/xml;type=fmx3, text/sgml;type=fmx3 |
|fmx4 |Formex V4 |application/xml;type=fmx4 |
|html |HyperText Mark-up Language |text/html |
|jpeg |JPEG |image/jpeg |
|mobi |Mobipocket eBook format |application/x-mobipocket-ebook |
|pdf1x |Portable Document Format (ISO 32000-1:2008) |application/pdf, application/pdf;type=pdf1x |
|pdfa1a |PDF archiving format (ISO 19005-1:2005), Level |application/pdf;type=pdfa1a |
| |A conformance | |
|pdfa1b |PDF archiving format (ISO 19005-1:2005), Level |application/pdf;type=pdfa1b |
| |B conformance | |
|pdfx |PDF printing format (ISO 15930) |application/pdf;type=pdfx |
|ppsx |Microsoft PowerPoint 2007 Slideshow |application/vnd.openxmlformats-officedocument.pre|
| | |sentationml.slideshow |
|ppt |Microsoft PowerPoint Presentation |application/vnd.ms-powerpoint |
|pptx |Office Open XML Presentation |application/vnd.openxmlformats-officedocument.pre|
| | |sentationml.presentation |
|rdf |Resource Description Framework |application/rdf+xml |
|rtf |Rich Text Format |text/rtf |
|sgml |Standard Generalised Markup Language |text/sgml |
|sparqlq |SPARXL Query |application/sparql-query |
|sparqlqr |SPARQL Query Results |application/sparql-results+xml |
|tiff |Tagged Image File Format |image/tiff, image/tiff-fx |
|txt |Text file |text/plain |
|xhtml |eXtensible HyperText Markup Language |application/xhtml+xml |
|xls |Microsoft Excel Workbook |application/vnd.ms-excel |
|xlsx |Office Open XML Workbook |application/vnd.openxmlformats-officedocument.spr|
| | |eadsheetml.sheet |
|xslt |Extensible Stylesheet Language Transformations |application/xslt+xml |
|xml |Extensible Markup Language |application/xml |
|zip |zip |application/zip |
DISSEMINATION/DISTRIBUTION APPLICATIONS
It is to be considered here all IT application used in the Publications Office as a dissemination tool: EU Bookshop, EURLex, TED, PORTAL-2012, Whoiswho, CORDIS, Simap, EUROVOC, etc.)
EU Bookshop () is a digital library and at the same time dissemination tool which aims to facilitate the free-of-charge online access and ordering of all EU general publications. It also offers the possibility to purchase a priced monograph with online payment by credit card.
EUR-Lex () provides free access to European Union law and other documents considered to be public. The contents of the site amount to some 2 815 000 documents with texts dating back to 1951. The database is updated daily and every year around 12 000 documents are added.
CORDIS (), the Community Research and Development Information Service for Science, Research and Development, is the official source of information on the seventh framework programme (FP7) calls for proposals; it offers interactive web facilities that links together researchers, policymakers, managers and key players in the field of research.
EU Whoiswho () is an electronic directory which presents the organizational charts of the EU institutions, bodies and agencies in all official EU languages. The directory is updated once a week. In addition to this electronic directory, a printed version is published annually in 3 languages
Simap () portal provides access to most important information about public procurement in Europe. Tender notices are published on TED website, the single official source of public contracts in Europe. Most of public procurement notices are sent for publication through an electronic channel. A web-based tool — eNotices — simplifies and speeds up preparation and publication of tender notices. eSenders service allows qualified organizations to submit notices directly as XML files.
TED () (Tenders Electronic Daily) is the online version of the 'Supplement to the Official Journal of the European Union', dedicated to European public procurement.
EuroVoc () is a multilingual, multidisciplinary thesaurus covering the activities of the EU, the European Parliament in particular. It contains terms in 22 EU languages (Bulgarian, Czech, Danish, Dutch, English, Estonian, Finnish, French, German, Greek, Hungarian, Italian, Latvian, Lithuanian, Maltese, Polish, Portuguese, Romanian, Slovak, Slovenian, Spanish and Swedish), plus Croatian and Serbian. EuroVoc is managed by the Publications Office, which moved forward to ontology-based thesaurus management and semantic web technologies conformant to W3C recommendations as well as latest trends in thesaurus standards. EuroVoc users include the European Parliament, the Publications Office, national and regional parliaments in Europe, plus national governments and private users around the world.
Publications Office website () represents the main Internet gateway to the Publications Office providing users with contacts, news and procurement information about our institution. This website will be completely integrated in the in the “About US” section.
PO-USER-PROFILING-SERVICES
has to provide a central profiling service in order to manage all registered user profiles. This service shall be independent and self-manageable so that it provides its capabilities to the other Publications Office public websites (e.g. EUR-Lex, EUBookshop, TED, eTendering, etc.). Once a profile is registered (through or any other Publications Office public website), it will be available for and recognized by all other websites. When a user registers through a public web site of the Publications Office, it does not only register with the application but it registers within the Publications Office thus it will be recognized by all our applications.
By establishing a common user profile and a central profiling service, other Publications Office websites or internal services can filter and analyze information to efficiently accomplish digital and physical content dissemination mission while trying to meet the needs and preferences of each specific user or group of users based on their profiles. Proper security policies implemented in the profiling service must provide security to the user profile information’s management, personal data protection compliance being the main challenge to meet. This profiling service for must be integrated later on in a much larger CRM policy. In order to be easily used by other systems and websites, the profiling services must be coherent and flexible, run as an independent and self-manageable service with standardized interfaces, support extension and custom definition of both attributes and preferences for registered users.
As seen in the figure below the PO-USER-PROFILING-SERVICE must ensure:
• User profile management and reporting
• User preferences management and reporting
• Synchronization of relevant information with PO-CENTRAL-AUTHENTICATION-SYSTEM
• Reuse data stored in the authority tables for defined attributes or preferences (e.g. languages, places, etc.)
[pic]
Figure 31 - PO-USER-PROFILING-SERVICE
The registered user profile is composed of relevant information which describes the characteristics of an individual user as well as its preferences as described in the Figure 5 - OP Common User profile & preferences from the chapter User profiles and audiences.
The user profile data and preferences must be managed under strict compliance to EU Commission data protection rules and in particular with Regulation (EC) No 45/2001 on the protection of individuals with regard to the processing of personal data by the Community institutions and bodies and the free movement of such data.
PO-CENTRAL-AUTHENTICATION-SYSTEM
wishes to present the most relevant content for each user. In order to do this, the foreseen personalization features require identifying the user. Registered users have to be authenticated so that they could be authorized access to specific functionalities or use the advanced personalization features. has to build and use a service which centralize user authentication and/or identification upon the request of client applications by federating existing authentication providers (e.g. ECAS). It must provide as well the single-sign-on service for the Publications Office. (e.g. PORTAL-2012, EURLEX-2012, TED, eTendering, etc.). Authentication should be done by a CAS (Central Authentication Service) which must ensure homogenization of user access security policies and password protection. This service must be built as an independent, highly secure and self managed service. It will be shared and used by all the other web applications in the Publications Office.
A central authentication system for the Publications office must ensure:
• Homogenization of user access security policies and password protection for all Publications Office web sites
• One and only place where the user identities and user profile password is stored under the control of the Publications Office
• A centralized management interface exists and allows quick and easy provisioning and deactivating of users
• Authentication of both human kind users and automated services (e.g. web services, ftp, mobile devices protocols, etc.)
• Reporting and monitoring - A single repository for auditing and logging access to resources provides streamlined regulatory compliance
• Federated authentication – allow users already having a digital identity to be authenticated in our system without creating other usernames and passwords which is more and more difficult to remember. (e.g. ECAS, allow large public users being identified using their OpenID, Google, Facebook, LinkedIn identities). In this context, ECAS must be federated by PO-CENTRAL-AUTHENTICATION-SYSTEM. As for other identity providers, this will have to be validated by the Publications Office
• Flexible and easy to use user identities and password policies (e.g. not imposing very restrictive password related policies which frustrates users and definitely does not encourage adoption) – nevertheless it must respect the security policy in place at the European Commission
• Customization capabilities (e.g. being able to be integrated by any web site using his own design and graphical identity)
• Easy synchronization with PO-PROFILING-SERVICE for user profile and preferences usage across any web site
• Complete independence and own management of this service by respect to any other applications
A Single Sign on service must allow the user to be identified and access multiple applications while providing their credentials only once (e.g. userid and password). This shall be directly applicable to users already authenticated by ECAS and in the future it should be applicable to any Publications office web site e.g. EURLEX-2012, TED, eTendering, etc.
Single Sign On reduce frustration of multiple log-on events and forgotten passwords - Users only have one password to remember and update, and only one set of password rules to remember. Their initial login provides them with access to all resources, typically for the entire day.
The Single Sign On solution proposed by the Contractor must ensure:
• Time-saving benefits for end users
• Improved productivity - It takes an average of 20 seconds for a user to log into a resource. Not having to enter a password each time a user needs to access a resource saves time and makes users more productive.
• Frustration reduction of multiple log-on events and forgotten passwords - Users only have one password to remember and update, and only one set of password rules to remember. Their initial login provides them with access to all resources, typically for the entire day.
• Increased adoption - SSO reduces the barriers of use for resources. Since it is easier to access applications, users will start using them more.
• Improved reporting and monitoring - A single repository for auditing and logging access to resources provides streamlined regulatory compliance.
• Increased security - A secure, enterprise-wide infrastructure with common password and security policies that can be centrally managed and secured. Users are also less likely to write down their passwords when there is only one to remember.
• Uniform security layer – adopt SAML as platform agnostic protocol allowing enterprise architects to implement a uniform security layer with existing assets.
• Reduced helpdesk costs - Fewer helpdesk calls for password resets relates directly to bottom-line savings.
For both authentication and single-sign-on services, ECAS must be integrated as the main authentication provider for all scenarios and complying with above stated requirements.
Please refer to Annex 24 “EURLEX 2012 REUSABLE MODULES” from the current call for tender specifications for technical details on modules already developed in the framework of EURLEX 2012 and that can be reused for .
As seen in the figure below the PO-CENTRAL-AUTHENTICATION-SYSTEM must ensure:
• User authentication service using:
o It’s own mechanism
o 3rd party authentication providers like for instance ECAS for all European Institutions staff.
• Single-sign-on service
• Synchronization of relevant information with PO-USER-PROFILING-SERVICE
• User identity secure management and storage
• Reuse data stored in the authority tables for defined attributes or preferences (e.g. languages, places, etc.) for its own repository of users’ identities.
• Highly security standards with compliance to applicable security policies and frameworks
[pic]
Figure 32 - PO-CENTRAL-AUTHENTICATION-SYSTEM
In order to be used by the PO-AUTHETICATION-SYSTEM, the user identity must be composed of relevant data on the user needed for the authentication process as well as for the audit and trail process. Part of this relevant data is provided or has to be synchronized with the PO-PROFILING-SERVICE: The figure below describes the user identity conceptual data model.
[pic]
Figure 33 - PO User identity
Interoperability and standards
All search interfaces and APIs must be OpenSearch standard compatible:
The web content management system must ensure it is CMIS (Content Management Interoperability Standard) compliant:
The list of CELLAR « core metadata » is based on Dublin Core metadata elements set used in the digital world (and for Europa). The following standards were used in this context:
• Dublin Core element set,
• FRBR (Functional Requirements for Bibliographic Record - data model),
• CIDOC/CRM (temporal data),
• XML / FORMEX,
• RDF / OWL,
• RDA (Resource Description Access),
• METS (Metadata Encoding and Transmission Standard).
For wide accessibility, should follow the W3C guidelines:
• Web Content Accessibility Guidelines (WCAG) 2.0:
• Authoring Tool Accessibility Guidelines (ATAG) 2.0 (draft):
As for the Semantic Web (web of data), the following standards will be used:
• RDF version 1.0:
• OWL version 2.0:
• SKOS version 18 August 2009:
HTML5 should be encouraged for an enhanced user experience in portal services: Nevertheless for specific components which could pose difficulties for the minimum supported browsers, alternatives for compatibility with older browser should be automatically proposed to users not having HTML5 supporting browsers. HTML5 must not in any case alter the user experience for users not having compatible browsers.
Electronic Publishing
The guidelines from the Information Providers Guide (IPG) of the European Commission should be an important source of information for the future Contractor for any editorial, technical and presentation solution proposed. These guidelines are regularly updated and freely available at the following address:
Operational requirements
Security
In particular, main security objectives are:
• Confidentiality of personal data
• Integrity of data (publications, content, etc.)
• Availability (of services proposed in this document)
• Authenticity (for JO)
• Reliability of content
• Non-repudiation (for email/RSS alerts & notifications)
Data protection is critical for the Publications Office. The user profile data and preferences must be managed under strict compliance to EU Commission data protection rules and in particular with Regulation (EC) No 45/2001 on the protection of individuals with regard to the processing of personal data by the Community institutions and bodies and the free movement of such data.
must implement all security controls necessary to protect the security objectives described above, including prevention for these threats typical for web sites:
• Injection
• Cross-Site Scripting (XSS)
• Broken Authentication and Session Management
• Insecure Direct Object References
• Cross-Site Request Forgery (CSRF)
• Security Misconfiguration
• Insecure Cryptographic Storage
• Failure to Restrict URL Access
• Insufficient Transport Layer Protection
• Invalidated Redirects and Forwards
• Search box cross scripting: the search feature should not allow expression queries containing any form of programming code (jss, xml, sql, sparql, etc.)
For more details please check the Open Web Application Security Project (OWASP) top 10 Web Application Security Risks ().
Secure Socket Layer should be activated for Website Administrators and for restricted areas access (e.g. features reserved to identified users). If your web server is configured to support the SSL (Secure Socket Layer) encrypted "https" web communications protocol, SSL can be turned on for website visitors. When SSL is turned on website visitors will automatically be redirected to a "https" login page when they access restricted areas of your website. SSL login minimizes the risk that usernames and passwords are captured by unauthorized individuals.
Search Engine Optimization (SEO)
Search engine optimization (SEO) is the process of improving the visibility of a website or a web page in Internet search engines via the "natural" or un-paid search results. One of the key objectives of the is to be designed for reusability and maximize it. Easy discoverable of and its content (EU law and publications) is essential in this context. It is particularly important for the portal to be indexed by other Internet search engines as easy and as exhaustive as possible.
The system and especially the technology chosen must provide easy to manage and easy to configure features and/or intuitive management interfaces which will support SEO methods and techniques:
• Getting indexed facilitation (e.g. XML sitemap generation and submission to major search engines ensuring that all pages are found, especially pages that aren't discoverable by automatically following links)
• Preventing crawling
o Generation of robots.txt file in order to avoid undesirable content in the search indexes, authorized user can instruct spiders not to crawl certain files or directories
o Generate and automatic inclusion of robots specific meta tags for pages that might need to be explicitly excluded from a search engine's database.
• Increasing prominence (URL normalization, cross-linking)
In addition, the contractor responsible for implementing must provide a specific deliverable containing directly applicable SEO guidelines and actions once the portal is in production. The following analysis must be part of this deliverable ( Search Engine Optimization Website Report):
• Keywords Research Analysis
• Website Validation Analysis
• Link Analysis (Internal/External)
• SEO Quality Control
• Web Directory Submissions
• Search Engines Inclusion
Availability
Availability of services should be 99% or superior at any time, 24h/24h, 7d/7d, independently from performances of other applications. This level takes into account maintenance operations: specific maintenance operations or backup operations with a shutdown of the system may require a period of unavailability of the site.
Performance
Based on previous years’ consolidated statistics of all the Publications Office websites and considering an increase of number of page views due to the increased usability and the promotion of linking open data, the portal is expected to perform in perfect conditions (see next paragraph) for the following service load:
• 100 millions de visits or 300 million page views annually
• Up to 5 000 concurrent page requests in a first phase and up to 10 000 concurrent page requests in a second phase
Performance must be judged in terms of tasks performed by the user and the returning results for these tasks. All the following actions must be performed by the system in less than 2 seconds at any time:
• Time to perform a simple search (average): Time elapsed from the moment a user submits his search query and the moment the results are displayed on the screen. (This must take into consideration time took by the system to display the related pages)
• Time to perform an advanced search (average): Time elapsed from the moment a user submits his search query and the moment the results are displayed on the screen. (this must take into consideration time took by the system to display the related pages)
• Time to refine the list of publications in browse by subject: Time elapsed from the moment user choses a filter (subjects, subject matters and terms) in the browse by subject page and the moment the list of publications results is displayed on the screen according to the filter. (this must take into consideration time took by the system to display the related lists as subject matters are dependent on the chose subject and the terms are dependent on the subject matter)
• Time to display any portal page and the associated content (except for the homepage): Time elapsed from the moment a user asks the page and the moment the page is completely displayed.
• Time to download any format of a chosen publication: Time elapsed from the moment asks the document and the moment the system returns it.
Time to display the homepage must be less than 1 second at any time.
Performance indicators above should include considerations on any operations and data exchanges with the other content sources or layers (e.g. search and index, CELLAR).
Authorized users (authors/publishers) must be able to rapidly change the published editorial content. The technical publishing process (systems publishing workflow) of the editorial content shall be fully automatized and it shall not exceed 1 minute of processing at any time.
Manageability & Maintainability
Software solution and all required software components shall be properly documented. Any developed, customized component or technology predefined component shall be documented. Different set of documentation shall be provided:
• Design and implementation, with all the relevant information concerning the origin of the software, references for web sites, access point for order/download, etc.
• Operation with all the relevant procedures and tasks for monitoring purposes, performances tuning, restart/shutdown operations, backup/restore operations, upgrade, etc.
• Administration for the management of configuration; reinstallation of the system, management of users, defining default setting for the running system, etc.
Within their quality plan, contractors/suppliers must define a detailed and unambiguous numbering scheme for the software deliveries. Contractors/suppliers must also propose procedures for the management of bug reports and change requests. These procedures must allow unambiguously identification of every bug and every change request.
In line with maintenance obligations, the Publication Office shall be informed about all perspectives of software evolutions, whatever is the nature of the software component (developed component, software package, etc.). The Publication Office will be informed about design updates and transition plan initiatives.
The annex 11 from the current call for tender specifications “OP TECHNICAL ENVIRONMENT” provides the detailed information on manageability.
Installation & Deployments
In principle, for each application, two distinct environments are set up at the Publications Office’s premises: a test environment and a production environment. This does not preclude the fact that several applications can share the same production or test environment.
The hardware installations (including OS installations) remain the exclusive prerogative of the Publications Office.
No software installation in the production environment will be allowed without prior validation in the test environment.
In principle, no development environment will be set up at the Publications Office’s premises. The Publications Office strongly advises contractors/suppliers to set up at their premises a development environment similar (e.g. same OS version, same RDBMS version…) to the target production environment. It remains the responsibility of contractors/suppliers to make sure that software deliveries will run correctly in the Publications Office’s technical environment.
The annex 11 from the current call for tender specifications “OP TECHNICAL ENVIRONMENT” provides the detailed information on software deliveries, installation and deployments in the Publications Office.
Ownership
Publication Office will become the owner of the system, including the developed source code. All software components required for running administrating and monitoring the system, which cannot be owned by the Publication Office shall be clearly identified, as well as the conditions of use (Acquisition conditions, renting conditions, subscribing conditions, licenses, etc.)
Traceability
must be able to provide at any time an essential audit trail of all anonymous and identified users: what was published/consulted/done/saved/canceled/started/stopped/etc. when, where, by whom, and on what authority.
Technical environment of the Publications Office
The Publications Office makes a distinction between systems used for office automation and administrative information systems on the one hand and systems used for production on the other hand. The quality of service and the constraints of availability are tighter for the production systems, since external partners with contractual agreements are already in place. Another important difference between these two types of information systems is linked to their architecture. The production information systems are usually spread over several servers and include complex production chains with processing on all nodes, whereas administrative and office automation systems are simpler and frequently use a one-to-one relationship between a server and its clients. However, the same basic infrastructure is made available for both types of information systems, as described hereafter. The hardware/software architecture to use within the framework of a project is generally proposed by contractors/suppliers. However, this architecture has always to be validated by the Publications Office before implementation in order to evaluate the consistency of the proposal with the environment of the Publications Office.
The annex 11 from the current call for tender specifications “OP TECHNICAL ENVIRONMENT” consists of a general overview of the technical environment of the Publications Office as well as some general rules linked to the technical organization of the Publications Office and applicable to all applications hosted at the Publications Office.
Legal & regulatory requirements
The publications office mission statement
The Publications Office of the European Union (Publications Office) is an interinstitutional office whose task is to publish the publications of the institutions of the European Union (see Decision No 2009/496/EC, Euratom).
• The Publications Office publishes the daily Official Journal of the European Union in 22 languages (23 when Irish is required) and produces (or co-produces) publicity for EU initiatives and activities.
• It publishes or co-publishes the publications in the context of the communication activities of the institutions.
Moreover, the Publications Office offers a number of online services giving free access to information on EU law (EUR-Lex), EU publications (EU Bookshop), public procurement (TED), and EU research and development (CORDIS).
Data protection legal framework
The user profile data and preferences must be managed under strict compliance to EU Commission data protection rules and in particular with Regulation (EC) No 45/2001 on the protection of individuals with regard to the processing of personal data by the Community institutions and bodies and the free movement of such data.
EU Commission security legal framework
The European Commission owns and maintains the overall EC Information Systems Security Policies (EC ISSP), based on the Commission decision C(2206) 3602.
The EC ISSP does not provide rules, procedures or guidelines for specific information systems. It defines, however, the general framework to derive Directorate-General / Department specific security policies and system specific security plans. All derived security policies and plans shall be consistent with the EC ISSP. In line with this requirement, the Publications Office has developed its own specific Baseline Information System Security Policies (BISP).
The BISP defines the boundaries within which all processes should take place. All products selected, processes, manuals and handbooks should be in compliance with the policy. The policy serves as the main reference to the best practice, to which all subsequent security documents - Technical Security standards, User Security standards and Security procedures - must adhere.
The compliance with decisions and standards are compulsory, guidelines are for guiding.
Decisions, standards and guidelines of the European Commission can be visualized at this link: .
The BISP document as well as the minimum requirement of the Publications Office Infrastructure department will be provided to Contractor for at the start of the contract.
User requirements
Wide accessibility
All the official websites of the EU institutions – including - should follow international guidelines for accessible web content, so they can be accessed and understood by as many people as possible without discrimination.
should follow the guidelines from Web Content Accessibility Guidelines (WCAG) 2.0 and Authoring Tool Accessibility Guidelines (ATAG) 2.0 issued by the World wide web consortium (W3C).
All new EUROPA sites should meet the criteria for level A (priority 1) compliance – the basic standards recommended by the WCAG guidelines. More on this subject can be read at the following address:
should follow these up-to-date WAI guidelines to make sure that it could be viewed, navigated and interacted with by anyone, particularly disabled people:
1. Web Content Accessibility Guidelines (WCAG) 2.0 :
• Perceivable
o Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, Braille, speech, symbols or simpler language.
o Provide alternatives for time-based media.
o Create content that can be presented in different ways (for example simpler layout) without losing information or structure.
o Make it easier for users to see and hear content including separating foreground from background.
• Operable
o Make all functionality available from a keyboard.
o Provide users enough time to read and use content.
o Do not design content in a way that is known to cause seizures.
o Provide ways to help users navigate, find content, and determine where they are.
• Understandable
o Make text content readable and understandable.
o Make Web pages appear and operate in predictable ways.
o Help users avoid and correct mistakes.
• Robust
o Maximize compatibility with current and future user agents, including assistive technologies.
2. Authoring Tool Accessibility Guidelines (ATAG) 2.0 :
o Support accessible authoring practices
o Generate standard mark-up.
o Support the creation of accessible content.
o Provide ways of checking and correcting inaccessible content.
o Integrate accessibility solutions into the overall "look and feel".
o Promote accessibility in help and documentation.
o Ensure that the authoring tool is accessible to authors with disabilities.
It is true that WAI compliancy might considerably limit the browsing/visualization capabilities in the portal. The aim is to find a solution to make the site available to WAI users without sacrificing usability.
Besides this, all web pages exposed to the user by the system should be as light as possible and compatible with the popular web browsers Firefox, IE, Safari and Chrome.
All mobile web pages exposed to the user by the system should be as light as possible and compatible with the most popular mobile browsers for iOS, Android and Windows Phone.
As for the Semantic Web (web of data), must ensure wide accessibility by complying with the following standards:
• RDF version 1.0:
• OWL version 2.0:
• SKOS version 18 August 2009:
Text to Speech (handicap accessibility)
could propose such a feature, reusable by any other web site, which would allow the user to hear the text on the current web page. This will be particularly useful to improve visually impaired users experience on our site.
The following list describes various text-to-speech behaviors:
o The system lets you specify a text string to be spoken when the user navigates to a label/button/content with the Tab key/mouse over.
o The system lets you specify a user event that can turn the text-to-speech feature on or off.
Browser compatibility
shall be accessible via widespread desktop internet browsers with a significant market share (refer to ):
• Internet explorer version 8.0 and later versions.
• Firefox version 10 and later versions.
• Safari version 5.1 and later versions.
• Chrome 17.0 and later versions.
• Opera 11.0 and later versions
No specific browser plug-in should be required for complete use of the portal services.
HTML5 should be encouraged for an enhanced user experience in portal services: Nevertheless for specific components which could pose difficulties for the minimum supported browsers, alternatives for compatibility with older browser should be automatically proposed to users not having HTML5 supporting browsers. HTML5 must not in any case alter the user experience for users not having compatible browsers.
No specific reader must be mandatory for users for the display of any content, page, and data.
For the mobile version, shall be accessible via widespread mobile internet browsers with a significant market share:
• Safari Mobile version iOS 4.2 and later versions.
• Android browser version 3.1 and later versions.
• Blackberry browser version 5.0 and later versions
• Opera Mini 4.2 browser
• Internet Explorer 9.0 for mobile version Windows Phone 7.5 and later.
Authoring tools
In addition to browsers and the provided solution, authoring tools such as Microsoft Office 2010 suite and Microsoft SharePoint available on OP workstation can be used for editing/publishing/document management purposes.
Authoring tools can be used directly, via the appropriate protocol or customized integration with the provided solution. Operations lie cut-and paste, drag and drop, publishing, check-in/check-out, etc. should be permitted from the authoring tools environment to the built-in editing functions of the Contractor’s proposed solution and technology. Any proposed integration or needed configuration must be implemented by the Contractor in the scope of this tender. Nevertheless, there will be restrictions and limits to properties and attributes to import (restricted fonts, restricted style sheet, etc.). Limitations shall be defined in detailed solution proposed.
Usability
must follow the Internet design usability guidelines for the web site as well as for the mobile site and particularly those listed below:
• Prioritize Content
o Be succinct & do not display irrelevant information and place the most important first.
o Emphasize the highest priority tasks so that users have a clear starting point on the homepage. Search must be promoted as top task on the site and on the homepage itself. Homepage should be kept clean at any moment of less important tasks and always reflect the chosen top tasks.
o Offer users direct access to high-priority tasks on the homepage. (e.g. Browse by subject, App store)
o If the website is down or important parts of the website are not operational, show it clearly on the homepage (check the proposed widget area)
• Consider the opportunity cost of each design element. Keep it short and simple.
• Simplify Navigation:
o Reduce the number of categories and levels and rearrange them based on priority
o Make links obvious (affordance), and provide clear and immediate visual feedback.
o Label graphics and photos
o Avoid watermark graphics (background images with text on top of them)
o Don't use animation for the sole purpose of drawing attention to an item on the homepage.
o Don’t animate critical elements of the page, such as the logo, tag line, or main headline.
o Avoid horizontal scrolling at 1024x768.
o Use high-contrast text and background colors so that type is as legible as possible.
o Use a liquid layout so the homepage size adjusts to different screen resolutions.
o Don't automatically refresh the homepage
o Show users the time that content (pages or publications) was last updated, not the computer-generated current time.
o Use a thousands separator appropriate to the selected local settings for numbers that have four or more digits.
o Align decimal points when showing columns of numbers.
• Minimize User Input and interaction cost
o Use techniques such as autocomplete, suggestions or sensible defaults and
specific devices features (for mobile) like the camera, microphone or geo-location.
o Input boxes should be wide enough for users to see and edit standard queries on the site.
• Take into account screen sizes diversity and constraints (for mobile)
• Design for Interruptions (mobile)
o At any moment the user’s task may get interrupted.
o Save state.
o Remember filled-in values.
• Simplify tasks.
• Windows and URLS:
o Begin the window title with the information-carrying word
o Don't include the top-level domain name in the window title but Include a short description of the site in the window title. Limit window titles to no more than seven or eight words and fewer than 64 total characters.
o Keep URLs as simple and memorable as possible. Portal website pages should be accessible by simple URLs. Additionally static URLs are search-engine friendly.
o Avoid popup windows (except maybe for Permanent Link)
o Take users to your "real" homepage when they type your main URL or click a link to your site. (no splash screen)
• Links
o Don't use generic instructions, such as "Click Here" as a link name.
o If a link does anything other than go to another web page, such as linking to a PDF file or another application, make sure the link explicitly indicates what will happen (e.g. suggestive icons).
o Differentiate links and make them scannable. Begin links with the information-carrying word, because users often scan through the first word or two of links to compare them.
o Don't simply provide plain links to registration on the homepage; instead explain (or at least link to) the customer benefits of registration.
• Search
o Unless advanced searches are the norm on your site, provide simple search on the homepage, with a link to advanced search or search tips if you have them.
o Search on the homepage should search the entire publications scope by default
should consider usage of an adaptive layout for its pages in order to optimize the display on any kind of device.
Deliverables of the project will be rejected if best practices mentioned in this annex will not be considered.
Please check the full list of guidelines for usability of the mobile version of the site in the Annex I – Mobile Web Usability guidelines.
Extensibility
is expected to cover a wider scope in the future, and to offer to its users extended access to new features and new data. The architecture of the new should support distributed solutions, (e.g. possibilities to take into consideration data and meta-data not stored directly in the CELLAR or the local repository of the system) as well as the extension of the portal features and functions to other web sites of the Publication Office (Ex: EU Bookshop or Whoiswho integration, social network tools, etc.) must be foreseen and easily provisioned.
Integration
Search layer
must reuse the search and index infrastructure put in place for EURLEX2012 project. The current infrastructure must be adapted it in order to consolidate an independent and self managed service application answering to all search and index needs of both requirements and the other specific services and websites (DISSEMINATION/DISTRIBUTION APPLICATIONS chapter).
Please refer to the Annex 18 “SEARCH AND INDEX LAYER INTERFACE DEFINITIONS” from the current call for tender specifications.
Please refer to Annex 24 “EURLEX 2012 REUSABLE MODULES” from the current call for tender specifications for technical details on modules already developed in the framework of EURLEX 2012 and that can be reused for .
CELLAR
must integrate CELLAR as the main content repository for all EU law and publications.
Translation systems (ATTO)
must integrate ATTO application service which provides 23 languages translated labels and messages for navigation items, menus, error messages and/or alerts.
Data Exchange between ATTO and the Client systems is performed using XML standardized messages. The typical workflow is based on a sequence of 7 steps:
• The Client system exports to ATTO (in XML) the list of codes to be translated (including optional first translation in master language); This first step is out of the ATTO scope;
• ATTO Loader module imports the XML files into ATTO database;
• ATTO initializes the repository in ATTO database for this particular client system. It creates Domain, table and code entities, if needed;
• Complementary translations are introduced from ATTO web interface;
• The translations are recorded and saved into ATTO database;
• The Domain administrator exports the new translations in XML;
• The Client system imports the new translation in its own system; This last step is out of the ATTO scope;
The Annex 22 of the current call for tender specifications provides information on the architecture overview of ATTO.
EUROVOC
EuroVoc is a multilingual, multidisciplinary thesaurus covering the activities of the EU, the European Parliament in particular. It contains terms in 22 EU languages. EuroVoc is managed by the Publications Office, which moved forward to ontology-based thesaurus management and semantic web technologies conformant to W3C recommendations as well as latest trends in thesaurus standards. EuroVoc users include the European Parliament, the Publications Office, national and regional parliaments in Europe, plus national governments and private users around the world.
The reference version of this thesaurus will be stored in CELLAR. As is concerned, these terms will be mainly used by
Browse by subject feature and in the search process (facets).
Metadata register - Authority tables
In the Publications Office there are two types of authority tables:
• Common Authority Tables (CAT), used at least in 2 systems
• Proprietary Authority Tables (PAT) which remain unique in a given system (CPV, Directory of Legislation, Themes, etc.) or unit.
uses a series data models (Publications core metadata, User profiles and preferences, user identity) which rely for some of their elements on values coming from CELLAR but managed in the Common Authority Tables (CAT). The CATs supply a unique OP-Code for all other codes, they map old/other codes to OP-Codes and they provide "official/canonical" labels for all OP-Codes, often in all 23 languages. Furthermore (but that's not implemented in the CELLAR yet) they can supply historical information about the entities represented in the tables, like predecessor/successor countries or corporate bodies. Below there is the precise list of these elements:
|Common Authority Tables |Source |
|Languages (ISO 639/1, 639/2B|T, 639/3) |ISO |
|Countries (ISO 3166/1-α2 and α3, 3166/3) |ISO |
|NTU (incl. NUTS and ISO 3166-2) |ISO + UNO + Eurostat |
|Currencies (ISO 4217) |ISO |
|Corporate Bodies |Various |
|Roles |LC + EurLex + Prelex |
|Places (locations, towns) |UN-LOCODE |
|Resource formats (incl. dimensions) |ONIX + IANA |
|Resource types (categories of resources) |Internal sources |
|Target Audiences |ONIX |
|Legislative Procedures |PreLex + Treaties |
|Events |PreLex |
|Treaties | |
Web-analytics, Statistics and reporting – Webtrends system
For the sake of rationality and efficiency, the Publications Office adopted the same system for web-analytics, statistics and consolidated reporting for all its sites: Webtrends analytics advanced version 8.7. must use the same existing Webtrends instance for all statistics and reporting requirements. The future Contractor shall adapt the existing Webtrends configuration in order to provide the needed analytics. All necessary adaptation, various installations, configuration and tests are included in the scope of this tender.
Besides the requirements presented in the chapter
Statistics and reporting, The Publications Office has also a minimum number of indicators (called Common indicators) that are requested for all its web sites. These indicators must be provided by the portal as well (some are obviously overlapping with the ones presented in the chapter
Statistics and reporting):
|Name of the indicator |
|Number of visits |
|Number of visits of registered users |
|Number of unique visitors |
|Number of unique visitors of registered users |
|Number of new visitors |
|Number of new visitors of registered users |
|Geographical breakdown of visitors |
|Number of page views by type |
|Number of page views by language |
|Number of documents consulted by type |
|Number of documents consulted by format |
|Number of documents consulted by language |
|Number of documents consulted by author |
|Total number of documents downloaded |
|Total number of documents downloaded by language |
|Information of the technical environment of the user (screen, internet accesses etc.) |
|Navigation paths |
|Type of request |
Other systems
should reuse as much as possible, the elements developed in EURLEX2012 project. The following features are candidates for reusability in project. The contractor must provide the best effort to analyze and adapt the following modules in order to create or consolidate them as independent and self managed service(s) and/or applications:
• User profile/preferences services
• ECAS integration as an authentication provider
• Multithreading EURLEX2012 Search API, Multithreading EURLEX2012 CELLAR API, EURLEX2012 logging API, Search results export module, RSS management
• EURLEX2012 Back Office Web content management
Annexes
Annex I – Mobile Web Usability guidelines
Accessing the mobile site
• Detect if the user is coming from a mobile phone and redirect.
• Link from the full web site to the mobile site.
• Include the word “mobile” in the title of the mobile site.
What to include in your mobile site
• Include a link to full site.
• On mobile site, include company logo on every mobile page.
• Include an explicit “Home” link on internal pages. Do not rely on the logo for taking users to the homepage.
• Allow saving and sharing of content seen during session
• Include a search box on each page at top of the page
• Make the search box wide enough so that users don’t need to scroll within it (30 chars for big screen smartphones).
• If a search returns zero results, offer alternative queries or link to the full site, if the full site search leads to more results.
Navigation; Carousels; Menus
• Use homepage navigation models (list like). Link to home from every page.
• Include some navigation option at the bottom of the page (either link to the top navigation bar or proper navigational links).
• Avoid deep navigation on a website.
• Do not use animated carousels.
• Make sure that the controls of the carousel are not separated from the carousel display.
• Make sure that menus have the right affordance (that is, they look like menus). Use a label that is suggestive of the menu’s content.
• Provide consistent navigation mechanism
• Do not cause pop-ups or other windows to appear
• Keep the number of externally linked resources to a minimum
Page Layout and Content
• Ensure that content is suitable for use in a mobile context (Limit content to what the user has requested, users will look for specific information rather than browsing)
• Divide pages into usable but limited size portions
• Ensure that the overall size of page is appropriate to the memory limitations of the device.
• Limit scrolling to one direction
• Do not use images that cannot be rendered by the device. Avoid large or high resolution images
• Do not use frames
• Do not use tables for layout
• Provide a text equivalent for every non-text element
• Do not rely on embedded objects or script (non text items)
• Use style sheets to control layout and presentation (check if the device support them)
• Keep style sheets small
• Ensure that content is encoded using a character encoding that is known to be supported by the device
• Provide informative error messages and a means of navigating away from an error message back to useful information
• Do not rely on cookies being available
Input
• Minimize user input by using techniques such as autocomplete, suggestions, sensible defaults (based on user history or current context). Use camera for input (e.g., identifier for example).
• Where possible, compute values for users instead of asking users to type them in.
• Clear placeholders when the user starts typing in the associated text box.
• Use textboxes wide enough so that the users don’t need to scroll within.
• Do not rely on user memory;
• Link to a calendar when users have to enter a date (e.g. for search refine on Publications Date)
• Make Telephone Numbers "Click-to-Call"
• Ensure Paragraph Text Flows
Login and Registration
• Avoid requiring users to login or register unless absolutely necessary. In order to give the same user experience, we’ll need to implement also login and registration for users from mobile.
• For ordering publications (future phase), allow users to complete the checkout with or without logging in or. Display first the option that does not require log in. Ask users if they want to create an account at the end of the checkout.
• Allow users to display their password in clear if they want so.
• Automatically log-in users where possible
Forms
• Minimize the number of separate steps (that require submission to a server). Group related information in a single step.
• Show all information pertaining to a transaction on a single screen. When users click the “Submit” button, all the transaction related information should be visible.
Touch Targets
• Leave space (1cm X 1cm) around buttons and links.
• When displaying items in a list view, use padding for each item in the list.
Lists, Sorting and Filtering
• It is better to split it in pages of 10-20 items per page (depending on the size of the images – vignettes of publications).
• Allow users to filter and sort it according to a variety of criteria (include facets on the mobile site)
• Allow users to sort items by the same options as defined for the web site
• When displaying content (e.g., list of publications in search or publications details), include links to related publications
• Use bullets and headings to make it easy for users to scan content.
• Do not repeat information: when a user clicks on a link, make sure that they see something new (that they haven’t seen already) on the page.
• Allow users to change text size.
• Prefer sans-serif font.
• Allow users to share publications links and content (e.g. like on the web site the ShareThis feature).
• Use captions for publications thumbnails
• Avoid shuffling the images on the page during download.
• Do not use images as navigation links.
• If the image carries a lot of content (e.g., a product image), allow users to see larger versions of an image.
Errors
• Simplify error messages so that users can understand them.
• Make the error messages informative and operational: tell users what they are supposed to do next.
• Tell users where the error is coming from.
• Place error messages next to the error.
• Do not use alerts to report errors.
• Use progress indicators to show how long users have to wait. Prefer progress bars for tasks that take more than 1-2s. Avoid making people wait for more than 15-20s.
• If an error occurs, return to the state before the error. Preserve all the values that the user has already entered.
Conservative use of resources (both web and mobile)
• Use Transfer Compression
• Minimize Application and Data Size
• Avoid Redirects
• Optimize Network Requests
• Minimize External Resources (larger requests should be favored over a larger number of smaller requests)
Annex II – Detailed schemas of business processes used by
A3 schemas from ARIS Business publisher can be found in the Annex 23 from the current call for tender specifications
[pic][pic]
................
................
In order to avoid copyright disputes, this page is only a partial summary.
To fulfill the demand for quickly locating and searching documents.
It is intelligent file search solution for home and business.
Related searches
- functional requirements document dod
- dod functional requirements document template
- functional requirements excel template
- sample functional requirements document
- functional requirements document dau
- free functional requirements template
- functional requirements format
- functional requirements document
- functional requirements list
- non functional requirements list
- functional requirements examples
- non functional requirements software examples