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

Compare with Current View Page History

« Previous Version 8 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

 

Benn Oshrin

Internet2 / Various

 

Eric Westfall

Indiana U / Kuali

(error)

Jeremy Rosenberg

SFU

 

Jimmy Vuccolo

PSU

 

Renee Shuey

PSU

(tick)

RL "Bob" Morgan

U. Washington / Internet2

 

Steven Carmody

Brown

 

Matt Sargent

Kuali

(tick)

Agenda

  1. Introductions/Roll Call
  2. Action Items Review from last meetings

Follow-up from previous week's action items

  • Bob will fold in the header from Ben's document into his page from a format perspective.
  • Add affiliate requirement to the enrollment / registration section - Steven.
  • Review and make notes in the document with regard to changes / additions / questions - All
  • Need a "general bag of requirements" (notifications, reporting etc.). Change notifications to General Enterprise Requirements - (I think Renee did this) - Steven will add some stuff here.
  • Consolidate requirements in one page by next Friday then start reviewing gaps. - All
  • Need to add information into requirements for registry regarding HR data, at least the core set
  • Should add some simple definition of terms at the top of the document, especially for terms that might be ambiguous
  • Need to add "calendar-driven" lifeycycle to the requirements list
  • Add mention in requirements of non-person entities and that there needs to be a flat namespace across person and non-person entities
  • Add a requirement to be able to store "test" users in the registry
    • needs to be some way to distinguish them from the rest of the population
    • need to not be considered in the reconciliation process
  • Add explicit requirements about the ability to create entries in the registry for these people who "self-register" (i.e. via federated or other processes)
  • Do we need to add any mention to the document about tools that might be needed as part of the whole package? workflow and rules engines?
  • No labels