Search engine - Request for Proposals pur1608/15

|
Request for Proposals pur1608/15
|
bet | 3/6 | Sana | 31.12.2019 | Hajmi | 0,69 Mb. | | #6778 | Turi | Request |
The Lucene search engine, included with Oracle WCS, is currently in use on the ebrd.com internet website. The Bank’s preference is to use this for the new intranet, but the capability of this search engine would need to be validated, in the context of its ability to deliver a robust and fully featured search experience incorporating, for example, the following requirements.
To explore options for configuration above and beyond the current simple ebrd.com implementation. In particular, autocomplete/suggestions for the search field, tolerance for minor misspellings and user access to own recent search history.
Minimal ongoing maintenance.
Implement analytics capabilities attached to the search engine, e.g. reports on search terms and behaviour.
Explore the possibility of federated search, for example, returning hits from both the website, EDRMS (see below) and the directory at the same time (i.e. within one set of search results). The minimum requirement would be for an intelligent and complementary format, e.g. a set of tabbed results for intranet pages, document and directory results.
Explore both technical and practical potential of having the search engine reference EDRMS content, to enable the major practical benefit of having all intranet documents housed within EDRMS.
If federated search is not possible (i.e. prohibitively costly / risky / complex), investigate the possibility of providing ability for users to set a preference for which search results they'd like to see by default or to open other search aspects by means of one click on the appropriate tab.
4.5 Integration with the Bank’s EDRMS
As stated above, the Bank uses Opentext Content Server CS10.5 (formerly Livelink) as the EDRMS repository for official Bank records, but there is minimal integration between the intranet and the document management system. During this refresh, there is a desire to ensure that there is a closer integration between the two systems, in order to gain efficiency advantages such as reduction in duplication, improvements in workflow around authoring and more relevant return of search results.
The following capabilities should be considered and reviewed for implementation.
The ability for content authors to drag/drop/include EDRMS documents to CKEditor.
The ability for content authors to select one or more EDRMS documents to a content attribute to be presented on a page as a list of documents.
The ability to make lists of links that include mix of EDRMS documents, internal and external links.
Links to the EDRMS documents to have the file type recognised by the system and appropriate file type icon to be added to the document links automatically.
Ideally other document meta-data will be added to the mouse over tooltip - for example: file size, version, author and a link to the EDRMS metadata screen.
Where a link to a EDRMS document is created but a document has expired or deleted, the users will be presented with a friendly message that document is not available
URLs of the EDRMS documents are not to be hard-coded in WebCenter Sites in case EDRMS base URL changes in the future.
All that applies to the EDRMS documents should apply to the EDRMS folders. Created hyperlinks will take users to the EDRMS web interface showing contents of the folder.
4.6 Development of interactive, per user, features.
Most of the applications within the Bank currently have some form of active directory (AD) based single sign-on (SSO) or at least simplified (network password synchronisation) authentication of users. As per the current trend with both internal and external sites, there is a desire to exploit the capabilities of WebCenter Sites to provide more targeted and relevant content to users to improve business efficiency. The extension of this SSO facility to user intranet access should therefore be extended in order to enable the following potential advantages.
Self-editing of a directory ‘profile’ page about the user, via the website and without needing any CMS access – see Appendix 2 – Figure 1.
Configurable homepage based on user tastes; User can opt to show/hide elements, reorder parts of page, or add regularly used links to a favourites bar – see Appendix 2 - Figure 2.
Configuration of news content to give additional weighting or reordering to content items based on particular tags that match user preferences
Explore implementation of some sort of per user customisation on homepage to show a set of user specific relevant links perhaps five recent pages visited, or notification that a page they own was commented on, etc.
Allow content authors to designate basic social interaction features to appear on certain pages (comments, ratings, votes, etc.), so that staff can once authenticated interact with the content.
Introduce other social components such as ‘walls’ that can be embedded on departmental homepages for users to post news and updates in the familiar and simple context of a social feed.
Possibly implement forum / message board functionality.
Tailored homepage widgets, so that users see e.g. local time and weather forecast dependent on either their current location (if this can be detected) or their typical location, as specified in that user’s preferences.
4.7 Browser Compatibility
There is a push at the EBRD for web-based apps (including Intranet content pages) to be supported by both desktop and mobile browsers. There is therefore a requirement for multi-device support to be provided in general for the pages served by the WCMS:
multi-device UI framework across tablet, mobile, desktop; and
Supporting responsive design at both page and UI component level and UI components able to render themselves based on screen space allowed.
Due to the lack of usability of the Documentum CMS, current Intranet content authoring and publishing is largely centralised within the Communications team. As a result there has been no need to include any significant authoring workflow and approval process.
The Bank would like to take advantage of the move to the simpler and richer usability available in Oracle WCS to decentralise authoring to departmental teams, with the Communications team providing guidance and oversight. To that end, a role based setup and authoring workflow should be enabled for Intranet pages with the following considerations.
Enable a system whereby CMS users have role-based publishing rights, with some subject to a simple workflow in order to publish, whilst others can publish directly.
Create a mechanism for general staff (i.e. non-content authors) to submit basic content that is then delivered through workflow to an editor, for approval and publishing. For example, a user pastes some content into a web form in a generic template, then a new page containing that content is automatically generated in Sites, and a designated content author(s) is notified with a production ready page which they can then push live or edit.
4.9 Portal integration (optional)
The Bank is running a parallel project to implement an Enterprise Portal and there is an expectation that the intranet will ultimately be surfaced through the portal, and therefore some integration of Oracle WCS with the portal would be necessary. The level of integration will need to be discussed and determined during the discovery phase, largely to agree the best approach, both in the short and longer term for search performance and personalisation aspects of the intranet.
The use of key functionality within the portal will need to be balanced against the complexity and risk introduced to ensure the timescales for delivery of the Intranet project are not jeopardised.
Review potential integration with the chosen portal supplier – interface to be confirmed pending the output of the portal proof of concept (PoC) outcome, which is scheduled to complete Q4 2016.
Explore the feasibility of integration with the portal via WebCenter Sites REST API/ATOM/CMIS protocols.
Explore use of the identity and access management (IAM) within the portal.
|
| |