Minor suggestion: I notice that on import of CSV, a boolean attribute only recognizes lowercase true and false. (actually I only tested title case, not sure about uppercase). I suggest that True and False and TRUE and FALSE should also be recognized.
I’d suggest you sent in a feature request, there is some sense in this (i.e. if the entire contents of an input field == lowercases to
false). It is also the case that
1, if imported to an existing Boolean attribute, will coerce to true and false respectively.
In fairness, Tinderbox documents that it uses (only)
false case-sensitively. So if importing data into Tinderbox it makes more sense to fix the data error at source. Or as so often seems the case, the source is some utility with new real export control, fix the data in a text editor before import. This doesn’t argue against the idea above but: garbage in, garbage out.