You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Presently, if a user were to have a typo in a shallow field, like awards or contracts, a single additional field would be reported. Similarly, if a user were to disclose a lot of additional information in new fields that were nested under a new field, only the nesting field would be reported.
This makes it harder to notice cases where a user is disclosing data under additional fields that ought to be disclosed under existing fields.
Instead, it would be preferred to include the child-fields of additional fields in the report.
The text was updated successfully, but these errors were encountered:
@jpmckinney this was an intentional decision. Especially considering showing all fields was easier to implement.
The reason why it was done this way was that any spelling mistake on the "shallow field" or on large undeclared extensions, would cause so many additional fields it would make the report unwieldy and would be hard to spot any of the other additional terms.
The compromise would be for any non leaf additional field to report how many fields that are contained within it and give the option to expand to see them.
The compromise would be for any non leaf additional field to report how many fields that are contained within it and give the option to expand to see them.
At the Feb retreat, we discussed making this data available via the cmdline tool / Kingfisher, and potentially adding it to the web version of the DRT as a popup/hidden box.
Presently, if a user were to have a typo in a shallow field, like
awards
orcontracts
, a single additional field would be reported. Similarly, if a user were to disclose a lot of additional information in new fields that were nested under a new field, only the nesting field would be reported.This makes it harder to notice cases where a user is disclosing data under additional fields that ought to be disclosed under existing fields.
Instead, it would be preferred to include the child-fields of additional fields in the report.
The text was updated successfully, but these errors were encountered: