Open mbrush opened 5 years ago
diatomsRcool
commented
5 years ago We have use cases wherein someone was notified about an error by someone else. The first someone then fixes the error. Would be nice to give credit to the original error-finder.
mbrush
commented
5 years ago This use case could minimally be addressed by capturing the error-finder as a contributor with an 'evaluation' or 'quality assessment' role (or some other role that more specifically gets at their contribution). Does this seem reasonable? It would not require any additions to the model - just well-defined roles in the CRO, and guidance in the data model spec for how to use the existing model and CRO roles to capture these types of contributions.
And if we wanted to capture some formal ticket that was created to report the error, this could be done using the proposed 'mediatingEntity' attributed discussed in #5.
mellybelly
commented
5 years ago how about organizationalContext? wasPerformedFor seems too strong/specific. Question is whether this can be in context of another person. This might imply shared contributions to the same artifact? That seems fine, but maybe there is a different way to handle this with simply a separate contribution triple? I would probably just use organization context here and keep it simple.
mellybelly
commented
5 years ago need to check to see if the following roles are in CRO: error-detection role, data quality assurance role (not exactly the same)
Is the wasPerformedFor attribute in the Contribution object sufficient to capture requirements around 'context' in which a contribution is made?
This property indicates that the contribution was made on behalf of some other agent/organization. But from what I have heard, there may be more nuance we want to capture. @mellybelly please comment.