Page Comparison

...

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

...

2. 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?
3. 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)
   1. generate nested list of section info
      • requests sections from CM API
        • enrollment set for which user is "official instructor"

...

1. 1. • • determine sections and sub-sections from enrollmentsets

...

1. 1. • • (potentially we could combine into a "convenience method"

...

1. 1. • • 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. 1. user

...

1. 1. selects a set of Sections fron list

...

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

...

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

...

1. 1. for each section, create a group

...

1. 1. Note
      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

   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. 1. produces find/search interface

...

1. 1. User selects sections from results that come back

...

1. 1. Selected results are

...

1. 1. added as options in the nested list

...

1. 1. 
      home tool modifications - new tool, not site info (give to Daphne/Marc for cut at display issues)
      1.official instructor
      2.meeting time/schedule
      3.asks mapping service for sections
      4.asks CM service for meta-data
      5.include tool in template
      what about customization?
      1.completely custom vs. stuff from API?
      2.changing meta-data?

put this in Confluence - we will review and add estimates

...