Skip to end of metadata
  • Created by Former user, last modified by Former user on Aug 16, 2006
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 4 Next »

Weekly Meeting Agenda for August 15, 2006

In attendance: Daisy, Daphne, Duffy, Josh, Lydia, Marc

Notetaker: Lydia

Agenda

  • from last week:
    • finishing mockups
    • IM chat conferences? happening? going well?
    • community review conclusions?
  • new business
    • what about making Section Info CM-aware? did we forget about this? (smile)
    • should we just do Accord w/no AC rather than Pinto+? (add TAs in Section Info)
    • review latest Home Tool mockups

Notes

Marc: first reviewed the agenda.
Daphne: working on work site setup (new site set up wizard) site info (add roster) mockup, Daisy doesn't need it right away. Will review later this week(marc will set up IM conf).
IM chat conferences? hasn't happened yet.
Duffy will follow up on emails re. community review, and Linda (oracle)'s email posted on cm-wg.

Marc: what about section info cm-aware? we haven't addressed it.
Josh: Section info is a layer on top of site groups. we need to add enerprise defined things on top of it.
Marc : main requirement from Berkeley was to intially get enterprpise data, and then turn it off, make data manually editable.
Josh: API can be exposed to allow enterprise data coming in, set up quartz job, read cm data and update sections. There will be tech. problem with section info once we get cm group provider. Section info may not even work, it's a tool overrides enterprise data, We need to experiement to see what it will do. could be problematic.

Daphne: If we don't touch section info? what happens?
Josh: section info doens't fit with cm group provider, must be changed. In Sakai, you can have provided site, you can also add members. Section info can do the same, ignore cm data and let Sakai do things. It's going to be a big change, need to figure out what it needs to do, what users expect to do, how much effort it's going to itake. it's a deep area of sakai. we need to think about this.

Daphne/marc: Let a couple of peole do the thinking first. Set up another call on this topic (josh, duffy, daphne.)

Should we just do Accord w/no AC rather than Pinto+?

Marc: courseManagemnt/section is required for fall rollout for Stanford. This is not necessarily true for Berkeley?  Can we talk to Mara to get more resources?
Josh willl talk to oliver/mara about this.

review home mockup:

  • there might be more synoptic tools, daphne pointed out they are more than nice to have, they should be kept , to not lose existing features.
  • how to deal with multiple titles for a meeting? Duffy suggested having a separate row for each title.
  • Description from site info, vs. cm home info . Duffy wants to add a revert button.
  • title/numer/term/ do we need to make them editable?(number/term should be coming from cm, not editable)
  • add char. limit for the title.

Josh: chatting with Glenn on authz service : An easy way is to add a couple of new methods to the existing Sakai authz service, rather making an entire new cm mapping service. This removes dev. overhead, no need for more apis. It's cleaner.  One limitation: we can't map an entire dept to a site, we can only map a string (section id) to a group.
Duffy raised some concerns...(Duffy please add here)

Daisy: can local admin functionality still be achieved?
Josh: local admin can still be achieved through group provider. Group provider will search upward, look into cm data.

  • No labels