meghalithic
commented
2 years ago from @nsewnath No real formatting constraint with the individualID besides not using hyphens because that causes issues on the GEOME side. So, an individualID like "PR-ind1" would change the hyphen to "PR_ind1 '', then append the number for every unique individual. It would have the same individualID if it's for elements that come from the same specimen.
jdeck88
I want to make sure we're all on the same page about IDs:
individualID: encapsulates multiple elements that belong to the same individual organism; usually they share the same catalog number, but there could be multiple catalog numbers for the same individual (e.g., carcass and skeleton of the same individual). This is created using UUID. This is typically done before we melt (i.e., make long) the dataset.
materialSampleID: my understanding is this unique to the element (e.g., bone) of the individual organism. So, if we have a complete skeleton of a horse, it would have the same individualID but each bone would have its own materialSampleID. Or, if we only have the skin of an animal, it would have one individualID and materialSampleID. This is a UUID.
diagnosticID: this is unique per measurement of each individual. We usually make this after the data is made long. This is typically just an index and is unique within a dataset.
eventID: this is primarily for GEOME since FuTRES users don't need this. This different from eventID in Darwin Core. This is unique per row, after the data has been made into long format, and is made as a combination of materialSampleID and other columns. (@nsewnath can you remind me?)
Can @nsewnath and @jdeck88 both verify that this is true? I think we are doing materialSampleID wrong.