| Beide Seiten der vorigen RevisionVorhergehende ÜberarbeitungNächste Überarbeitung | Vorhergehende ÜberarbeitungNächste ÜberarbeitungBeide Seiten der Revision |
| faq:emrex_en [2022/01/28 10:55] – tm1019 | faq:emrex_en [2022/01/28 13:15] – [Known Issues] tm1019 |
|---|
| * [[https://emrex.eu|EMREX]] | * [[https://emrex.eu|EMREX]] |
| * [[https://pim-plattform.de/en|Platform for Inter*national Student Mobility (PIM)]] | * [[https://pim-plattform.de/en|Platform for Inter*national Student Mobility (PIM)]] |
| In principle, all mechanisms developed in these projects and initiatives are not only suitable for international mobility, but also for student mobility within Germany. In particular, in the course of the [[https://pim-plattform.de|PIM project]], some functionalities for the campus management system HISinOne were defined and implemented, which are now technically (after 2022-01-27) also available in the HISinOne system at ALU. Before operational use at ALU, a whole range of strategic, operational, legal and technical questions still need to be clarified. **The functionality is currently only used experimentally at ALU. The actual recognition processes are governed by the processes described in the faculties and institutions.** | In principle, all mechanisms developed in these projects and initiatives are not only suitable for international mobility, but also for student mobility within Germany. In particular, in the course of the [[https://pim-plattform.de|PIM project]], some functionalities for the campus management system HISinOne were defined and implemented, which are now technically also available in the HISinOne system at ALU. Before operational use at ALU, a whole range of strategic, operational, legal and technical questions still need to be clarified. **The functionality is currently only used experimentally at ALU. The actual recognition processes are governed by the processes described in the faculties and institutions.** |
| |
| ===== Basic principles of transfer via EMREX ===== | ===== Basic principles of transfer via EMREX ===== |
| ===== Known Issues ===== | ===== Known Issues ===== |
| * Calling other universities, from which achievements should be retrieved, currently in some cases still not possible, although these universities participate in the EMREX network (we are waiting here for a hotfix from the system vendor). Example: when trying to retrieve services from the (test) system of EPICUR University Uniwersytet im. Adama Mickiewicza w Poznaniu the error message "Przepraszamy. Wystąpił błąd serwera. Administratorzy zostali powiadomieni i postaramy się go szybko naprawić. Jeśli problem będzie się powtarzał przez dłuższy czas, prosimy o kontakt." | * Calling other universities, from which achievements should be retrieved, currently in some cases still not possible, although these universities participate in the EMREX network (we are waiting here for a hotfix from the system vendor). Example: when trying to retrieve services from the (test) system of EPICUR University Uniwersytet im. Adama Mickiewicza w Poznaniu the error message "Przepraszamy. Wystąpił błąd serwera. Administratorzy zostali powiadomieni i postaramy się go szybko naprawić. Jeśli problem będzie się powtarzał przez dłuższy czas, prosimy o kontakt." |
| * Imported data cannot be deleted again by the student or the examination office. | * Imported data cannot be deleted again by the student or the examination office. If data is to be deleted, please email [[cm@rz.uni-freiburg.de|cm@rz.uni-freiburg.de]]. |
| * URL to module description (<url>) is included in Technical Message (XML file) generated by HISinOne, but is not displayed on the interface when received from another HISinOne system. | * URL to module description (<url>) is included in Technical Message (XML file) generated by HISinOne, but is not displayed on the interface when received from another HISinOne system. |
| * Generation date <generatedDate> of the generated Technical Message (XML file) is always date with time T00:00:00, but XSD says: "The datetime when the file was generated.". [...] Example values: "2015-08-01T12:00:00+02:00", "2015-08-01T10:00:00Z") | * Generation date <generatedDate> of the generated Technical Message (XML file) is always date with time T00:00:00, but XSD says: "The datetime when the file was generated.". [...] Example values: "2015-08-01T12:00:00+02:00", "2015-08-01T10:00:00Z") |
