Library Website Redesign

University of Toronto Mississauga Library

Library Website Redesign

Functional Requirements

Version 1.3
April 8, 2009

Functional Requirements v 1.3 1 6/5/2009

 Library Website Redesign

Document History
Date Modifier Version Description

March 16, 2006 Susan Senese 1.0 Initial Document Created

March 17, 2009 Rochelle 1.1 Applied changes to the initial document

March 18, 2009 Rochelle 1.2 Applied changes to the edited document

April 9, 2009 Rochelle 1.3 Applied changes to the edited document

Functional Requirements v 1.3 2 6/5/2009

 Library Website Redesign

Table of Contents

1 FUNCTIONAL REQUIREMENTS...................................................................................................................7
1.1 OVERVIEW......................................................................................................................................................7
1.2 PRIORITIES......................................................................................................................................................7
2 FUNCTIONALITY .............................................................................................................................................8
2.1 USER MANAGEMENT ......................................................................................................................................8
2.1.1 Description ............................................................................................................................................8
2.1.2 Functional Requirement List .................................................................................................................8
2.1.3 User Interface Functions / Interaction...................................................................................................8
2.1.4 Error Handling ......................................................................................................................................8
2.1.5 Assumptions ...........................................................................................................................................8
2.2 TEXT SIZING ...................................................................................................................................................9
2.2.1 Description ............................................................................................................................................9
2.2.2 Functional Requirement List .................................................................................................................9
2.2.3 User Interface Functions / Interaction...................................................................................................9
2.2.4 Assumptions ...........................................................................................................................................9
2.3 AUTHENTICATION ..........................................................................................................................................9
2.3.1 Description ............................................................................................................................................9
2.3.2 Functional Requirement List .................................................................................................................9
2.3.3 User Interface Functions / Interaction.................................................................................................10
2.3.4 Assumptions .........................................................................................................................................10
2.4 SEARCH – CATALOGUE.................................................................................................................................10
2.4.1 Description ..........................................................................................................................................10
2.4.2 Functional Requirement List ...............................................................................................................10
2.4.3 User Interface Functions / Interaction.................................................................................................10
2.4.4 Assumptions .........................................................................................................................................11
2.5 SEARCH – SCHOLAR’S PORTAL.....................................................................................................................11
2.5.1 Description ..........................................................................................................................................11
2.5.2 Functional Requirement List ...............................................................................................................11
2.5.3 User Interface Functions / Interaction.................................................................................................11
2.5.4 Assumptions .........................................................................................................................................12
2.6 SEARCH – PAST EXAMS ................................................................................................................................12
2.6.1 Description ..........................................................................................................................................12
2.6.2 Functional Requirement List ...............................................................................................................12
2.6.3 User Interface Functions / Interaction.................................................................................................12
2.6.4 Error Handling ....................................................................................................................................12
2.6.5 Assumptions .........................................................................................................................................12
2.7 SEARCH – WEBSITE ......................................................................................................................................13
2.7.1 Description ..........................................................................................................................................13
2.7.2 Functional Requirement List ...............................................................................................................13
2.7.3 User Interface Functions / Interaction.................................................................................................13
2.7.4 Assumptions .........................................................................................................................................13
2.8 SEARCH - RESERVES .....................................................................................................................................14
2.8.1 Description ..........................................................................................................................................14
2.8.2 Functional Requirement List ...............................................................................................................14
2.8.3 User Interface Functions / Interaction.................................................................................................14
2.8.4 Error Handling ....................................................................................................................................14
2.8.5 Assumptions .........................................................................................................................................14
2.9 SEARCH – GOOGLE SCHOLAR .......................................................................................................................14
2.9.1 Description ..........................................................................................................................................14
2.9.2 Functional Requirement List ...............................................................................................................15
2.9.3 User Interface Functions / Interaction.................................................................................................15

Functional Requirements v 1.3 3 6/5/2009

 Library Website Redesign

2.9.4 Assumptions .........................................................................................................................................15

2.10 E-JOURNAL MANAGEMENT ..........................................................................................................................15
2.10.1 Description ..........................................................................................................................................15
2.10.2 Functional Requirement List ...............................................................................................................15
2.10.3 User Interface Functions / Interaction.................................................................................................16
2.10.4 Assumptions .........................................................................................................................................16
2.11 LIBRARY HOURS...........................................................................................................................................16
2.11.1 Description ..........................................................................................................................................16
2.11.2 Functional Requirement List ...............................................................................................................16
2.11.3 User Interface Functions / Interaction.................................................................................................17
2.11.4 Error Handling ....................................................................................................................................17
2.11.5 Assumptions .........................................................................................................................................17
2.12 STAFF DIRECTORY........................................................................................................................................17
2.12.1 Description ..........................................................................................................................................17
2.12.2 Functional Requirement List ...............................................................................................................17
2.12.3 User Interface Functions / Interaction.................................................................................................18
2.12.4 Assumptions .........................................................................................................................................18
2.13 WORKSTATION AVAILABILITY .....................................................................................................................18
2.13.1 Description ..........................................................................................................................................18
2.13.2 Functional Requirement List ...............................................................................................................18
2.13.3 User Interface Functions / Interaction.................................................................................................18
2.13.4 Error Handling ....................................................................................................................................19
2.13.5 Assumptions .........................................................................................................................................19
2.14 LOANER LAPTOP (EQUIPMENT) AVAILABILITY DISPLAY .............................................................................19
2.14.1 Description ..........................................................................................................................................19
2.14.2 Functional Requirement List ...............................................................................................................19
2.14.3 User Interface Functions / Interaction.................................................................................................19
2.14.4 Error Handling ....................................................................................................................................20
2.14.5 Assumptions .........................................................................................................................................20
2.15 STUDY SPACE AVAILABILITY DISPLAY ........................................................................................................20
2.15.1 Description ..........................................................................................................................................20
2.15.2 Functional Requirement List ...............................................................................................................20
2.15.3 User Interface Functions / Interaction.................................................................................................20
2.15.4 Error Handling ....................................................................................................................................20
2.15.5 Assumptions .........................................................................................................................................20
2.16 BLOGGING APPLICATION ..............................................................................................................................21
2.16.1 Description ..........................................................................................................................................21
2.16.2 Functional Requirement List ...............................................................................................................21
2.16.3 User Interface Functions / Interaction.................................................................................................22
2.16.4 Assumptions .........................................................................................................................................22
2.17 FAQ .............................................................................................................................................................22
2.17.1 Description ..........................................................................................................................................22
2.17.2 Functional Requirement List ...............................................................................................................22
2.17.3 User Interface Functions / Interaction.................................................................................................23
2.17.4 Assumptions .........................................................................................................................................23
2.18 EVENTS CALENDAR ......................................................................................................................................23
2.18.1 Description ..........................................................................................................................................23
2.18.2 Functional Requirement List ...............................................................................................................23
2.18.3 User Interface Functions / Interaction.................................................................................................24
2.18.4 Error Handling ....................................................................................................................................24
2.18.5 Assumptions .........................................................................................................................................24
2.19 CONTENT AGGREGATION - TWITTER ............................................................................................................25
2.19.1 Description ..........................................................................................................................................25
2.19.2 Functional Requirement List ...............................................................................................................25
2.19.3 User Interface Functions / Interaction.................................................................................................25
2.19.4 Assumptions .........................................................................................................................................26

