My thought on this was that the periods for user define periods would never be generated and they would only be available when users are able to contact the server. It would be up to implementers to define all required future and past periods. I guess we will never be able to cater to all requirements in terms of the periods which may be required. I am also thinking of the requirements from Nepal, where there is really no easy to to calculate the periods at all (algorithmically) but there are lists of Nepali months available for the next 20 years or so, which could be easily enough converted into DHIS2 type periods (startdate/enddate).
Regards, Jason On Fri, Mar 28, 2014 at 1:08 AM, Lars Helge Øverland <larshe...@gmail.com>wrote: > > > >> >> A question to the developers...would it be possible to support a "user >> defined period type", which would require that users create their own >> start/enddates? I realize that this would create problems for the offline >> features of DHIS2, but this requirement, along with similar ones in >> countries which do not use the Gregorian calendar, point to the need for >> something more flexible than what we currently have. >> > > > It is definitely possible (as with most things) and could be done. But it > will require a significant development effort, since dhis is currently > based on periods being generated in memory and persisted when needed. I do > understand the need for it and we are hearing it from multiple sources now. > > Lars > >
_______________________________________________ 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
