On 9 January 2011 19:45, Bob Jolliffe <[email protected]> wrote: > Hi Ola > > Quick question: > > the resource table _dataelementgroupsetstructure lists all > dataelementnames. Similarly with _indicatorgroupsetstructure, > _orgunitstructure and _orgunitgroupsetstructure. > > In the pivot views you are familiar with, should it be necessary to > also have access to dataelement, indicator and orgunit tables or are > the resource tables sufficient? >
If not, could/should we make it so? eg to bring shortnames into these > tables if they are used. Or, if it is desirable to be able to use the > "source" tables, to remove the names from the resource tables? > > It would be enough to get the names either from the source or from the resource tables yes, no need to have them both places. At least I can't see any reason for duplicating these names. You know better what is the most efficient way to set this up. One related comment: The way I have set up the pivot views (you have them) joining the source tables (data element, indicator, orgunit) with the above mentioned resource tables (using the IDs) only the names present in the resource tables are coming through to the pivot table, e.g. an indicator without any groups/groups sets or an indicator added after the last refresh of the resource table are not coming through in the pivot view. This might be too restrictive. Still we should enforce grouping all elements in at least one group set for easier browsing both in the DHIS UI and in pivots etc. Ola ------- > Regards > Bob >
_______________________________________________ Mailing list: https://launchpad.net/~dhis2-devs Post to : [email protected] Unsubscribe : https://launchpad.net/~dhis2-devs More help : https://help.launchpad.net/ListHelp
