Bill Dooley from DBMS demonstrated their calendar system. Written in Perl and was developed in house by a programmer who has since left the department; has admin and access features. Very easy to update; has an e-mail feature and can schedule the notification e-mail so can notify so many days/hours in advance of event. Can also send immediately if necessary. Has links to show details for each event. Link for questions is included on the detail page. Some tie-in to Big Brother monitoring could improve the system.
Is fairly slow, but comprehensive.
Would like to see it combined with the University calendar and the IT Critical Dates calendar (calendar.vt.edu; written by another person who has left). There are about 157 calendars online already. Need a way to combine/filter all these.
Next step: Who is taking responsibility to deal with calendars and other tools? Is there a subcommittee covering this, or is this something for the full committee to discuss?
The SAMS group will make a recommendation on features a calendar system should have. Discussions will ensue at future meetings. Be thinking about what you think should be included in such a system; filtering for users/level of announcements/how to subscribe, etc. Not only to notify, but also use for choosing event dates. If this became an "authoritative source" for such events, everyone would benefit.
Check it out: https://dbweb.db.vt.edu/dbcalAnonymous access is allowed.