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
- Established tasks are high level and need to be broken down into plausible chunks of work
- 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
- 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?
- Work on Site Info setup wizard is to replace CMProvider with cm-mapping API and CMGroupProvider
- 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
- Create mock data for CM API impl that can be used in our development
- Changes to site info CM screen (uses velocity)
- 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);
- requests sections from CM API
- user selects a set of Sections fron list
- site info wizard maps these sections by calling CM Mapping service (public void setMappedSectionEids(String sakaiReference, Set sectionEids);)
- for each section, create a group
Should this be default behavior? Perhaps there should be a checkbox for "make groups/don't make groups"
- generate nested list of section info
- 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?
- select "find course" from nested list page
- produces find/search interface
- User selects sections from results that come back
- Selected results are added as options in the nested list
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
work in trunk
call for comments on changes to site info
release should be on a branch - 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:
home tool and "realm-style" mapping tool (Josh)
meanwhile someone doing prep on site info
deeper work
group provider
cm chaining
API changes (Schedule object?)
Aug 1.
Daisy and Lydia 50%
Josh ?%
Me 20% (coordination mostly)
verify mockups are done... what are their statuses? what is usable from the PPT?