#event_scheduler
1. ACADEMIC Activities:
Description: Create an academic activity event.
Fields: ASSINGMENTS, QUIZZES, EXAM, VIVA, LAB-REPORTS, COURSE NAME, INSTRUCTORS NAME, MARKS, DEADLINE, TARGET BATCH, TARGET BRANCH, TIMING, REMINDER TIME.
Database: All COURSE NAMEs added to the db.
2.BRANCH Related Activities:
Description: Create an activity event specific to a branch.
Fields: ASSINGMENTS, QUIZZES, EXAM, VIVA, LAB-REPORTS, COURSE NAME, INSTRUCTORS NAME, MARKS, DEADLINE, TARGET BATCH, TARGET BRANCH, TIMING, REMINDER TIME.
Database: All course are added to the db with respect to each branches specifically.
3.CLUB Related Activities:
Description: Create new event for a club.
Fields: MEETINGS, PARTIES, TUTORIAL, WORKSHOP, PROJECTS,DEADLINE, TARGET BATCH, TARGET BRANCH, TIMING, and REMINDER TIME.
Database: All the clubs name were added in the database, like CODING CLUB, AERO-MODELLING etc.
- OCCASSIONAL Activities:
Description: Create a new event for special ocassions.
Fields:MEETINGS, PARTIES, WORKSHOP, PROJECTS, DEADLINE, TARGET BATCH, TARGET BRANCH, TIMING, and REMINDER TIME
Database: ALl types of ocassional activities are added in the database. Like Alcheringa, UDGAM
5.ORGANIZATIONAL Activities:
Description: Create a new event for organization.
Fields:MEETINGS, PARTIES, TUTORIAL, WORKSHOP, PROJECTS, DEADLINE, TARGET BATCH, TARGET BRANCH, TIMING, and REMINDER TIME
Database: All the organizations are added in the database. Like SWC, SAIL, IITG.AI
- OTHER Activities:
Description: Create event that is not related to above five categories.
Fields: INTERNSHIP, PLACEMENT, HACKATHONS, SCHOLARSHIP PROGRAMS, VISTING FACULTY TALK, MINORS, COURSE REGISTRATION, COURSE DROP, COURSE FEEDBACK, FEE PAYMENT, DEADLINE, TARGET BATCH, TARGET BRANCH, TIMING, and REMINDER TIME.
Database: All these added to the database.
![image](https://user-images.githubuser content.com/84286157/130616595-2ec52ae4-0aa2-4650-ac5b-db5e8f3abd55.png)
- RSVP Options:
Description: It get created automatically each time any event is created, It is unique for an unique event. There are total 29 types of RSVP Model for to hold details of each of 29 events{AEROCLUB, AICLUB, ALCHERCLUB, ASTROCLUB, BT, CACLUB, CCDCLUB, CE, CH, CL, CODINGCLUB, CSE, DES, ECE, EDCLUB, EECLUB, EEE, FNCCLUB, MA, ME, OTHERCLUB, PH, PRAKRITICLUB, SAILCLUB, SWC, Task, Techniche, UGCLUB, ROBOTICSCLUB}
Fields: YES(all the profiles who clicked yes), NO(all the profiles who clicked no), MAYBE(all the profiles who clicked maybe), EVENT(The event for which this rsvp is for).
API Endpoint: for each RSVP model there are in total 2 urls:-\ - "root_url/RSVP/{event_name}" : Lists all the RSVPs of {event_name} that has occured,occuring or will be occuring. It also has searching and ordering filters for the fields of YES, NO, MAYBE, EVENT.\
- "root_url/RSVP/{event_name}/int:pk/" : Provides options for GET, PUT, PATCH, DELETE requests for that specific instance of RSVP with id=pk
where event_name can be => {AEROCLUB, AICLUB, ALCHERCLUB, ASTROCLUB, BT, CACLUB, CCDCLUB, CE, CH, CL, CODINGCLUB, CSE, DES, ECE, EDCLUB, EECLUB, EEE, FNCCLUB, MA, ME, OTHERCLUB, PH, PRAKRITICLUB, SAILCLUB, SWC, Task, Techniche, UGCLUB, ROBOTICSCLUB} (the above name specifies also the event for which that api is for\ e.g. RSVP/SWC endpoint is for RSVP for events of SWC)