Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Current »

Weekly Meeting Agenda for November 7, 2006

New Meeting Time!!!: 1pm GMT-7 PST

Call-in Phone Number: (734) 647-7898
Code: 1620
In attendance:
Notetaker: Marc

Agenda

  • updates on where we are with the different projects
  • from Daisy
    • Home Tool mock up :
      • need clarification on Course Meeting and Staff Information
      • need mock up to add and remove additional customizable course descripton
    • Who would be QA-ing HomeTool for me? I would prefer some testing within the CM group after the tool is done and then QA by the community during the 2.4 QA period.
  • Auto section creation configurations
    1. Never create sections -- for any institution that wants section info with current functionality only. This option also significantly reduces the burden on integrators who have to deal with the new CM dependency, but whose institutions have no interest in sections. Cannot switch to auto.
    2. Create section for Multiple Rosters only -- this would be the default. Can switch to manual.
    3. Create sections for all rosters -- can switch to manual
    4. All auto, all the time -- cannot switch to manual
  • update on conference presentations

Notes

Roster

  •   UI pretty solid at this point
  •   Need to clarify the roll authorization

Gradebook

  •   Commenting feature is working out
  •   internal Nov 24 deadline looking good

Section Info

  • Requirements posted a couple weeks ago included ad hoc grouping functionality
  • Met yesterday and decided that it wasn't worth it to do for 2.4 for those req's are removed
  • Big question is the auto creation of sections for all sections even if just one? Most are just one. If then you go to the tools and there is a section for the whole course, it's confusing. Also confusing if you have a section info tool and you don't intend to have any sections
  • Decided that the best UX would be make a choice whether they'd want to have sections or not. But they've come up with presets to where these things can be pre-chosen, default setting would be "Create section for Multiple Rosters only"

CM Browser

  • needs to dive into SiteAction and figure things out
  • not going to be realistic to have one tool that is the CM browser and also go into SiteInfo wizard
  • Josh: has got agreement from Chuck that 2.4 for have dependencies
  • Marc needs to do a full spec for browser tool and take out Ajax stuff

auto Section creation configurations

  • need these because section info tool has a dependency on CM, so need a way to have sections created based on how a campus has integration
  • #1 is for when there really isn't any meta data and/or an institution is using legacy provider
  • #2 is the default, talked a lot about whether this made sense and it seemed to by the end
  • No labels