rename class slot quality_control_report and/or QualityControlReport so they're distinguishable in spoken conversation

[turbomam]

@aclum you did follow a good pattern here is CamelCasing the class and lower_snake_casing the slot. That means that computers will not get confused between the two schema elements. I think they're pretty clear in print documents intended for humans, too.

However, they could easily be confused in spoken conversation. Could we please rename at lest one of them?

Naming the slot has_quality_control_report would follow the verb-like slot naming pattern, although that would make it one of our longer slot names.

[turbomam]

@aclum I agree that this isn't a really high priority, but you have argued that some other name changes I requested were proposed too late, because the elements were already in production.

I guess I need to be more meticulous about element names as soon as PRs are created.

Please let me know if you have any other suggestions.

[aclum]

@turbomam both the class and slot are already being used (on class Extraction for example) so at this point changing the class name would be more straightforward, that could be done as part of the PR to expand quality control report #1428

[aclum]

Linked PR will make this ticket obsolete b/c the class and slot won't exist anymore.