-
Notifications
You must be signed in to change notification settings - Fork 31
Add disclaimer for free text aggregates #344
Comments
Likewise for Schedule A aggregates by employer and occupation. |
@emileighoutlaw can you weigh in on how this language looks?
|
Does this seem more clear to you? "Note: These totals are calculated from filing data that the committee reported with free text input. As such, totals don't take into account misspellings or variations." |
I'm not crazy about calling a committee or treasurer out on their spelling. How about something like this: "Note: The totals by purpose are summed based on free text input as reported by this committee. Variations in spelling or abbreviation will produce multiple totals for the same purpose of disbursement." The note could go on to suggest to the user to scan the entire list to guarantee they are getting all the information they want. |
Oh that's a good catch. I'd like to keep it more general so that the same language can be used for aggregating purpose / employer / occupation, etc. What about:
|
@noahmanger I like that 👍 |
Me too! |
This is a little nit-picky but I'll suggest changing "For the most accurate information" to "For the most complete information" The aggregations aren't necessarily inaccurate but they may be incomplete because of the nature of the free text data entry. |
+1 |
For the aggregates on the Disbursements tab we need to add language that explains they are the result of aggregating free text fields, so stuff may not be included.
The text was updated successfully, but these errors were encountered: