dhis2-users team mailing list archive

[Martin Van Aken <martin@xxxxxxxxxxxxxxxx>]

Hi,
Thanks for your reply and proposal - my example was just that - an example.
I don"t have fixed periodicity for changes (else I agree that it could be
easy to setup a set with the given periodicity). I keep the csv import
idea, could actually be useful in other cases I'm facing.

Thanks and regards,

Martin

On Tue, Aug 30, 2016 at 11:03 PM, Elmarie Claasen <elmarie@xxxxxxxx> wrote:

> Hi Martin,
>
> It seems like your frequency is 6 monthly in which case you can set up a
> dataset with that frequency or any other you choose and then create a csv
> import file with all your facilities in, currect period, data element and
> value (just copy the same value for every facility and import. Keep the csv
> and every frequency you need to just change the period and value and
> possibly check you dont have new reporting units and import the same file.
>
> You can create similar xml or json imports but csv seems easier.
>
> Maybe this could work for you?
>
> Elmarie Claasen
> HISP-SA
>
> On 19 Aug 2016 09:16, "Martin Van Aken" <martin@xxxxxxxxxxxxxxxx> wrote:
>
>> Hi everyone,
>> I'm wondering about the best way to manage a use case of ours in DHIS2.
>> We have a specific element of data (prices for services in an RBF system)
>> which is normally the same for every org unit for a given period (and in
>> most case stable for several periods). As an example, we could have
>> something like:
>>
>> Consultation Price:
>> - Jan-December 2016: 2.5$
>> - Jan-June 2016: 2$
>> - July-December 2016: 3$
>>
>> I'm not sure what to use to represent this kind of data in DHIS2:
>>
>> - Constant is not good as it can evolve
>> - Standard Data Element means that when we make a change, we need to
>> "apply" it to every entity for the given period (thus generating hundreds
>> or thousand of copies of that values)
>>
>> Added question: if we go for a Data Element, how could we "fill it" at
>> regular basis (like for the next period each time) - we don't want people
>> to fill as a data entry for individual entities (it does not make any
>> sense, and it's not something they "report" anyway).
>>
>> Any opinion is welcome!
>>
>> Martin
>> --
>> *Martin Van Aken - **Freelance Enthusiast Developer*
>>
>> Mobile : +32 486 899 652
>>
>> Follow me on Twitter : @martinvanaken <http://twitter.com/martinvanaken>
>> Call me on Skype : vanakenm
>> Hang out with me : martin@xxxxxxxxxxxxxxxx
>> Contact me on LinkedIn : http://www.linkedin.com/in/martinvanaken
>> Company website : www.joyouscoding.com
>>
>> _______________________________________________
>> 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
>>
>>
> *This message and any attachments are subject to a disclaimer published at
> http://www.hisp.org/policies.html#comms_disclaimer
> <http://www.hisp.org/policies.html#comms_disclaimer>.  Please read the
> disclaimer before opening any attachment or taking any other action in
> terms of this electronic transmission.  If you cannot access the
> disclaimer, kindly send an email to disclaimer@xxxxxxxx
> <disclaimer@xxxxxxxx> and a copy will be provided to you. By replying to
> this e-mail or opening any attachment you agree to be bound by the
> provisions of the disclaimer.*
>



-- 
*Martin Van Aken - **Freelance Enthusiast Developer*

Mobile : +32 486 899 652

Follow me on Twitter : @martinvanaken <http://twitter.com/martinvanaken>
Call me on Skype : vanakenm
Hang out with me : martin@xxxxxxxxxxxxxxxx
Contact me on LinkedIn : http://www.linkedin.com/in/martinvanaken
Company website : www.joyouscoding.com