Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add multiple variables to detailed and custom export [2] #5229

Closed
maxiheyner opened this issue Apr 26, 2021 · 5 comments · Fixed by #6341
Closed

Add multiple variables to detailed and custom export [2] #5229

maxiheyner opened this issue Apr 26, 2021 · 5 comments · Fixed by #6341
Assignees
Labels
backend Affects the web backend cases change A change of an existing feature (ticket type) contacts import-export qa-verified Issue has been tested and verified by QA

Comments

@maxiheyner
Copy link

maxiheyner commented Apr 26, 2021

Feature Description

The user asked for multiple variables, that are missing so far in detailed and custom case export. These are the following:

  1. sequelae (YES; NO; UNKNOWN) & sequelae details (text)
  2. symptoms
  3. clinicianName, clinicianPhone, clinicianEmail
  4. reportingUser & responsibleUser, as name in one column with separate user role in another column
  5. status and date of investigation
  6. help needed in quarantine - text
  7. add the symptom journal status to exports for contacts
  8. prohibition to work (YES/NO/UNKNOWN) and from/until dates

Problem Description

So far many important variables are missing within detailed and custom export.

Proposed Change

Add the variables mentioned above to detailed and custom export.

@maxiheyner maxiheyner added the change A change of an existing feature (ticket type) label Apr 26, 2021
@MateStrysewske
Copy link
Contributor

MateStrysewske commented Apr 26, 2021

Hey!

symptoms

These are already part of the detailed and custom case export. They're also part of the detailed contact export as "Symptoms at last cooperative visit". What exactly are you missing here?

reportingUser & responsibleUser, as name in one column with separate user role in another column

What would be the reason to combine them in one single column? Also, reporting user is automatically filled in during import; the purpose of this field is to contain the user that created the case in SORMAS

status and date of investigation

Investigation status is already there, but date is missing

provide a custom PERSON and a custom TASK export (providing all available variables from the db)

This would require two separate issues

@maxiheyner
Copy link
Author

@MateStrysewske Hey!

symptoms
These are already part of the detailed and custom case export. They're also part of the detailed contact export as "Symptoms at last cooperative visit". What exactly are you missing here?
Is it possible to show only the symptoms that were checked to get a better overview and to limit the number of columns?

reportingUser & responsibleUser, as name in one column with separate user role in another column
What would be the reason to combine them in one single column? Also, reporting user is automatically filled in during import; the purpose of this field is to contain the user that created the case in SORMAS
sorry this was misleading: the user wants to have the reporting user as name and user role in separate columns AND the responsible user as name and user role in seperate columns.
status and date of investigation
Investigation status is already there, but date is missing
the date would be also of interest for the user
provide a custom PERSON and a custom TASK export (providing all available variables from the db)
This would require two separate issues
ok

@MateStrysewske
Copy link
Contributor

@maxiheyner

Is it possible to show only the symptoms that were checked to get a better overview and to limit the number of columns?

Currently not, no. Would be a feature we would need to add.

sorry this was misleading: the user wants to have the reporting user as name and user role in separate columns AND the responsible user as name and user role in seperate columns.

Understood!

@maxiheyner
Copy link
Author

@MateStrysewske Currently not, no. Would be a feature we would need to add.
Yes please this would be a nice feature

next points:

  1. the "names of the guardians" should be included to detailed export for cases and contacts
  2. within the detailed export of cases the users recognized that, when paragraphs within free text fields are used, several lines are produced within the export file - is it possible to prevent this?

@markusmann-vg
Copy link

@maxiheyner

  • Person export will be covered with Provide PERSON Exports (basic, detailed, custom) [3] #6206

  • We discussed internally, that showing only the checked symptoms could be a new feature for the custom export and therefore you should create a new issue.

  • "within the detailed export of cases the users recognized that, when paragraphs within free text fields are used, several lines are produced within the export file - is it possible to prevent this?" => will not be covered with this issue and a new issue should be created

@markusmann-vg markusmann-vg changed the title Add multiple variables to detailed and custom export Add multiple variables to detailed and custom export [2] Jul 23, 2021
@vidi42 vidi42 added this to the Sprint 106 - 1.63.0 milestone Jul 26, 2021
@vidi42 vidi42 added this to Backlog in SORMAS Team 4 - TEC - Iteration Backlog via automation Jul 26, 2021
@leventegal-she leventegal-she self-assigned this Aug 9, 2021
@leventegal-she leventegal-she moved this from Backlog to In Progress in SORMAS Team 4 - TEC - Iteration Backlog Aug 9, 2021
leventegal-she pushed a commit that referenced this issue Aug 12, 2021
@leventegal-she leventegal-she moved this from In Progress to Review in SORMAS Team 4 - TEC - Iteration Backlog Aug 12, 2021
leventegal-she pushed a commit that referenced this issue Aug 12, 2021
SORMAS Team 4 - TEC - Iteration Backlog automation moved this from Review to Testing Aug 13, 2021
@AndyBakcsy-she AndyBakcsy-she added the qa-verified Issue has been tested and verified by QA label Aug 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend Affects the web backend cases change A change of an existing feature (ticket type) contacts import-export qa-verified Issue has been tested and verified by QA
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants