---
# System prepended metadata

title: Doubts Document

---

# Doubts Document 

1) In organiser details it is mentioned to store organiser category. Does this mean the following categories : Clubs, Councils, Fest Teams.
2) In section 9.5 it is mentioned that emails need to be sent out to the participants, do we actually need to send an email to them or just simulate sending an email?
3) Do we need to allow the participant to cancel their merchandize purchase and add that back to the remaining stock?
4) Does eligibility mean iiit/non-iiit?
5) Do we need to follow the flow of event creation (given in section 10.4) strictly or can we have an option to publish directly without creating a draft first?
6) What is meant by participant type?
7) What does team completion mean analytics in section 10.3?
8) In section 10.3 it is mentioned that we need to list if the participant was present in an event, how do know if a participant went to an event, should we just simulate and randomly assign present/absent?
9) What areas of interests are required to be given to the participant to select from?
10) In section 9.6 it is mentioned that follow/unfollow clubs option has to be given on the profile page but in section 9.7 it is mentioned that it has to be given on the clubs/organizers listing page, do we have to give the option on both the pages?
11) Can we change the links present in navbar, basically cosmetic changes like remove logout from there and keep on it on dashboard etc.?
12) Are we allowed to use mongoose instead of just mongodb? And also nodemon instead of node?
13) Are we allowed to modify the package.json (which u get after entering 'npm init -y') file "type": "commonjs" to "module"?
14) Refering to question 8,if we are not doing the 3rd task in section 13.1 then do we not need to put the attendance field?
15) Do we just directly insert the admin credentials into the database directly or do we have to create a seeding script?
16) In section 11.2, if the system auto-generates email and password whilst creating the organizer, that means the admin does not have an existing email for the organizer, which means we cant check if that organizer already exists. Should we assume that the names will be unique to check for the same?
17) can we use javascript xml for frontend instead of using standard javascript?
18) "Use services like Google reCAPTCHA v2/v3 or hCaptcha" Can we use any other Captchas like turnstile?
19) "IP-based blocking for suspicious activity" Won't this make our website basically unusable when a lot of people from same college start registering together?
20) In 11.2 2nd part, we are asked to block accounts such that clubs etc. can't login. Does this mean the next time they try to login since we can't really block accounts while using pure jwt logic?
21) Can we use clubs' official iiit email id for login and contact both as that's what they are used to and it'll be easier to implement cas in future?
22) " Search: Partial & Fuzzy matching on Event/Organizer names" Using $regex in MongoDB to allow Partial matching is fine, right?
23) In section 7.2 what does "individual purchase only" mean?
24) Can normal event registerations be paid as well or do only the merchandize events need to have paid registerations?
25) Are we allowed to use daisyui, react-toaster or tailwind for the frontend?
26) In case an organizer is permanently deleted by the admin, how should the system handle events associated with that organizer—should they also be deleted?
27) Are we allowed to use Prisma with the native MongoDB driver for the backend?
28) What do we have to display on Admin dashboard?