Why are we doing this?
Presently it is hard to access data across higher education. Data interchange standards are not widely implemented by vendors, academic institutions, and government agencies. Where standards are implemented they are not registered or documented in an infrastructure that allows them to be readily used by people building integrations and looking for data. EdUnify infrastructure will allow vendors, academic institutions, and government agencies to register their data interchange specifications and implementations and map them to standard termininology for interoperability. Users of EdUnify will be able to use this registry and vocabulary services to build integrations, inventory services, and access data across higher education. PESC is the right organization to undertake this effort, because it is a neutral party with a track record of success in developing and implementing standards.
For a list of Task Force members and contact information, see the PESC EdUnify Task Force Participants page. To enroll other participants contact Michael Sessa, PESC Executive Director, at email@example.com.
How to Help
- Presently, we most need folks to review this "high-level epic stories" and make comments, changes, and corrections (see below).
- We also need people to suggest new concrete use case names and topics which we can start working on together at the meeting December 17/18. We will complete a few examples in the meeting.PESC EdUnify Use Cases
- Example of the applications such infrastructure can enable, application to cancer research caGRID.
- Questions, Questions, Questions FAQ Frequently Asked Questions
- Planning the agenda for the inaugural meeting - December 4, 2009
- Use case template and use case background posted - December 3, 2009
- Initial functional goals posted (see this page below) - November 17, 2009
- Wiki, distribution list, and Subversion repository available - November 10, 2009
- Glossary and Acronyms
Big ideas are often difficult to achieve. Before going to deep into EdUnify, think about your use of email today and how easy it is for you to send and receive mail. Then, ponder how easy it is to travel by car up and down or east and west across state lines. On many toll roads, we now have Ezpass, a device put on your windshield that can be read from toll booths while traveling 35 MPH. It eliminates stopping, wasting gas and time. It consolidates monthly billing for tolls. It works on many highways and even parking garages. It is simple to establish one account that works across many States. And, it does not add costs to the trip. In our recent memories, events often collapse and we forget about how difficult it was prior to let's say Google or the Cell Phone. Or, what was life like before Amazon or Facebook for many younger today. Do you recall Gopher, Compuserve or BackRub? Collaborative efforts can realize great results. Read more about three major collabortions that changed our world, the face of America and impacted the world over. Revolutionary Ideas
EdUnify is a set of core services enabling the universal registration, lookup, and invocation of web services and other forms of data exchange allowing clients to find, access, and secure data exchange calls. EdUnify will address deployed, implemented, and abstract services. Deployed services are those that are operational and can be accessed on the web. Implemented services have been defined and implemented, but are not deployed and operational. Abstract services are typically either specifications or designs. Abstract services may or may not have implementations at any point in time. The high-level goals of EdUnify are to:
- open and secure access of structured information managed across distributed databases.
- compatibility with existing technologies, tools and applications.
- enable development of new technologies, tools and applications.
- connect disparate systems, applications and technologies.
- leverage internet connectivity.
- abstract services to buffer physical properties underlying data sources.
- utilize a common framework, protocols and semantics accepted by industry stakeholders.
- communicate data and processes securely, reinforced by reuse.
The specific technical goals of the task force are to:
- document use cases that articulate our goals
- design a registry with metadata about web services
- define the metadata about web services that is essential to maintain to achieve our goals
- design any integration services required to achieve our goals (for example, an ontology service)
- develop web service registration and registration maintenance processes that make sense for higher education
- prove the concept with reference implementations among participating organizations
- formalize specifications through PESC
- drive adoption within our organizations
Statement of the Problem
Across education, the utilization and effectiveness of data and information technologies is severely inhibited by access methods, differing protocols, non-standard payloads, varying data definitions, and inability to trust disparate applications stove piped by proprietary design. Billions of dollars are spent annually trying to move data across components employed by stakeholder computer systems. The current state of automation, with all its redundancy, unnecessary aggregation and inaccuracy render a tremendous burden on the educational investment society as a whole is making.
Policy, governance, research, teaching, administration, funding, and learning are all impacted. The unintended consequence of metered design without considering the external interchanges which contribute to additional obstacles and costs is avoidable. The accurate, authoritative and secure transmission of data spanning components and stakeholders would respect and reinforce autonomy and roles, by connection, rather than push the work around mentality that has been fostered by the industry fearful of data access, use and security.
The education industry spends approximately 4% of operating expenses on IT which approximates $50 Billion annually. Of that, approximately 50% or $25 Billion is spent supporting connections and movement of data across disparate applications inside and outside the institution poorly. Even with that much money spent to keep things band-aided together where funding has been applied, the ineffective use of technology is wasting away the capacity of tools and the investment in automation. Without addressing the challenge to bridge systems and components, we will be continually haunted by what could be, rather than what is. Automation can empower and serve the industry with innovation and unity in purpose. Thus, the call for EdUnify, to create a registry, lookup, and supporting services to enable applications and computer systems to seek and connect through a common abstract pipe following community developed methods, protocols, payloads and services promoted on a voluntary basis.
Functional Goals and Epic Stories
The following are examples of potential high-level functional goals. Dave Moldoff to provide initial goals...Ed Hauser and Steve Wheat will review and edit them as well.
- Registry and Lookup Services
- Student and Faculty Data Services
- Institutional and Academic Data Services
- Course and Program Transferability Disclosure Services
- 21st Century Learners Spanning Multiple Institution Services
- Student Access to their Data through Electronic Services
- Enabling New and Innovative Technologies to Support Teaching and Learning Services
The Task Force is preparing very specific, structured use cases that the EdUnify frameworks will support to help identify specifications and technology it will develop or apply. The Task Force is preparing use cases in a common format to help identify the constituents served and processes addressed in each use case. There is a template which can be used to start each new use case. For more details visit the Use Case page.
- EdUnify Use Cases
- EdUnify Subversion Repository
- EdUnify Organization Efforts
- Technical Design Documentation
- Glossary and Acronyms