hied-course-brainstorming - Revision history

TomMorris: added some UK specific details - other microformateers elsewhere may wish to do similarly

2009-08-15T10:09:39Z

added some UK specific details - other microformateers elsewhere may wish to do similarly

← Older revision		Revision as of 10:09, 15 August 2009
Line 35:		Line 35:
	The [http://www.pesc.org/ Postsecondary Electronic Standards Council] has an approved standard for EDI and [http://www.pesc.org/library/docs/standards/College%20Transcript/XMLCollegeTranscriptImplementationGuideV1.0.0.pdf XML Transcripts] which already offers a basic data model for Courses in the academic history. The standards of the PESC are supported by many of the mayor HiEd ERP vendors. ([https://spaces.internet2.edu/display/macedir/eduCourse+and+IMS+Enterprise+Services+Spec+2.0+draft interesting])		The [http://www.pesc.org/ Postsecondary Electronic Standards Council] has an approved standard for EDI and [http://www.pesc.org/library/docs/standards/College%20Transcript/XMLCollegeTranscriptImplementationGuideV1.0.0.pdf XML Transcripts] which already offers a basic data model for Courses in the academic history. The standards of the PESC are supported by many of the mayor HiEd ERP vendors. ([https://spaces.internet2.edu/display/macedir/eduCourse+and+IMS+Enterprise+Services+Spec+2.0+draft interesting])

	The ~~british~~ eXchange of Course-Related Information, is an approved standard which is gaining good visibility among UK schools, even within the PESC.		The British eXchange of Course-Related Information, is an approved standard which is gaining good visibility among UK schools, even within the PESC.

	===Normalizing available standards===		===Normalizing available standards===
Line 80:		Line 80:
	*XCRI: N/A		*XCRI: N/A
	*eduCourse: N/A		*eduCourse: N/A

			===Data offered on courses by admissions agencies===
			* [http://www.ucas.com/ University and College Admissions Service (UCAS)] is the UK body for admissions applications for undergraduate degree courses. For each course they offer, they have the following data:
			** Degree course name
			** Degree course code
			** Institution course code
			** Address and details of institution
			** Entry profile - that is, what requirements there are for admission
			** Date of application close

	===Suggested entities for a microformat===		===Suggested entities for a microformat===
Line 93:		Line 102:
	*Enrollment requirements. Criteria needed to enroll in the course. Commonly known as pre-requirements, etc. Different from course requirements.		*Enrollment requirements. Criteria needed to enroll in the course. Commonly known as pre-requirements, etc. Different from course requirements.
	*Credits/Credit-Hours. Unit of effort required to complete the course and at the same time earned. The notion of credits hours are standard in the US and its territories (PR, GUAM, Virgin Island).		*Credits/Credit-Hours. Unit of effort required to complete the course and at the same time earned. The notion of credits hours are standard in the US and its territories (PR, GUAM, Virgin Island).
			**In the United Kingdom, credits are offered on a course-by-course basis. One must have the adequate number of credits to graduate, but it is more of a formality than it is in the United States.
	*Level. Is it a Undergraduate, Graduate, Professional, etc. Commonly associated to the level of the degree for which this course is a requirement.		*Level. Is it a Undergraduate, Graduate, Professional, etc. Commonly associated to the level of the degree for which this course is a requirement.

Line 101:		Line 111:
	*Section ID. A unique identifier for the teaching section. Commonly used along the Course ID. Important for enrollment. Particular to the institution.		*Section ID. A unique identifier for the teaching section. Commonly used along the Course ID. Important for enrollment. Particular to the institution.
	*Meetings. Times/dates in which the section meets. Commonly on week basis for the duration of a particular term. Seldom listed as absolute dates, instead most sites list them as reoccurring day and time events.		*Meetings. Times/dates in which the section meets. Commonly on week basis for the duration of a particular term. Seldom listed as absolute dates, instead most sites list them as reoccurring day and time events.
			**To make this slightly more complicated: there can be a mixture of different meeting types, and some are optional - for instance, a course may state that you have to turn up to all the lectures, and have to turn up to one or more of three field trips.
	*Meeting modality. Is it a lab, lecture, field practice, online		*Meeting modality. Is it a lab, lecture, field practice, online
	*Professor. Who is teaching the course section. [http://microformats.org/wiki/hcard hCard]!		*Professor. Who is teaching the course section. [http://microformats.org/wiki/hcard hCard]!
	*Location. Commonly a classroom and building. Must of the time the location is paired to a meeting. [http://microformats.org/wiki/adr adr], [http://microformats.org/wiki/geo geo]!		*Location. Commonly a classroom and building. Must of the time the location is paired to a meeting. [http://microformats.org/wiki/adr adr], [http://microformats.org/wiki/geo geo]!
	*Term. The actual value ranges from textual values, to structured identifiers. Particular to an institution. Things commonly used are Summer, Spring, Fall and the year or academic year.		*Term. The actual value ranges from textual values, to structured identifiers. Particular to an institution. Things commonly used are Summer, Spring, Fall and the year or academic year.
			** A list of some (traditional) academic terms can be found in the See also section of [[wikipedia:Michaelmas term]]

	'''Course Catalog'''<br>		'''Course Catalog'''<br>

CtkJose: Suggested entities for a microformat

2009-08-14T17:34:32Z

Suggested entities for a microformat

← Older revision		Revision as of 17:34, 14 August 2009
Line 104:		Line 104:
	*Professor. Who is teaching the course section. [http://microformats.org/wiki/hcard hCard]!		*Professor. Who is teaching the course section. [http://microformats.org/wiki/hcard hCard]!
	*Location. Commonly a classroom and building. Must of the time the location is paired to a meeting. [http://microformats.org/wiki/adr adr], [http://microformats.org/wiki/geo geo]!		*Location. Commonly a classroom and building. Must of the time the location is paired to a meeting. [http://microformats.org/wiki/adr adr], [http://microformats.org/wiki/geo geo]!
	*Term. The actual value ranges from textual values, to structured ~~identifies~~. Particular to an institution. Things commonly used are Summer, Spring, Fall and the year or academic year.		*Term. The actual value ranges from textual values, to structured identifiers. Particular to an institution. Things commonly used are Summer, Spring, Fall and the year or academic year.

	'''Course Catalog'''<br>		'''Course Catalog'''<br>

CtkJose: Existing Microformats

2009-08-14T17:33:23Z

Existing Microformats

← Older revision		Revision as of 17:33, 14 August 2009
Line 113:		Line 113:

	===Existing Microformats===		===Existing Microformats===
	~~Seems clear that there is a great deal of work already done with~~ microformats approved ~~and~~ in draft that could help a new Course microformat.		Other microformats approved or in draft that could help a new Course microformat.

	[http://microformats.org/wiki/hcard hCard]<br>		[http://microformats.org/wiki/hcard hCard]<br>

CtkJose: More analysis

2009-08-14T17:07:11Z

More analysis

← Older revision		Revision as of 17:07, 14 August 2009
Line 111:		Line 111:
	'''Degree'''<br>		'''Degree'''<br>
	An academic program that needs to be completed to earn a degree. Includes courses as requirements.		An academic program that needs to be completed to earn a degree. Includes courses as requirements.

			===Existing Microformats===
			Seems clear that there is a great deal of work already done with microformats approved and in draft that could help a new Course microformat.

			[http://microformats.org/wiki/hcard hCard]<br>
			All people references must be in hCard. Eg professor.

			[http://microformats.org/wiki/adr adr], [http://microformats.org/wiki/geo geo]<br>
			Location references must use geo and adr. Yet not quite sure if "adr" is suitable because must of the time locations are listed as building and room number.

			[http://microformats.org/wiki/hCalendar hCalendar]<br>
			Seems a perfect candidate for meeting times, yet given that meetings are listed as reoccurring events on particular days and times this may not quite fit.

			[http://microformats.org/wiki/hlisting hListing]<br>
			There is good potential to make course catalogs and course listings a hListing. At first glance this may require to broaden the scope of hListing.

CtkJose: More analysis

2009-08-14T16:51:06Z

More analysis

← Older revision		Revision as of 16:51, 14 August 2009
Line 80:		Line 80:
	*XCRI: N/A		*XCRI: N/A
	*eduCourse: N/A		*eduCourse: N/A

			===Suggested entities for a microformat===
			This section attempts to summarize the observations made and the result of a survey of course catalogs, course listings and course information published on the web.

			'''Course'''<br>
			The course itself is used as a "academic activity" that belongs in a "Degree"/"Programe". It is an entity of transcripts and academic history and enrollment offerings.

			Common core attributes of a course are:
			*Title. A human readable title. May appear in multiple languages. Short/abbreviated and long forms.
			*Description. A human readable description of the academic activity. Course requirements are often part of the description. While for must part enrollment requirements are listed separately.
			*Course ID. A unique identifier of the course. Particular to the institution. Format varies. Usually a structured nomenclature is used. Used by information systems during enrollment and another system tasks as an ID.
			*Enrollment requirements. Criteria needed to enroll in the course. Commonly known as pre-requirements, etc. Different from course requirements.
			*Credits/Credit-Hours. Unit of effort required to complete the course and at the same time earned. The notion of credits hours are standard in the US and its territories (PR, GUAM, Virgin Island).
			*Level. Is it a Undergraduate, Graduate, Professional, etc. Commonly associated to the level of the degree for which this course is a requirement.

			'''Course Offering'''<br>
			A course offering is the actual teaching section of a course. A course may have multiple teaching sections.

			Common core attributes of a course offering are:
			*Section ID. A unique identifier for the teaching section. Commonly used along the Course ID. Important for enrollment. Particular to the institution.
			*Meetings. Times/dates in which the section meets. Commonly on week basis for the duration of a particular term. Seldom listed as absolute dates, instead most sites list them as reoccurring day and time events.
			*Meeting modality. Is it a lab, lecture, field practice, online
			*Professor. Who is teaching the course section. [http://microformats.org/wiki/hcard hCard]!
			*Location. Commonly a classroom and building. Must of the time the location is paired to a meeting. [http://microformats.org/wiki/adr adr], [http://microformats.org/wiki/geo geo]!
			*Term. The actual value ranges from textual values, to structured identifies. Particular to an institution. Things commonly used are Summer, Spring, Fall and the year or academic year.

			'''Course Catalog'''<br>
			A listing of courses available at a institution.

			'''Degree'''<br>
			An academic program that needs to be completed to earn a degree. Includes courses as requirements.

CtkJose: Normalizing available standards

2009-08-14T16:06:52Z

Normalizing available standards

@@ Line 39: / Line 39: @@
 ===Normalizing available standards===
-. Comparison of fields supported among standards
+====Comparison of fields supported among standards====
-.1. '''Title'''
+.1. '''Title'''<br>A human-readable title of the course.
-PSEC: 'CourseTitle', one language supported.
+*PSEC: 'CourseTitle', one language supported.
-XCRI: title, multiple languages using the 'xml:lang' attribute.
+.2. '''Description'''<br>A human-readable description of the course.
-eduCourse: N/A
+.3. '''Institution'''<br>

CtkJose: More analysis

2009-08-14T14:21:46Z

More analysis

@@ Line 3: / Line 3: @@
 ==Contributors==
 * Jose Cuevas
 ==What is happening?==
@@ Line 12: / Line 17: @@
 * A community format allows the use and sharing of course data commonly publish on the web.
 * Provides semantics to academic information.
-* Provides means to mechanically operate on web content for data that otherwise is published on PDF, printed, published with proprietary EDI or XML interfaces or worst jailed in a SIS database.
+* Provides means to mechanically operate on web content for data that otherwise is published on PDF, printed, published with proprietary EDI or XML interfaces or worst jailed in a Student Information System.
-==See Also==
+==Course entity analysis==
-* [[hied-course-examples]]
+There are various attempts to produce an schema or data model for Course information.
-* [[hied-course-formats]]
-* [[hied-course-brainstorming]]
+In 2005 [http://middleware.internet2.edu/MACE/ MACE] and the [http://middleware.internet2.edu/courseid/ Course Working Group] published the first schema for [http://middleware.internet2.edu/courseid/docs/internet2-mace-dir-courseid-educourse-ldap-200507.html eduCourse]. eduCourse was largely centered to an LDAP Schema and the eduPerson efforts. The primary motivation of the Course WG was the access to on-line e-learning materials. (IMHO!)

CtkJose: /* Brainstorming on Course format */

2008-03-19T18:30:29Z

Brainstorming on Course format

← Older revision		Revision as of 18:30, 19 March 2008
Line 17:		Line 17:
	* [[hied-course-examples]]		* [[hied-course-examples]]
	* [[hied-course-formats]]		* [[hied-course-formats]]
			* [[hied-course-brainstorming]]

CtkJose at 18:29, 19 March 2008

2008-03-19T18:29:09Z

New page

=Brainstorming on Course format=

==Contributors==
* Jose Cuevas

==What is happening?==
* Course information is available in disparate formats which makes it hard to compare information, extract information and find information.
* Students Information Systems lack proper data exchange schemes and standards.
* No data syndication of course information among campuses.

==Why would it help?==
* A community format allows the use and sharing of course data commonly publish on the web.
* Provides semantics to academic information.
* Provides means to mechanically operate on web content for data that otherwise is published on PDF, printed, published with proprietary EDI or XML interfaces or worst jailed in a SIS database.

==See Also==
* [[hied-course-examples]]
* [[hied-course-formats]]