MACE-CourseID Conference Call June, 7th 2004

[AI] All: Please let Keith know of people to include in a discussion regarding DOI handles and strategies in comparison with courseID.

[AI] Barry will e-mail the courseID list about just in time provisioning issues. Keith will forward it to parties of interest outside of courseID.

[AI] Jeanette will update the courseID draft and place in a more prominent position on the web page.

*Attendees*

Barry Ribbeck, UT-HSCH

Keith Hazelton, U. Wisconsin

Tom Barton, U. Chicago

Jeanette Fielden, Internet2

Lisa Hogeboom, Internet2

Steve Olshansky, Internet2

*Discussion*

Barry indicated that just in time provisioning is raising its head in terms of assertion. He is looking for direction in terms of being an early adopter what the best position for that attribute will be since they don’t want to build attributes in the directory and have to later remove them. Keith indicated that it hasn’t been defined but will probably be related to course offering and the role of the person coming in.

Has any work been done in the area of allowing/controlling an assertion from another institution to be more than a student? How do you manage post course access, payments etc. \This is more of a policy issue than a technical issue. It was not a topic of discussion at the Internet2 Spring Member meeting.

Should we propose identifiers for course listings now that we have identifiers for course offerings? Is there value in a quick deliverable of a guideline for assigning course-listing identifiers? What should they really be called? Will this spawn a need for a new eduObject? Are there scenarios where this course listing identifier would be useful? Who can imagine using a course catalog/listing identifier? A version number might be needed. At some institutions degrees are based on the course catalog in effect at the time the student matriculates so the catalog year might need to be part of the identifier.

It would be useful to look at the set of objects that we might be naming over time to get a sense of how any one object might be named using the UML model as a starting point. There are three main objects classes: course, offering, and section. The name course might be changed to listing. Session and members come into it as well. Which of these might need to be globally unique? Are the needs for global uniqueness to support sharing without confusion covered by the fact that we have unique identifiers for offerings? For any given offering the unique identifier and it’s relation to other objects could be leveraged to get to the course, which would have some identifier.

Which things in the UML diagram could benefit from a universal global standard for identifiers and which use cases would demonstrate the need for that and how would they be prioritized? This will be discussed on the next call.

What is the rational solution to dividing the universe between different identifiers? What criteria should come into play in DOI vs. courseID? More information is needed from people who work in that world on DOI handles and strategies.