Minutes of the Meeting - November 14, 2012
Davis Centre Library, 1568
Present: Alex McCulloch, Annie Bélanger (Chair), Abdelaziz Aboueleinin, Chris Gray, Doug Morton, Pascal Calarco, Steve Weber (Recorder)
Regrets: Charles Woods, Esther Millar, Graham Faulkner, Nancy Collins, Marian Davies
Approval of Minutes of October 24
- Approved with minor corrections
Business arising from the Minutes of October 24
- Usability documents
- Action: Marian working on a two pager, which will be shared with LibExec.
- Action: Marian and Annie to present to Library about methodology and results in December
- Libguides in primo
- Generate xml metadata file that can be imported into primo
- (Pascal, Katherine E Szigeti, Chris) bring this discussion to TugPrimo [Action]
- Study Rooms Booking and Accessibility - (Chris) [Resolved]
- Changing the Maps: Geospatial Centre heading - (Chris) [Resolved]
Agenda review
- Emergency - Home page updating
- Project Management (Chris)
- Working Groups - User Stories/Use Cases and Personas (Annie)
- A-Z ERM Prototyping - Getting input from Librarians (Annie / Graham)
- Other suggestions on getting background engagement for the redesign (All)
Emergency - home page updating
- Notifying public when closed to an emergency.
- Perhaps use other tools such as Facebook and Twitter
- Give access to more staff users to update homepage. (Chris) will talk to Nancy [Action]
- We should keep this function in mind for the upcoming Library Drupal website
Project management (Chris)
- Agile: http://en.wikipedia.org/wiki/Agile_management
- User Stories: http://en.wikipedia.org/wiki/User_story
- Waterfall: http://en.wikipedia.org/wiki/Waterfall_model
- Extreme programing: http://en.wikipedia.org/wiki/Extreme_programming
- User Stories: http://en.wikipedia.org/wiki/User_story
- Highlevel overview:
- We should use Agile project management because it:
- supports small increments of development
- handles scope creep well
- can handle large teams
- manages critical path
- We should use user stories to create requirements because:
- provides excellent communication between stakeholders and technical staff
- Discussion:
- perhaps train other staff to be familiar with user stories
- add Agile project management approach into Library website redesign project charter.
Working groups - User stories/use cases and personas (Annie)
- User stories group: (Annie, Chris) will work on this
- User Profiles / Personas: (Annie, Nancy) will work on this
- Training users for project management (Pascal)
A-Z ERM Prototyping - Getting input from librarians (Annie / Graham)
- Create spreadsheet and have librarians weight database by subjects based on dynamic tags selected in section.
- Until (Graham) available [Deferred]
A test CMS site - Services for pages (Steve)
- (Steve) is looking into creating something similar to “Services For...†pagesin drupal. For the most part, this is strictly for learning more advanced Drupal topics in content reuse. [Action]
- (Steve) also talked about sandboxes. If staff wants to get their feet wet he can setup sandboxes, or the WCMS team can. Just before warn our CMS will differ once we hit the construction phase.
Other suggestions on getting background engagement for the redesign (All)
- Trainings (web course - accessibility, user stories)
- Starting groups to get staff and students involved
Around the table
Next meeting
- Date: December 12th
- Time: 1:30-3:00
- Location: DP 428
- Recorder: Doug Morton
If you have any queries or concerns about this page, please contact .
February 1, 2013