You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Sample table does not efficiently describe replicate samples. For example, when you take multiple grab samples on the same day at the same location. Therefore I would suggest adding an index field to this table, similar to the one in the WWMeasure table.
The text was updated successfully, but these errors were encountered:
@NielsNicolai yes agree but the experience from MECP is that this index is not being used properly and we need some other built in key(s) as a redundant way to get this information when we aggregate the worksheets.
Hi @vipileggi, how is it used at the moment?
One way of dibble checking whether it's a replicate or not is by validating if the date, site and type combination already exists. Yet this can only be done in the data validation/post-processing I think.
Hi @NielsNicolai on #103 (comment)
that is what I've done as a temporary hack or workaround but not ideal. We had some MECP internal discussion on this and decided to try and communicate back to the users to clarify the use of the index variable and still necessary and can't think of a better way at the moment.
The
Sample
table does not efficiently describe replicate samples. For example, when you take multiple grab samples on the same day at the same location. Therefore I would suggest adding anindex
field to this table, similar to the one in theWWMeasure
table.The text was updated successfully, but these errors were encountered: