Page History

...

• UNIC Virtual Campus Admin (superadmin)
  • a person employed at University Computing Center, University of Zagreb
  • has the privilege of administering UNI Admins and common data

Process

Becoming a UNI Admin

1. A list of persons who will become UNI Admins is communicated with the University Computing Centre, Uni Zagreb (via e-mail or regular mail).
2. A person logs in the VC Admin application using their own IdP. Confirms the GDPR statement regarding the personal data. The account is not valid yet, it is pending approval. Superadmin gets a notification. 
3. A superadmin logs in the system, checks the list of preapproved UNI Admins, and grants/denies a UNI Admin privilege.

Becoming a OrgUnit Admin

1. A person logs in the VC Admin application using their own IdP. Confirms the GDPR statement regarding the personal data. The account is not valid yet, it is pending approval. UNI Admin gets a notification. 
2. A UNI Admin logs in the system, checks the person and grants/denies a UNI Admin privilege.

Offering a Course

Course offers can be updated each academic year.

Via API: 

1. A course that will be offered to UNIC students needs to be described in local SMS 
2. Local SMS pushes the course offering to VC via API. 

Manually:

1. 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). 

1. 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.
2. Home OrgUnit Admin checks the prerequisites for the course (if needed consults with the students mentor / study programme lead / …). Enters a decision in VC (deadline: CS_DATE-25):
1. denied - the process ends here, student gets a message
2. approved - the process continues; receiving OrgUnit Admin gets a message
3. 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):
1. denied - the process ends here, student gets a message
2. approved - the process continues
4. Student is enrolled (deadline: CS_DATE-10):
1. the data are copied in receiving SMS (and LMS) via API or
2. the data are entered manually in receiving SMS (and LMS) by home OrgUnit Admin
   
5. Course starts (at CS_DATE).

Course ending

1. If the student drops off the course during the course, that information is entered in VC via API or receiving OrgUnit Admin;
   Otherwise, when a student finishes the course, the final grade is entered in VC via API or receiving OrgUnit Admin.
2. If home OrgUnit is using API
1. 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
3. If home UNI is not using API:
1. home OrgUnit Admin gets a message
2. home OrgUnit Admin logs into VC, gets the data and enters it in home UNI SMS

Student Card Issue

1. Student logs in the Student portal using their IdP via eduGAIN
2. Gives GDPR consent for using personal data, data from IdP is stored in VC
3. Using the portal, student generates a card; a card is sent to student's e-mail
4. A card can be stored in the mobile device 

Student Card Verification

1. Student presents a card to anyone interested
2. Using a QR-code reader app, interested person scans the QR code of the card
3. Scanned QR code leads to part of the public VC portal, the application that checks the validity of the card and presents the result on the web page (valid / not valid)

Invalidating the UNIC Student Status

If a home UNI uses API, the status of the UNIC student can be revoked via API. Otherwise, the UNIC student status is revoked by the home UNI Admin via Admin portal.