404 warning if user switches repository

404 warning is shown, if the user switches to another repository. But repository is loading correctly.

Use previous code system when adding a new code

prefill code system field with the last one in the list
add shortcut to add rows more easily (e.g., arrow down to jump to next code field, if non exists: add a new row)

Fix deep link to entity

Let users select from a list of default constants

Constants are used in composite and derived expressions. Currently, users can only enter numbers, but there may also be constants like Pi, true and false. They should be retrieved from the backend and provided via a select field.

Introducing default aggregation function

Some functions do not support multiple values for a phenotype argument. They will use a default aggregation function, to generate a single value. This aggregation function should be selectable by users, when building queries. Each in-/exclusion criterion has it's own default aggregation function.

add field where users can select the default aggregation function

Make restrictions distinguishable

Improve input fields for restrictions/ranges

restrict selectable comparators for minimum (>, >=) and maximum (<, <=)
add stacked labels to minimum and maximum field
remove "values" text between minimum and maximum fields

Truncate repository name above entity tree

Entity tab should automatically scroll to bottom

e.g., if the user adds some code fields, the tab should scroll down. Otherwise it is really painful to add a long list of codes, because the user always has to scroll manually after adding one entry.

Close unchanged tabs on tab switch

Currently, tabs remain open and the tab bar gets messy very fast. The user is forced to occasionally close some unused tabs.

if user switches to another tab: close previous tab if it was not changed
add function to "pin" tabs, so that they remain open, even if they are unchanged

Use expression editor for mathematical formulas

Manipulation of term codes

Allow users to search for taxonomy terms by selecting a taxonomy (e.g. LOINC) and entering codes or term names. The term should then be saved as annotation in the neo4j database.

It is currently unclear where terms can be searched in. Maybe we will store them in the backend or we will query a dedicated terminology service.

Remove item type

Item type is no longer required.

Restrictions are not properly displayed

The input component switches to values state.

URL not updated when new tab is added

Related to property preserve

Cannot set date time restriction for query eligibility criteria

Add switch component to specify mapping to scores

Unrestricted boolean phenotypes and restricted phenotypes shall be mapped to score values. For this, a simple component is required, where each row represents one mapping. The user should be allowed to select one phenotype per row and specify a score value. One additional row is required for default values.

Mockup:

col 1	col 2	col 3
phenotype select field	input field	add btn
default value:	input field
phenotype 1:	1	remove btn
phenotype 2:	2	remove btn

Dangling context menu shows up when repository is opened.

Managing entity versions

Entities have one or more versions.
One of this versions is the current version.
All versions of an entity can be listed, including version number, creation date and current version state.
- Versions are deletable - except for the current version.
- An entity can be reverted to a version, that is not the current version. Revert is possible independently from the chronological order.
- The entity form can be populated with data from another version. After population the user is able to modify the data and save if as a new version.
Entities are deletable too. Deleting an entity will delete all of it's versions.
To be discussed: Where should the function to delete an entity be placed?

Add parameter to disable authentication

In it's current development state an authentication service is mandatory to run the TOP framework.

There should be an option, parameter or environment variable to control whether the user must be authenticated to use the frontend.

Min and max of ranged restrictions are flipped after saving

Add some description about item types

add description to each item type
add overall description about what an item type is
add option to filter entity tree by item type

Properly handle errors in Keycloak initialisation

Remove version after deletion

When deleting an entity version, the modal should not close and the version should be removed from the table.

Autofocus entity title field

When the user creates a new entity (i.e., right click on entity tree > select one of the create options), the title field in the new entity tab should be focused automatically.

Fix duplicated query IDs

If queries are executed multiple times, they might have the same ID.

Remove scores from single and derived phenotypes

Query projection entries are not displayed correctly

Unit should be mandatory

Currently the form can be submitted without providing a unit.

Truncate titles in entity tree

Query builder

Kannst Du Dir im Frontend ein Formular zur Spezifikation von Abfragen vorstellen mit folgenden Feldern: Age, Gender, Inclusion, Exclusion und Projection (vielleicht noch ein Paar andere Sachen, wie z.B. das Datum), in die man dann z.B. per d&d die gewünschten Klassen ziehen kann?

Fix deep link access when running behind nginx

If the frontend is deployed with docker, deep links (e.g.: http://127.0.0.1/repository) are not working.

A special nginx configuration seems to be missing.

Enable user to change query set operators

Eligibility criteria should also be combineable with OR.

Updating IDs

Users cannot update the ID of content (e.g., organisations). The new ID is used as URL parameter, thus the old entity is not referenced correctly when sending a PATCH request.

Expression: operands are lost when enclosed

Duplicate entities option

Extend the context menu of the entity tree with an option to duplicate the selected entity. When this option is used, a new entity should be created with the same data as the duplicated entity.

an ID must be generated for the new entity
maybe this option should be restricted to a selected set of entity types?

At least one title should always be present

Add check for titles array size to validation

Improvements to entity form

focus title field when new entity is created
preselect unused language when adding a new title field
rearrange form components
make some fields mandatory, check presents of values and add indicator e.g.: "*"

Add indicator to required fields

The user should be able to see what fields are mandatory.

Let the user move entities in the tree

Add keyboard shortcuts

e.g.:

submit current entity form (ctrl+s)
close current entity tab (maybe esc)
switch tabs (ctrl+arrow)

Restriction values cannot be added for data type 'string'

Switching repositories while loading results in inconsistently displayed data

Data are loaded in async functions and populated when promises are resolved. If, for example, a repository is very large and takes some time to load, users may switch to another repository while loading is still performed in background. The result would be that entities from the previous repository are displayed in the entity tree.

Before resolving a promise, it must first be checked if the repository is still the same as it was when the promise was created.