If posting has been light, one reason is I’m spending nearly all my non-working hours trying to sort out a new membership management system for my club. I consider this part of the “local engagement” I was speaking about earlier.
We largely decided not to go with a cloud-based solution, which is fine with me. Maybe this will be my curmudgeon technology issue, because the young folks seem to love the cloud, and even I have to admit, having worked with Amazon Web Services professionally, and helped a few clients through migrations, Bezos has built one hell of a nice ecosystem. But I like the saying, “There is no cloud. There’s just someone else’s computer.” I don’t like the idea of trusting personal data to an entity I don’t really know or trust, and who only sees me as one of many income sources. Also, AWS is damned expensive. So are most other Cloud solutions.
We have an existing card access system for the gate and for the various doors around the property. The old system worked off an Access database. Recently we upgraded that software, and the new version is backed by SQL Server. The old card access system was a mess. There were people in the system who had been dead for some time and still had active cards. People were missing from the system who were members. I think some of them may be grandfathered lifers who just never bothered picking up an access card. It took another trustee helping me sort that out, and I’m still not sure all the cards are assigned correctly.
Originally I had chosen to put the member database in MySQL. Since I already have SQL Server running, why not just use that? Saves having to run a Linux machine and cuts down on the number of skill sets needed to maintain the system. As long as I’m cutting MySQL out of the picture, I might as well also cut OpenLDAP and set up Active Directory to use with Google Cloud Directory Sync (GCDS). I’m teaching myself a bit of PowerShell to make a script that will push out changes in the member database to the card access system, to QuickBooks (via qODBC), and to Active Directory.
After working with PowerShell scripting a bit, I’ve decided I hate it with a burning white hot passion. At this point I’ll probably stick to it because I’ve already invested the time, but the future of that function will probably be with Python if serious changes are ever required in the future. So in the end the system has ended up being far more Microsoft than I expected going in, becauseÂ I had no idea what the new card system would look like. Our new card system will even work with an ID card printer to manage and print member badges, so we got one of those too.
I think what I’m coming up with will be a decent platform for the next decade or so. It will certainly make managing dues processing for our 1300 members easier than the old paper process.