imisdevelopers / sormas-project Goto Github PK

Clarify list of placeholders in quarantine related document available from SORMAS.

Values for placeholders must be available in the context of quarantine and must have a mapping to (values from) entities in SORMAS.

Problem Description

• Cut down *.sh
• Does the SORMAS container really needs R installed?
• [ ]

Don't use varchar(25) to store YES|NO|UNKNOWN.

Situation Description

REST API is protected by HTTP auth. Provide JWT, also needed for single page application UI.

• Can this be done with keycloak?

Situation Description

• delete old repo in SORMAS
• transfer upstream repo
• include into docker-compose deployment
• setup database
• test Grafana

A service providing:

• persisting a template on PostgreSQL along with meta data (here: the workflow for which the template is relevant)
• reading a template from PostgreSQL
• reading a list of templates available for a workflow
• deleting a template

Templates are docx files. "List of templates" means list of identifiers as used for reading a template from DB. Workflow identifiers have to be agreed upon.

Bug Description

Es wird kein Dokument heruntergeladen.
Netzwerkanalyse ergibt:

Steps to Reproduce

1.Use Safari 14
2.Quarantäneanordnung erstellen: auf erstellen klicken

System Details

• Device: MacOS
• SORMAS version: feature-2696-document-generation-quarantine
• Android version/Browser: Safari 14
• User Role: SurvSup

Feature Description

Investigate why we are using zulu11jdk in the first place and try to move to plain old openjdk OS package. Makes setup again easier.

The UI should provide:

• upload of template files
• showing available template files
• download a template
• deleting of template files

SORMAS-Foundation#3735
SORMAS-Foundation#2866
SORMAS-Foundation#2375
SORMAS-Foundation#3728
SORMAS-Foundation#326

First concept: see Design MVP (in German)

Related SORMAS issue: Letter/ certificate of quarantine automation

Problem Description

Building the project takes long.

Proposed Change

• investigate
• get rid of the 1000s of warnings printed during testing

Goal: Provide a mechanism to file generated documents. Documents can be filed per case and are secured against manipulation (revisionssicher). In a first step, the mechanism applies for generated documents related to quarantine. In the long run however, it should be open to arbitrary documents, cf. SORMAS issue Option to attach document.

Situation Description

Returning travelers is currently a hack. Design and implement returning travelers with recorded persons.

• Cleanup sormas-cargo
• Use development domain.xml not the production version as we currently do
• autodeploy of payara and then drop the applications xml node from domain.xml DONE
• Remove sormas-serverlibs and move pom.xml to sormas-base?
• Remove sormas-cargo and move it to sormas-base?
• Build all artifacts with mvn install DONE
• use mvn postgres plugin instead of docker postgres? maintainability hazard
• write documentation and emphasis that this is the easy way to kickstart SORMAS development
• open issue in SORMAS repo
• squash commits, reference issue in commit and open PR

Bug Description

Currently, all uuid fields in the DB are of type varchar(36) and not of type UUID. Investigate speedups, if any.

Situation Description

The current REST docs are minimal.

Feature Description

• mention editor.swagger.io
• mention REST user permission

Situation Description

The templating engine could be used to print event lists and so on.

Goal: Templates for quarantine related documents can be uploaded and are persisted in PostgreSQL

A service providing:

• extract a list of placeholders used in a given template
• generate a document from a template and a list of key/value pairs
• find a suitable templating engine, which makes it easy for the public health offices to create templates

Feature Description

Use prettier or editorconfig for formatting and remove the section on formatting from the development docs

Goal: a template engine to fill in placeholders a template and generate a document

The UI should provide:

• selection of a template from a workflow-specific list
• identification of placeholders used in the template not available from the SORMAS context (e.g. Zimmer-Nr. Bearbeiter)
• the possibility to provide values for these extra placeholders
• persistence of these extra values in Localstorage client-side
• generating a document from the selected template and key/value pairs for placeholders using the Service from issue #8
• download of the generated document