dhis2-devs team mailing list archive

[Bob Jolliffe <bobjolliffe@xxxxxxxxx>]

Just registered the blueprint.

On 11 May 2010 05:27, Kim Anh Vo <catakim@xxxxxxxxx> wrote:
> so, is it included somewhere? a blueprint yet? Any plan for it?
> Agree with the suggestion!
>
> --
> Default data entry forms: tables should be created based on sections and not catcombos
> https://bugs.launchpad.net/bugs/509554
> You received this bug notification because you are a member of DHIS 2
> coordinators, which is the registrant for DHIS.
>
> Status in DHIS 2 - District Health Information Software: New
>
> Bug description:
> When using multidimensional data elements and datasets with multiple catcombos, data set sections can be used to group data elements by catcombo and to provide titles for each generated table.
>
> Sometimes it also makes sense to split a long list of data elements with the same catcombo into sections (smaller tables) based on their meaning.
>
> When using sections and default forms then the generated tables should be generated off the sections and not the catcombos. Right now you will get one big table per catcombo eben though you might have defined several sections, which seems strange.
>
> Not sure we have restriction formally defined yet, but I would like to see a restriction on data set sections to only have 1 catcombo. Then it would be easy enough to create one table per section when generating the default form.
>
>
>

-- 
Default data entry forms: tables should be created based on sections and not catcombos
https://bugs.launchpad.net/bugs/509554
You received this bug notification because you are a member of DHIS 2
developers, which is subscribed to DHIS.

Status in DHIS 2 - District Health Information Software: New

Bug description:
When using multidimensional data elements and datasets with multiple catcombos, data set sections can be used to group data elements by catcombo and to provide titles for each generated table.

Sometimes it also makes sense to split a long list of data elements with the same catcombo into sections (smaller tables) based on their meaning.  

When using sections and default forms then the generated tables should be generated off the sections and not the catcombos. Right now you will get one big table per catcombo eben though you might have defined several sections, which seems strange. 

Not sure we have restriction formally defined yet, but I would like to see a restriction on data set sections to only have 1 catcombo. Then it would be easy enough to create one table per section when generating the default form.