epam / epam/badgerdoc

[Chat] Support conflict block

Open
#1,075 0 comments 0 reactions 0 assignees Claimed by @andreisakirkinepam View on GitHub
front-end priority
Dominant language
Python
Stars
44
Forks
52
PR merge metrics
No merged PRs in 30d

Description

**Pre-requisite:** This task requires a discussion with back-end to agree on representation of "conflict" blocks in hOCR mode.

Conflict block is a special type of Extraction Block where results of extraction are not certain and human intervention is nesessary.

There is an implementation of working conflict block in the spike branch, however, it relies on the old approach with custom tags. Please first agree on how conflict data will be represented within hOCR and then feel free to adapt the solution from the spike.

Conflict block must have several tabs:

- 'council' - an oversight agent making deciaion which extraction value is more likely to be correct
- a separate tab per each "model" with it's own results
- each tab contains
- results of extraction of this block by the specific model. meaning that all tabs show the same data different only in the conflicting area
- comment/reasosning from the "model" on the content of the conflict
- conflicting area might be any tag and potentially even a word
- conflicting area must be visually highlighted

User must be able to switch between tabs.

User must be able to edit or accept data in the "council" tab as a correct one. Content of other tabs must be read-only.

Version 1 implementation, should just handle "conflict" class included into an element:
```xml










Dry mouth






Dry eyes






Headache






Change in your sense of taste




```

In that case the last element should be rendered with a highlight based on the class.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.