dhis2-devs team mailing list archive

[Prosper BT <ptb3000@xxxxxxxxx>]

Hi Abyot

Thanks for the quick response. My concern is of duplicate records per
stage. We have implementations of the tracker where data will be entered
from tables (rows and columns) of different visits like below. Unless one
is keen and keeps ticking the line he has entered, its very possible to
repeat the line and the system will accept

[image: Inline image 1]

Regards

On Mon, Feb 22, 2016 at 5:48 AM, Abyot Gizaw <abyota@xxxxxxxxx> wrote:

> Hi Prosper,
>
> No, this is not supported. A problem is what if we have some kind of
> sensor device that sends event data every hour or so. There was also a
> discussion to use time stamp than date for events.
>
> Will it solve your problem is you configure  your program stage as
> periodic?
>
> ---
> Thank you,
> Abyot.
>
> On Mon, Feb 22, 2016 at 8:54 AM, Prosper BT <ptb3000@xxxxxxxxx> wrote:
>
>> Thanks Markus for the detailed explanation.
>>
>> Lets adjust our training materials moving forward.
>>
>> One other thing not yet supported maybe we could write a blue print if
>> you agree.
>>
>> Now that we have all the completed events lumped up together in the long
>> list of boxes, chances of duplicating records for a given date are high,
>> like someone who is entering line listing data could easily enter the same
>> record many times since there is no check of duplicates by report/visit
>> date.
>>
>> Is this supported or something that needs to be built.
>>
>> A prompt when same report/visit date is entered.
>>
>> Or also the ability to search completed events on the tracked entity
>> dashboard
>>
>> Regards
>>
>> On Fri, Feb 19, 2016 at 6:21 PM, Markus Bekken <markus.bekken@xxxxxxxxx>
>> wrote:
>>
>>> Hi Prosper,
>>> thank you for your usual vigilance :)
>>> As you point out there has been some adaptations and changes to this in
>>> the last releases. The order of the events is chronological based on
>>> execution or due date. The timeline displays events from all program stages
>>> to form a complete list of the events that has been registered - following
>>> the chronological sort order mentioned, but across all program stages. This
>>> will give a complete picture for the program, and in cases where the order
>>> of the events is not always the same as the program stages sort order - a
>>> more correct picture.
>>>
>>> The functionality of adding new program stages this has also been
>>> changed a bit the last two releases. The current solution has buttons for
>>> adding program stages to the right. Even though the program stage sort
>>> order is no longer concidered when determining the list of events in the
>>> vizualisation, it plays an important role in the program stage that is
>>> suggested to the user in the "Add event" dialog. When making a suggestion,
>>> all the current events in the program is concidered together with the sort
>>> order of these events, and the next logical program stage will be suggested
>>> for the user. Of course the user can change the selection if he wants to
>>> create a new program stage. It is also possible to click the arrow button
>>> at the top to expand the list of possible events, giving the user one-click
>>> access to adding program stages.
>>>
>>> As you point out - in some cases it might make sense keeping the program
>>> stages more separate. We are working on an alternate view of the
>>> vizualization that has a "top level" menu, and vizualisations for events
>>> within each program stage. The below screenshot illustrates this(please
>>> disregard the other customized terms and widgets below, these are specific
>>> adjustments that would not be part of the main menu solution). As you can
>>> see, the different program stages are presented each in a box based on the
>>> sort of the program stages. Each box shows the number of events, and the
>>> most significant status among the events in the box. If all events are
>>> complete within a program stage, the box is grey(the new "Completed"
>>> color), of any one of the events are open(yellow - being filled but not
>>> completed), or any scheduled events exists, this will be vizualised on the
>>> main menu level.
>>>
>>> When clicking into an element on this main menu, the normal
>>> vizualisation will be displayed, but only for the selected event below you
>>> can see how the post partum care vizualisation would look. When postpartum
>>> care is selected as the program stage, you would be in "postpartum" mode
>>> and the add buttons would primarily add new postpartum care visits. To go
>>> back to the menu there would be a button to take you back to the main menu.
>>> The idea of this top level/main menu is that it can be an alternate view
>>> where it makes more sense to keep program stages separate, not as a common
>>> stream of events across all program stages. It would be possible to turn
>>> off or on, perhaps even by the user himself - the changes is not
>>> functional, only a different way of visualizing and accessing the events.
>>>
>>> Please provide any inputs or thoughts on this :)
>>>
>>> Best regards,
>>> Markus
>>>
>>> 19. feb. 2016 kl. 17.07 skrev Prosper BT <ptb3000@xxxxxxxxx>:
>>>
>>> Thanks Markus
>>>
>>>
>>> Good to see its has been backported, tested on the demo server and
>>> working fine with 2.22
>>> <Screen Shot 2016-02-19 at 11.03.51 AM.png>
>>> Could you throw more light on the switch of stage display and order.
>>> Originally we had a stage and all related events in the same box with
>>> little numbers, but now they are spread all over, what order is followed?
>>>
>>> Its a big shift in training user especially on adding new events. And
>>> with programs that have many stage it gets messy.
>>>
>>> Regards
>>>
>>>
>>> On Wed, Feb 17, 2016 at 2:56 AM, <markus.bekken@xxxxxxxxx> wrote:
>>>
>>>> Hi Ese, thanks for reporting.
>>>> This is a bug. It was fixed in trunk earlier, and will be backported.
>>>>
>>>> Markus
>>>>
>>>> Den 17. feb. 2016 kl. 07.39 skrev Ese Egerega <egerega@xxxxxxxxx>:
>>>>
>>>> Hello Devs,
>>>>
>>>> Many thanks for the new improvements in the tracker but there is
>>>> something you may want to look into.
>>>>
>>>> With the new design of the data entry form, the name of the program
>>>> stage is listed after "date" and "Org unit". This may cause problems during
>>>> data entry because the person entering data may not see the name of the
>>>> program stage in cases where you have a long org unit name (see snapshot
>>>> below).
>>>>
>>>> The snapshot below is supposed to display "Birth" and "Baby Postnatal"
>>>> but as you can see, the program stage does not show up because of the
>>>> length of the org unit name.
>>>>
>>>> In my opinion, the old design is better for the following reasons:
>>>>
>>>>    - The name of the program stage is displayed clearly
>>>>    - Program stages are in different "boxes" so you can navigate
>>>>    events in a program stage separate from other stages
>>>>
>>>> Thanks,
>>>> Ese
>>>>
>>>> <image.png>
>>>>
>>>>
>>>> _______________________________________________
>>>> Mailing list: https://launchpad.net/~dhis2-users
>>>> Post to     : dhis2-users@xxxxxxxxxxxxxxxxxxx
>>>> Unsubscribe : https://launchpad.net/~dhis2-users
>>>> More help   : https://help.launchpad.net/ListHelp
>>>>
>>>>
>>>> _______________________________________________
>>>> Mailing list: https://launchpad.net/~dhis2-users
>>>> Post to     : dhis2-users@xxxxxxxxxxxxxxxxxxx
>>>> Unsubscribe : https://launchpad.net/~dhis2-users
>>>> More help   : https://help.launchpad.net/ListHelp
>>>>
>>>>
>>>
>>>
>>> --
>>> Prosper Behumbiize, MPH
>>> Global HISP| University Of Oslo/HISP Uganda
>>> +256 752 751 776 | +256 776 139 139
>>> prosper@xxxxxxxxxxxxxx <ptb3000@xxxxxxxxx> | prosper@xxxxxxxxx | Skype:
>>> prospertb
>>>
>>>
>>>
>>
>>
>> --
>> Prosper Behumbiize, MPH
>> Global HISP| University Of Oslo/HISP Uganda
>> +256 752 751 776 | +256 776 139 139
>> prosper@xxxxxxxxxxxxxx <ptb3000@xxxxxxxxx> | prosper@xxxxxxxxx | Skype:
>> prospertb
>>
>
>


-- 
Prosper Behumbiize, MPH
Global HISP| University Of Oslo/HISP Uganda
+256 752 751 776 | +256 776 139 139
prosper@xxxxxxxxxxxxxx <ptb3000@xxxxxxxxx> | prosper@xxxxxxxxx | Skype:
prospertb