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

Enhancement/Document-level annotation guideline #487

Open
wants to merge 2 commits into
base: master
from

Conversation

@c-w
Copy link
Member

c-w commented Dec 6, 2019

Doccano currently supports project-level annotation guidelines which is a very useful tool to help labelers in their work. However, in some scenarios it can be helpful to also provide additional context to a labeler on a document-level, e.g. if the vocabularies of some documents vary wildly or if the classification in may depend on domain knowledge beyond the immediate document content.

This pull request implements document-level annotation guidelines: if a document has the metadata key "guideline", the content of this field will be rendered in the guideline display instead of the project-level guideline. If the "guideline" metadata key is not present, the project-level guideline is displayed as previously.

Animation showing display of document-level and project-level guideline

Given that this pull request introduces a second "magic" metadata value after documentSourceUrl introduced in #269, this pull request also adds functionality to exclude the "magic" metadata values from the display of the document metadata to avoid cluttering up the screen.

@c-w c-w force-pushed the CatalystCode:guideline-per-document branch from a2adfa7 to 331e12f Dec 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.