Page Comparison

...

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

      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
   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. - 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
      • asks CM service for meta-data
   2. 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

...