Open PipBrewer opened 10 months ago
@JesperMJensen Did you do anything regarding this?
Not much. We essentially compiled a list of the various naming possibilities, but never moved on to any solutions. It was my understanding, a decision was made to essentially scrap this task.
Some of the things we looked at already have their separate issues (Hybrids, s.l.). I think we had a meeting where it was decided that this was enough for now and the other things will be looked at if or when they become a problem.
We need to investigate and document how the taxon spine should work ideally and where we are at with it in Specify, the app db, the app UI and the GREL script – so for hybrids, var., subvar., forma, sub forma, synonyms, new taxa, new family or higher taxa, cf., aff., sp., subgenera etc we should state what the situation is with each for how written (e.g., on label), how parsed out in Specify, how seen in app (in UI), how parsed out in app db, how enter new one in app.
This will assist communication, documentation, how to deal with updates, understanding older versions of the app and bug testing.