Overview

Background

The current Polopoly search has limited functionality and isn’t easy to use, as such it needs to be improved in a number of areas.

The search features are spread over a number of different tabs. All searches cover all content (of certain type) within the system and there is no way to filter results for content within specific sections of the system. Users cannot search articles, sections and media bank resources at the same time. The main ‘Search’ tab has three options available through the following tabs:

1. Recently changed
2. Advanced
3. Locked

Within ‘Recently changed’ users can search on the following criteria:

• Type of content (Article or Section)
• Time of save - select from:
  • Latest hour
  • Latest 24 hours
  • Latest week
  • Latest month
• Saved by user - select from:
  • Saved by me
  • Saved by anyone

On this tab users can only select one criterion to search on.

Within ‘Advanced’ users can search on the following criteria:

• Type of content (Article or Section)
• Template type (different types of articles available)
• Name field
• Min/Max date
• Min/Max ID

On this tab users can select multiple criterions to search on.

Within ‘Locked’ users can search on the following criteria:

• Type of content (Article or Section)
• Locked by user - select from:
  • Locked by me
  • Locked by anyone

On this tab users can only select one criterion to search on.

Scope, Objectives and Deliverables

• Give the developer an initial degree of time to complete some R&D on the search functionality and to define what aspects of the functionality requested can be delivered and highlighted any simple enhancements that may have not be defined.
• Ensure that the necessary time is given to any new interface/layout that is proposed and allow usability testing to be completed.
• To consolidate all search functions onto a single tab in interface.
• To develop search function so any combination of criteria can be selected for a single search query.
• Allow search to be set at a specific point in the content tree so that it displays results from only the selected section.
• Use a fuzzy search on the ‘Name’ field.
• Introduce fuzzy search on ‘Title’ field.
• Ability to search on articles/sections saved by any individual user (based on UUN).
• Display total number of results rather than statement such as ‘at least 60 results’.
• Ability to search on orphaned article and sections.

Project Organisation

After planning is completed, the project will be suspended until the middle of December. After the Christmas break an initial R&D task of 5 days effort over 10 days will be conducted by Development Services and thereafter the next actions, and corresponding success criteria, will be defined. At that point an updated estimate of the work will be defined.

Success Criteria

• R&D to identify suitable aspects of the functionality to be improved. The subsequent success criteria are desirable, however are dependent on this.
• Improved search function, with usable and intuitive interface.
• Ability for users to search pages/sections within their specific section of the content tree on any combination of criteria covering:
  • Content/template type (different types of articles/section available, including media bank)
  • Name field (fuzzy search)
  • Title field (fuzzy search)
  • Min/Max date and time
  • Min/Max ID
  • UUN of last author on latest version
  • Review date
  • Workflow status (draft, ready for approval, published to live)
  • Disconnected from content tree
  • Locked articles/sections
• Ability for users to search workflows by UUN or group name.
• Ability for users to search groups by UUN or workflow name.
• For users to clearly see how many results a particular search has resulted in.
• Users should only be able to search article and section types that they have permission to access; core system files shouldn’t appear in results.