You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Conference Call Info: Video Bridge 22102

  1. Dial the Auto Attendant at 812-856-7060
  2. Enter the conference number (22102) followed by the # key (e.g., 22102#)

Attendees

Who

With

Attended

Aaron Neal

Indiana U / Kuali

(tick)

Benn Oshrin

Internet2 / Various

(tick)

Eric Westfall

Indiana U / Kuali

(tick)

Jeremy Rosenberg

SFU

 

Jimmy Vuccolo

PSU

(tick)

Renee Shuey

PSU

(tick)

RL "Bob" Morgan

U. Washington / Internet2

(tick)

Steven Carmody

Brown

(tick)

Matt Sargent

Kuali

(tick)

Agenda

  1. Introductions/Roll Call
  2. All - short review of fit/gap analysis updated/additions
    1. Steve - new items on schemes and life-cycle
    2. Eric/Aaron - KIM
    3. Benn/Jeremy - OpenRegistry
    4. Renee - PSU
  3. All - discussion on what our recommendation should be

Notes

  • Steve - in reference to the new items that were added, the start date on affiliations is an effective date for that type of assignment
    • Eric - I'm assuming this can be future dated for pre-population?
    • Steve - yes, we also use it in conjunction with the end date to force account review for guest accounts.  Helps ensure that they should remain active or not
    • Bob - this does kind of walk the line between access management and a registry,
    • Eric - when we looked through the new items that Steve added most of them are related to Life Cycle and while that is not currently part of KIM, we see it being added in the future.  With the schemes being extensible, that didn't seem obvious to me at first, it was a new idea.  But it seems to bore than just extending a tables attributes
    • Steve - the intent is that we should make it easy, to make the system easy, to use for the specific relationships that an institution has. It should be easy to setup and use them
      • Bob - at UW, that's our biggest problem right now is that our registry isn't extensible
      • Eric - seems like we have to have extensibility as a requirement and that our charge is to make it simple and easy to do
    • Bob - we've not really dived into having the registry store non-person entities, but it seems like that's a natural part of a registry
      • Eric - with KIM that's definitely a requirement.  We have that on the additional KIM notes page related to requirements
      • Renee - in Chicago I thought we determined that non-persons were out of scope
      • Bob/Steve/Eric - that's correct, but being that it would all live in the same name space we have to offer some level of support for that.  We give accounts out for person and non-persons; however this could be a very large undertaking
      • Eric - however, in the use cases we've come across in KIM, non-persons seem to be pretty simple and don't require much information be tracked.
        • Bob - it seems that connecting these non-persons with responsible parties is the tough part
  • Bob - without a doubt we have more requirements that can be added but we need to have some discussion of our recommendations for this coming Friday's meeting.
  •  
  • No labels