Feature #680
closedFeature #653: Document annotation
Create new annotations in document
50%
Description
As a user, I want to be able to created new annotations in a document. The functionality should be something like: I select a piece of text in the rendered document, for this text, I am able to select a vocabulary term offered by the application, add a short text description, and then submit the annotation. Editing existing annotations is not a part of this task!
Acceptance criteria:
- The document rendering component allows to select portions of text.
- When a part of text selected, a component (probably a popup) is displayed, containing selector of terms and a description input field (a textarea).
- The term selector offers terms contained in the vocabulary related to the rendered document.
- Selecting a term is required for submitting the annotation, description is optional.
- Once the data are filled in, the annotation can be submitted.
- At least two selectors are generated for the annotation. (The generation will probably occur on the client side)
- Backend contains API for storing these new annotations.
- Annotations are assigned provenance info about their author and creation date.
- Newly added annotations are visualizes accordingly.
- Tested.
Related issues
Updated by Martin Ledvinka about 6 years ago
- Estimated time set to 20.00 h
- Subject changed from create new annotations in document to Create new annotations in document
As a user, I want to be able to created new annotations in a document. The functionality should be something like: I select a piece of text in the rendered document, for this text, I am able to select a vocabulary term offered by the application, add a short text description, and then submit the annotation. Editing existing annotations is not a part of this task!
Acceptance criteria:
- The document rendering component allows to select portions of text.
- When a part of text selected, a component (probably a popup) is displayed, containing selector of terms and a description input field (a textarea).
- The term selector offers terms contained in the vocabulary related to the rendered document.
- Selecting a term is required for submitting the annotation, description is optional.
- Once the data are filled in, the annotation can be submitted.
- At least two selectors are generated for the annotation. (The generation will probably occur on the client side)
- Backend contains API for storing these new annotations.
- Annotations are assigned provenance info about their author and creation date.
- Newly added annotations are visualizes accordingly.
- Tested.
Updated by Martin Ledvinka about 6 years ago
- Related to Feature #679: Render annotations in document added
Updated by Martin Ledvinka about 6 years ago
- Related to Feature #681: Edit annotations in document added
Updated by Petr Křemen almost 6 years ago
- Target version changed from 0.2.0 to 0.3.0
Updated by Petr Křemen almost 6 years ago
- Target version changed from 0.3.0 to 0.4.0
Updated by Miroslav Blaško almost 6 years ago
I suggest to split it into:
As a user, I want to be able to created new annotations in a document. The functionality should be something like: I select a piece of text in the rendered document, for this text, I am able to select a vocabulary term offered by the application and then submit the annotation. Editing existing annotations is not a part of this task!
Acceptance criteria:
- The document rendering component allows to select portions of text.
- When a part of text selected, a component (probably a popup) is displayed
- The term selector offers terms contained in the vocabulary related to the rendered document.
- Newly added annotations are visualizes accordingly.
- Tested.
Note:
- This task includes only RDFa related properties of annotation (Provenace info about annotation as well as annotation description are part of different task)
- Update of term occurrences within server is part of diffrent task
- Generation of a selector of an annotation is part of different task
Updated by Petr Křemen almost 6 years ago
- Target version changed from 0.4.0 to 1.0.0
Updated by Miroslav Blaško almost 6 years ago
- Status changed from New to In Progress
Updated by Miroslav Blaško almost 4 years ago
- Status changed from In Progress to Feedback
I suggest to reject this task as it is high level task that contains too many subtasks where some of them are out dated.
Updated by Petr Křemen almost 4 years ago
- Status changed from Feedback to Rejected