annotation-tool

Describe the bug
I am trying to label Hebrew text (RTL language). When labels are attached to the text, the words of the text are mixed and not shown in their original order.

To Reproduce
Steps to reproduce the behavior:

1. Create a project with attached dataset.json dataset.txt
2. Choose NER template
3. Start

My actions before raising this issue

• Read/searched the docs
• Searched past issues

Expected Behaviour

I want to access the traefik dashboard. I have cvat setup on a server with https. I modified the docker-compose.https.yml according to the comment for using the traefik dashboard. So included the lin

How to reproduce the behaviour

The error occurs in the Step 5/9 of the docker build process

fetch http://dl-cdn.alpinelinux.org/alpine/v3.11/main/x86_64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/v3.11/community/x86_64/APKINDEX.tar.gz
WARNING: Ignoring http://dl-cdn.alpinelinux.org/alpine/v3.11/main/x86_64/APKINDEX.tar.gz: BAD signature
WARNING: Ignoring http

Add a way to change the sample id output in the annotation process to a specific number (see picture).

Reason: I want to annotate large text and the app don't like it when the documents to annotate are too large, so I spitted in a sentence the document but I would like to be able to

The default RubrixLogHTTPMiddleware record mapper for token classification expect a structured including a text field for inputs. This could make prediction model inputs a bit cumbersome. Default mapper could accepts also flat strings as inputs:

def token_classification_mapper(inputs, outputs):
    i

What?

Currently, API manually throws its own messages and errors. We should move them to werkzeug exceptions.

Could be useful for helping people debug issues with annotations not created by Annotorious. This would trigger when calling the .setAnnotations, .loadAnnotations and .addAnnotation API method.

If it doesn't add too much download size, an existing (JSON schema?) validation library could be used. Otherwise, it might be enough to write a small custom validator that checks the key props of t

allowTouch should be true by default, however, the fact that it disables scrolling can feel very janky.

It should have an intuitive toggling mechanism - i.e. only allow annotation creation when the image is clicked at least once (focusing on image)