many thanks for your activity for the improvement of the Searching and
sorting of events in the Event Capture App
*JIRA (DHIS2-254) Search for an event in all Events of the selected
Program, (DHIS2-149) Searching and sorting of events.*
Is it already ported to the c. 2.25? If not, when it is planned?
For our users this features are important. Gust yesterday the ask for this
*I have some suggestions about Capture event Page face and data entry, *
*First Previews table sorting (incident date) field data in all pages,
descending sort better than ascending sort.*
*Why? Because the Users can see last his saved data i.e. always (last data
saved) preview on the user screen, so user know end work time!*
*Searching operation in any fields should be searching all pages at the
*For example we want to find (Suha Samir) patient name, it must display
whit out we will search page by page. *
*According to print operation, when we will select (All) option it must
print all data saved in our data base ... please check it be carefully!*
*Hama Kh. Hama - Qaladze Hospital*
---------- Forwarded message ----------
From: Lars Helge Øverland (JIRA) <firstname.lastname@example.org>
Date: 2016-12-15 17:54 GMT+01:00
Subject: [dhis2-issue] (DHIS2-254) Search for an event in all Events of
the selected Program
Lars Helge Øverland
*updated* [image: Improvement] DHIS2-254
DHIS 2 <https://jira.dhis2.org/browse/DHIS2> / [image: Improvement]
Search for an event in all Events of the selected Program
Change By: Lars Helge Øverland
Status: Testing Done
[image: Add Comment]
<https://jira.dhis2.org/browse/DHIS2-254#add-comment> Add Comment
This message was sent by Atlassian JIRA (v7.2.3#72005-sha1:73be91d)
[image: Atlassian logo]
2016-11-23 0:44 GMT+01:00 Antonia - Pro <email@example.com>:
Actually when I make a search in the Event Capture window, the search is
limited to the only visible page of the events for the selected Program
(for the specific OrgUnit).
Probably the search is made on the client side.
It will be very useful if the search is made on the server side and the
output of the search are all events in the selected program, which meet he
search filter, not only in the visualized page.
For example, when an verification audit is done and some strange value is
found by the statistics, we have to find the event with this value to
correct or examine it.
When the events in the program are not too much, we can scroll the pages,
or make a biggest page with more than the default 50 events (200, 500). But
when the events are more than 10 000 or 50 000 it is inconvenient.
It will be more useful and faster to make the search as a query with the
search filter to the server and than visualize the output result of the
query on the Event Capture window.
[image: Immagine incorporata 1]
[image: Immagine incorporata 2]
I created an issue with the new JIRA for issue tracking, I hope I done it
www.informa.pro - *Seguici su *LinkedIn
INFORMAPRO S.r.l. - via Luigi Rava 43, Rome 00149 , Italy
tel. +39 06 5758926 <+39%2006%20575%208926>, fax +39 06 62207168, P.IVA
Eng. Antonia Bezenchek - CIO - ICT Engineer