Meeting Minutes – 01/27/2010

Summary
Meeting Type Team of 9
Date: Wednesday, January 27, 2010 Time: 10:00am Location: Commerce 1
Recorder: James Turner
Attendees List
Debra, Susan, Sally, Sue, James, Ryan, Shantell, George, Salim
Agenda Items and Notes
1. Meeting Minutes and Wiki:

  • Sue Dass briefed team on changes made to wiki in role as workspace manager
  • Salim will work with Sue on wiki concerns

2. Team presentations with summaries and discussion topics:

  • Team 1 discussion points:
    • Discussed potential case histories that exemplify the use of the Explore section: general research, target research for latest and greatest technology, target a specific technology
    • Identified possible Explore functions: search, browse, save/mark favorites, print, upload, access internet, RSS feeds
    • Considered effects of a vetting process
    • Listed possible types of content to populate Explore: “7 things” by EDUCAUSE, Advantages/Disadvantages, papers, documents, best practices, lessons learned, recommended readings
    • Determined that technical requirements and infrastructure will be addressed by DAU and programmers
  • Team 2 discussion points:
    • Narrowing down the factors to (bandwidth, cost)
    • Mandated technology use case
    • Having the system generate a factor report – vs. making it criteria to be entered by the user
  • Team 3 discussion points:
    • Definition of component: tutorials and best practices and examples of how technology is implemented
    • Tutorials: could be videos, websites on how it is done (focus on examples on how it is being used in higher education, business, military and government) built out examples using content from 201 A/B
    • How to use tech (only the tech not the content e.g. podcast, blogs, wiki, games)

General Discussion

  • How do all three components interact?
    • Tool Wide Search/Browse function
    • Tool Wide Navigation function
    • Tool Wide 508  Compliance
    • Tool Wide 3 “clicks” or less
    • Tool Wide Save/Mark/Print functions
    • Interconnectivity between three components

3. Discussion regarding developer meeting next week

  • Each Team will prepare a draft of information requirements (for the tool components) they need from the other teams
  • Visit BeanCreative.com to visit past projects
  • Prepare brief on “why” components must be interconnected
  • Narrative based on the questions from Constantine and lockwood (pg. 30)
  • 2 examples of use cases
Action Items
# Task Person responsible Due date
1 See Agenda Item #3 for tasks Individual Teams February 4
Next Meeting: Wednesday, February 03, 2010 10:00 am