Continuing Enhancements Ahead. More service provisioning and de-provisioning, departmental roles that can be used for provisioning services, increased use of uniqname self-registration, self-service password resets, and more.
2013. Improvements made to the MCommunity Sponsor System administrative application.
2012. MCommunity Directory groups synchronized to M+Google to allow group sharing of M+Google resources. Course groups introduced. MCommunity used to provision and de-provision M+Google accounts.
2011. MCommunity Directory released. MCommunity Directory data used to provision and de-provision Active Directory (UMROOT) accounts.
2009. MCommunity Sponsor System released to authorized departmental staff. (This system is used to get uniqnames and manage online identities for sponsored affiliates—members of the U-M community who are not faculty, staff, students, retirees, or alumni.)
2008. MCommunity infrastructure in place.
2007. Implementation work began.
2006. Governance Board with representation from across the university produced recommendations for data use and access.
2005-2006. Project plans developed. Preparatory work for development completed.
2004. Business case submitted to university executive officers. This included a conceptual architecture and an overall description of what a U-M enterprise directory should include.
2003. A group of information technology staff members from across the university published a report calling for a business case for an enterprise directory.