Activity
From 30.08.2018 to 28.09.2018
28.09.2018
- 14:26 Task #666 (Closed): Top-level term creation
- 00:37 Task #700 (Closed): Reactify faceted search results
27.09.2018
- 12:17 Task #699 (Closed): Unify create new vocabulary and create new term buttons
- The button for new vocabulary creation has a + icon. In contrast, the button for new term creation has a 'Create new ...
- 10:41 Feature #698 (Closed): Display a list of term assignments on the term detail screen.
- Whenever a term is selected and its detail screen displayed, a list of resources is shown to which the term is assign...
- 01:30 Task #691 (Closed): Create a test deployment of Termit
- 01:23 Task #683 (Closed): Make Urban Planning Ontology Termit compatible
- 01:21 Feature #682 (Closed): Faceted search for assets
26.09.2018
- 20:08 Task #697 (Closed): Do not generate duplicate term occurrence on repeated document text analysis
- As a user, I want to be able to rerun text analysis on a specified file. Currently, rerunning text analysis would res...
- 17:59 Feature #641 (Closed): Vocabulary detail screen
- 17:37 Task #696 (Rejected): Provide rich UI for properties and types visualized in UI
- On many screens, properties of ontology assets are presented (vocabulary metadata, term metadata, etc.) in terms of a...
- 17:31 Task #695 (Closed): Implement unified URL scheme for assets
- Part of the application URL scheme points to asset details, e.g. Vocabulary detail, Term detail - implement each of t...
- 17:23 Feature #694 (Closed): Support for unified asset visualization in UI
- Each asset (currently namely document, term, user) managed by TermIt should be visualized in a uniform way.
Accept... - 17:14 Task #665 (Resolved): Design a testing scenario for IPR
- 17:14 Task #691 (Resolved): Create a test deployment of Termit
- > - The deployment will contain data referencing pubby at http://onto.fel.cvut.cz/ontologies
The current deployment ... - 08:46 Task #691: Create a test deployment of Termit
- > - the deployment will be running at http://onto.fel.cvut.cz/termit
Done, running at
- http://kbss.felk.cvut.cz/t...
25.09.2018
- 22:33 Task #693 (Rejected): Create a popis-dat publication pipeline
- Acceptance criteria:
- create a pipeline for publishing Popis Dat ontology to the onto.fel.cvut.cz server. The ontol... - 12:53 Feature #681: Edit annotations in document
- I believe there is nothing like "modify description", because annotation does not have description.
I believe that "... - 12:50 Task #691 (Closed): Create a test deployment of Termit
- Acceptance criteria:
- the deployment will be running at http://onto.fel.cvut.cz/termit
- the deployment will conta... - 12:10 Task #666 (Resolved): Top-level term creation
- 12:10 Feature #645 (Resolved): Term creation
- 10:38 Bug #688 (Closed): Cannot create a new vocabulary
- 10:30 Feature #682 (Resolved): Faceted search for assets
- Currently, only react wrapper over an angular component is created. Thus, angular component is reinitialized on each ...
23.09.2018
21.09.2018
- 15:25 Feature #654 (In Progress): Automatic annotation of document with existing terms
- 15:22 Feature #681 (In Progress): Edit annotations in document
- 15:22 Feature #679 (In Progress): Render annotations in document
- 14:47 Task #665 (In Progress): Design a testing scenario for IPR
- 14:28 Task #683 (Resolved): Make Urban Planning Ontology Termit compatible
- Implemented as:
- the termit-dev repository now contains all datasets from the VocBench repo for IPR
- the same Tri... - 14:00 Feature #671 (In Progress): Full-text search field
- 09:18 Bug #688 (Resolved): Cannot create a new vocabulary
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