You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 5, 2022. It is now read-only.
Why run for ODs if the app can do the running for you?
After the student logs in, an OD section should be displayed where students could apply for ODs. Once they have applied, a notification goes to the faculty in charge. Once they accept it, a notification goes to the student's advisor. And once that is accepted, the student gets a notification that the OD has been sanctioned.
The text was updated successfully, but these errors were encountered:
Woot. That's a great idea but I do see a lot of fallbacks here.
I'm not sure how this is going to work. If this has to be implemented as a feature of the AUMS, it is going to be painful. Even if it is going to be part of AUMS, staff authentication is anyway not gonna work because the port (8443) in which the staff login is configured is IP restricted and possibly even MAC filtered. Unless the university decides to provide an API to authenticate a staff somehow, I don't think staff logins will be possible.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Why run for ODs if the app can do the running for you?
After the student logs in, an OD section should be displayed where students could apply for ODs. Once they have applied, a notification goes to the faculty in charge. Once they accept it, a notification goes to the student's advisor. And once that is accepted, the student gets a notification that the OD has been sanctioned.
The text was updated successfully, but these errors were encountered: