Page Comparison

...

• Course Management - Josh Holtzman
  1. The ability to query for sections down an institutional hierarchy.
     This might look like List<Section> getChildSections(String
     courseSetEid). Translating to hierarchy speak, it's
     getLeafNodes(Node). I'm pretty sure this simple use case will be covered
  2. The ability to query for memberships up a hierarchy. This might look
     like List<Membership> getMembershipsAboveSection(String userEid, String
     sectionEid), returning all memberships for any course offering or course
     set (node) above this section (leaf node).
     This is complicated by the fact that a child node can have multiple
     parents (e.g. a course can be in multiple departments). We may need to
     model this where a course has a node in multiple places in the CM
     hierarchy... I'm not sure if that's possible, or if that negates any
     performance improvements the hierarchy service is attempting to provide.
• Checklist - Dick Elis
  1. Simple hierarchies unlimited in number and depth but unlikely to be deep - e.g., Grad Tools checklists consist of two hierarchies of three levels (institutional requirements for most graduate students or for music performance graduate students, which are inherited by associated departments and to which departmental requirements are added, and which in turn are inherited by their students, to which faculty committee and the student may add personal as opposed to institutional steps) - Masters checklists would consist of 100 hierarchies of 2 levels (the department and students under the department), personal or project checklists might consist of 1000 hierarchies of 1 level.
  2. Cascading CRUD - administrators may make retroactive changes to checklists that should be carried over to checklists that inherit from this checklist - interactive batch processing where speed is an issue, as is connection time out
  3. Lock a section of the hierarchy for cascading CRUD
  4. View Progress - At any level above, show all leaf nodes and individual checklists below showing completion progress
  5. allowUpdateChildren, allowBasedOnChecklist, getChildChecklists, getSharedChecklists, hasChildChecklist, getTree(String root)
  6. Attached screen shots show how the root (blank checklist), branch (based on checklist) and leaf (use checklist) are created, and sharing of a checklist by owner