@MarcusStrobl , we had another discussion about Eddy data yesterday and concluded, that we need to introduce a new column to Entry, called is_partial, a boolean column that is False by default. If an Entry is partial, it has to be part of a EntryGroup of type==composite. The metadata described by these kind of Entry do only make sense in conjunction with the other Entry records in the same composite, while the others are self-contained and also make sense without the partialEntry.
Example
The Eddy data in principle consists of wind measurements (Entry no. 1), e.g. CO2 fluxes (Entry no. 2) and Covariances between all the components (<- partial Entry). It makes sense to use only wind measurements or CO2 fluxes and not caring about the Eddy tower. You can use either without the other. But if you are interested in Eddy, you need all three. Thus if a user searches for wind, he should find Entry no. 1 (and only that), with a note that the data is part of a composite. If he searches for Eddy (the EntryGroup) and 'clicks' on Entry no. 1, the system has to load Entry no.1, no. 2 and the partial Entry.
The partial Entry itself does not make any sense like this and should not be found.
@MarcusStrobl , we had another discussion about Eddy data yesterday and concluded, that we need to introduce a new column to
Entry
, calledis_partial
, a boolean column that isFalse
by default. If anEntry
is partial, it has to be part of aEntryGroup
oftype==composite
. The metadata described by these kind ofEntry
do only make sense in conjunction with the otherEntry
records in the same composite, while the others are self-contained and also make sense without the partialEntry
.Example
The Eddy data in principle consists of wind measurements (Entry no. 1), e.g. CO2 fluxes (Entry no. 2) and Covariances between all the components (<- partial Entry). It makes sense to use only wind measurements or CO2 fluxes and not caring about the Eddy tower. You can use either without the other. But if you are interested in Eddy, you need all three. Thus if a user searches for wind, he should find Entry no. 1 (and only that), with a note that the data is part of a composite. If he searches for Eddy (the EntryGroup) and 'clicks' on Entry no. 1, the system has to load Entry no.1, no. 2 and the partial Entry. The partial Entry itself does not make any sense like this and should not be found.
metacatalog
checklist was transferred to the PR #58