Member Institution Requirements

Rutgers University

Version

Milestone

Objective

Deliverables

Status

RIAR-1

New Population Management

Add, modify, delete, and reconcile populations not covered by existing People Database, including identifier assignment where appropriate, with callouts to and data synchronization with the PDB; extract data in a format suitable for existing LDAP build procedures

Deploy R1 for the Rutgers environment with appropriate end-user training

In progress

RIAR-2

ID Cards

Create identities for new people immediately upon arrival at the University, possibly with provisional privileges until SOR data is processed

This may be implementable with R1 functionality

 

RIAR-3

SOR Data

Process SOR data (HR, Student, and possibly others such as Alumni) directly, including assuming responsibility for identifier assignment and directly building LDAP with real-time updates

Deploy R2 for the Rutgers environment with appropriate end-user training

 

Derived OpenRegistry Release Requirements

Version

Use Cases Covered

Functional Requirements Covered

R1


  • Identities for populations not currently in the identity management infrastructure (Rutgers-1)
  • Guest sponsorship (Rutgers-4)
  • Identity lifecycles (Rutgers-5)
  • Directory construction (Rutgers-6)
  • Data dictionary and versioned attribute definitions (Rutgers-9)
  • Data Normalization (Rutgers-14)
  • Audit all changes (Rutgers-20)
  • Tools for support staff and administrators (Rutgers-21)


  • Add, modify, and remove people from System of Record-provided role records via batch file processing (FR1)
  • Add, modify, and remove (manage) people from role records via a user driven web interface (FR2)
  • Reconcile new people against existing identities, possibly using callouts to existing systems that currently holds identity data (FR4)
  • Assign identifiers to new people, possibly using callouts to existing systems that are currently canonical for identifier assignment (FR5)
  • Attach biodemographic data, role data (including start/end dates), and attributes to people, such that an individual has one overall record with zero or more role records attached to it (FR6)
  • Attach sponsors to person records such that roles can be audited and possibly expired when a sponsor disappears (FR8)
  • User driven bulk update operations via a user-friendly web interface and file (xls, csv) upload capabilities (FR9)
  • Construct people directory via extract of appropriate data (FR10)
  • Update people directory view real-time incremental diffs (FR11)
  • Version all attribute definitions (FR14)
  • Provide a dictionary of attribute definitions and versions (FR15)
  • Normalize input data to common standards regardless of source (FR20)
  • Record all changes applied to a person (FR24)
  • Expose privileged operations to support staff and administrative users to diagnose and resolve end user issues (FR25)