From a revision comment by an anonymous reviewer of the GeoPick manuscript for Ecography:
"Considering the focus on benefiting from the work of others, that recordedByID be added. In this manner (especially since more and more collections are providing this), georef work benefits from larger projects focused on certain times / regions / taxa and then different institutions more effectively benefit from the geo work done by others. The WHO is now a realistice and valuable clue that can be used to reconstruct the where (especially for legacy data), considering that our digitization efforts / priorities vary widely across the world. And, sometimes there will be lovely synchronicity allowing one to geoference not by one locality string at a time --- rather by the corpus created around the WHO. It's a great opportunity (imho). And I encourage you to add mention of its potential to our future geo adventures."
We think the idea can be a nice one, but should be implemented at the project level in terms of the corpus to be georeferenced, not in the georeference output. Those data are about the event, not the georeference, which is the output GeoPick seeks to produce. If GeoPick took tabular input, the recordedBy//recordedByID could be included there and maintained in output. We have added this as a feature request in the GitHub repo for a later version of GeoPick.
From a revision comment by an anonymous reviewer of the GeoPick manuscript for Ecography:
"Considering the focus on benefiting from the work of others, that recordedByID be added. In this manner (especially since more and more collections are providing this), georef work benefits from larger projects focused on certain times / regions / taxa and then different institutions more effectively benefit from the geo work done by others. The WHO is now a realistice and valuable clue that can be used to reconstruct the where (especially for legacy data), considering that our digitization efforts / priorities vary widely across the world. And, sometimes there will be lovely synchronicity allowing one to geoference not by one locality string at a time --- rather by the corpus created around the WHO. It's a great opportunity (imho). And I encourage you to add mention of its potential to our future geo adventures."
We think the idea can be a nice one, but should be implemented at the project level in terms of the corpus to be georeferenced, not in the georeference output. Those data are about the event, not the georeference, which is the output GeoPick seeks to produce. If GeoPick took tabular input, the recordedBy//recordedByID could be included there and maintained in output. We have added this as a feature request in the GitHub repo for a later version of GeoPick.