For maintaining the timetable scheduler need a admin panel

Sarath191181208 / vitap-timetable-scheduler

vitap-time-table-scheduler.vercel.app

3 stars 10 forks source link

For maintaining the timetable scheduler need a admin panel #2

Closed sanjay7178 closed 2 months ago

sanjay7178 commented 3 months ago

Or we can make a github action upon uploading csv need to create a artifact and create a PR for preprocessed data

sanjay7178 commented 3 months ago

Need a UUID or ULID based url approach for persistent/cached timetable for sharing

sanjay7178 commented 3 months ago

Need a semester drop down as well

Sarath191181208 commented 3 months ago

Or we can make a github action upon uploading csv need to create a artifact and create a PR for preprocessed data

We already have the python scripts required for this task to generate the json data and we could just copy paste the required data. As any errors generated by copy paste are caught by tsserver. So, therefore I having GitHub actions to having a PR open up and merging the ourselves wouldn't be better as the scope of the project is super focused.

Sarath191181208 commented 3 months ago

Need a UUID or ULID based url approach for persistent/cached timetable for sharing

How would you suggest that we should build this feature. I could think of two types of approaches:

As you have suggested give UUID to a user and save his data and just send a sharable link. Requires a persistent store like DB. Firebase would be easier to manage as it automatically provides Google Oauth for authorisation.
Save the data as query params and give the link. Have to research on this idea and the data we have to send is relatively big to usual links

sanjay7178 commented 3 months ago

Need a UUID or ULID based url approach for persistent/cached timetable for sharing

How would you suggest that we should build this feature. I could think of two types of approaches:

As you have suggested give UUID to a user and save his data and just send a sharable link. Requires a persistent store like DB. Firebase would be easier to manage as it automatically provides Google Oauth for authorisation.

Save the data as query params and give the link. Have to research on this idea and the data we have to send is relatively big to usual links

adhering to query params for entire data will be difficult , better to have a KV database like redis or cloudflare workers kv for faster retrieval of json data with prior jwt/session based approach , or simple use firestore for long term data persistence

Sarath191181208 commented 3 months ago

Good suggestion for a solution. But having another service to manage for a webapp that would be used once a semester is debatable.I'll try making query params happen.If that doesn't work, I am open to any other persistent store/ session management etc.