Skip to content

Rework DSE feature search #362

@paulolaup

Description

@paulolaup

IS:

We should rework how profiles (serving as the basis for selecting what data points should be extracted) can be searched in the Feature Selection section of the feasibility portal. ATM, researchers can (only) navigate a tree with grouping nodes based on the module profiles originate from and what profiles they are based on.

Multiple issues can be identified with this approach:

  1. Grouping by module is only a proxy for the concepts we actually want to group by: use cases, topics, etc. There are much more useful data points within a profile for grouping by these categories, such as the category element many FHIR Resources contain.
  2. Users cannot search profiles via search bar like is possible for criteria. While there is a tree to navigate through, finding the fitting profile (e.g. data model) is still cumbersome. A tag-based search would be much more helpful.
  3. The current implementation uses a lot of additional files to provide mappings and metadata to display all the information in the portal. We should ideally rely only on information derived from or provided by the packages and the profiles they contain. That way we not only reduce the required maintenance but also ensure that the information displayed in the portal stays consistent with the package versions we use.

TODO

Metadata

Metadata

Labels

Priority 3minor problem - low priority fixingdseenhancementNew feature or requestunspecifiedIssue requires additional description

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions