Sept. 23 UCB and SU Meeting Notes

Owned by Former user (Deleted)
Last updated: Sept 24, 2005Version comment
6 min read

Contents
Part 1: Minimum Set of Needs for SU Winter Pilot (Pre Meeting)

  • Section Tool
  • Course Management/ Sakai Legacy Site Management
  • SU Terminology Challenges

Part 2: Meeting Notes

Part 1: Minimum Set of Needs for SU Winter Pilot (Pre Meeting)

Section Tool

Before this meeting, we reviewed all the test cases posted on http://bugs.sakaiproject.org/confluence/display/SECT/Use+Cases

Out of the list of use cases, for our winter pilot, we need at the minimum the following:
1,2,3,5,6,7,8,9,10,11, 12, 13, 14,17,19
and 1a: the ability to set secondary sections in advance, but not make them available.
13 and 14 are for students.

1. Goal: Create a new section(s) or group(s) for a course (Only the term "section" will be used below). yes

2. Goal: Remove a section(s) or group(s) for a course (Only the term "section" will be used below): yes

3. Goal: Views list of per-section specific info (days, time, instructor, room,current enrollment, availability, max enrollment): yes

5. Goal: View roster by section : yes

6. Goal: Add Student(s) to Section(s): yes

7. Goal: Manually add a bunch of students to a section at once: No, do not support batch upload

8. Goal: Switch students among sections :yes

9. Goal: Remove Student(s) from Section : yes from section, not course

10. Goal: Allow students to sign up for and/or switch sections: yes. but not clear on mockup

11. Goal: Set maximum size for Section(s): yes

12. Goal: Edit Variable for Section(s): yes

13. Goal: Views list of per-section specific info (days, time, instructor,
room,current enrollment, availability, max enrollment) : yes

14. Goal: Signs up for / joins a section : yes

17. Goal: Associate enterprise defined students in a course with their sections : at risk

19. Goal: Reconcile official enrollment data with Sakai roster : at risk

Questions SU had for UCB
1. placeholder sections - status?
non-issue

2. Can TA add student to class roster , as well as section?
A: add students to sakai roster and then add them to section
site.add.user ? (give the sakai permission to ta)
has to be done in 2 places

3. Can you change the category of section?
not once it has been created 'cuz of rules like 'one student can only be member of one category' can't change category type , need to delete and create a new one)
categories predefined by institution

4. on section overview page, (for instructors) is the name a real name, or a generic category name + number?
They are the section title names; you can rename them. For mockups, they are lab1, lab2...etc

Course Management/ Sakai Legacy Site Management

  • course provider: populate roster (SIS data), one time pull
  • new/modified site info/work site setup UI
  • preserve current SU business practice

SU Terminology Challenges

1. SU has separate course offerings that the registar calls "sections" of course. CW represents these as separate course sites and sometimes combiens them into one site with multiple secondary sections.

2. SU supports separate course offerings which represents cross listings

3. within an offering these are sections

4. CW's use of this takes several forms

  1. one cw site, combined roster from FEED
  2. one cw site, w/ cw sections
  3. multiple cw sites from one RR definition
    (taking specific sections -> diff. cw - sites
  4. one cw site w/ multiple RR offerings (x-list)
  5. one cw site w/ arbitrary rosters (cw-x-list) ... more (jackie's comments)

Part 2: Meeting Notes

1) Review of the Berkeley Work
who has done a build?
what's the impression?
items thought to be landing in the short short term...

currently sakai is responsible for the list of members in a site.

the sections tool refers to as a set of available users in a site
then what sections does is takes all the users who are 'students' and then further
sections them up.

another permissions allows one to be designated TA/Section Leader

another permission indicates Instructors

currently if you remove a student from a site they don't get removed from
the sections, Josh is working on that right now

also thinking about exposing Sgt as a 'service' for others to use w/in sakai, that's a future.
as is some Glenn work surrounding sub groups.. (note to casey: check about this
as a service deployment so it can be grabbed from elsewhere)

Ray points out that these later too are future bits

what we don't have is how do we get the section data into Sakai in the first
place.

Ray is hoping that he will hit his milestone by the end of the wee allowing someone to
review the GB for section management

Discussion vis administration tools, ugly hacks of scripts, funky web pages for
course requests.

Berkeley pilot - no sections in pilot. will need reconciliation later, but not on the hook
for right now.

2) preparing to move forward
2.1) protecting the utility of the Berkeley Work from random hairball problems on the trunk
ie: remain on the Trunk, request a Branch?
A Stanford "vendor drop" in a separate SVN repo? (note: all headaches)

Conclusion: Take a snapshot at Nov 15 the milestone release

2.2) Sakai tool maturity review vis current trunk work & suitability for section work
Which of the below are ready to move into introducing section code, what's in the air, what has to land
for enough code stability? is it soup? is it stock? is it still a chicken?

2.2.1) Section Tool

q: what ever happened with the placeholder section bru ha ha.?
a: it is a non-issue. it's called give me all people not in required sections...

a: can TA add student from roster?
q. give TA the site.add permission in the template, has to be done in 2 tools, which suxor. should work.

q: can you change the type of section on the fly
a: no, because of the section type rules. exclusion rules. each institution will have to define their section types.
(types may be also called categories)

q: instructor view looking at overview.. .all the sections.. .you have the name columns... .is that a direct correspondence to the title of the section? we don't see the section type anywhere else...
a: when you go to add section page

2.2.2) Gradebook
2.2.2.1) UI design, UI impl
2.2.2.2) other bits

Hellaciously behind on everything, need more Lydia, need more Ray; onward! Ray has been doing only the most important bugs and the section awareness API.

Ray: as soon as I deliver a nicely packaged section aware tool I'm turning back to prior promised octover work, but it is a risky prospect.

Oliver: sectioning is the driver for just now, haven't heard a lot of other requirements. So, what about you stanford?

Stanford: Huh? We're happy!

2.2.3) Samigo
2.2.3.1) UI design, UI impl
2.2.3.2) other bits

Lydia - no sectioning work as been done. Bugfixes only. Not just Indiana, but the Indiana bugs
are prioritized.

Charles - the drop down menu from the UI POV, is what we're really waiting.

Ray - so you'll be ready to go once I have my stuff in for you.

Mara - so, are these going to show up in these rolling milestones, or ...? Samigo is
critical to the entire project and has many users?

Marc - Lydia is the manager now....

Lydia - (silence) (smile)

Marc describes some of the usability feedback efforts being considered.... there may be
some low hanging fruit.

2.2.4) Announcements
2.2.4.1) UI design, UI impl
2.2.4.2) other bits

they are great aren't they?

new twist - glenn is working on framework changes, longer term, and we're
thinking they may appear in the announcement tools.

UI -
Charles - it is also lacking the drop down, having check boxes. have to do multiple
check boxes.

Black hole in Michigan, the UI is in Indiana? UI is in gonzalo, but it hasn't seen anything.

They said they would do it.

Lois - should we push on Mike for status?

Josh has delivered something they could work on

Summary - we'll ask at the next 2.1 meeting

2.2.5) "Admin Tools"
2.2.5.1) UI design, UI impl
2.2.4.2) other bits

May be shell scripts at Stanford ! (smile)

Same basket as announcements. Unknown

Permissions is the most important thing, and that may be ready to go now.

3) Assignments / # of effort per above

Casey - I'm going to try to exercise the importing and the section management
API right away, in parrallel.

Daisy = CMgt, then bug fixes and lydia has given me sections in samigo

Stanford has to re-vet the work that Ed has been doing.

4) Additional stanford-only work to be done for Pilot
I/C loader into Sakai for stub courses
Document Harvester into Sakai to populate courses

that is casey, see above

5) Needs projected to be un-met for Stanford Winter Pilot, but w/in agreed upon Pilot scope

6) Needs projected to be un-met for Stanford service-replacement deployment
6.1) Course Management

Some discussion surrounding

UI - there is nothing now and noone resourced available for it?
Can we trust the core to do CMgt? nope.

? starts in october ?

7) Needs project to be un-met for Berkeley next step (pilot? production?)

We need everything.

Lois - what about QA? if Carol knows what is going to land ahead of time she can direct effort
accordingly. Also we'll have some help from UC Davis to that effect

Daisy - so what about this Dr. Chuck proposal to call the milestone a full release; what do we feel about that?

berkeley - well, it's not all there - that won't fly. (josh) maby it will!