[Feature] Admin dashboard for viewing page scrapes and corresponding output data for all updates #164

New issue

Open

opened 2025-02-02 19:24:28 +00:00 by cirex-web · 3 comments

cirex-web commented

2025-02-02 19:24:28 +00:00

(Migrated from github.com)

Description

Will be incredibly useful for debugging future data-accuracy issues (that will inevitably arise)

Auditing/overwrites on api response (and future scrapes, idk) (when the times are from 10:30 PM to 8:30 PM, for instance.)
Warning system for anomalous times
Auto-send email to dining services when we modify hours

Designs

No response

### Description Will be incredibly useful for debugging future data-accuracy issues (that will inevitably arise) - Auditing/overwrites on api response (and future scrapes, idk) (when the times are from 10:30 PM to 8:30 PM, for instance.) - Warning system for anomalous times - Auto-send email to dining services when we modify hours ### Designs _No response_

ajxu2 commented

2025-03-15 21:55:02 +00:00

(Migrated from github.com)

Monday, March 16, 2025, Hunan hours mistakenly start at "11:45 PM" instead of "11:45 AM"

Monday, March 16, 2025, Hunan hours mistakenly start at "11:45 PM" instead of "11:45 AM" <img width="571" alt="Image" src="https://github.com/user-attachments/assets/542962b7-c479-4489-baa8-2fe39cf8af6d" />

GhostOf0days commented

2025-03-15 23:38:13 +00:00

(Migrated from github.com)

Ok. Let's add a simple change to scraping that fixes this issue based on whether the opening time is (>= 12:00 PM and <= 11:59 PM), and the closing time is >= 12:01 AM. If this is the case, make the hour for "start" hour - 12 (or simply modify the string itself). Note that I didn't say 12:00 AM because we already deal with that iirc.

ajxu2 commented

2025-03-16 05:11:22 +00:00

(Migrated from github.com)

#178 fixes the issue in the image, obviously only fixes this one very specific instance. We could also implement more advanced logic which I posted about in the Slack channel.