Web Content Management System, Migration and Maintenance Services for ECDC Web Portal

Web Content Management System, Migration and Maintenance Services for ECDC Web Portal WCMS Requirements Reference B March 2015 Information and Communication Technologies Unit Web Portal 2.0 - Content Management System Core Requirements Page 1

Table of Contents 1 Document Purpose... 3 2 Requirement Prioritisation and Responses... 3 2.1 Tenderer response... 3 2.2 Priority... 3 3 Table of WCMS Requirements... 4 Page 2

1 Document Purpose This document presents the core requirements for the web portal Web Content Management System (WCMS). It is part of a set of reference documents supporting the Web Portal 2.0 Call for Tender. 2 Requirement Prioritisation and Responses 2.1 Tenderer response The full list of reference documents can be found in section 2.2.6 of the Tender specifications. 2.2 Priority The table contains one of three values (,, Low) which signify the following: The requirement is mandatory. Alternative suggestions on how to provide a solution for the requirement may be considered but non compliance will be highly detrimental in the evaluation of the proposal. (14 points) The delivery of this requirement is highly desirable and alternative suggestions may be considered. Non compliance will be detrimental in the evaluation process. Low (0,52 points) The requirement is not mandatory but compliance will be viewed favourably in the evaluation process. Alternative suggestions on how to provide a solution for the requirement may be considered. Page 3

3 Table of WCMS Requirements ID Requirement Priority 0001 The WCMS shall have an established and recent user base across a variety of public and private sector organisations 0005 The WCMS shall have extensive development resources available whether that be through a developer community, authorised partners or chargeable channels. 0010 The implementation of the CMS shall comply with EU legislation on personal data protection 0015 0020 0025 0030 The WCMS shall provide content authors with the ability to produce content in accordance with the Web Content Accessibility Guidelines 2.0 Level AA requirements (WCAG 2.0 AA). In the event of justified technical or practical reasons for not complying with WCAG 2.0, level AA guidelines, the exceptions should be explained in an accessibility page http://ec.europa.eu/ipg/standards/accessibility/index_en.htm http://www.w3.org/wai/wcag20/quickref/overview.php The WCMS shall have rich out-of-the-box functionality to reduce the number of customisations required to fulfil the requirements contained in this document The WCMS shall support the creation, modification and deletion of templates to enable easy management of site and page layout and navigation Layout and content shall be managed separately (i.e. it must be possible to create and edit content without having to amend or create a template) Page 4

0040 The web interface shall support the creation and application of styles using Cascading Style Sheets (CSS) enabling the swift alteration of the look and feel (colour, font, image size and positioning, link attributes, table properties). It must be possible to use multiple stylesheets with any style conflicts being resolved by the CSS rule of last in, first out. All controls should be rendered through CSS as should most of the look and feel - graphics should be optimized to support page loading performance. Graphics should be avoided altogether with regard to navigation (e.g. no navigation buttons - these should be text, which gets its look and feel through CSS). This approach makes it easier to change the font size to help people with sight issues to better read the pages. 0045 The WCMS shall be delivered with configurable navigation functionality 0050 The WCMS shall be delivered with a configurable function to render a breadcrumb. 0055 The WCMS shall be delivered with a configurable function to render a sitemap. Note: It is not anticipated that this functionality should be fully automated semiautomated support is desirable but the site map should be under the control of the web editing team. 0060 The WCMS shall be supplied with an image library function 0065 The WCMS shall be delivered with a default template for the display of one or more RSS feeds 0070 The WCMS shall be delivered with templates and styles reflecting ECDC branding (described separately) 0075 The WCMS shall enable the hierarchical creation of sites (i.e.parent/child sites in the same domain) and also enable the child site to either inherit the look & feel of the parent site or have its own style and branding 0080 It shall be possible to integrate 3 rd party tools and other ECDC services 0085 It shall be possible within the WCMS web interface to create metadata and content types for use across the web portal. 0090 0095 The WCMS shall be capable of storing and categorising documents, images, video and audio files. It must be possible to assign content types and metadata to repositories and be possible to assign metadata values to objects (documents, images, video and audio files) The WCMS shall be implemented with a default set of metadata which will consist of the Dublin Core metadata element set, W3C meta tags and ECDC specific metadata (described separately). It must be possible to retrieve metadata values from the ECDC Terminology Server (connection details to the web service supplied separately) Page 5

