Activity
From 03.11.2018 to 02.12.2018
02.12.2018
- 20:52 Feature #649 (Resolved): Full text search
- 20:51 Bug #745 (Resolved): text analysis service annotates same term multiple times
- 15:13 Feature #779 (In Progress): Support export into CSV/Excel
01.12.2018
- 14:34 Bug #732 (Feedback): Terms with Czech accents do not resolve properly
- I am reopening the issue, because I encountered another problem. When the namespace query parameter contains encoded ...
30.11.2018
- 18:38 Feature #649: Full text search
- Attached, you can find,
- The configuration file to setup Lucene-index for RDF4J. (no property found to set the Luce...
29.11.2018
- 18:41 Feature #649: Full text search
- - A Lucene connector (index) is implemented in GraphDB under the name (czech_index). see [1].
- In the attachemen...
27.11.2018
- 10:59 Feature #698 (Resolved): Display a list of term assignments on the term detail screen.
- 10:55 Task #781 (Closed): Fix the semantics of controller-service contract
- Each controller should :
1) have a single main service to which it passes its calls
2) the only data transformation...
26.11.2018
- 13:25 Feature #698 (In Progress): Display a list of term assignments on the term detail screen.
- 13:24 Feature #739 (Resolved): Allow attaching arbitrary properties and values to vocabularies and terms
- 13:24 Task #768 (Resolved): Attaching arbitrary property values to vocabularies
25.11.2018
- 23:51 Bug #772 (Resolved): Text analysis service - Annotations are split by stopwords
- Resolved by not excluding stop words from the annotation process, unlike the previous implementation.
Stopwords wi... - 19:00 Task #768 (In Progress): Attaching arbitrary property values to vocabularies
- 16:37 Feature #709 (Closed): Create a button to run the text analysis service
- 16:37 Feature #694 (Closed): Support for unified asset visualization in UI
- 11:30 Feature #739 (In Progress): Allow attaching arbitrary properties and values to vocabularies and terms
- 11:30 Task #767 (Resolved): Attaching arbitrary property values to terms
22.11.2018
- 16:01 Task #780 (Closed): Redesign full text search results UI
- As a user, I want full text search results to contain the label of the matching asset, its type, visualization of the...
16.11.2018
- 16:43 Feature #779 (Closed): Support export into CSV/Excel
- As a user, I want to be able to export vocabularies into an Excel-compatible file.
The relevant columns should be:... - 12:54 Task #777 (In Progress): Resource Detail Screen
14.11.2018
- 15:23 Feature #649 (In Progress): Full text search
- 14:54 Feature #671 (Resolved): Full-text search field
- 14:12 Bug #770 (Feedback): Tree of sublasses contains some values twice and some are not present at all
- Fixed several issues in the tree-view component (mostly related to the fact that terms may have multiple parents). Pl...
- 14:11 Bug #771 (Resolved): Subterms not clickable
- Fixed.
- 14:11 Task #726 (Resolved): Synchronize term detail view with routing
- Replaced the tabbed term detail view with a dedicated term component, which allows a more straightforward integration...
13.11.2018
- 23:21 Task #736 (Closed): Visualization of types statistics
- 23:21 Feature #705 (Closed): Support for a simple UFO-based Language
- 23:20 Task #731 (Closed): Dev deployment
- 18:34 Bug #732 (Resolved): Terms with Czech accents do not resolve properly
- 18:32 Bug #732 (In Progress): Terms with Czech accents do not resolve properly
- 18:29 Task #726 (In Progress): Synchronize term detail view with routing
12.11.2018
- 17:33 Task #778 (Closed): Backend for a resource CRUD
- CRUD for each resource (IRI,label,description) should be doable by a web service.
Acceptance criteria:
- the web ... - 17:29 Task #777 (Closed): Resource Detail Screen
- Each resource is:
- IRI
- label
- description
- set of terms assigned to it (its semantic tags)
This task is t...
09.11.2018
- 18:10 Feature #776 (Rejected): Support multiple terms open in the tabbed vocabulary detail view
- As a user, I want to be able to have multiple tabs with term details open.
Acceptance criteria:
* Selecting a ter... - 17:34 Task #729 (Resolved): Do not generate new terms for keywords
- 17:09 Bug #774 (Resolved): Creation of new term fails if type is not selected
- 15:15 Task #773 (Resolved): Fake API for NKOD integration
08.11.2018
- 14:03 Bug #774 (Closed): Creation of new term fails if type is not selected
- When I try to create a new term and do not select a type, creation fails with an exception:...
- 13:40 Task #773 (In Progress): Fake API for NKOD integration
- 08:38 Feature #671 (In Progress): Full-text search field
06.11.2018
- 14:52 Task #767 (In Progress): Attaching arbitrary property values to terms
- 09:52 Task #773 (Closed): Fake API for NKOD integration
- Publicly available REST methods:
- getResourceTerms
input: resource IRI
output: list of terms (IRIs, labels, de...
05.11.2018
- 19:12 Task #766 (Resolved): Model update
- 12:52 Bug #772 (Closed): Text analysis service - Annotations are split by stopwords
- For example, for term occurrence: "plocha rozdílného využití pro stanovení výškové regulace" in the document, text an...
- 09:16 Bug #771 (Closed): Subterms not clickable
- In the detail o fa term, subterms are listed in the right side of a window. It looks like clickable, but once they're...
- 09:14 Bug #770 (Closed): Tree of sublasses contains some values twice and some are not present at all
- In the tree of subclasses in the left side of the vocabulary window renders some terms twice (charakter-uzemi as seen...
Also available in: Atom