dhis2-devs team mailing list archive

[Lars Helge Øverland <larshelge@xxxxxxxxx>]

>
> Yes this is true.  But what do you think of the idea to enforce
> DataSet membership having a default DataSet for all the delinquents?
> I'm not sure if it can be enforced by the schema, but at least by the
> application.


OK but what does this give us in terms of PeriodType-determining if this
default DataSet has a null PeriodType?


>
>
> I don't know if its about right or wrong.  There are pros and cons of
> both approaches.  What you gain on the swings you lose on the
> roundabouts :-)
>
> In the explicit case the application will have to enforce that DataSet
> members all have the same periodType.
>
> In the implicit case the application will have to enforce that
> DataElements can only be members of multiple groups if these share the
> same PeriodType.
>
> The net result as far as the Data API is concerned can and must be the
> same.  Perhaps we should define exactly what extra methods we want in
> the API first.  We have already identified a few.  Then decide whether
> a database change is necessitated by these.
>

Yes. We need at least service method:

Collection<DataElement> getDataElementsByPeriodType( PeriodType )

and getter on the DataElement object:

PeriodType getPeriodType()


I guess we could make a branch, start coding and see how it works out.


Another issue would arise in the (exotic) situation where someone assigns a
DataElement to a DataSet, enter data for it, then removes it from the
DataElement. The data is there, but how do we deal with it in regard to the
mentioned required functionaly (trend analysis, datamart) ?