Taxonomic Swap 45300
(Guardado el 05/01/2019)
|
|
Reemplazado con |
|
Comentarios
I agree with Jakob, you changed a family name in a genus name, that it is not possible.
I guess I'm not understanding the problem. My objective was to move content (IDs observations etc) from Family Myocastoridae to Genus Myocastor. This swap accomplished that. Am I missing something?
I think it is not correct, even if the only species inside the family is Myocastor coypus. You changed the systematic tree putting a genus at the same level of a family. You can collect all the observations of M. coypus simple by gathering both taxa.
There are 2 issues here: a taxonomic one (whether or not the family Myocastoridae can be considered a synonym of the genus Myocastor), and a practical one in terms of observation IDs. The 2 issues shouldn't be linked in this case. It would be actually a good idea to code taxonomic changes as to prevent higher taxa to be swapped with any rank equal to or lower than genus.
As I've said above, a family cannot be the synonym of a genus (due to the swap, it is listed as such under the genus Myocastor, which is wrong). If you want to put Myocastoridae into synonymy, you could have swapped it with the tribe Myocastorini.
The ID issue should be handled simply by adding species IDs to those identified at a coarser level.
I am exactly of the same opinion of @jakob .
For what the observations are concerned, if you know that the family Myocastoridae contains only the Myocastor genus and only the species M. coypus, you can get all the Myocastor observations or all the M. coypus observations simple collecting all the Myocastoridae observations, and you can do that by the filter options.
For the systematic concern, you can swap Myocastoridae to Myocastorini since it can be recognized as a tribe belonging to the family Echimyidae.
OK thanks - I agree a swap from Myocastoridae to Myocastorini would have been prefferable if it had avoided this controversy. But from a practical issue everything seems fine and properly curated here (ends justify the means?) so I don't see any reason to revert or spend more time disputing unless you do. (Myocastoridae is not a inactive scientific name associated with Myocastor. I agree that that would be bad which is why after committing that swap I removed that name.)
re: whether preventing higher taxa to be swapped with any rank equal to or lower than genus, need to think more about that with real examples but will keep that in mind
Apparently all fine, everything resolved. We just tried to explain the issue, as you said you didn't understand the problem.
Would be good if a swapping block of higher taxa into anything equal or lower to genus could be implemented as this should simply never happen.
Please do not swap taxa higher than genus-level with genera, that's a taxonomic no-no