lfoppiano / supercon2

Staging-area for automatically collected experimental data for the SuperCon database with a curation interface with enhanced-document viewer and curation-ready interface
https://supercon2.readthedocs.io
4 stars 0 forks source link

Error type in case of multiple errors #126

Open lfoppiano opened 2 years ago

lfoppiano commented 2 years ago

(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 commented 2 years ago

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.