Skip to content

Using Attendizer

thegu5 edited this page Nov 1, 2023 · 3 revisions

How Do I Use Attendizer?

Presumably, you've followed the instructions in Running Attendizer. If not, go there first.

Using Attendizer Locally

  • Once you have the project running, you can go to http://localhost:3000 to see the main page of the frontend. This is where you can scan in people each day.
  • You'll notice you need a password/key. If you're running this locally, the password will be stored in your .env file and be what you set it to previously. If you type the incorrect password, you won't be able to send any requests to the backend (serverless functions) from the frontend.
  • You can see the other pages in /pages/, where the name of the file will correspond with the name of the page. (except index.js which is the default page and anything in /api which are part of the backend)
  • To access these other pages, go to http://localhost:3000 + whatever page you want to go to (case sensitive). For example, http://localhost:3000/admin.

Main Page

  • As detailed before, this is where you can "scan people in" each day. This will take in any UID or Student ID (as seen on the admin page) and tell the database to mark them as present for the day.
  • The Student ID or UID must be 9 or 13 digits respectively. Each file checking for these values will ensure they are the correct length, so they can be modified there.

Admin Page

  • This is where you can add students or edit their information. This is important as the UID of a student will change each time they get a new ID card from the school.
  • You again will need a password here, but it will be the same password as the main page.
  • Again, the student ID and UID must be the correct lengths.
  • There's a button to export all of the student data. This exports in the .xlsx format, and contains all studen data along with their meeting attendance.

Meetings Page

  • This is where you can delete meetings.
  • This is usually for cleaning up accidental meetings created, in that event. Otherwise, this page should almost never be touched.
Clone this wiki locally