2006-07-28 Developers' Planning Meeting

In Attendance: Lydia, Daisy, Josh, Duffy
Note taker: Duffy

Purpose: Establish work schedule for August as initial phase of development for work agreed upon at 2006-07-20 Stanford and UCB Scope Meeting

1. Established tasks are high level and need to be broken down into plausible chunks of work
2. For initial task mapping service and group provider need to be validated - can happen simultaneous to work on site info setup wizard and home tool
3. Assumption that we should work from HTML mockups for our tools. Marc will be producing these
   • Marc suggested JSF click-throughs though was discouraged by Duffy that nothing with JSF is simple and quick
   • All developers concur, HTML or PPT is sufficient
   • Are current mockups presented at 2006-07-20 Stanford and UCB Scope Meeting representative of the functionality required?
4. Work on Site Info setup wizard is to replace CMProvider with cm-mapping API and CMGroupProvider
   1. Backward compatibility to CMProvider is not a concern; sentiment was expressed that adopter schools want to get away from the old model

Breakdown of tasks

1. Create mock data for CM API impl that can be used in our development

1. Changes to site info CM screen (uses velocity) - Daisy, 4 weeks
   1. generate nested list of section info
      • requests sections from CM API
        • enrollment set for which user is "official instructor"
        • determine sections and sub-sections from enrollmentsets
        • (potentially we could combine into a "convenience method" in the future)
      • request existing mappings for these sections from cm-mapping service - this is to display which sections are already mapped
        • public Set getSakaiReferences(String sectionEid);
   2. user selects a set of Sections fron list
   3. site info wizard maps these sections by calling CM Mapping service (public void setMappedSectionEids(String sakaiReference, Set sectionEids);)
   4. for each section, create a group

      Should this be default behavior? Perhaps there should be a checkbox for "make groups/don't make groups"

2. Create a Find Sections page for Sections that didn't show up

   We need clarification about the permissions and workflow for approval around adding a course for which the user is not an "official instructor"
   Proposed Solution:

   • Sakai admin is notified user x tried to add sections x,y,z to site b
   • admin can create a Site and can map sections by using the Find page?
   1. select "find course" from nested list page
   2. produces find/search interface
   3. User selects sections from results that come back
   4. Selected results are added as options in the nested list
3. Home Tool - new tool, not site info

   This may have display issues. How does the display alter when showing a single section, parent and child sections, sibling sections and distant cousin sections?
   This should be reviewed by Daphne and Marc.

   1. Details to show about each section
      • official instructor
      • meeting time/schedule
      • asks mapping service for sections
      • asks CM service for meta-data
   2. Home Tool can be included in site template

      A question arose about customization:
      Should the Home Tool information be customizable?

      • completely custom data could just replace stuff from API
      • user could simply change meta-data, but that makes this a writable tool

Task Scheduling:

Several things can happen conncurrently:

• home tool and "realm-style" mapping tool

  Caution that we do not want to allow a "hokey" designer tool to be used as "the tool"
  it may be useful to have a simple tool for administrator mapping anyway, but some UI design would be comforting
  paraphrased from Josh
  -Duffy 8/1/6

• prep on site info
• deeper work
  • group provider
  • cm chaining/federation
  • API changes (Schedule object?)

August 1 availability:

Daisy and Lydia 50%
Josh ?%
Duffy 20% (coordination mostly)

Action Items