Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: removed repeated section (2nd level indent repeated what followed)

...

 - JC: IT group is stuck between rock & hard place: Registrar and HR are 20-30 year old systems. Historically we have user group needs that are "met in other ways. IT is in the middle. We are more agile than the registrar, more production than the quick one-offs

  • TomD: Our registrar\'s system is old enough to be drafted. IT is authoritative for more and more over time, it makes us nervous, but what are the alternatives.
  • JPRobinson: It may be justified to have many authoritative systems.
  • TD: CS department has their own IdM infrastructure. They and others flatten these intrinsically hierarchical, nested groups for internal use.
  • Heather Flanagan: Stanford U. SHameless!!
  • Scotty Logan: Stanford: Rich notion of affiliation subtypes and roll-ups.
  • RL"Bob:" Discussions have commenced on chartered activity to when we were defining ePAffiliations, they were a carefully controlled set. There is pressure to increase. Specifically for those with library privileges. The info in the current spec defining faculty and staff is minimal, could be better. Notion exists that the entire set of definitions could be made more precise. Students off for a term student or not, adjunct faculty faculty or not. Qualified affiliations: student:onLeave. Recently at Terena: The affiliation values need to be multilingual All vs. ePEntitlement - Kathryn Huxtable, KU: we made our own KUeduPerson. MACE-Dir could help by capturing some good/best practices, but should not actually get into defining values for local use. Even for eduPerson level.
  • TB: library privileges question. Are there other specific use cases that would drive us toward a workable problem set?
  • RL"Bob:" Let's define things that seem useful and see what happens. Student affiliation in particular is likely to be generally useful because resource providers are looking for ease of use and are not particularly concerned about precision of definition (some leakage ok). met in other ways. IT is in the middle. We are more agile than the registrar, more production than the quick one-offs

 - TomD: Our registrar's system is old enough to be drafted. IT is authoritative for more and more over time, it makes us nervous, but what are the alternatives.

...