Preliminary Draft of OR Mockups

Open Registry - Mockups

The following mockups show a home page for a Department Administrator or a user with Person Role. Roles with more privileges, including Help Desk Admin and Super User will have more menu items.

Add Access:

The Add Access Page initially requires that the user select the affiliation and the role that is being added.

After the user indicates the affiliation and role and clicks "Select Access", the Access Page will be populated with the fields that are appropriate for that affiliation and role with respect to whether or not reconciliation is to be done and the data that will be specified for that access.
Question: will we attempt to do reconciliation on name only? For some types of access we would not want to ask for SSN, Birth Date, etc.
After the user fills in the fields, possible matches will be displayed, when reconciliation is done.

The user may select one of the possible matches or may click "Add New Person". At this point the Person Information Page is displayed populated with known data and the user may fill in additional data for the new access.
If reconciliation is not done then the Person Information Page will be displayed, pre-populated with the supplied data.
Department Administrators should only be able to establish access for some affiliations/roles. For example, a department admin for OIT would not be able to create Faculty or Students. Need to be able to configure which affiliations/roles are appropriate for a given department and user. Users with Person role will have a very limited set of affiliations/roles that they can establish. These will likely include wireless and program.

Person Information:

Person data is presented on the Person Information Page. There will be one tab for each affiliation/role. The required data to establish access for a given affiliation/role varies for the given affiliation and role.

Manage Person Info and Access:

This page enables the user to find the person they want to edit. The criteria can be pre-populated with the user's department to show all people in the department. We could consider keeping user profile data which could remember the last entered criteria and that could be used to pre-populate the criteria.

Bulk Update:

Users will have the ability to specify the location of an excel spreadsheet to upload. A format must be defined to support establishing access for multiple people. Question: The user can supply an email address so that a report can be sent indicating the result of processing the spreadsheet. Is this the preferred approach or should results be available via the web pages? The input file could also be used as the template for the output file and the information to be returned could be add to the Excel file.

Patrick: I recommend using the Apache POI libs over JXL for parsing excel. POI 3.5 is be able to understand the Office Open XML format (standard format for Excel 2007 and beyond) and I've found it is able to read some older format Excel files that JXL was not able to.

Self Service:

Fields on this page include: privacy indicator, preferred email, roles to show on directory listing, and address to show first in directory listing. Functions on this page include: password change. Question: What other fields belong on the self service page? What other functions belong on this page?

Troubleshoot:
Troubleshoot will be available to Help Desk and Super Users. This page will support resolving reconciliation problems.

In General:
Aesthetics need to be worked on, but I thought we should focus on trying to get the basics of the interactions correct first.

Rutgers Affiliation and Roles (Needs to be configurable for other Universities)

Affiliation	Role	Reconciliation	Data Required to Create

Employee	Faculty	Y	Name, SSN, DOB, Start and End Date, Status, Sponsor, Sponsor Type, Division, Department, Campus, local address fields, home address (cell phone and email are optional), gender.
	Staff	Y	Name, SSN, DOB, Start and End Date, Status, Sponsor, Sponsor Type, Division, Department, Campus, local address fields, home address (cell phone and email are optional), gender.
	Student Worker	Y	Name, SSN, DOB, Start and End Date, Status, Sponsor, Sponsor Type, Division, Department, Campus, local address fields, home address (cell phone and email are optional), gender.
	Retiree	Y	Name, SSN, DOB, End Date, Status, Sponsor, Sponsor Type, Division, Department, Campus, local address fields, home address (cell phone and email are optional), gender.

Student	Admit Coming	Y	Name, SSN, DOB, Start and End Date, Status, Campus, local address, home address (cell phone and email are optional), gender.
	Student	Y	Name, SSN, DOB, Start and End Date, Status, Campus, local address, home address (cell phone and email are optional), gender.
	Summer Student	Y	Name, SSN, DOB, Start and End Date, Status, Campus, local address, home address (cell phone and email are optional), gender.
	Winter Student	Y	Name, SSN, DOB, Start and End Date, Status, Campus, local address, home address (cell phone and email are optional), gender.
	Alumni	Y	Name, SSN, DOB, Start and End Date, Status, Campus, home address (cell phone and email are optional), gender.

Guest	Guest	Y	Name, SSN, DOB, Start and End Date, Status, Sponsor, Sponsor Type, Division, Department, Campus, local address fields, home address (cell phone and email are optional), gender.

Transient	Program	?	Name, ?

Other	NJIT	Y	Name, SSN, DOB
	UMDNJ	Y	Name, SSN, DOB
	Wireless	?	Name, NetID, email addr
	Sakai	?	Name, email addr

Note: Data necessary for reconciliation includes ID (SSN, RUID, RCPID, IID, or NetID), name and Date of Birth (DOB).

Other Data Values:

Field	Populated From or Hard coded values...

Status	?
Sponsor Type	Person, Department, Role (taken from data model)
Division	HRINFO Division Table
Department	HRINFO Department Table
Campus	HRINFO Campus Table
Building	HRINFO Building Table
Mail Code	?