VolDB
Doc Link: http://apourl.co/VolDB
The Apogaea Volunteer Database is custom built solution that is used to create and track volunteer shifts during the event. Email VolDB@apogaea.com if you have questions or need help, this is the team that managed the VolDB content and is a sub-department of IT.
The goals are to have it on-line about the same time tickets go on-sale each year so the general public can choose volunteer shifts. It should be opened for leads\admins to enter shift data a couple of weeks before the public go live date. Then two weeks before the event the DB is locked down so only admins can manage changes.
You can access the VolDB here: http://volunteer.apogaea.com. We suggest setting up an account in the VolDB using your personal email address, not your @apogaea.com account, unless you are a lead who will be managing departments or shifts in the VolDB. This is due to the fact that @apogea.com accounts are only kept for those with a current role in Apogaea for the year, accounts are disabled and then deleted after 2 years of non-use otherwise. The VolDB is also used by Elsewhence, CBE, and Denver DeComp. Accounts in the volunteer database are setup by users themselves, then a current admin can give accounts more rights (like to add\edit\delete department and shifts). There is no per event or per department delegation support in the VolDB, so limited people are given rights to manage content in it, to prevent accidents and to ensure things (mainly shifts) are setup the best way.
For more info on the VolDB see the About page at https://volunteer.apogaea.com/about.
2024 VolDB Ember Report - Google Docs
The VolDB is hosted on Digital Ocean hosting site, currently running on Debian 9 and the team is working to move it to Docker in the future. The team has been lead by Rachel Fish since 2017 and can be contacted at voldb@apogaea.com.
The first three of these require your account in the VolDB is setup as a "department-lead", which can be done by emailing your login\email used for the VolDB to VolDB@apogae.acom. These rights are given out on an AS NEEDED basis, since rights apply to ALL events and ALL depts and shifts in the VolDB
Edit/Delete Scheduled Shift - DO NOT edit a shift once people have signed up for one in the series, their sign-up will be LOSS. You can make a note of such shifts and then manually reassign them those shifts though.
These are for the Apogaea 2025 event ONLY. You must be setup as a Dept Lead in the VolDB, if you aren't or can't access these pages email VolDB@apogaea.com
Create the dept here: department/create
Add shifts to it here: shift/create
Add schedules for the shift here: schedule/create - Click Does this shift happen on a specific date & time? to set the day & time for the shift
History
The 2011-2016 VolDB was managed by the VolDB team and written in Django and Python and hosted on Heroku. The source code is stored in GitHub here: https://github.com/Apogaea/voldb/. The initial code was created in PHP and MySQL by Bug sometime before 2010. When Bug left in 2013, Koda and Piper rewrote the application in Python and PostgreSQL for 2014. For Apogaea 2015, a 5-member team of developers re-factored new code base in a move towards splitting client and server architecture. Ultimately, not all of the work from 2015 made it into the release branch. For 2016 Piper maintained the system, but he was the only active member of the VolDB Dev team.
Backup plan
Should there come a time when no community members are available to able to support or replace the existing software see this document on this topic: Other Volunteer DB Solutions
VolDB Lead Job Description
Ultimately, the Volunteer Database Lead is responsible for ensuring Apogaea has a public-facing piece of software that allows the community to schedule volunteer shifts at the event. This lead will work directly with the Volunteer Department Lead to define each year's specific requirements and ensure that software and support are available. The Volunteer Database Lead for 2014 and 2015 organized a team of volunteers to assist in the development and maintenance of the existing software and some of these volunteers are likely to be interested in continuing their support.
A software developer with a moderate level of group development experience and a basic grasp of Python/Django will probably have little trouble understanding and managing the existing software. With a clean, readable, well-documented code base, an experienced Django developer should be able to immediately move into adding features and improving the existing tool. While this lead will enjoy the autonomy of choosing how to meet the requirements laid down by the Volunteer Department Lead, this lead has the potential to benefit from the established momentum and volunteer interest from previous years.
Jan: Pick solution and setup admins to start leaning
Early Feb: Shift data imported from previous year
Late Feb: Team leads setup with shift admin access
Early March: Team leads have all shift entered and VolDB opens to public
April: People sign-up for shifts
End of May: Lockdown DB and get data exported to binders or some other method to be accessible at the event
June: Event
Should there come a time when no community members are available to able to support or replace the existing software,:
Moved to: Other Volunteer DB Solutions
2018- 2025 Team Members
Team group: VolDB@apogaea.com
VolDB Lead: Rachel Fish
Admins: Izzy & Birthday
2017 Team Members
VolDB Lead: Chris Dobell
VolDB XXXO:
Volunteer Lead: Dana Sunshine
Admins: Izzy & Birthday
2016 Team Members
VolDB Lead: Chris Dobell - cdobell@apogaea.com
Lead Developer: Aaron Merriam "Piper" - piper@apogaea.com - Django
Admins: Koda, Izzy
2015 Team Members
Team Lead: Lead Koda@apogaea.com
Lead Developer: Aaron Merriam "Piper" - piper@apogaea.com - Django
Data Management: Arthur Ketchman - apriori@apogaea.com
Data management: Dan Singer
Front-end & style: Amelia
Admins: Koda, Izzy