...
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
| Panel | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
Basic definition and factsWhat is it? UNIC Virtual Campus is an information system consisting of a central database (central register) and several web applications and application programming interfaces (APIs). What will it serve for? Firstly, it will cover the mobility of students and virtual student cards. Later on, it will connect research activity information as well. Who is building it? University of Zagreb, primarily University Computing Centre (SRCE). How is it funded? Initial phase of development is funded through UNIC and UNIC4ER projects. Everyday maintenance, superadmin tasks and further development funding should be discussed. Where will it be stored and running? On the servers of the University Computing Centre, University of Zagreb. There are two data centres with a shared virtualization platform for redundancy. How will users interact with the Virtual Campus? Mostly through the web applications of the Virtual Campus, but some data could be imported or obtained through APIs. Web applications will cover all the functions of APIs, and more. Abbreviations VC - Virtual Campus (UNIC Virtual Campus Information system) SMS - Student Management System (a local information system containing data about students, courses, teachers, exams, etc.) LMS - Learning Management System (a local information system containing data about courses, learning materials, exams, etc.) IdP - Identity Provider (authorization and authentication infrastructure used for storing and verification of electronic identities of students and staff at the university) |
...
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
ProcessOffering a courseCourse catalog Course enrollment Course ending and grades Joint programmes catalog Student Card Issue Student Card Verification Invalidating the UNIC Student Status |
...
More about the possibilities of working in the system can be found on the following links:
Children Display
Process
Offering a Course
Course offers can be updated each academic year.
Via API:
- A course that will be offered to UNIC students needs to be described in local SMS
- Local SMS pushes the course offering to VC via API.
Manually:
- OrgUnit Admin edits a course offering in the Admin portal manually.
Course enrollment
This process is time-framed, based on when the course starts. All parts of the process should be over by the date when the course starts (CS_DATE).
- A student browses through courses offered in the VC and chooses the one (or more) that she/he wants to enroll in (deadline: CS_DATE-35). Home OrgUnit Admin gets a message.
- Home OrgUnit Admin checks the prerequisites for the course (if needed consults with the students mentor / study program lead / …). Enters a decision in VC (deadline: CS_DATE-25):
- denied - the process ends here, student gets a message
- approved - the process continues; receiving OrgUnit Admin gets a message
- Receiving OrgUnit Admin checks the prerequisites (is the course already filled up etc.; if needed, she/he consults with the student, teacher, home OrgUnit Admin). Enters a decision in VC (deadline: CS_DATE-15):
- denied - the process ends here, student gets a message
- approved - the process continues
- Student is enrolled (deadline: CS_DATE-10):
- the data are copied in receiving SMS (and LMS) via API or
- the data are entered manually in receiving SMS (and LMS) by home OrgUnit Admin
- Course starts (at CS_DATE).
Course ending
...
- Upon the entry of the grade or drop-off info into VC, the grade or drop-off info is returned to home OrgUnit via API
...