Implications of "answer": "accept" being automatically added to all imported examples with db-in

[ryanwesslen]

hi @gruff!

@Gruff

Edit: I've now determined that the issues I initially reported are not down to the data, so I've removed those references. I'll ask about those particular issues on the spaCy discussion board.

Thanks for your questions! Yes, please reach out to the spaCy discussion board for training specific questions.

I still think your general questions about the "answer" keys and how to handle them are important (likely other users have had similar questions about what's their function).

@Gruff

By using db-in without "answer": "accept", have I now added "answer": "accept" to unannotated entries somehow?

The "answer" corresponds to the annotation choice users can decide for each example: "accept", "reject", "ignore".

This has a slightly different interpretation per task; like for example, binary text classification the "accept" and "reject" can mean positive and negative examples of a class. But for many of the recipes, "answer": "accept" means you want to use this data in training (or evaluation) data.

What do the accept, reject and ignore buttons do?

Hi @strickvl , You're right that when drawing bounding-boxes, ACCEPT and IGNORE should suffice. Say in an image.manual task, we want to draw bounding-boxes for all "cats": Accept: "these are all the cats in this image, I have drawn bounding boxes for each of them, please save them in the database" IGNORE: "this image is corrupted and not in good quality. I want to remove this from both my training and test set." It can also just mean: "I don't know the answer and I just want to move on." I…