Closed Vikhyath08 closed 3 years ago
Also, what do we call their heads? I don't think it is "Secretary" or "Joint Secretary".
I guess renaming it to "Point of Contact" will be ok. We might be adding occational fests like technex as entities.. so a generalized POC will serve our purpose? WDYT?
@nishantwrp @nishantkr18 Before merging, please confirm whether the heads of SCS or E-Cell create the events, and there aren't any sub-divisions or sub-heads in them who create the events.
Instead of complicating into subdivisions, IMO, for now lets keep it simple. No subdivisions, we can add them later if we want. But again, its just an opinion..
@nishantkr18 Renaming to POC will be alright. As of now, we have a Secy (only one) and Joint-Secy (multiple) in an Entity. So, shall we change this to Point of Contact (multiple)?
@nishantkr18 Renaming to POC will be alright. As of now, we have a Secy (only one) and Joint-Secy (multiple) in an Entity. So, shall we change this to Point of Contact (multiple)?
Yeah sure👍
@Vikhyath08 Please make this change, so that we can merge this PR.
I think, in the authentication/views.py
file, in ProfileSearchView
, the POC of an entity shall be allowed to search a user so that the POC can search and add the contacts to the workshops (events).
I think, in the
authentication/views.py
file, inProfileSearchView
, the POC of an entity shall be allowed to search a user so that the POC can search and add the contacts to the workshops (events).
Yep true. Had overlooked that
Merged! :tada:
Added model, serializers, views and urls for entities.