Planning notes from meeting 9‐11 - CSC4790-Fall2024-Org/Sororify GitHub Wiki
order of operations call:
super admin page can be done by one of us
- clean up stuff, delete old people, reset passwords
- can start on this separately
- assign roles to people
- are the roles given to them by someone on recruitment or do they sign on and make an account?
- be careful about what data you take from users, opens up a lot of data protection regulations
- integrate with something like google SSO API
- log in w a gmail account
- google will send us basic info back
- google info will be cached in a db, some long kind of id
- verify if people have logged in twice
- are the roles given to them by someone on recruitment or do they sign on and make an account?
when someone signs in, should they be given a pin specific to their chapter?
- won’t mesh well with google log in most likely, possible tho cross check
- admin can always throw out people who shouldn’t be there
if not using google api:
- django may have built in features: register for a new account and you are given basic access
- admin goes in later and assigns roles
- look at how django assigns users and roles Django: a web server
- project creation may be interactive, db access, etc
- we’ll write code that plugs into django for logic
- put algo, rbac stuff
we can ask django to interact with the db to do : create django project all together, make sure everyone has it running. django is the key to starting everything someone can go off and write python objects corresponding to db someone can do log in stuff we can tell django what kind of db we want to connect to
then we can divide tasks out
next: CORS will bite us at some point cross-site requesting blah blah prevents people from skipping frontend and going to backend look up ways to disable CORS when it comes up
API? django will act as our API. we’ll create a python object (member), make a class with their info then we’ll put an annotation in python (@something) above variable this will map stuff to our database
django allows us to save member object it also has a load method hand it a member object and say load, django will reach the db and populate fields
how does the frontend fit in this? api driven frontend-django-db
http endpoints for frontend to django interaction
method called submit survey or something
https://github.com/jdob/rayner-service/blob/master/rayner/urls.py models.py will show db stuff
just get it to where survey calls django and django dumps it into db do rbac later