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
Describe the bug
There isn't any unique field in the FacultyMember model currently. There should be a unique field throughout the model which can be used to identify one Faculty from the list. I think employee_id can be one such field, as added in the commit in shell for IIT-R.
The text was updated successfully, but these errors were encountered:
I know about the id, but my concern is identifying the faculty not the primary key. Just like a Student have a unique enrolment number, Faculty should have a unique number.
This can help in two ways:
Whenever there is required a migration from some institute data to the Omniport or vice-versa, there should be some key which maps both the data.
With this we can offer a login through employee_id just like student can login through their enrolment number.
I am not sure if for every institute, faculty get an employee id, but if it is true, there is no field in the Omniport to store this data.
Describe the bug
There isn't any unique field in the
FacultyMember
model currently. There should be a unique field throughout the model which can be used to identify one Faculty from the list. I thinkemployee_id
can be one such field, as added in the commit in shell for IIT-R.The text was updated successfully, but these errors were encountered: