| 1. |
Document -Need for privacy/security position -Problems/benefits -Ownership statement -Portfolio vendor certification statement (authentication/watermark)
|
who DB/DM Coordinate with (AJ/JC/BC)
|
when 7/28
|
| 2. |
White Paper on architecture -How is authentication handled? -Data elements (starting) -Protocols for exchange of data -Who/How data updated
|
BC Coordinate with (AJ/JC/DB)
|
7/25
|
| 3. |
Participation -Discuss Consortia approach -Discuss LEAP communications approach
|
BC Coordinate with (AJ/JD/DB)
|
7/15 |
| 4. |
-Business plan -Project schedule -Marketing plan -Work product schedule |
IBM Coordinate with (AJ/JD/BC) |
After the "Orange County Meeting", Stuart Lynn was to update the Vision and Allison Jones update the Outcomes document.
We need to develop a description of LEAP to be used in a marketing sense that can be used when talking with other institutions.
We need to move along to be able to have materials for the Fall conferences (EDUCOM, CAUSE, etc.).
PATHWAYS and MENTOR web sites are starting up in California.
Push Technology (PointCast) is being used at institutions to rely information to students about scholarships/etc.
There are bills in legislature in CA concerning transmission of information from K-12 to higher ed. Debate about what is included in a student's academic portfolio and the privacy of it.
Need to start developing a student information portfolio/repository.
PATHWAYS and MENTOR will both be able to accept the portfolio information from LEAP. Students may start building their portfolios at a very young age. In California, the state wants to be able to share academic records from Kindergarten on because of the mobility of the population.
The proposal before the CA legislature was to use EDI for transmission of the student records. Also there might be some retention of data. The battle that developed was over what was in it and how it was controlled.
We need to concentrate on what are the data elements, what are the data interface standards; privacy, security, interface standards and requirements.
The student identifier will be a big problem and will need quick definition and approvals.
LEAP model is to provide common services based on common data but no necessarily common software.
Minnesota is very interested in intrastate system for applications. Then link back to other things external to the state.
IBM intends to offer an Internet-based electronic application and let schools have a presence on the bulletin board in the sky. An un-affiliated person would have the ability to apply to a number of schools. It also provides a way for the independent schools to link-in; extra services like scanning for scholarships. It provides a basis for international and out-of-state students to choose and apply to institutions.
Other portfolio offerings: advise/guide; lifetime student record; test scores, certifications, competences, financial aid/scholarship, communications records.
Students wouldn't have to reenter any data.
With XAP students controls whether their data is stored on XAP or if it is maintained locally.
Three years from now, we want to be providing better services to student We want to have a concise, marketing oriented description to give to other institutions of what LEAP is and why they need to do it.
September 1
(Need to freeze and then publish 9/15-30)
October 1
(10/1 final review of communications material)
1. Communications ready
October 28/31