![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
A&S is a pleasant place to volunteer. The stints are two hours each, in a shady little spot, with half the time being pretty slow. You're mostly just giving directions and talking people off the ledge when their class is canceled. Yes, we understand, it all sucks, complaints are over there. And, of course, you know with authority where your classes are.
Class schedules had a lot of drama. The booklet decided to cut the 80+ pages that contained the daily schedule, something that pleased no one. Something like nearly half the classes offered came in after the deadline. The schedule was the Word doc still available on the web site. It served for publication, but wasn't that helpful accepting changes or presenting in a different form. Don't you guys have a database?
It seems there was an MS Access database that was used successfully in the past. However, it apparently required some computer savvy and the computer savvy person was a no show. The Lady in charge was not an IT geek and ended up spending all waking hours getting the evil little computer beast to do her bidding. I put in some time doing this, as well. However, from the source material it was not trivial.
I offered my services as a DBA to get the thing tamed for next war, to whoever gets saddled with the job. I really hope they take me up on it.
I've written most of it in my mind. A database back end holding classes, teachers, locations, scheduling, etc. The ability to not just schedule but make edits, like moves or cancellation, and track it. Represent the data to the user in a myriad of ways. Have the data be updated to the website live. Ideally, the Daily Tidings could make use of this at printing.
I've done projects like this before. The complexity of scheduling is usually in assigning and validating students, which can be avoided for this. I'm considering just writing it and saying, "here, it works, take it, enjoy."
Class schedules had a lot of drama. The booklet decided to cut the 80+ pages that contained the daily schedule, something that pleased no one. Something like nearly half the classes offered came in after the deadline. The schedule was the Word doc still available on the web site. It served for publication, but wasn't that helpful accepting changes or presenting in a different form. Don't you guys have a database?
It seems there was an MS Access database that was used successfully in the past. However, it apparently required some computer savvy and the computer savvy person was a no show. The Lady in charge was not an IT geek and ended up spending all waking hours getting the evil little computer beast to do her bidding. I put in some time doing this, as well. However, from the source material it was not trivial.
I offered my services as a DBA to get the thing tamed for next war, to whoever gets saddled with the job. I really hope they take me up on it.
I've written most of it in my mind. A database back end holding classes, teachers, locations, scheduling, etc. The ability to not just schedule but make edits, like moves or cancellation, and track it. Represent the data to the user in a myriad of ways. Have the data be updated to the website live. Ideally, the Daily Tidings could make use of this at printing.
I've done projects like this before. The complexity of scheduling is usually in assigning and validating students, which can be avoided for this. I'm considering just writing it and saying, "here, it works, take it, enjoy."