Functional Requirements v 1.3 4 6/5/2009

 Library Website Redesign

2.20 CONTENT AGGREGATION – RSS FEED DISPLAY ...........................................................................................26

2.20.1 Description ..........................................................................................................................................26
2.20.2 Functional Requirement List ...............................................................................................................26
2.20.3 User Interface Functions / Interaction.................................................................................................27
2.20.4 Assumptions .........................................................................................................................................27
2.21 CONTENT AGGREGATION – INTERNAL RSS FEEDS .......................................................................................27
2.21.1 Description ..........................................................................................................................................27
2.21.2 Functional Requirement List ...............................................................................................................27
2.21.3 Assumptions .........................................................................................................................................27
2.22 CITATION / BIBLIOGRAPHY ...........................................................................................................................28
2.22.1 Description ..........................................................................................................................................28
2.22.2 Functional Requirement List ...............................................................................................................28
2.22.3 User Interface Functions / Interaction.................................................................................................28
2.22.4 Assumptions .........................................................................................................................................28
2.23 WYSIWYG EDITING ...................................................................................................................................29
2.23.1 Description ..........................................................................................................................................29
2.23.2 Functional Requirement List ...............................................................................................................29
2.23.3 User Interface Functions / Interaction.................................................................................................29
2.23.4 Assumptions .........................................................................................................................................30
2.24 CONTENT EXPIRATION .................................................................................................................................30
2.24.1 Description ..........................................................................................................................................30
2.24.2 Functional Requirement List ...............................................................................................................30
2.24.3 User Interface Functions / Interaction.................................................................................................30
2.24.4 Assumptions .........................................................................................................................................30
2.25 POLLS ...........................................................................................................................................................31
2.25.1 Description ..........................................................................................................................................31
2.25.2 Functional Requirement List ...............................................................................................................31
2.25.3 User Interface Functions / Interaction.................................................................................................31
2.25.4 Assumptions .........................................................................................................................................31
2.26 SURVEYS ......................................................................................................................................................31
2.26.1 Description ..........................................................................................................................................31
2.26.2 Functional Requirement List ...............................................................................................................32
2.26.3 User Interface Functions / Interaction.................................................................................................32
2.26.4 Assumptions .........................................................................................................................................32
2.27 COMMUNICATION TOOLS - CHAT .................................................................................................................33
2.27.1 Description ..........................................................................................................................................33
2.27.2 Functional Requirement List ...............................................................................................................33
2.27.3 User Interface Functions / Interaction.................................................................................................33
2.27.4 Assumptions .........................................................................................................................................33
2.28 COMMUNICATIONS TOOLS – DISCUSSION BOARDS.......................................................................................34
2.28.1 Description ..........................................................................................................................................34
2.28.2 Functional Requirement List ...............................................................................................................34
2.28.3 User Interface Functions / Interaction.................................................................................................35
2.28.4 Assumptions .........................................................................................................................................35
2.29 COMMUNICATION TOOLS - COMMENTS ........................................................................................................36
2.29.1 Description ..........................................................................................................................................36
2.29.2 Functional Requirement List ...............................................................................................................36
2.29.3 User Interface Functions / Interaction.................................................................................................36
2.29.4 Assumptions .........................................................................................................................................36
2.30 COLLABORATIVE TOOLS – UPLOAD AND SHARE FILES ................................................................................37
2.30.1 Description ..........................................................................................................................................37
2.30.2 Functional Requirement List ...............................................................................................................37
2.30.3 User Interface Functions / Interaction.................................................................................................37
2.30.4 Assumptions .........................................................................................................................................37
2.31 COLLABORATIVE TOOLS – WIKIS .................................................................................................................37
2.31.1 Description ..........................................................................................................................................37

Functional Requirements v 1.3 5 6/5/2009

 Library Website Redesign

2.31.2 Functional Requirement List ...............................................................................................................37

