Share internal USGS blog posts on ORCID?
Tanner here, from back in the NBII and DataONE days.
I’m doing a post-masters’ ORISE fellowship in science communication with the U.S. Forest Service’s Pacific Northwest Research Station in Portland, Oregon. (And yes, I’ve already evangelized here about getting the Forest Service Research Data Services repository on board as a member node for DataONE).
I’m writing today because I’m looking in to the USGS’ use of ORCID. We recently had a PNW Research Station employee as a co-author on a USGS publication, and this brought USGS use of (requirement of) ORCID to our attention.
I have learned the Forest Service has a fair number of researchers already using ORCID – nothing to brag about.
While I don’t think we’re in a position to “require” that our researchers use ORCID, I think it’d be worthwhile to encourage them to sign up for one and share it with us.
Enter a science communication problem: communicating the value of ORCID to our scientists.
I figured USGS already had some promotional material or documentation on why ORCID is a good idea – a quick search of “ORCID site:usgs.gov” pulled up promising material at <https://my.usgs.gov/confluence/pages/viewpage.action?pageId=555648166>.
However, two documents detailing USGS leadership thinking on the value of ORCID are internal only.
I was wondering if you could copy and paste the content of those posts to share with me?
Also – if you have any other contacts who might have “promotional” material on the value of ORCID – I’d much appreciate if you could forward my inquiry on to see if anyone has material that could help me communicate the value of ORCID at the Forest Service.
This electronic message contains information generated by the USDA solely for the intended recipients. Any unauthorized interception of this message or the use or disclosure of the information it contains may violate the law and subject the violator to civil or criminal penalties. If you believe you have received this message in error, please notify the sender and delete the email immediately.