Fall 2009 Day 1 - OpenRegistry Session

Open Registry Wiki Site

• Important to get other schools on board

• Simon Fraser University is the first school after Rutgers to start committing

• Why is OpenRegistry a better option then ILM?

• OpenRegistry isn't a solution for people who need a solution today

• Rutgers has a new HR system coming which is going to change their IDM stuff

• Rutgers has to do something about the new HR anyway, so they threw their energy into creating a new OR instead of re-writing the old one

• Bring up OR before the HR system

• Columbia built their own solution over 20 years

• Rutgers has the same story

• So does SFU

• So why not go open source?

• Buying a solution is just as much effort building one when all the glue code is accounted for

• Rutgers had a VP on board and hence got traction

• Upper management likes having JASIG on board

• OpenRegistry roll out upstream of current PDB (Rutgers home grown system)

• Over time move other systems to upstream of OR

• Use OR to capture people not currently covered by PDB

• Continuing ed students are a first use case, since they have no presence in the current system

• Workflow is not tied in to OpenRegistry?

• Work on common themes (general flow and local common internal magic)

• OR provides a framework that covers the general flow from Systems of Record to directories with hooks for custom configuration through multiple channels

• Handles custom reconciliation in the middle

• Oracle's solution doesn't even handle the concept of multiple SoR

• Reconciliation is a unique concept in OpenRegistry

• Buy in for higher ed

• Rutgers is officially committed through next summer

• Governance needs to be shored up to demonstrate that this is truly a community driven project, not just a Rutgers project

  • Possible advisory committee (might be overkill)

  • Lighter weight solution like bi-weekly developer conference calls

• Done something already, like a home grown system that they are happy with, or vendor solution with glue code, but have sustainability issues

• Haven't done anything yet and can't contribute to an open source solution, but need something eventually

• 1-2% of schools that need to do something and are willing to jump in to a bleeding edge solution (like SFU)

• 2 page glossy, but product might not be ready

• Continued informal conversations with many Institutions

• Talk about overall design and architecture at conferences

• Need to have something new to talk about at each subsequent conference

• Frame discussions as technical talks like "JPA and Spring: A match made in Maven" and use OR as the background

• Frame discussions as problem and solution for Institutions that don't even know they have these problems

• Develop and open framework for developing plugins

  • Here is the tool and here are the ways to modify the tool locally

  • If you already have Java developers, look how easy this is

• Move out of incubation into full project

  • OR is halfway through the process

Action Item: set up a bi-weekly developer call