Skip to end of metadata
Go to start of metadata

This page will describe the difference between PESC and ELMO.

Quick summary

The PESC standard that is closest to ELMO is the "College transcript". This XML-format describes a college transcript for a student.

The XML-format is very american, meaning a lot of the fields are named based on american/canadian standard, for instance classification of courses.

A lot of the fields in the XML-format is also present in the ELMO-format and covers what we basically have in the ELMO format.

The PESC-format is missing (compared to ELMO)

  • A hierarchical course structure
  • Attachments (this is provided by a separate XML-format)
  • Extended description for elements
  • The possibility to make many generic user defined ID's 
  • The possibility to have several reports in the same report
  • To be able to specify language on several of the elements

The whole PESC standard can be found at http://www.pesc.org/pesc-approved-standards.html

The while ELMO standard can be found at https://raw.githubusercontent.com/emrex-eu/elmo-schemas/v1/schema.xsd

More in depth comparison

I will here go through each field of the ELMO to see if there is a mapping to PESC

 

ELMO - elements
PESC - elements
Comment
 
elmoCollegeTranscript 
reportCollegeTranscriptTop level for PESC, cannot be more than one
generatedDateCollegeTranscript.TransmissionData.CreatedDateTime 
learnerCollegeTranscript.StudentType.Person 
attachmentNot presentThere is a separate XML format for sending attachments
signatureNot present 
extensionUserDefinedExtensions 
 
LearnerCollegeTranscript.StudentType.Person 
citizenshipResidencyResidency is an object that contains several items (state, province...), ELMO only has ISO-code for citizenship
IdentifierSIN, NSN, SSN, SchoolAssignedPersonID, AgencyAssignedID, RecipientAssignedIDSeveral ID's named for the american system, it is not possible to have generic ID's
givenNamesName.FirstName, Name.MiddleName

The Name object contains several items

familyNameName.LastNameThe Name object contains several items
bdayBirthBirth is an object that contains several items (BirthCity, BirthYear...), ELMO only has date in ISO-format
 
ReportCollegeTranscript 
issuerCollegeTranscript.TransmissionData.Source 
learningOpportunitySpecificationCollegeTranscript.StudentType.AcademicRecord 
issueDateCollegeTranscript.TransmissionData.CreatedDateTimeThere is, as far as I can see, only one date, so it is not possible to determine when the college finalized the transcript, only when the XML was generated
attachmentNot presentThere is a separate XML format for sending attachments
   
AttachmentNot present 
title  
type  
description  
content

 

 
extension  
 
IssuerCollegeTranscript.TransmissionData.Source 
countryNot presentThe PESC standard assumes a college in Canada or US, it seems
IdentifierOrganization.LocalOrganizationID + Lots of group typesAll of the identifiers seems very US/Canada specific, for instance LocalOrganizationIDQualifier: "Code for US states, etc., and Canadian provinces"
titleOrganization.OrganizationName 
urlNot present, can be put in NoteMessage, but that is not intuitive 
 
LearningOpportunitySpecificationCollegeTranscript.StudentType.AcademicRecord.Course 
identifierOriginalCourseIdSeems to be the closest. There are several ID's for classification and references, but they are all hard coded and you cannot put your own. Unless you want to use UserDefinedExtensions.
descriptionSeveral fields combined + NoteMessageThere are a wide array of fields to specify a course that in Elmo would be put in description (Requirement classification, Course classification, Proficiency classification ad so on)
titleCoursetitle 
typeN/AEverything seems to be courses, unless degrees are somewhere else
subjectAreaCourseSubjectAreaCodeFrom PESC: A code indicating the general subject area for a course. This code set is derived from the NCES - SCED taxonomy which represents subject area in the first two digits of the code (see documentation for CourseSCEDCodeType). It is intended to be kept synchorized with the SCED.
iscedCodeCourseScedCode?From PESC: The School Codes for the Exchange of Data maintained by the Center for Educational Statistics (NCES) code to describe the area of study for the course.
urlNot present 
specifiesN/A 
hasPartN/ANo hierarchy i PESC
extensionUserDefinedExtensions 
 
LearningOpportunityInstanceCollegeTranscript.StudentType.AcademicRecord.Course 
startCourseBeginDate

 

dateCourseEndDate 
academicTermNot present 
engagementHours  
languageOfInstructionLanguageOfInstruction 
resultLabelCourseAcademicGradeThere are several fields on CourseAcademicGrade that results in a very good description of the academic grade
shortenedGradingCourseAcademicGradeScaleCodeDoesn't seem to be directly transferable, as it leans on the American system and have no need to describe the system itself
resultDistributionNot present 
creditCourseCreditUnits, CourseCreditLevel, CourseCreditValue, CourseCreditEarnedAll four combine to describe credits
extensionUserDefinedExtensions 
   
AcademicTermNot present 
title  
start  
end  
 
IdentifierNot presentNot present how we see it. PESC uses a multitude of identifiers to accurately describe their data, but they are all specific for US/Canadian academic records.
notation  
type  
schemaAgency  
 
CreditCollegeTranscript.StudentType.AcademicRecord.Course.CourseCredit* 
schemeCourseCreditUnits 
levelCourseCreditLevel 
valueCourseCreditEarned 
   
Result distributionNot present 
category  
description  
   
CategoryNot present 
label  
count  
description  
   
ShortenedGradingTableCollegeTranscript.StudentType.AcademicRecord.Course.CourseAcademicGrade*Several fields to describe but not really transferrable to ELMO
percentageLower  
percentageEqual  
percentageHigher  
   
Extension  
anyAttribute  
any  
  • No labels