Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

...

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

...

  1. and need to be broken down

...

home tool is read only on the CM service

changes to site info to change how courses are connected to site

  1. into plausible chunks of work
  2. For initial task mapping service and group provider

...

  1. need to

...

  1. be validated - can happen simultaneous to work on site info setup wizard and home tool

...

add sections

marc JSF Clickthroughs - just do HTML or ppt; we will return clickthroughs

Site info (site setup wizard) replacing CM provider with CM mapping API and CM Group provider
we are just ditching CM provider

...

  1. 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?
  2. 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);

...

    1. user

...

    1. selects a set of Sections fron list

...

    1. site info wizard maps these sections by calling CM Mapping

...

    1. service (public void setMappedSectionEids(String sakaiReference, Set sectionEids);)

...

    1. for each section, create a group

...

    1. Note

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

...

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

    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

...

    1. produces find/search interface

...

    1. User selects sections from results that come back

...

    1. Selected results are

...

    1. added as options in the nested list

...

  1. Home Tool - new tool, not site info

...

  1. . - Lydia, 4 weeks
    Note

    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

...

put this in Confluence - we will review and add estimates

work in trunk

call for comments on changes to site info

release should be on a branch (question) - we work in trunk? need to coordinate with release schedule
assuming full release to community next summer
how do we cut a release for the folks who want to play with this in Nov/Dec. timeframe

relationship to release tags
can have them point to our tags

proposal:

...

      • asks CM service for meta-data

...

    1. Home Tool can be included in site template
      Note

      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 - clarification: mapping tool would be an admin-facing tool to manage individual section/site relationships. It is not part of site info, but rather is a tool that an administrator could use to tweak amd query mappings
    Note

    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 ?%
Me Duffy 20% (coordination mostly)

Action Items

Task

Who

Due

Add notes to Confluence

Duffy

7/28

Determine how changes to Site Info will live in SVN given Nov/Dec. release will be maintenance only \ How do we permit those who want to use/test CM work to cut a release in Nov./Dec.?

Josh? Duffy?

8/1?

verify mockups are done

...

or request mockup work from Marc. what are their statuses? what is usable from the PPT?

Duffy

8/1

Developers review tasks and "bid" a time estimate on the tasks that they would like to complete

Josh, Daisy, Lydia, Duffy

8/1