Sormas-project: task export should enclose phone number, address, dob, email of the associated person

Created on 15 Dec 2020  路  6Comments  路  Source: hzi-braunschweig/SORMAS-Project

First of all, thanks for the new feature of task export!!!

Feature Description

The task export should be enclose more personal details of the case/contact. We would need the phone number, address, dob.

Problem Description

Our department f眉r organizing the tests is using the tasks to do it. They would need the dob, address and phone number to be exported together with the task. Otherwise the have to look up it every morning manually.

Proposed Change

Exporting of the mentioned fields.

change

Most helpful comment

@bernardsilenou With this request we should actually consider a detailed export for tasks alongside the basic one and refine all the things that should be included. As you mentioned, this will likely differ depending on the referred entity but also differ considering the diversity of task types and their implications.

All 6 comments

@Marko-ilmkreis Thanks fro creating this request. I have a question.
Task are usually assigned users of the system and can be related to cases, contacts, events and general (not linked to any specific entity).
You request to have the phone number and address of the entity that the task is related to. If this is an event or general task, then this will be missing.
Please can you explain whey this is needed? I thought you would have asked for the address of the user that the task was assigned to.
Thanks

@bernardsilenou thats a good point. We currently uses tasks only for cases and contacts.

e.g. the investigation officer creates a task for taking a probe on 18.12.2020 by a mobile team. This task is assigned to a user called "Mobile", as the team which is organizing the routing of the mobile swap teams shifts every day (part of the Rescue Departement).
To organize the tour the can now filter (thanks!!) the user and the due date. Then they write the details in Excel, finding out the phone number and address.

@bernardsilenou With this request we should actually consider a detailed export for tasks alongside the basic one and refine all the things that should be included. As you mentioned, this will likely differ depending on the referred entity but also differ considering the diversity of task types and their implications.

@Marko-ilmkreis
I just want to make sure i understand you well.
You have a user in the system called "Mobile" and you assign tasks to this user to collect sample of a case called "Ben".
Your goal is to export the task assigned to "Mobile"+

  1. email, dob, address and phone number of "Mobile"
  2. email, dob, address and phone number of "Ben"

Do you need 1 or 2 or both ?
If it is 2, do you not also need the name of the contact person "Ben"? Ofcourse this will depend if psudonymize or not.

The option 2 would be the best, but the name of the contact person is not
needed in our case.

Many thanks for your help.

In summary

  • Add detailed export for contact
  • List of variables to be added to the basic export list:

    • email

    • dob

    • home address (region, district, community, postal code, city)

    • phone number

of persons linked to the entity (case, contact, event participants) of the task.

@kwa20 , @Candice-Louw @Candice-Louw any more variables to add ?

Was this page helpful?
0 / 5 - 0 ratings