Darwin Core is well suited to describe(museum) collection or observational field data, but does not come with specific terms to capture experimental data. This becomes challenging if experimental information, such as treatment should be stored for individual records (for example individual events, which are sampling events of individual plots to which different treatments were applied).
One way of storing such information is to store the treatment description as a fact in the measurement or fact class and linking these fact to the individual events by eventID. This is however a bit cumbersome and also leads to redundancy of information if, for example, a treatment only has been applied to a plot once but that plot is then sampled several times because treatment information then needs to be repeated for every sampling event.
Another option to store this type of information would be to use one of the terms fieldNotes or eventRemarks that belong to the Darwin Core class event and can therefore directly be added to the events/event file. This does however seem a bit random to add this type of crucial information into a type of remark fields and wouldn't be the preferred option to use.
Darwin Core is well suited to describe(museum) collection or observational field data, but does not come with specific terms to capture experimental data. This becomes challenging if experimental information, such as treatment should be stored for individual records (for example individual events, which are sampling events of individual plots to which different treatments were applied).
One way of storing such information is to store the treatment description as a fact in the measurement or fact class and linking these fact to the individual events by eventID. This is however a bit cumbersome and also leads to redundancy of information if, for example, a treatment only has been applied to a plot once but that plot is then sampled several times because treatment information then needs to be repeated for every sampling event.
Another option to store this type of information would be to use one of the terms fieldNotes or eventRemarks that belong to the Darwin Core class event and can therefore directly be added to the events/event file. This does however seem a bit random to add this type of crucial information into a type of remark fields and wouldn't be the preferred option to use.