Activity
From 22.08.2018 to 20.09.2018
20.09.2018
- 15:35 Feature #689 (Rejected): Get Configuration from server to client
- Server contains some config to be reused also by client. This task is to create a REST service to get it.
Acceptan... - 15:06 Bug #688 (Closed): Cannot create a new vocabulary
- Using latest termit-ui against latest termit server, I get the following log after trying to create a new vocabulary....
- 15:04 Task #685 (Resolved): Generate RDFa out of text analysis output
- 14:51 Feature #677 (In Progress): Render HTML document
- 14:48 Task #687 (Resolved): Store text analysis output as file content
- 14:34 Task #687 (In Progress): Store text analysis output as file content
- 13:45 Task #687 (Closed): Store text analysis output as file content
- As a developer, I want to store the text analysis output by replacing the previous file contents, so that it can be p...
- 13:42 Task #686 (Resolved): Generate new terms based on text analysis suggestions
19.09.2018
- 17:43 Task #686 (In Progress): Generate new terms based on text analysis suggestions
- 17:17 Task #686 (Closed): Generate new terms based on text analysis suggestions
- As a user, I want new terms to be created based on suggestions by the text analysis service.
Suggested terms are i... - 16:28 Task #678 (Resolved): Generate annotations based on text analysis output
18.09.2018
- 22:42 Task #685: Generate RDFa out of text analysis output
- This task ensures generation of RDFa markup for the text analysis output. This task is a part of the text annotation ...
- 13:33 Task #685 (Closed): Generate RDFa out of text analysis output
- 14:16 Task #678 (In Progress): Generate annotations based on text analysis output
- 09:35 Task #684 (Resolved): Invoke text analysis
17.09.2018
12.09.2018
- 09:08 Feature #641 (Resolved): Vocabulary detail screen
- Fixed by migrating to JB4JSON-LD 0.3.5.
- 08:50 Feature #681: Edit annotations in document
- As a user, I want to be able to edit existing annotations in a document. I want to be able to: select a different ter...
- 08:44 Feature #680: 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 ...
- 08:36 Feature #679: Render annotations in document
- As a user, I want to be able to view annotations generated as a result of the text analysis executed on a document. T...
- 08:31 Task #684 (Closed): Invoke text analysis
- As a developer, I want the application to contain an API which invokes the text analysis service with content of a se...
- 08:23 Task #678: Generate annotations based on text analysis output
- As a developer, I want the application to be able to generate document annotations based on term occurrences discover...
- 08:18 Feature #677: Render HTML document
- As a user, I want to be able to view an HTML document (rendered, i.e., with markup interpreted as usual) attached to ...
11.09.2018
- 00:51 Task #683 (Closed): Make Urban Planning Ontology Termit compatible
- Acceptance criteria:
- transform the UPO into a SKOS glossary and an ontological model. - 00:41 Task #661 (Closed): Extend the datasource description ontology
- 00:33 Feature #682 (Closed): Faceted search for assets
- The faceted search should help to find terms using facets.
Acceptance criteria:
- allow searching assets based on... - 00:28 Task #656 (Closed): Messaging framework in the UI
- 00:17 Feature #667 (Closed): Language switching in the application
- Tested all bullets - all OK.
- 00:15 Task #673 (Closed): Change browserhistory to hashhistory
10.09.2018
- 18:44 Feature #681 (Rejected): Edit annotations in document
- As a user, I want to be able to edit existing annotations in a document. I want to be able to: select a different ter...
- 18:44 Feature #680 (Rejected): 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 ...
- 18:44 Feature #679 (Closed): Render annotations in document
- As a user, I want to be able to view annotations generated as a result of the text analysis executed on a document. T...
- 18:43 Task #678 (Closed): Generate annotations based on text analysis output
- As a developer, I want the application to be able to generate document annotations based on term occurrences discover...
- 18:42 Feature #677 (Closed): Render HTML document
- As a user, I want to be able to view an HTML file (rendered, i.e., with markup interpreted as usual) which is a part ...
06.09.2018
- 18:22 Task #674 (Resolved): Change view of the Vocabulary Detail screen
- %%% - clicking on the vocabulary title deselects a term
Implemented as tabs (not clicking the vocabulary title but t... - 14:34 Task #674 (Closed): Change view of the Vocabulary Detail screen
- Acceptance criteria:
- whenever a term is not selected, the metadata are shown in its full form in the right pane
-... - 17:16 Task #673 (Resolved): Change browserhistory to hashhistory
- 14:33 Task #673 (Closed): Change browserhistory to hashhistory
- 17:15 Feature #667 (Resolved): Language switching in the application
- 11:06 Feature #667 (Feedback): Language switching in the application
- All OK, but
%%% Application remembers the selected language so that when the user opens the application later, it ... - 16:19 Task #656 (Resolved): Messaging framework in the UI
- 14:21 Task #666 (Feedback): Top-level term creation
- 14:21 Task #666: Top-level term creation
- More specific criteria:
- put it out of the modal - align with vocabulary creation
- implement IRI generation based... - 14:16 Feature #636 (Closed): Dashboard UI
- My/Recently Edited/Most Viewed Assets facets will be added in #672.
- 11:37 Feature #636: Dashboard UI
- After a discussion with Martin, we decided not to add the placeholder components at this level.
- 10:57 Feature #636 (Feedback): Dashboard UI
- All OK, but:
%%% My/Recently Edited/Most Viewed Assets facets are replaced with placeholder components, they will b... - 14:15 Feature #672 (Closed): My Assets / Recently Edited Assets /Most Viewed Assets
- Implement My Assets / Recently Edited Assets /Most Viewed Assets widgets to the dashboard and adjust layout according...
- 14:10 Feature #634 (Closed): User registration
- Approval in task #638
- 10:57 Feature #634 (Feedback): User registration
- 10:54 Feature #634: User registration
- All OK, but:
%%% Newly registered users have read-only access to public vocabularies (achieved via a special type ... - 13:02 Feature #642 (Closed): Vocabulary creation
- 12:53 Task #670 (Closed): Mock server REST API for development
- Perfect.
- 11:16 Feature #641 (Feedback): Vocabulary detail screen
- All OK, but
'Created' field is empty (the date of creation). - 11:07 Task #661: Extend the datasource description ontology
- The ontology should be aligned. It is present in the two TTL files in the root of the project.
- 11:06 Task #662 (Closed): Plan meeting with IPR - last two weeks of sept
- 10:26 Task #662 (Resolved): Plan meeting with IPR - last two weeks of sept
- arranged 26.9. 14.00-16.00
- 10:58 Task #668 (Closed): Logout from application
- 10:39 Task #655 (Closed): MainView with navigation panel
- Full-text search field is missing, but BL implementation ( #649 ) is planned for version 1.0.0.
Moving Full-text ... - 10:39 Feature #671 (Closed): Full-text search field
- Implement a full-text search field into the navigation panel.
- the field should provide suggestions, according to t...
04.09.2018
- 13:38 Feature #641 (Resolved): Vocabulary detail screen
- UI layout of vocabulary detail (especially the metadata panel) is up to discussion.
- 10:49 Feature #642 (Resolved): Vocabulary creation
- Postponing authorization (i.e. the acceptance criterion where pending users cannot create new vocabularies).
Also available in: Atom