dhis2-devs team mailing list archive

[Lars Helge Øverland <larshelge@xxxxxxxxx>]

Hi Juan,

thanks for explaining this. Its useful to know how you operate.

On Tue, Dec 10, 2013 at 6:32 AM, Juan M Alcántara Acosta <
jmalcantara@xxxxxxxxxxxxx> wrote:

> Hi Lars
> I'm sorry I think I did a poor job explaining, the selected parent and all
> the children I was referring to is the org unit the user is allowed to
> see/use, so the search would include org unit(s) assigned to the user and
> all the children.
> Let me give you a brief description of what we are doing. We have a first
> contact program (IPCs) with which we register clients at a municipality
> level (level 4) and a clinical services program that links services to
> specific providers (level 6, level 5 is the clinic). When the office
> receives the report of clinical services they don't know where the client
> was first contacted by an IPC and even if they can asume this took place at
> the same municipality where the clinic is located (not always the case).
> This is the procedure they use to do this as fast as possible:
>
> 1. Search and select the provider of the clinical service (org unit)
> 2. Search for the client by name, it would be great if they could also
> search by referral number which is a DE in a program.
>

Yes we can do this.


> 3. Once the client is found, the user opens the person panel to enrole the
> client in the clinical program and add the event(s). At this point the
> person can be moved to the org unit where the clinical services were
> received, but they are not doing this to save time.
>
> In this particular case a search on the selected org units (and all
> bellow) will not return the record of the client since it's located two
> levels above and it could even be on a different branch. We have to use
> "all visible" to get the result and this requires assigning an org unit and
> some or all of the children.
>


Lets just clarify the meaning of all those options:

All: All org units in the system (must require authority)
Children only: Org units in sub-tree(s) from selected org unit(s)
Immediate children: Direct children from the selected org units(s)
Selected: The explicitly selected org units

(I think we need to improve naming here, at least move from "children" to
"sub units".)

So it seems what you would like is to allow users to perform search in a
specific sub-tree of the org unit hierarchy, e.g. to allow search inside a
province or country, but constrain them from searching for other e.g.
countries. And that this permission to search is independent from the
access to registering new clients and registering data, which could be
constrained to another (smaller) sub-tree. Is this correct..?




>
> The users have made two more observations related to the search:
> 1. An advance search done with the options "Selected and bellow" and "All
> visible" takes at least 45 seconds
>

Yes I know its slow, we hope to rewrite that function for 2.14.


> 2. The search returns all the hits per word. For example, if you search
> for "Maria Luisa" you'll get back all the records that contain "Maria" plus
> all the records that contain "Luisa". Is there a way to get the results of
> only the records that contain all the words?
>

Okay I agree, I think that is the way it should be.

regards,

Lars