2.31.3 User Interface Functions / Interaction.................................................................................................38
2.31.4 Assumptions .........................................................................................................................................39
2.32 COLLABORATIVE TOOLS – WEBSITE ANNOTATION ......................................................................................39
2.32.1 Description ..........................................................................................................................................39
2.32.2 Functional Requirement List ...............................................................................................................39
2.32.3 User Interface Functions / Interaction.................................................................................................40
2.32.4 Assumptions .........................................................................................................................................40
2.33 BOOK REVIEWS ............................................................................................................................................40
2.33.1 Description ..........................................................................................................................................40
2.33.2 Functional Requirement List ...............................................................................................................40
2.33.3 User Interface Functions / Interaction.................................................................................................41
2.33.4 Assumptions .........................................................................................................................................41
2.34 TAGGING / CATEGORIES ...............................................................................................................................42
2.34.1 Description ..........................................................................................................................................42
2.34.2 Functional Requirement List ...............................................................................................................42
2.34.3 User Interface Functions / Interaction.................................................................................................42
2.34.4 Assumptions .........................................................................................................................................43
2.35 PRINTER-FRIENDLY ......................................................................................................................................43
2.35.1 Description ..........................................................................................................................................43
2.35.2 Functional Requirements List ..............................................................................................................43
2.35.3 User Interface Functions / Interaction.................................................................................................43
2.35.4 Assumptions .........................................................................................................................................45
2.36 QUIZZES .......................................................................................................................................................45
2.36.1 Description ..........................................................................................................................................45
2.36.2 Functional Requirements List ..............................................................................................................45
2.36.3 User Interface Functions / Interaction.................................................................................................46
2.36.4 Error Handling ....................................................................................................................................48
2.36.5 Assumptions .........................................................................................................................................48
2.37 PODCASTING DELIVERY SUPPORT ................................................................................................................48
2.37.1 Description ..........................................................................................................................................48
2.37.2 Functional Requirements List ..............................................................................................................48
2.37.3 User Interface Functions / Interaction.................................................................................................48
2.37.4 Assumptions .........................................................................................................................................48
2.38 FAVOURITES .................................................................................................................................................49
2.38.1 Description ..........................................................................................................................................49
2.38.2 Functional Requirements List ..............................................................................................................49
2.39 GOOGLE ANALYTICS ....................................................................................................................................49
2.39.1 Description ..........................................................................................................................................49
2.39.2 Functional Requirements List ..............................................................................................................49
2.40 SYSTEMS STATUS .........................................................................................................................................49
2.40.1 Description ..........................................................................................................................................49
2.40.2 Functional Requirements List ..............................................................................................................49

Functional Requirements v 1.3 6 6/5/2009

 Library Website Redesign

1 Functional Requirements

1.1 Overview
This document presents the functionality requirements for the University of Toronto Mississauga Library
Website Redesign project. The functional requirements define the functions that the system must perform in
order to enable the business activities defined in the Business Requirements document.

1.2 Priorities
The prioritization categories are as follows:

Priority 1 – Required

Priority 2 – Desired

Priority 3 – Optional

Functional Requirements v 1.3 7 6/5/2009

 Library Website Redesign

2 Functionality

2.1 User Management

2.1.1 Description

The user management functionality component supports a granular approach to user management for website
content contributors.

2.1.2 Functional Requirement List

The user management functionality component has the following requirements:

Functional Requirement Priority

1. The system owner must have the ability to create multiple user groups 1

2. The system owner must have the ability to assign rights and functionality to user groups 1

3. The system owner must have the ability to designate pages for user group content creation/editing 1

4. The system owner can alter the user interface based on user group 2

2.1.3 User Interface Functions / Interaction

• Clean, clear user interface for the system administrator

2.1.4 Error Handling

• To be determined by existing modules.

2.1.5 Assumptions

• Most user management tasks will be accomplished via direct database interaction by scripts

• Library staff user management will be managed manually via the web interface

• A layer between the Drupal users database will import user data from a UTORauth (or other) dump at
regular intervals

• Owner will be able to create new roles for users after the installation period

• Sufficient user management tools exist within Drupal.

Functional Requirements v 1.3 8 6/5/2009

 Library Website Redesign

2.2 Text Sizing

2.2.1 Description

The text sizing functionality component allows users of the site to adjust the display size of text to better
accommodate their viewing preferences.

2.2.2 Functional Requirement List

The text sizing functionality component has the following requirements:

Functional Requirement Priority

5. The user must be able to change the font size of any page through the browser. 1

2.2.3 User Interface Functions / Interaction

2.2.4 Assumptions

o The vendor will allow for altering font sizes as part of the overall design.

2.3 Authentication

2.3.1 Description

The authentication functionality component allows users to log into the site using their UTORid and password and
be presented with a website constructed based on their user roles, preferences, courses, and program.

2.3.2 Functional Requirement List

The authentication functionality component has the following requirements:

Functional Requirement Priority

1. Authenticate to an external database using Kerberos or CAS 1

Functional Requirements v 1.3 9 6/5/2009

 Library Website Redesign

2. Key information (name, course enrollments, program) will feed into drupal db 1

3. Users cannot change their password in Drupal 1

4. No password information stored in Drupal db 1

2.3.3 User Interface Functions / Interaction

• Login replaced by local login solution (currently pubcookie or CAS)

2.3.4 Assumptions

• Local id integration is possible without months of work effort

• Local programming assistance is available to help implement this solution

2.4 Search – Catalogue

2.4.1 Description

The search catalogue functionality component allows users of the site to search the UTL catalogue for print and
eResources.

2.4.2 Functional Requirement List

The search functionality component has the following requirements:

Functional Requirement Priority

1. Search box looks integrated to the main website, but is actually searching an external database 1
(Sirsi/Endeca)

2. Default search perimeters to be determined by system owner 1

2.4.3 User Interface Functions / Interaction

Functional Requirements v 1.3 10 6/5/2009

 Library Website Redesign

2.4.4 Assumptions

• We can design the catalogue search as we like without conforming to style rules from Endeca/Sirsi

• We can place the catalogue search high on the page without interfering with other functions or theme
constraints

2.5 Search – Scholar’s Portal

2.5.1 Description

The search – Scholar’s Portal functionality component allows users of the site to search the scholar’s portal database
for articles.

2.5.2 Functional Requirement List

The search – Scholar’s Portal functionality component has the following requirements:

Functional Requirement Priority

1. Search interface looks similar to catalogue interface 2

2. Search begins on the website and transfers the user to the scholar’s portal results 1

2.5.3 User Interface Functions / Interaction

• Clean, clear user interface

Functional Requirements v 1.3 11 6/5/2009

 Library Website Redesign

2.5.4 Assumptions

• Scholar’s Portal search will be visible depending on whether it’s chosen by librarians for inclusion in a
generic profile

• Scholar’s Portal will be part of a non-login version of the library’s webpage

2.6 Search – Past Exams

2.6.1 Description

The search –past exams functionality component allows users of the site to search ERes for past exams.

2.6.2 Functional Requirement List

The search – past exams functionality component has the following requirements:

Functional Requirement Priority

1. System checks to see what courses a student is enrolled in and offers those course codes as prompts 3

2. Search starts on the website and displays results in ERes 1

3. Search can be relocated to more prominent locations on the main website or deeper, organic course- 3
related parts of the site as needed

4. Search looks similar to catalogue and other searches on the website 1

2.6.3 User Interface Functions / Interaction

• Similar to basic search look/feel on the rest of the site

2.6.4 Error Handling

• Fails gracefully; doesn’t prevent the rest of the page from loading

• Loads independently when displaying auto-generated links

2.6.5 Assumptions

• We have the ability to link directly to results within ERes

• We can create an external search via html that will produce valid ERes results

Functional Requirements v 1.3 12 6/5/2009

 Library Website Redesign

2.7 Search – Website

2.7.1 Description

The search – website functionality component allows users of the site to search the Library website.

2.7.2 Functional Requirement List

The search - website functionality component has the following requirements:

Functional Requirement Priority

1. Allow users to search the website and receive relevant search results 1

2. Results give preference to nodes tagged with keywords 2

2.7.3 User Interface Functions / Interaction

2.7.4 Assumptions

• Internal search within Drupal is robust and preferable (Google custom search not superior)

Functional Requirements v 1.3 13 6/5/2009

 Library Website Redesign

2.8 Search - Reserves

2.8.1 Description

The Search - Reserves functionality component allows users of the site to easily access Reserves materials for
courses.

2.8.2 Functional Requirement List

The Search - Reserves functionality component has the following requirements:

Functional Requirement Priority

1. Simple search function that appears prominently on the main website 1

2. Sends a search request to ERes and displays back all reserve material for a course 1

3. When used on login, displays links to all available reserves lists from the courses in which the user 3
is enrolled (undergraduate)

2.8.3 User Interface Functions / Interaction

• Simple, clean interface

2.8.4 Error Handling

• Fails gracefully; doesn’t prevent the rest of the page from loading

• Loads auto-generated links separately from the rest of the page

2.8.5 Assumptions

• ERes will produce stable links per course to which we can link

• Website search can send a search query to ERes and produce results

• Results can show within ERes, but would ideally be reformatted and shown within the website

2.9 Search – Google Scholar

2.9.1 Description

The search - Google functionality component allows users of the site to perform a search using the Google Scholar
search function to find locally available materials.

Functional Requirements v 1.3 14 6/5/2009

 Library Website Redesign

2.9.2 Functional Requirement List

The search - Google functionality component has the following requirements:

Functional Requirement Priority

1. Allow users to use google scholar to find U of T materials.

2. Have google search results appear embedded in the website page. 1

2.9.3 User Interface Functions / Interaction

2.9.4 Assumptions

• Library staff will accept a google scholar link on the library’s website

• Google scholar link could be added by the user

• Google scholar link could be added as part of a portal package, and not by default

• Google scholar link could be added to a generic main page

• Google scholar search link would not be difficult to include

2.10 E-Journal Management

2.10.1 Description

The E-journal management functionality component allows the website owner to create and manage e-journals, with
RSS subscription, reviewing tools, and comments.

2.10.2 Functional Requirement List

The e-journal management availability functionality component has the following requirements:

Functional Requirements v 1.3 15 6/5/2009

 Library Website Redesign

Functional Requirement Priority

1. Separate CSS design for each journal, and independent of the site’s CSS

2. Ability to submit and review material for the journal

3. Tagging for articles and issues

4. Clean URLs for journals, issues, and articles

5. Unique URLs for individual articles

6. User comments on articles

7. Ability to host multiple journals

2.10.3 User Interface Functions / Interaction

• Simple, clean user interface

2.10.4 Assumptions

• E-journal management could be used in house to manage elements of the website, including Foreword

• Library staff could employ this tool in the future as part of their communication to faculty and students

• A drupal module already exists to provide this functionality

2.11 Library Hours

2.11.1 Description

The library hours functionality component allows users of the site to quickly determine library hours.

2.11.2 Functional Requirement List

The library hours functionality component has the following requirements:

Functional Requirement Priority

1. Displays today’s library hours in a prominent location on the website 1

2. Link to a listing of all library hours 1

Functional Requirements v 1.3 16 6/5/2009

 Library Website Redesign

3. Today’s library hours can be displayed on the library’s digital signage 2

2.11.3 User Interface Functions / Interaction

2.11.4 Error Handling

• Fails gracefully, defaulting to a link to hours if the auto-generated hours statement cannot load.

2.11.5 Assumptions

• We can simply create a database of the library’s hours that the website can draw from based on date

• There is a module within Drupal to help us accomplish this

2.12 Staff Directory

2.12.1 Description

The staff directory functionality component allows users to browse all library staff profiles.

2.12.2 Functional Requirement List

The staff directory functionality component has the following requirements:

Functional Requirement Priority

1. Automatically updates when new library staff profiles are added or removed 1

2. Contains subcategories of types of library staff 2

Functional Requirements v 1.3 17 6/5/2009

 Library Website Redesign

2.12.3 User Interface Functions / Interaction

• Clean, simple user interface

2.12.4 Assumptions

• Staff directory would not be prominent on the website, but would act as a last-chance attempt to find a
specific person if all other available options have failed.

• Directory of users by role comes with a basic Drupal installation

2.13 Workstation Availability

2.13.1 Description

The workstation availability functionality component allows users of the site to quickly locate online an available
workstation in the library.

2.13.2 Functional Requirement List

The workstation availability functionality component has the following requirements:

Functional Requirement Priority

1. Website displays existing flash application 1

