5 ms·

I agree with this. My group uses google sheets to manage a very complex collaborative process which is highly record oriented and requires relational semantics

I agree with this. My group uses google sheets to manage a very complex collaborative process which is highly record oriented and requires relational semantics and database-like integrity controls, but which also needs spreadsheet-like sorting, grouping, formula work, rapid data entry, pivot tables, and so on. We kind of work around spreadsheet limitations now by having a separate google sheet hold source data in various tabs (one for each relational table), then importing data from that sheet into the working spreadsheets (where we do enrichment and analysis) using various lookup and query functions. It's precisely as fragile as the attention span of the most easily distracted team member.

jessaustin 11y ago
Oh wow, that could be scary. How is data entered or modified?Is the schema changing too much to put this in an actual relational DB? Are you using versioning or backups?
- scrumper 11y ago
  Each instance is a short-term, tactical thing, so the fallout from any particular error is at least localized. Everything is entered manually. Schema is fixed at the core, with small numbers of custom columns needed every now and then. A relational DB would be a better tool for storing the core data, but the tooling itself is wrong: we'd have to build a UI to front it, whereas using google sheets gives a free UI that everyone knows how to use (and supports all the various analysis cases I mentioned above). Version control is just that provided by google sheets (irritatingly granular, with no ability to create a marked checkpoint version - I hate it), plus whatever naming convention discipline any team comes up with. It's not great. I can't really be more specific unfortunately - NDAs etc.
spitfire 11y ago
Have a look at Quantrix. It's a spreadsheet that separates data from formulas and reporting. Database access is built in. It a hidden gem of many finance departments.
- scrumper 11y ago
  Thanks - was not aware of this at all. Will check it out.

jessaustin 11y ago

Oh wow, that could be scary. How is data entered or modified?Is the schema changing too much to put this in an actual relational DB? Are you using versioning or backups?

scrumper 11y ago
Each instance is a short-term, tactical thing, so the fallout from any particular error is at least localized. Everything is entered manually. Schema is fixed at the core, with small numbers of custom columns needed every now and then. A relational DB would be a better tool for storing the core data, but the tooling itself is wrong: we'd have to build a UI to front it, whereas using google sheets gives a free UI that everyone knows how to use (and supports all the various analysis cases I mentioned above). Version control is just that provided by google sheets (irritatingly granular, with no ability to create a marked checkpoint version - I hate it), plus whatever naming convention discipline any team comes up with. It's not great. I can't really be more specific unfortunately - NDAs etc.

spitfire 11y ago

Have a look at Quantrix. It's a spreadsheet that separates data from formulas and reporting. Database access is built in. It a hidden gem of many finance departments.

scrumper 11y ago
Thanks - was not aware of this at all. Will check it out.