0100 The WCMS shall be implemented with a default set of ECDC specified content types (described separately). It is important that the WCMS demonstrates the capacity and versatility to store and present the full array of contents types for current and future usage at ECDC. This includes the ability to download content. 0105 The WCMS shall provide a web interface to manage the web content 0110 The web interface shall contain a WYSIWYG editor and provide standard Word authoring features (also known as a Rich Text Editor) to enable an editor to add and format text, links and images to content areas, create tabular layouts within a text area and apply styles without needing HTML skills 0115 The web interface shall have a drag and drop feature to enable easy management of content within the WCMS Low The WCMS shall support the following minimum preview and publication functions: 0120 - Preview only (not visible to users) - Save as unpublished (draft) - Preview then publish - Publish immediately - Send for approval - Approve - Publish after approval (i.e. after successful completion of the approval workflow) - Unpublish (save as unpublished, not visible to users) - Publication scheduling - Publication expiration date (automatic unpublish) Preview mode shall show the behaviour of affected active content (e.g., 3 rd party content) and links 0125 The WCMS shall support collaborative content editing through a check-in and check-out feature 0130 The WCMS shall support configurable version control (turn on/off, number of versions) and it must be possible to restore previous versions of a content item Page 6

The WCMS shall support the bulk uploading of files and include metadata support as part of the publication workflow including: 0135 Asigning a metadata classification to a group of uploaded files Integrating with the Terminology Server to automatically populate metadata Ability to manually edit metadata prior to publication 0140 The WCMS shall supply a configurable image rotator function to provide: - image source - vertical or horizontal rotation - rotation speed - text manipulation - hyperlinks from images - hyperlink target (new window, existing window) 0145 The WCMS shall be delivered with an image library that is capable of automatically creating thumbnails of images at predefined sizes 0147 The WCMS must support displaying of the last revision date on pages to the user The WCMS shall be capable of rendering dynamic content from multiple sources, examples being: - SQL Server Reporting Services reports hosted at ECDC 0150 - Dynamic web pages (ASP.NET) developed at ECDC or by 3 rd party tools (e.g., Atlas of Infectious Diseases, MapsAlive, data visualisation modules) - Web services developed internally or externally (e.g., the ECDC Terminology Server, ECDC Epidemic Intelligence Systems, MS Health Authorities) Page 7

The WCMS shall provide a personalisation feature. This feature must require the visitor to first register a profile before being able to customise content. 0155 Personalisation feature shall enable registered users to customise content to suit their needs, for example: - - Select events - Use calendar and date picker - Subscribe to alerts - Create quick links to favourite content 0165 The WCMS shall support selection of content to build a newsletter 0170 0175 0180 0185 The WCMS shall deliver a subscription function enabling site visitors to select content to be sent to them at specified intervals. It must be possible for site visitors to amend their selection criteria and subscription information The solution shall be delivered with an email distribution tool (inbuilt or 3 rd party) to support content delivery such as newsletters and subscriptions The WCMS shall provide the functionality to receive and store abstract submissions (brief summary of a research article). This can be delivered through a 3 rd party product (e.g. module) The WCMS shall provide the functionality to handle conference registrations. This can be delivered through a 3 rd party product (e.g. module) Low Low 0190 The WCMS shall be capable of rendering in all browsers specified in technical Reference F 0195 The WCMS shall support responsive design 0200 The WCMS shall provide the configurable functionality (inbuilt or 3 rd party) to create polls and surveys as well as the functionality to view, moderate and publish the results Page 8

0205 0210 The WCMS shall provide an easy method of creating an RSS feed which must include the ability to specify the following: - Number of items - Title - Site URL - Description - Feed target Once created, it must be possible to display the RSS feed on pages The WCMS shall provide a expand/collapse function that can be used in the web interface, to accommodate easier viewing of long page content. Similar to anchor links, it should be possible to specify by a web editor that an area of a page should be revealed or hidden through the click of a hyperlink Low 0215 The WCMS shall provide the functionality to enable site visitors to easily print pages and download documents (including images and maps) 0220 The WCMS shall provide a disclaimer function that can be applied to an activity or content item, making it unavailable until the disclaimer is accepted. For example, a disclaimer may be required before enabling the download of a publication or in accepting the use of cookies 0225 0230 0235 0240 The WCMS shall include a social media integration module that allows configurable sharing of content (pages, interactive data visualisations, images, videos) to a variety of social media (Facebook, Twitter, Google+, LinkedIn, Pinterest, Tumblr, StumbleUpon, Digg and others to be specified). It must be possible to easily add other social media The WCMS shall provide, in-built, plug-in module or 3 rd party, blog capability and the ability to post and respond to the blog shall be determined by user rights (i.e. a blog responder must register his/her profile). It must be possible to enable/disable moderation of all comments before publication A comprehensive search facility shall be provided (it is envisioned that the ECDC FAST Search will be used). This facility should provide auto-completion and support metadata, partial words & phrases and boolean searches. It should be possible to index content for search upon publishing. The search facility must be capable of integrating with the ECDC Terminology Server and the ECDC FAST Search (technical details supplied separately) The search facility shall return results (links to content) in an optimised (scored) order. The search result should be meaningful to the user and contain the page title and snippets in which the search term occurs. The content type (web page, PDF file, ) should be indicated by an icon Page 9

