You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If an NCA3 authors, use what is used there
else: if Health Assessment author, use what is there
else: the most complete formal name used in a GCIS publication
My suggestion for the convention is as follows:
If the author provides us with their preferred name and their OrcID, use the provided name.
We could only use custom name requests if they give us the OrcID to connect them with their publications moving forward
Use the authors name as it appears on our Quadrennial Assessments or their supporting report, starting with our most recent release and moving backwards.
for example, as of 2017-02 we would consider:
the CSSR
the Health Assessment
NCA3
NCA2
NCA1
Use the author's name as it appears in any other USGCRP publication.
i.e. Strategic Plan, Our Changing Planet, etc.
Use the author's name as it appears on their OrcID profile
this can be done in an automated manner, skipping those that fit one of the above categories and naming the others accordingly.
Final fallback: any official name we can find (author's website, facebook, researchgate, outside articles, etc).
Drawbacks:
Option 1 (custom name) and Option 4 (source from OrcID) both rely on the author having an OrcID they have told us.
Minor increase in level of effort creating the Persons when we publish a report
The text was updated successfully, but these errors were encountered:
I think this is fine, but would just add that in the unlikely case when going down the list there are still multiple answers (e.g. we get to option 3 and they listed their names differently in 2 different USGCRP documents), we choose the most complete formal name of those.
Our current convention for figuring our which name for use for a
Person
s is due for an update.Our Current convention
My suggestion for the convention is as follows:
Drawbacks:
The text was updated successfully, but these errors were encountered: