I can see a use for dwc:dynamicProperties. We are just about to have our diatom collections databased and these come with things like 'salinity', 'pH', 'nitrates' and 'phosphates'. It is also a handy spot to put all sorts of other information that we record, but that wouldn't otherwise show in AVH.
There is something similar in older versions (< 5) of HISPID, namely the 'Non-standard option', which allowed you to extend HISPID with extra elements. In ABCD you would probably use the MeasurementOrFacts. There is a MeasurementOrFact class available in Darwin Core as well, which will in many cases be strictly more appropriate than dynamicProperties. The advantage of dynamicProperties is that it will show in AVH.
I wouldn't mind adding MeasurementOrFact elements to HISPID as well, but perhaps we wait until we have a use for it? Pretty sure the Seed Bank Hub is using this class.
Actually, maybe not include these terms. There is nothing for us to define here and, as they are in Darwin Core, not having the terms in HISPID doesn't prevent one from delivering them.
I can see a use for dwc:
dynamicProperties
. We are just about to have our diatom collections databased and these come with things like 'salinity', 'pH', 'nitrates' and 'phosphates'. It is also a handy spot to put all sorts of other information that we record, but that wouldn't otherwise show in AVH.There is something similar in older versions (< 5) of HISPID, namely the 'Non-standard option', which allowed you to extend HISPID with extra elements. In ABCD you would probably use the MeasurementOrFacts. There is a
MeasurementOrFact
class available in Darwin Core as well, which will in many cases be strictly more appropriate thandynamicProperties
. The advantage ofdynamicProperties
is that it will show in AVH.I wouldn't mind adding
MeasurementOrFact
elements to HISPID as well, but perhaps we wait until we have a use for it? Pretty sure the Seed Bank Hub is using this class.