(http://firedome.utm.utoronto.ca:8080/public/labmap_list.jsp#)

2.13.3 User Interface Functions / Interaction

Functional Requirements v 1.3 18 6/5/2009

 Library Website Redesign

2.13.4 Error Handling

• Standard failure to load protocol TBA

2.13.5 Assumptions

• Labstats application will produce practically-sized flash or image content to embed in library’s website

2.14 Loaner Laptop (Equipment) Availability Display

2.14.1 Description

The loaner laptop (equipment) availability display functionality component allows users of the site to quickly
determine availability of a loaner laptop in the library. The loan information is kept in our Sirsi catalogue, and
available via a web interface without a login.

2.14.2 Functional Requirement List

The loaner laptop availability functionality component has the following requirements:

Functional Requirement Priority

1. Connects to Sirsi to gather information on which laptops are available for loan via: 1

a. http://search2.library.utoronto.ca/UTL/search.jsp

b. Click “course reserves”

c. Search for “equipment UTM”, click “course code”

d. STL Reserves, UTM

e. Click “details” at UTML LAPTOP

2. Displays: “X laptops are available. Next laptop due at: X:XX. Click here for more information.” 2

3. “More information” link should display all due dates on loaned laptops in a user-friendly fashion. 3

4. Information can be displayed on the library’s digital signage. 2

2.14.3 User Interface Functions / Interaction

Simple, clean display.

Functional Requirements v 1.3 19 6/5/2009

 Library Website Redesign

2.14.4 Error Handling

• Fails gracefully; provides a link to information about loaner laptops if the applicaton cannot load

• Does not prevent the rest of the page from loading

2.14.5 Assumptions

• Data format will remain static

• If no permanent link is available, the navigational process will remain static.

2.15 Study Space Availability Display

2.15.1 Description

The study space availability display functionality component allows users of the site to quickly determine available
study spaces in the library.

2.15.2 Functional Requirement List

The study space availability functionality component has the following requirements:

Functional Requirement Priority

1. Displays different video feeds from of study areas on rotation 1

3. Location of each video feed is clearly labeled 1

2.15.3 User Interface Functions / Interaction

Simple, clean interface.

2.15.4 Error Handling

• Fails gracefully; if the application fails, it is replaced by a static picture and a link to a page containing all
the webcam feeds.

2.15.5 Assumptions

• Feeds from each camera have unique URLs.

• Cameras can be set up in 8 places throughout the library

Functional Requirements v 1.3 20 6/5/2009

 Library Website Redesign

• Feeds can be managed into one application

• View can be blurred enough to obscure individuals but display available study space

• A drupal module or third party application exists to assist with this objective

2.16 Blogging Application

2.16.1 Description

The blogging functionality component allows the Library to easily update library patrons of items of current interest
via blogging format; the blogging functionality allows users of the site to view library created blogs of interest to
them.

2.16.2 Functional Requirement List

The blogging functionality component has the following requirements:

Functional Requirement Priority

1. Must support multiple blogs by multiple authors 1

2. Must have categories and/or tags attributable to each post 1

3. Group blogs can be generated by pulling all posts using a particular tag 3

4. Must support embedded video (youtube, etc.) 1

5. Must have flexible design tools to allow users to add elements to the sidebar 2

6. Must store archived posts in an easily-browsed manner 1

7. Must be searchable 1

8. Displays used tags as a tag cloud 2

9. Must support user comments and comment moderation 1

10. Supports embedded video posts and comments (seesmic) 3

11. Employs categories, allowing posts by all users to be viewed by category 2

12. Employs free-form tags users can add to posts 3

Functional Requirements v 1.3 21 6/5/2009

 Library Website Redesign

2.16.3 User Interface Functions / Interaction

2.16.4 Assumptions

• The library’s website will house multiple blogs

• Many library staff will have individual blogs on which they report on their thoughts and activities

• Posts that need to be promoted to the front page could come from any blog

• Category views will be more useful to the average user than individual blog views

• Categories will be predetermined and chooseable; tags are free-form

• A fully-featured blogging module exists for Drupal installations

2.17 FAQ

2.17.1 Description

The FAQ functionality component allows users of the site to easily generate an FAQ on any topic.

2.17.2 Functional Requirement List

The FAQ functionality component has the following requirements:

Functional Requirements v 1.3 22 6/5/2009

 Library Website Redesign

Functional Requirement Priority

1. Allow users to create a question/answer formatted document 1

1. Allow users to place such a document within any group of documents, linked to any group of 1
documents

2.17.3 User Interface Functions / Interaction

• Clean, simple interface

• Style dictated by a pre-designed stylesheet

2.17.4 Assumptions

• FAQ pages will be created by library staff or by users

• FAQ pages created by students may require moderation or proof-reading for accuracy

• There is an existing FAQ module for Drupal

2.18 Events Calendar

2.18.1 Description

The events calendar functionality component allows users of the site to see events and schedules relating to the
library.

2.18.2 Functional Requirement List

The events calendar functionality component has the following requirements:

Functional Requirement Priority

1. Displays the reference schedule, with links to reference staff profiles 2

2. Displays in a monthly calendar format 2

3. Library staff can add events 1

4. View can be modified based on user or page: public view (events) and a view based on user, 1
location (reference schedule)

Functional Requirements v 1.3 23 6/5/2009

 Library Website Redesign

2.18.3 User Interface Functions / Interaction

2.18.4 Error Handling

• Fails gracefully; doesn’t prevent the rest of the page from loading if the calendar fails.

2.18.5 Assumptions

• Calendar events are only added by library staff

• Calendar will display the reference schedule

• There are a variety of Drupal elements and modules that can be used to produce an events calendar

• Calendar data will be inputted manually, and is also available in CSV

Functional Requirements v 1.3 24 6/5/2009

 Library Website Redesign

2.19 Content Aggregation - Twitter

2.19.1 Description

The content aggregation-twitter functionality component allows library staff to easily embed twitter posts.

2.19.2 Functional Requirement List

The content aggregation-twitter functionality component has the following requirements:

Functional Requirement Priority

1. Allows users to post to twitter from an interface on the website 3

2. Allows users to easily populate sidebars of pages with the most recent twitter posts from specific 1
library twitter accounts

3. Twitter updates on the main page only appear when they are current (today’s date) 2

2.19.3 User Interface Functions / Interaction

Functional Requirements v 1.3 25 6/5/2009

 Library Website Redesign

2.19.4 Assumptions

• The library will have multiple twitter feeds

• Some twitter feeds will appear on the main page, some will not

• Library staff can have a personal twitter feed if they like

• Library staff can have their twitter feed appear in multiple places as need warrants

• There is a Drupal/Twitter integration module already available; if not, Drupal will allow us to drop in
Twitter badges

2.20 Content Aggregation – RSS Feed Display

2.20.1 Description

The content aggregation-RSS Feed Display functionality component allows users of the site to add external content
to the website.

2.20.2 Functional Requirement List

The content aggregation-RSS Feed Display functionality component has the following requirements:

Functional Requirement Priority

1. Allows library staff to add an RSS feed, and have the content of that RSS feed display, as node 1

2. The RSS feed content will conform to the local stylesheet 1

Functional Requirements v 1.3 26 6/5/2009

 Library Website Redesign

3. External content must be available to appear on library staff profiles 1

4. Ability for library staff to delete the feed 2

2.20.3 User Interface Functions / Interaction

• Text box where library staff can enter an RSS/Atom feed

• Button to delete the feed

2.20.4 Assumptions

• Librarians may add content to their profiles, or to pages created to assist students with assignments or
resources.

• Feeds will likely not be added permanently

• There is an existing RSS reader module for Drupal

2.21 Content Aggregation – Internal RSS Feeds

2.21.1 Description

The content aggregation-internal RSS Feeds functionality component allows users of the site to take content from
the library’s website and aggregate it into other websites.

2.21.2 Functional Requirement List

The content aggregation-internal RSS Feeds functionality component has the following requirements:

Functional Requirement Priority

1. Allows content creators to create RSS feeds based on a tag, a user, or a section of the website. 1

2.21.3 Assumptions

• Internal RSS feeds will be employed exclusively by systems, computing services or other website design
staff

• Internal RSS feeds will appear on digital signage and possibly other UTM or library websites

• Drupal natively supports this kind of granular RSS feed creation

Functional Requirements v 1.3 27 6/5/2009

 Library Website Redesign

2.22 Citation / Bibliography

2.22.1 Description

The citation / bibliography functionality component allows users of the site to create bibliographies to share with the
community.

2.22.2 Functional Requirement List

The citation / bibliography functionality component has the following requirements:

Functional Requirement Priority

1. Allows users to add items to a shared or personal public bibliography 3

2. Prompts users to add tags to each item in a bibliography 3

3. Allows users to heavily annotate each item using a WYSIWYG interface 3

4. Allow users to auto-generate bibliographies based on one or more tags 3

2.22.3 User Interface Functions / Interaction

2.22.4 Assumptions

• This tool could be available for students as part of assignments;

• This tool could allow librarians to create collections of resources for students;

• There is an existing Drupal module that will support this objective.

Functional Requirements v 1.3 28 6/5/2009

 Library Website Redesign

2.23 WYSIWYG Editing

2.23.1 Description

The WYSIWYG editing functionality component allows users of the site to not know or use any HTML code to
create rich document. The WYSIWYG editor should be bypassable so that advanced users can insert code (twitter
badges, etc.)

2.23.2 Functional Requirement List

The WYSIWYG editing functionality component has the following requirements:

Functional Requirement Priority

1. Allows content creators to insert basic style elements (bold, italics, tables, bullets) into a node 1
without the use of raw code

2. Ability to embed youtube videos 1

3. Image, video and audio upload support 1

2.23.3 User Interface Functions / Interaction

Functional Requirements v 1.3 29 6/5/2009

 Library Website Redesign

2.23.4 Assumptions

• We will be able to choose from a range of WYSIWYG options already created for Drupal installations

• We will be able to choose a WYSIWYG editor that allows for copying and pasting from Word documents
without getting thrown by all the additional Word code

2.24 Content Expiration

2.24.1 Description

The content expiration functionality component allows content creators to set their data to disappear and/or become
less relevant in a search after a set time.

2.24.2 Functional Requirement List

The content expiration functionality component has the following requirements:

Functional Requirement Priority

1. Allows content creator to set the expiry date of all created material 3

2. Demotes expired content in current searches (find content related to current course before that of a 3
previous course)

3. Stores expired material and clearly labels it expired 3

4. Displays the document’s creation date 3

2.24.3 User Interface Functions / Interaction

• Allow users to easily choose a date by which the content will have expired

2.24.4 Assumptions

• Content expiration removes elements from prominent view, but doesn’t prevent them from being found at
all

• Content expiration demotes content inside a search

• Content expiration makes the date of the content very prominent

• Content expiration functionality is available for Drupal installations via an existing module.

Functional Requirements v 1.3 30 6/5/2009

 Library Website Redesign

2.25 Polls

2.25.1 Description

The polls functionality component allows content contributors to engage the users of the site to get their feedback on
single topics or questions; to poll for a response.

2.25.2 Functional Requirement List

The polls functionality component has the following requirements:

Functional Requirement Priority

1. Allows library staff to easily and simply create polls 1

2. Allows each user to vote only once 1

3. Can be included in any kind of node or page 1

4. Fits easily into a sidebar 1

2.25.3 User Interface Functions / Interaction

2.25.4 Assumptions

• Polls would be created by library staff and only occasionally appear on the main library page

• Poll creation interface already exists for Drupal

2.26 Surveys

2.26.1 Description

The surveys functionality component allows content contributors to engage the users of the site to gather and
analyze data for multiple questions.

Functional Requirements v 1.3 31 6/5/2009

 Library Website Redesign

2.26.2 Functional Requirement List

The surveys functionality component has the following requirements:

Functional Requirement Priority

1. Allows each user to take the survey only once 1

2. Tracks email addresses of survey takers, in order to contact draw winners 1

3. Anonymizes responses 1

4. Allows for a wide variety of question types 1

5. Supports images, audio, video and html as part of the questions 3

6. Includes a survey building tool that allows content creators to easily generate surveys without code 1

2.26.3 User Interface Functions / Interaction

2.26.4 Assumptions

• A tool exists that allows users of Drupal to create robust surveys

• Use of the survey creation tool can be limited to a select number of users

Functional Requirements v 1.3 32 6/5/2009

 Library Website Redesign

2.27 Communication Tools - Chat

2.27.1 Description

The chat functionality component allows users of the site to engage in text chat with other users. University of
Toronto Mississauga has an existing Jabber server that can be employed if needed.

2.27.2 Functional Requirement List

The chat functionality component has the following requirements:

Functional Requirement Priority

1. Widget on any website that allows users to contact any specified account 1

2. Optional desktop management of chat (client based) 2

3. Audio/video chat support 3

4. Ability to create multi-user chatrooms 1

5. No storage of chat logs/transcripts 1

2.27.3 User Interface Functions / Interaction

2.27.4 Assumptions

• Mutiple chat widgets leading to a few specific chat accounts

• Drupal supports a variety of text chat options via an existing module; if it does not, that third party products
(including proprietary sources, ie, LivePerson) can be employed to support this objective

• Multiple drupal modules exist to support chat, both text and audio/video

Functional Requirements v 1.3 33 6/5/2009

 Library Website Redesign

2.28 Communications Tools – Discussion Boards

2.28.1 Description

The discussion board functionality component allows users of the site to contribute to various discussion boards.

2.28.2 Functional Requirement List

The discussion board functionality component has the following requirements:

Functional Requirement Priority

1. Simple and intuitive user interface 1

2. Ability to reply directly to a comment (threaded) 1

3. Ability to subscribe to a thread or forum 3

4. Ability to restrict access to discussion boards based on user role or course/program enrollment 1

5. Ability to easily remove all content from discussion boards after a certain date 2

6. Allows users to post and reply to topics 1

7. Allows users to remove their own posts 1

8. Allows users to create threads/topics 1

9. Individual users can be blocked 1

10. Individual user’s posts can be moderated (not posted until approved by a moderator) 1

Functional Requirements v 1.3 34 6/5/2009

 Library Website Redesign

2.28.3 User Interface Functions / Interaction

2.28.4 Assumptions

• Library has the staff to effectively moderate discussion boards

• A tool exists within Drupal that allows sites to support discussion boards

Functional Requirements v 1.3 35 6/5/2009

 Library Website Redesign

2.29 Communication Tools - Comments

2.29.1 Description

The comments functionality component allows users of the site to leave comments on content posted on the website.

2.29.2 Functional Requirement List

The comments functionality component has the following requirements:

Functional Requirement Priority

1. No anonymous comments; only logged in users can post comments 1

2. Ability to subscribe to a page in order to receive alerts about new comments (for the content creator 3
and users)

3. Ability to respond to a particular comment (threaded comments) 1

4. Ability to delete comments 1

5. Ability to withdraw a user’s ability to post comments (blocking) 2

2.29.3 User Interface Functions / Interaction

2.29.4 Assumptions

• Most of the time, content will be open to comments from the users.

Functional Requirements v 1.3 36 6/5/2009

 Library Website Redesign

• Drupal natively supports comments on any node

• Drupal’s tools already permit content creators to choose when commenting functionality will and will not
be available

2.30 Collaborative Tools – Upload and Share Files

2.30.1 Description

The upload and share files functionality component allows users of the site to upload and share documents with a
group.

2.30.2 Functional Requirement List

The upload and share files functionality component has the following requirements:

Functional Requirement Priority

1. Access to files can be restricted to a group 1

2. Uploaded files can be presented in a user-friendly manner 1

3. Files can be deleted by website owners or by the user 1

4. Ability to shut off this functionality in some community areas 1

2.30.3 User Interface Functions / Interaction

Simple, clean user interface.

2.30.4 Assumptions

• This function may be built into other tools (ie, discussion board, etc.)

• There already exists a Drupal module that will support this functionality

2.31 Collaborative Tools – Wikis

2.31.1 Description

The wiki functionality component allows users of the site to collaboratively generate documents.

2.31.2 Functional Requirement List

The wiki functionality component has the following requirements:

Functional Requirements v 1.3 37 6/5/2009

 Library Website Redesign

Functional Requirement Priority

1. Versioning 1

2. WYSIWYG editor rather than new code 1

3. Themed to appear part of the larger website 2

4. Supports multiple instances; multiple groups using the functionality whose work does not bleed into 1
each other

5. Tool can be made available to groups of users 1

6. Specific wikis can be kept private to only the participants (e.g., library staff) 1

2.31.3 User Interface Functions / Interaction

Functional Requirements v 1.3 38 6/5/2009

 Library Website Redesign

2.31.4 Assumptions

• There is an existing Drupal wiki module that is robust enough to fill our requirements

• If there is no suitable wiki module, that there is a bridge between Drupal and another wiki product that will
allow us to support wiki functionality within our website

2.32 Collaborative Tools – Website Annotation

2.32.1 Description

The website annotation functionality component allows users of the site to make sophisticated comments on
websites produced by the library. (Assignment-related materials, readings, etc.)

2.32.2 Functional Requirement List

The website annotation functionality component has the following requirements:

Functional Requirement Priority

1. Allow selected users to leave comments in the margins of web documents 3

2. Comments must be clearly marked as comments 3

3. Allow content creator to make comments public or keep them private 3

Functional Requirements v 1.3 39 6/5/2009

 Library Website Redesign

2.32.3 User Interface Functions / Interaction

2.32.4 Assumptions

• A tool exists to provide this kind of functionality within Drupal. We do not require custom work for this
functionality.

• This tool would be used experimentally; not crucial to the website launch

2.33 Book Reviews

2.33.1 Description

The book reviews functionality component allows users of the site to add book/article/video reviews to the library’s
website.

2.33.2 Functional Requirement List

The book reviews functionality component has the following requirements:

Functional Requirement Priority

1. Simple interface for content creators 3

2. Searchable through keywords and tags 3

3. Available to selected content creators 3

4. Available for viewing and comment by all users 3

Functional Requirements v 1.3 40 6/5/2009

 Library Website Redesign

2.33.3 User Interface Functions / Interaction

2.33.4 Assumptions

• The University of Toronto does not buy LibraryThing for Libraries; if they do, we won’t need this function

• All book reviews are public

Functional Requirements v 1.3 41 6/5/2009

 Library Website Redesign

• Book reviews would be primarily gathered through experimental assignments, and thus moderation would
be mostly built in

• A module already exists for Drupal installations to support this functionality

2.34 Tagging / Categories

2.34.1 Description

The tagging / categories functionality component allows the content creators to classify their content with
keywords, and allows users of the site to find content based on those keywords.

2.34.2 Functional Requirement List

The tagging / categories functionality component has the following requirements:

Functional Requirement Priority

1. All nodes capable of being tagged 1

2. Multiple tags can be assigned to a single node 1

3. Clicking a tag creates a search for all nodes with that tag 1

4. Can easily and intuitively create tag clouds 1

5. Nodes can be tagged by users 1

2.34.3 User Interface Functions / Interaction

Functional Requirements v 1.3 42 6/5/2009

 Library Website Redesign

2.34.4 Assumptions

• Tags are built into Drupal and thus are easily available within any Drupal installation

• Search is already built to function using tags

2.35 Printer-Friendly

2.35.1 Description

A "printer friendly" version of the web page removes the navigation, header graphics, and utility menus to create a
printable format of page. A printer friendly page may also display a new header, change the styles of the page, and
have few or no graphics.

2.35.2 Functional Requirements List

Functional Requirement Priority

1. Content contributors must be provided the ability to insert the printer-friendly component on any 1
page

2. Pages must reference the print.css file when printing from the browser. Additionally, when a user 1
clicks on the component link on the page, the printer-friendly css is called.

3. Content contributors must be provided the ability to define the text or images of the printer-friendly 1
component

4. Content contributors must be provided the ability to define a printer-friendly component from within 1
the web publisher editor

2.35.3 User Interface Functions / Interaction

2.35.3.1 Screen Layout

Functional Requirements v 1.3 43 6/5/2009

 Library Website Redesign

Functional Requirements v 1.3 44 6/5/2009

 Library Website Redesign

2.35.4 Assumptions

• Print-friendliness is defined by the CSS written by the designer

• The designer knows how to provide this functionality as part of the overall design

• Drupal may have a module to support this functionality

2.36 Quizzes

2.36.1 Description

Patrons will be presented a series of questions with radio button, check box, or text box answer choices in a two
column structure. The answers will appear directly below the question in the first column. Each answer will have
associated feedback. Text boxes may only be used for calculations. As such the feedback associated to the text
boxes will be a range of values with feedback for each range. In the case of checkboxes and radio buttons answer
choices can range from one to many (for checkboxes) or one (for radio buttons). The user will read each question
and select or enter the answer that best answers the question for them. Users will be required to answer each
required question before proceeding to the next page of the quiz. The quiz will support branching. Once they have
completed the entire quiz the consumer is brought to an optional summary page containing the answers and answer
feedback they selected. The consumer can than print out the summary page. Note: An unchecked checkbox is
considered an answer.

2.36.2 Functional Requirements List

Functional Requirement Priority

Content contributors must be provided the ability to define required elements on the quiz 1

Content contributors must be provided the ability to define the order elements as the appear on the quiz 1

Content contributors must be provided the ability to specify instructions to be displayed at the top of the 1
quiz form from within the web publisher editor template.

Content contributors must be provided the ability to create a quiz with an unlimited number of
2
question/answers

Content contributors must be provided the ability to determine the next question displayed on the page
based on the answer provided to the previous question (branching)
3

Content contributors must be provided the ability to add/modify/delete questions and answers from
1
within the web publisher editor template.

Content contributors must be provided the ability to set up multi-page quizzes

1
Content contributors must be provided the ability to dictate which elements appear on which pages.
1
Content Contributors would like the ability to save data to a database and retrieve information at a later
2
time.

Functional Requirements v 1.3 45 6/5/2009

 Library Website Redesign

The following field is required on the quiz form

2
Answers
• Check boxes, Radio buttons, or text boxes
• By default this is a required field on both the contribution and consumption sides
• Content contributors must be provided the ability to determine if an answer is required or not
o Note: An unchecked check box is considered an answer
• Content contributors must be provided the ability to determine if they would like the answers to
be displayed below the question in single column or if they would like the answers to be
displayed in their own column
• Content contributors would like to be provided the ability with text boxes to do calculations
• Content contributors must be provided the ability to specify how the answers will be
displayed (horizontally or vertically)
• For option buttons one answer must be selected; for check boxes multiple check boxes can
be selected
• Content contributors must be provided the ability to enter multiple answers per question.

2.36.3 User Interface Functions / Interaction

2.36.3.1 Screen Layout

Question and Answer are displayed in the first column; the answer feedback will appear in the second column

Functional Requirements v 1.3 46 6/5/2009

 Library Website Redesign

Once the consumer answers a question; the answer feedback appears in the second column. Different answer
feedback will appear in the second column based upon the answer selected in the first column.

Functional Requirements v 1.3 47 6/5/2009

 Library Website Redesign

2.36.4 Error Handling

If a consumer forgets to select an answer they are brought back to the quiz location where the error occurred. A
page error message is displayed along with an element error message. The consumer must correct the error before
proceeding in the quiz

2.36.5 Assumptions

• This functionality is supported by an existing Drupal module and requires no custom code.

2.37 Podcasting Delivery Support

2.37.1 Description

Using the RSS 2.0 syndication format, podcasts are made available to subscribers just like news feeds.

2.37.2 Functional Requirements List

Functional Requirement Priority

Content contributors must be provided the ability to insert the “Podcast” component on any page 1

Content contributors must be provided the ability to select the MP3 file. 1

Content contributors must be provided the ability to define the RSS feed. 1

2.37.3 User Interface Functions / Interaction

2.37.3.1 Screen Layout

2.37.4 Assumptions

• The MP3 files will created in house.

• Size and retention guidelines will need to be determined.

• This functionality is supported by an existing Drupal module.

• This functionality may be part of another tool or Drupal module, (e.g. Blogging tool)

Functional Requirements v 1.3 48 6/5/2009

 Library Website Redesign

2.38 Favourites

2.38.1 Description

Allows users save a page to their saved favorites.

2.38.2 Functional Requirements List

Functional Requirement Priority

Content contributors must be provided the ability to insert the “save this page to favourites” component 2
on any page

2.39 Google Analytics

2.39.1 Description

Allows website owners to get visualizations and data on web traffic.

2.39.2 Functional Requirements List

Functional Requirement Priority

Google analytics code embedded on each page created without any input from the user 1

2.40 Systems Status

2.40.1 Description

A box on the website that shows users whether or not key external systems are up or down.

2.40.2 Functional Requirements List

Functional Requirement Priority

This functionality exists at U of T: http://preview.its.utoronto.ca/I_TS.htm 1

Monitored systems for the library:

Functional Requirements v 1.3 49 6/5/2009

 Library Website Redesign

1. Portal (stream of data already in place)

2. Webmail (stream of data already in place)

3. ROSI (stream of data already in place)

4. Laptop availability (ex. 3 laptops currently available; 0 laptops available, next due at 1:15)

Functional Requirements v 1.3 50 6/5/2009