Unterschiede
Hier werden die Unterschiede zwischen zwei Versionen angezeigt.
Beide Seiten der vorigen RevisionVorhergehende ÜberarbeitungNächste Überarbeitung | Vorhergehende ÜberarbeitungNächste ÜberarbeitungBeide Seiten der Revision | ||
faq:emrex_en [2022/01/25 14:18] – [Overview] tm1019 | faq:emrex_en [2022/01/25 14:20] – tm1019 | ||
---|---|---|---|
Zeile 26: | Zeile 26: | ||
===== Basic principles of transfer via EMREX ===== | ===== Basic principles of transfer via EMREX ===== | ||
- | * Transfer takes place between the IT systems of the participating universities. Either directly from university to university or via an intermediate platform such as [[https:// | + | * Transfer takes place between the IT systems of the participating universities. Either directly from university to university or via an intermediate platform such as [[https:// |
* The transfer is always intiated and confirmed by the students themselves. There is no automatic transfer of data that has not been initiated by students themselves. | * The transfer is always intiated and confirmed by the students themselves. There is no automatic transfer of data that has not been initiated by students themselves. | ||
* In order for students to initiate and approve a transfer, they must have valid accounts for both IT systems involved in the transfer at the time of transfer. | * In order for students to initiate and approve a transfer, they must have valid accounts for both IT systems involved in the transfer at the time of transfer. | ||
+ | |||
+ | ===== Which data will be transmitted ===== | ||
+ | The data is transferred in the EMREX ELMO format. "The ELMO XML format is the basis for the exchange of result information. Elmo is based on the CEN standard EN 15981-2011 EuroLMAI. EuroLMAI is a data model describing assessments, | ||
+ | |||
+ | The EMREX ELMO format provides for a few mandatory data and a very large amount of optional data. Basically, students (for systems known to ALU campus management) are shown which data to transfer before a transfer is made. Students can decide at any time not to transfer the displayed data by not triggering the transfer. | ||
+ | |||
+ | In the ALU campus management system HISinOne, only a part of the basically possible data is provided during export. This part is described below. The import should be able to handle all content defined in the EMREX-ELMO format. If necessary, certain elements are not displayed on the interface, but are only contained in the Technical Message (XML file), which can be displayed at any time for control purposes. | ||
+ | |||
+ | In HISinOne, the following are provided for transmission: | ||
+ | * Creation date of the technical document creation. | ||
+ | * Information identifying the student: | ||
+ | * First Name | ||
+ | * last name | ||
+ | * matriculation number | ||
+ | * System internal GUID | ||
+ | * (First) nationality | ||
+ | * Date of birth | ||
+ | * Place of birth | ||
+ | * Gender | ||
+ | * Identification information University issuing the certificate of achievement: | ||
+ | * For all modules marked for transfer by the student: Module information: | ||
+ | * As embedded PDF: "EXA 251 EMREX(e) (01a-2022) Performance Overview Students" | ||
+ | |||
+ | The embedded performance overview is provided in the EMREX-ELMO scheme as a lowest common denominator or fallback level in case there are problems with the automatic processing of the transferred " | ||
+ | |||
+ | *learningOpportunityInstances: | ||
+ | |||
+ | |||