My 2025 motto is: No Spreadsheet.
Build a proper infrastructure and database for your community.
I'm going to invoice you instead of filling in your google forms. 😤
My 2025 motto is: No Spreadsheet.
Build a proper infrastructure and database for your community.
I'm going to invoice you instead of filling in your google forms. 😤
Living up to my 2025 motto: No more spreadsheets!
I got to speak to @djangonaut yesterday about this very topic. Can't wait to share more publicly about what we're up to with #PyLadiesCon.
Stay tuned for the video recording.
@astraluma @mariatta This isn't exactly that, but it's interesting.
@glyph @pathunstrom If you're just going to read the data, if you're the only one who need the data: yeah excel/spreadsheet is ok
Don't use spreadsheet if:
- you need to write email/communicate with all/some of the people who submitted the form (eg volunteer sign up/scheduling)
- you need to discuss the data submitted via form with your other team members (eg CFPs)
- you / your team members need to update various records in the spreadsheet at various times (eg club membership info)
@mariatta My current home project is building a spreadsheet parser, with the goal of migrating spreadsheet data to a database, then automatically building a web-based front end for maintaining the data.
The OpenXML Office data specification is hard enough to deal with, but most of the spreadsheets I've come across are also horribly constructed, which makes the task even harder.
So far, I can parse data .xlsx format, print out simple data errors (divide by zero, etc) and bulk export to csv.