Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error type in case of multiple errors #126

Open
lfoppiano opened this issue Nov 1, 2022 · 1 comment
Open

Error type in case of multiple errors #126

lfoppiano opened this issue Nov 1, 2022 · 1 comment
Labels
curation Discussions related to the curation

Comments

@lfoppiano
Copy link
Owner

(Adding on github to make it available to everybody)

CF: Email from @ChikakoSakai

If a Tc classification and compositon resolution error is happening at the same time, which one should I classify?
They happen in parallel -> Instead of narrowing down the error type to one, is it better to determine that this extraction error is caused by both Tc classification and compositon resolution?

image

CF: discussion with @kensei-te

In case that the entity has multiple errors, we need to specify only one corresponding error, based on the priority. But, it is less informative, since if you succeed in revising your system based on this curated dataset, you would still need to face other remaining errors again.
My question is, is it difficult to have multiple errors for one entity?

@lfoppiano lfoppiano added the documentation Improvements or additions to documentation label Nov 1, 2022
@lfoppiano
Copy link
Owner Author

lfoppiano commented Nov 1, 2022

First of all, multiple error code will slow down people doing curation - although I am not too strict on keeping a single error code, I wish to keep it simple for the moment.

In general, the schema of the error code which are placed in the flow, indicate the priority... I would choose one error code and the one that appears earlier.

Reference here and here (To be merged)

For the question from @ChikakoSakai, Tc classication takes priority toward composition resolution.

@lfoppiano lfoppiano added curation Discussions related to the curation and removed documentation Improvements or additions to documentation labels Nov 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
curation Discussions related to the curation
Projects
None yet
Development

No branches or pull requests

1 participant