Collection profiles and associated created containers are not associated with OTUs. Currently only label fields are added as a notes field. Can we pull OTUs from the "Taxon Number" field in Filemaker?
@proceps The otu is only needed to generate the label, once it is generated, the otu is not needed, that is why it is not transfered
@tmcelrath I disagree. The OTU is needed so we can search through containers and gather information for grants. E.g. if I can't search for "approx. how many containers of ticks do I have" because the containers or collection profiles are not liked to an OTU, then what is the point of profiling? The labels are not standardized, so it will be much more difficult to search through them than if we had the standard OTUs applied from the TaxonCode.
I've added issues for new Profiles Tasks in Github that are related to this (1058/1059).
Collection profiles and associated created containers are not associated with OTUs. Currently only label fields are added as a notes field. Can we pull OTUs from the "Taxon Number" field in Filemaker?
@proceps The otu is only needed to generate the label, once it is generated, the otu is not needed, that is why it is not transfered @tmcelrath I disagree. The OTU is needed so we can search through containers and gather information for grants. E.g. if I can't search for "approx. how many containers of ticks do I have" because the containers or collection profiles are not liked to an OTU, then what is the point of profiling? The labels are not standardized, so it will be much more difficult to search through them than if we had the standard OTUs applied from the TaxonCode. I've added issues for new Profiles Tasks in Github that are related to this (1058/1059).