Thanks Lars! This would work for us. -Aravind
On Tue, Apr 22, 2014 at 1:29 PM, Lars Helge Øverland <larshe...@gmail.com>wrote: > Hi Aravind, > > for this I suggest you use the "dynamic attributes" feature. Through UI, > you navigate to data administration > attribute > add new, then enter the > attribute name and value type (e.g. "Location", "Text") and check > "organisation unit" (which makes this attribute apply to org units). Now > when adding new org units, these new attributes will be available as input > fields, and will also be present in the web api resource representation. > > cheers > > Lars > > > > On Tue, Apr 22, 2014 at 7:12 AM, Aravind Muralikrishnan < > aravi...@thoughtworks.com> wrote: > >> Hello all, >> >> We are implementing DHIS2 for MSF <http://www.msf.org/>. We have a >> requirement in which, we want to store a couple of additional details at an >> organisation unit level. The following are the additional fields that we >> will have to capture: >> >> 1) Location >> 2) Type (Direct, Indirect, Coordination, etc.) >> 3) Context (Armed conflict, Post conflict) >> 3) Number of consultation days per week (1-7) >> 4) Type of population >> >> We were looking at adding these additional fields to the organisation >> unit domain object. >> Is this the right approach, or is there a better way of doing this? >> Also, we wanted to find out if this is a generic enough use case for >> DHIS. If yes, we could submit a patch for the same. >> >> Thanks, >> Aravind >> >> _______________________________________________ >> Mailing list: https://launchpad.net/~dhis2-devs >> Post to : dhis2-devs@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~dhis2-devs >> More help : https://help.launchpad.net/ListHelp >> >> >
_______________________________________________ Mailing list: https://launchpad.net/~dhis2-devs Post to : dhis2-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~dhis2-devs More help : https://help.launchpad.net/ListHelp
