Logistics

Yale University will host an OpenRegistry design session on Friday, December 12.

The meeting will take place in Yale ITS' new home at 25 Science Park from 11:30 - 2:00. The address is 150 Munson St., New Haven, CT 06511. Lunch will be provided. Below are directions from I-91. If you need more information about the logistics please give SusanBramhall a call at 203 432 6697.

Directions from I-91

Take exit 3 to merge onto Trumbull St (straight ahead)
Turn right at Prospect St (the end of Trumbull at 4th light)
Turn left at Hillside Pl (top of hill after about .5 miles)
After 2 blocks Hillside Pl becomes Munson St.
25 Science park is large bldg on the corner which is the intersection of Winchester and Munson
To park: Turn left onto Winchester and right into the parking lot. There are visitor spaces on the left in this lot. However, they are usually taken. If so, you should be able to find parking on the street along Winchester.
Walk around to the lobby in the front of the building and give Susan a call (203 432 6697 or cell: 203 494 4448). We will be meeting on the 4th floor in room 446.

If appropriate, this session may continue afterward, possibly in another location. There is plenty of seating to continue in the kitchen area next to the conference room.

Network Access

Non-Yale attendees should have a received an email enabling them to register their laptops for use on the Yale network. If you have not received the email and need network access, please contact SusanBramhall

Attendees

Columbia University
- Jeff Eldredge
Rensselaer Polytechnic Institute
- Ice storm prevented travel
Rutgers University
University of Connecticut
- Matt Smith
Yale University
- SusanBramhall
- Roger V. Despres
- Howard Gilbert
- Rod Gustavson
- Andrew Newman
- Joseph Valerio
- Eric Wittman
JASIG
- Jonathan Markow

Agenda

This will be Unconference format, specific topics will be decided at the beginning of the meeting. Potential topics include

Status of Rutgers work
In depth discussion of open development questions
Alignment of OR work with other institution's needs
Establishment of an OpenRegistry Advisory Committee (stale)

Notes

Project overview, architecture, data model
- Interfaces should support "-n" option to see what happens before a change is submitted
- Should SORs be able to provide name data as name,type={preferred|maiden|typo} to help OR elect best name?
- Is multiple stage deprovisioning supported properly in the data model? ie: you're expired but not deleted, oh, now you're deleted (this might just be two business rules)
Discussion of Yale's current needs and architecture
- Business Rules use cases, data model, architecture
  - Rules as Java code? SQL? Both?
- SOR inbound APIs
- Provisioning outbound APIs, message queues
- PR data model/implementation
Extended discussion of proposed roles and data flow

Browser not supported