The Google Calendar API is best dealt with via Python, IMHO. This would be a good starter app to build. One page would display the available events and whether you are listed as attending, request pending approval, or absence approved. Clicking on your status would let you change it. The admin page would show pending requests and let the admin click to approve or reject. You wouldn't need a database, as you can repurpose the status field (and the associated text field) to store the state.
You could probably do this without using the API. Invite people and have them click "no" to ask permission to be absent. The facilitator then approves the request by deleting them from the invite list. It will look a little unpolished and "home brew" but that might be sufficient to meet your needs. Tom On Wed, May 14, 2014 at 8:27 AM, Adam Levin <[email protected]> wrote: > Hey all, I've got a question that hopefully the collective can help me > answer. > > A local choir group has asked around for some help with some web > development, and since I'm "a computer guy" I've been specifically asked if > I can help. > > I've done basic web development in the past (CGI scripting and such), > usually in PERL. I haven't done it in a while, and I've never worked on a > project basis -- always salaried for a company. > > What they want looks relatively simple. They want a calendar of events, > and they want members to be able to submit requests to be absent. The > calendar events would be manually entered, I think, but they want to > automate the absence requests as much as possible. > > There needs to be some logic about making sure that if too many of a > particular voice (say, lots of tenors) have requested absence, it will > automatically deny the request, otherwise it'll approve it. So, a small > database of members and who's planning to be absent for which events would > be kept, probably in the calendar itself or maybe in a small backend > database. > > It looks like I can do this using a Google calendar and some PHP API > calls. I'd need to learn PHP unless there are PERL API calls I can use > instead -- that's not a show stopper. > > What I'm curious about is getting some guidance as to what a project like > this might be worth? I have no idea how long it might take, or what the > going rate is for a dev project like this. > > I realize this isn't a lot to go on. I need to talk more with the > director to find out exactly what he wants, but any input would be > appreciated. It's been a long time since I've done web dev work. > > Thanks! > -Adam > > _______________________________________________ > Discuss mailing list > [email protected] > https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss > This list provided by the League of Professional System Administrators > http://lopsa.org/ > > -- Email: [email protected] Work: [email protected] Skype: YesThatTom Blog: http://EverythingSysadmin.com
_______________________________________________ Discuss mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
