Activity
From 19.11.2018 to 18.12.2018
18.12.2018
- 17:27 Feature #671: Full-text search field
- Yes, I found out about this yesterday. However, I'm not fixing it as it is still unclear to me whether the popup with...
- 14:37 Feature #671 (Feedback): Full-text search field
- When I type a string, delete it and type another one, e.g. "ab" and then delete it and type "can", I get a list mixin...
- 16:44 Feature #812 (Feedback): Create new annotations with RDFa properties
- Selecting a term sometimes (wrongly) overtakes the type of a subsequent term in the text. E.g. s-247-1995.html, selec...
- 15:56 Feature #812 (Resolved): Create new annotations with RDFa properties
- 15:55 Feature #812 (Closed): Create new annotations with RDFa properties
- As a user, I want to be able to created new annotations in a document. The functionality should be something like: I ...
- 16:11 Feature #728 (Rejected): Allow importing vocabularies
- Partially covered by #815
- 16:09 Task #815 (Rejected): Each vocabulary can import other vocabularies
- Each vocabulary should support importing of other vocabularies.
Acceptance criteria:
- UI: Vocabulary detail wil... - 16:07 Bug #814 (Closed): Selecting part of already annotated phrase behaves strange
- If there is an already created anotation (e.g. "zastavene uzemi"), it is possible to select part of this annotation (...
- 16:05 Task #813 (Closed): Terms should link its super terms, not subterms.
- Term detail and Term metadata should support editing/viewing super-terms (skos:broader) instead of sub-terms (skos:na...
- 15:57 Feature #680 (In Progress): Create new annotations in document
- 14:54 Bug #745 (Closed): text analysis service annotates same term multiple times
- 14:47 Bug #771 (Closed): Subterms not clickable
- 14:00 Bug #771 (Resolved): Subterms not clickable
- 14:00 Bug #771 (New): Subterms not clickable
- 14:00 Bug #771: Subterms not clickable
- x
- 14:47 Task #729 (Closed): Do not generate new terms for keywords
- 14:45 Feature #643 (Feedback): Vocabulary editing
- 14:42 Feature #643: Vocabulary editing
- Updating a vocabulary ends up with an exception on save (500 from the server).
- 14:43 Task #768: Attaching arbitrary property values to vocabularies
- Looks like a manifestation of the same problem as #643
- 14:10 Task #768 (Feedback): Attaching arbitrary property values to vocabularies
- Not working:
1) Choose "ML-test" vocabulary on termit-dev
2) Edit the vocabulary and add a new property (tested on ... - 14:39 Feature #649 (Closed): Full text search
- Tested only on GraphDB.
- 14:29 Feature #698 (Closed): Display a list of term assignments on the term detail screen.
- 2) moved to #811
- 14:29 Task #811 (Closed): List of resources for a term augmented by document annotations
- As a user, I want to be able to see not only Resources to which a Term has been assigned, but also Resources in which...
- 14:25 Task #726 (Closed): Synchronize term detail view with routing
- 14:23 Feature #739 (Feedback): Allow attaching arbitrary properties and values to vocabularies and terms
- Feedback on children
- 14:18 Task #766 (Closed): Model update
- 14:15 Task #767 (Feedback): Attaching arbitrary property values to terms
- Tested from the UI (on termit-dev):
- saving the changed term proceeds successfully
- afterwards, the new property ... - 14:01 Bug #770 (Closed): Tree of sublasses contains some values twice and some are not present at all
- 13:57 Bug #772 (Feedback): Text analysis service - Annotations are split by stopwords
- Stop-words should be filtered out to make the output consistent and not containing unnecessary tags.
- 13:55 Task #773 (Closed): Fake API for NKOD integration
- 13:54 Bug #774 (Closed): Creation of new term fails if type is not selected
- 13:53 Task #777 (Closed): Resource Detail Screen
- 13:51 Feature #779 (Closed): Support export into CSV/Excel
- 13:49 Bug #787 (Closed): Full text search does not work
- 13:28 Bug #732 (In Progress): Terms with Czech accents do not resolve properly
- 13:27 Bug #732 (Feedback): Terms with Czech accents do not resolve properly
- 13:25 Feature #798 (In Progress): Edit term occurrence properties outside of RDFa
- 13:24 Feature #798: Edit term occurrence properties outside of RDFa
- Parts that are done:
- Approved and not approved annotation are visualized differently.
- Approving suggested annot... - 12:05 Task #810: Dashboard layout
- The goal is to implement a new layout as shown in the picture.
- 11:12 Task #810 (Closed): Dashboard layout
- 11:07 Task #809 (Closed): Refactor annotation metadata retrieval within annotator
- Currently it is done using queue of promises which should be better integrated into redux lifecycle.
- 10:34 Feature #808 (Closed): It should be possible to create term from annotator UI
- 10:24 Bug #807 (Closed): Document file list does not refresh correctly when different vocabulary is selected
- 09:48 Task #806 (Closed): Replace icon buttons with labelled ones
- From the UX perspective, icon buttons without any text may be difficult to understand. Besides some exceptions (e.g.,...
- 09:08 Bug #805 (Closed): Tree select goes into infinite loop when user scrolls down in result list
- The tree select tends to go into an infinite loop when the user scrolls down in the result list.
Steps to reproduc... - 07:59 Task #804 (Closed): Unify annotator style with the rest of the UI
- As a user, I want the annotator to look the same as the rest of the application. This holds mainly for the popups occ...
17.12.2018
- 23:45 Feature #803 (New): Backend should store rejected term occurrences
- Backend should stores rejected term occurrences that can be used for text analysis service.
Acceptance criteria:
... - 23:44 Feature #802 (New): Edit provenance data of an annotation
- Within termit annotator UI it should be possible to track provenance data:
- Author
- Date of CRUD operation/appro... - 23:42 Feature #801 (New): Backend API to track provenance data of term occurrences
- Backend should contain API to store provenance data related to term occurrence management.
Acceptance criteria:
-... - 23:40 Feature #800 (Rejected): Annotator UI should provide selector for term occurrences
- Annotator UI should provide selector on creation of term occurrence.
Acceptance criteria:
- Create annotation gen... - 23:39 Feature #799 (New): Backend API for term occurrence management
- - Backend should contain API to manage term occurrences and their properties that are not serialized in RDFa.
Acce... - 23:38 Feature #798 (Feedback): Edit term occurrence properties outside of RDFa
- As a user, I want to be able to edit existing annotation poperties that are not included in RDFa. I want to be able t...
- 23:34 Feature #797 (Closed): Edit RDFa properties of 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:07 Bug #787 (Resolved): Full text search does not work
- This has been fixed by automatically adding a wildcard into the search string and configuring the application profile...
- 18:05 Feature #779 (Resolved): Support export into CSV/Excel
- 1) Fixed.
2) Resolved. - 14:12 Feature #779 (Feedback): Support export into CSV/Excel
- 1) Terms containing commas in the URL break the export (e.g. http://onto.fel.cvut.cz/ontologies/slovnik/oha-togaf/poj...
- 17:15 Task #796 (Closed): Track last editor and last edited datetime of terms, vocabularies and resources
- As a developer, I want to track last change provenance data (author of the last change, datetime of the change) of re...
- 14:39 Task #762 (Closed): Create a language for the eGovernment vocabulary at the Ministry of Interior
- Difficult to verify without any description/explanation or acceptance criteria. But there are some types for the l-SG...
- 14:37 Bug #732 (In Progress): Terms with Czech accents do not resolve properly
- Reopening and moving to 1.0.0 as this desires a proper fix.
- 14:35 Task #737 (Closed): Resource Tagging
- 14:33 Task #765 (Closed): Prepare use-case for MVCR presentation
- 14:33 Bug #783 (Closed): text analysis service generates same about for different spans
- 14:30 Bug #785 (Closed): text analysis assigns strange entities to term occurrences
- 14:25 Task #778 (Closed): Backend for a resource CRUD
- 14:25 Task #782 (Closed): CUD for resources
- 12:13 Task #795 (Closed): Chart of term frequency in vocabularies
- 12:11 Task #794 (Closed): ChangeLog
- 12:10 Task #793 (Closed): Action Panel
- As a user, I want to have a panel of quick, most often used, actions on top of the dashboard.
The panel should con... - 12:10 Feature #792 (Closed): Dashboard refactoring
- 10:59 Task #791 (Closed): Visualize the information about text analysis status
- When the text analysis is run, the UI should show that the document content is not up-to-date.
- 10:30 Task #790 (Closed): CU for resources - UI
- As a user, I want to be able to create (register) new resources, edit existing ones and, if need be, also remove them...
- 10:27 Task #789 (Closed): Vocabulary Export to RDF
- As a user, I want to be able to export a vocabulary's glossary into RDF. The export should omit application dependent...
- 10:21 Task #788 (Closed): Refactor Documents to be considered as special Resources
- Specification:
- Document extends Resource, so other parts of the application should reflect it and avoid code dupli...
14.12.2018
- 14:18 Feature #649: Full text search
- Lucene supports Wildcard Searches, see [1]
"*SearchString*" pattern could be used for partial matching.
In [1] ... - 09:17 Feature #640 (Closed): Vocabulary management screen
- 09:05 Task #725 (Resolved): Revisit the structure of term hierarchies in glossary
- I believe this has been resolved. An inferred property now specifies the vocabulary to which a term belongs, so getti...
- 08:56 Task #782 (Resolved): CUD for resources
13.12.2018
- 14:59 Feature #649: Full text search
- Updates on Lucene for RDF4J:
Adding the Czech analyzer to the configuration file as follows:
"lucene:analyzer "...
09.12.2018
- 00:19 Bug #787 (Closed): Full text search does not work
- Two problems:
1) When I start writing 'kandi' I do not get anything ("Nenalezeny zadne vysledky"), although the vo...
07.12.2018
05.12.2018
- 15:27 Bug #786 (Resolved): text analysis service cannot be used if redirected
- 01:44 Bug #783 (Resolved): text analysis service generates same about for different spans
04.12.2018
- 19:44 Bug #786 (Closed): text analysis service cannot be used if redirected
In such case invalid document is created (I believe without any warning).
Content of such document if used for...- 19:39 Bug #785 (Closed): text analysis assigns strange entities to term occurrences
- Term occurrences should be assigned only to terms. However, based on TermIt backend server logs it seems that occurre...
- 16:59 Task #784 (New): Reorganize Term metadata
- As a vocabulary editor,
I want to simplify deciding on parent terms and types
In order to create a vocabulary easi... - 16:53 Task #765 (In Progress): Prepare use-case for MVCR presentation
- 15:40 Task #737 (Resolved): Resource Tagging
- Tags have the form of vocabulary terms here.
Implemented:
- resource list
- resource term editing
- integrated... - 15:38 Bug #732 (Resolved): Terms with Czech accents do not resolve properly
- Only quick-fixed, the problem seems to be somewhere on parameter passing through react routing (probably in thunk)
- 13:04 Feature #779 (Resolved): Support export into CSV/Excel
- 12:39 Bug #783 (Closed): text analysis service generates same about for different spans
- Based on discussion with Lama, it seems that it is caused by line of code:...
- 09:59 Feature #680: Create new annotations in document
- I suggest to split it into:
As a user, I want to be able to created new annotations in a document. The functionali... - 09:45 Feature #681: Edit annotations in document
- I suggest to split task to:
[1] Feature: Edit RDFa properties of annotations in document
As a user, I want to b...
03.12.2018
- 11:36 Task #737 (In Progress): Resource Tagging
- 11:29 Task #762 (Resolved): Create a language for the eGovernment vocabulary at the Ministry of Interior
- 11:19 Task #764 (In Progress): Unify Termit UI style
- 11:13 Bug #770 (Resolved): Tree of sublasses contains some values twice and some are not present at all
- 11:10 Task #777 (Resolved): Resource Detail Screen
- 11:09 Task #778 (Resolved): Backend for a resource CRUD
- 11:08 Task #778: Backend for a resource CRUD
- The retrieval API is done.
The CUD to be moved to another ticket. - 11:09 Task #782 (Closed): CUD for resources
- CUD for each resource (IRI,label,description) should be doable by a web service.
Acceptance criteria:
- the web s...
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...
Also available in: Atom