0245 0250 0255 0260 The WCMS shall support faceted searching enabling the application of multiple filters to search request results using drill-down (sequential) and parallel (concurrent) selection methods, through integration with the FAST search engine. The WCMS shall support the creation of an alert in response to a specific event, examples being: - Content amendment - Content expiration date approaching - Orphaned links The triggering of an alert shall cause a notification to be sent to the target(s) of the alert. It must be possible to define a list of recipients for each alert type which will be used in the notification process The WCMS shall support presentation of content in different languages and shall respect formatting of properties, such as the date format, according to the country locale of the specific language site Low Low 0265 The WCMS shall be capable of exporting content for translation and importing the result in its original format to the appropriate locale 0270 The WCMS shall support the Unicode character set (UTF-8) 0275 0280 0285 The web interface shall contain a content approval workflow to enable the approval of modifications (create, modify, delete) before publication (i.e. before becoming visible to the public) It shall be possible for the Administrator (or a designated user with an appropriate permission level) to assign and reassign users to workflow tasks (i.e. define the targets within the workflow) The WCMS shall be delivered with a feature, in-built or 3 rd party, to customise URLs. Generated URLs must be search engine friendly and easy to share with others by e-mail or other media 0290 The facility shall be provided to detect orphaned links within the site structure and to external content. A report must be produced 0291 0292 URLs to pages and documents on the current web site have been published. Facility, in-built or 3 rd party, shall be provided to map existing URLs to the new location of the pages or files. This should also work with dynamic, parameterized content. In order to bookmark parameterized dynamic content or share links to such dynamic pages it must be possible to code the parameters in the page URL. Page 10

0295 0300 The WCMS shall provide a role-based user access mechanism where an administrator can create and manage users, user groups, roles and role permissions. For the initial roles see Reference F, Section 2.2 The web interface shall require a web editor to log in (username, password) to manage web content. The term 'web editor' is an example of a security role and will apply to anybody who manages web content 0305 The security model shall enable the assignment of permissions to registered visitors 0310 The WCMS shall be delivered with an administrative interface with the tools necessary to initiate a complete recovery of the content and web server from backup files 0320 The WCMS shall provide an archive facilty to manage content based on expiry date or manually 0325 It shall be possible to connect a web analytics function to pages and content within pages (images, graphs, expanded articles,pdfs) 0340 The WCMS shall provide a facilty to customise messages for common errors The WCMS must support multiple categories of content feeds, including but not limited to: File transfer o HTTP and HTTPS o FTPS 0345 Manual Entry Web Services Feeds (via SOAP) Database Integration 0350 Ability to support dynamic content feeds and content transfers (within a template e.g. such as, but not limited to, curl, snarf, wget, pavuk, fget, fetch, lftp, aria2, HTTrack, iframe, rss and/or web part) The WCMS shall be able to provide an intuitive, user friendly interface to access and read reports. The solution shall also be able to catalogue the reports in a proper structure based on topic categories or other classification formulated by ECDC. Editing or adding to the classification must be an easy and straightforward task to do. Page 11

0355 0360 The WCMS shall have the ability to link to and present content feed from the Threat Tracking Tool (TTT). The portal shall be able to receive current outbreaks and threat alerts from TTT and publish the information. The portal shall be able to receive and publish geo-spatial content types from GIS systems which may include static, dynamic and interactive map rendering (via web services). 0365 The WCMS shall cater for the creation of branded sub-sites that have a different look and feel from the main site e.g. EAAD; ESCAIDE. 0370 0375 0380 0385 To be able to support mobile devices, the WCMS shall be able to dynamically render the presentation to fit screen size. While specific mobile friendly pages can be an option, dynamic rendering is a good feature since it does not relay on a specific presentation template or set of presentation templates. The WCMS will need to support a robust campaign function - this is the ability to rapidly develop and deploy a set of related content. This functionality maps well to supporting ECDC's mission in responding to a public health crises by making it easier to put together and publish content as a matter of urgency. The WCMS shall have a well defined framework for extending the functionality of the core product, by adding more modules. This will enable ECDC to request an additional module or set of modules without impacting either the core WCMS application or other modules already in service. The WCMS shall be able to support caching in a manner that content can be preloaded into memory to avoid hard disk requests - this is known to significantly speed up page serves. 0390 The WCMS shall be able to integrate with the Single Sign-On protocol at ECDC. 0395 The WCMS shall be able to work with Directory Services to manage users and their preferences. 0410 0415 The WCMS shall have the ability to look at past content (what was on the website at a specific date or date and time), and shall be able to support content re-use. The WCMS shall offer the following ease-of-use features: Friendly URL's Spell Checker Subscriptions Undo Preview Content before publishing Page 12

0420 0425 0430 0435 The WCMS shall provide the following security features: Audit Trail Captcha Login History Problem Notification SSL Support The WCMS shall be able to provide the following performance features: Advanced Caching Database Replication Load Balancing Page Caching The WCMS will support the following web management facilities: Content Scheduling Web Statistics The WCMS shall be able to offer the following built-in facilities: Document Managment Event Calendar Event Management FAQ Management Glossary Polls Syndicated Content (RSS) Page 13