@rachell_aristo

Added tables to admin dashboard

• ‘Today’s bookings’ (loan pick up = today)
• ‘New bookings’ (status = pending)
• ‘Overdue bookings’ (status = overdue)

This is just an intial structure tho…this isn’t very user friendly and is currently a lot of repeated code. I wonder if I can try using more visual diagrams and not tables to help with that

Added a reusable banner as a Jinja macro and used it in check out page to warn admin if the user has any overdue loans

Added equipment return function + fixed some bugs on check out

Added error handling for check out system. Includes:

• Check if user role = admin
• Try/except for writing to database, error messages for server error
• Checks for assets (Does the scanned asset exist? Is it avaliable?)

Added an equipment check out system that allows the media technician to check out a loan by typing in the barcodes of specific assets.

• Checks if scanned asset exists in catalog
• Checks if the same assets are scanned > once
• Checks if a scanned asset is not requested in this loan

And then saves the scanned barcodes to db.

to do: add error handling for this + add barcode scanner with cam function

Added/changed all email templates into HTML to allow more formatting options in the future

Added variables to approve emails (with Jinja) so it’s dynamic

• Also added a few util functions for converting int ids to the string value (for equipment ids, studio space ids, timeslot ids etc) I wonder if there is a built in method for doing this with sql alchemy?

Added fully booked (depending on avalibility from selected date) + not avali for year group messages

I added an equipment item column to the equipment bookings table so that admin can also filter search by equipment :)

Also added error handling for Flask Mail functions + updating loan status to db, which sends an appropriate message to admin about whether data was updated, email was sent etc.

Added functionality for studio booking table - modals, action buttons etc. Also added filters to all tables. This sounds simple cuz previously all worked on equipment table, but was actually a mess to refactor because now there’s equipment bookings and studio bookings not just one type 🫠

omg SO MANY UPDATES!! >:)

• Updated the equipment booking system to dynamically update quantity counts depending on the date range selected by user (JS fetch)
• My app now sends AUTO EMAILS WHATTT with Flask Mail. Legit so cool :)) When admin changes a booking, eg by approving/cancelling, it will trigger an email to the user
• Added a filter system to bookings table! Can filter by searching a value in any column

Added accept/reject/cancel button functions to admin page + table of bookings with color coded status. Clicking on rows brings up a modal with more info + action buttons

• Added verification for equipment booking: equipment must be allowed for the user’s year group, user must not have overdue loans and each loan has a limit for # of items loaned per equipmen type
• Basic table record display for all bookings on admin_home.html
• Updated CSS color scheme to fit school colors + unrounded elements (cuz I think the round UI design is over hyped) + made records more space efficent

AI use: used Gemini to help update CSS

Fixed a really serious problem I didn’t spot previously where the equipment loan record getting saved to db wasn’t saving the quantity properly when u book >1 of each equipment type…simply forgot to iterate through the quantity list I had made 🫠

Also added to student_home page so that equipment bookings also get shown :)

Finally have a working equipment booking page and system! Figuering out how to select the data of equipment type and quantity and send to py was low key a nightmare…

Basic tab system for sorting the equipment cards based on category :)

Created a CSV parser with pandas (first time using!) which I can incorperate into the admin interface later on. Sorted out a lot of logicial tough questions such as how do you iterate through a 2D array to create records?

Changed html + js so that the studio booking page allows for div cards w/ photos for each studio space instead of a boring form like structure

(css not fixed yet!)

Added comments to all my code + implemented Flask-Login. POV u came back to coding after like a month and realized you don’t understand what you wrote…comments for future me now. As for Flask-login, I implemented it cuz it makes sense to use it instead of manualy building login functions

(in screenshot - goodbye manual login functions woop)