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 2 Next »

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

Purpose: Establish work schedule for August as initial phase of development for work agreed upon
tasks are high level - 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

mapping service and group provider validation - need to happen while site info setup wizard and home tool are happening

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

create mock data
(velocity!!!)
changes to old screen
1)requests nested list of course info from CM API
1.enrollment set for which user is "official instructor"
2.determine sections and sub-sections
3.(potentially we could combine into a "convenience method")
2)requests CM Mapping - information about those sections that already have sites
public Set getSakaiReferences(String sectionEid);
3)user clicks a set of Sections
4)site info maps by calling CM Mapping - public void setMappedSectionEids(String sakaiReference, Set sectionEids);
5)for each section, create a group (check box for "make groups/don't make groups")
inclusion of find course page
1)select "find course" from nested list page
2)produces find/search interface
3)select results that come back
4)those results are simply added as options in the nested list
need some workflow/permission scheme to allow this to move on to permanent addition via mapping service (TBD)
admin who is notified user x tried to add sections x,y,z to site b
admin can go in and manually map sections
or "approval" button?
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 (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:

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?

  • No labels