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
This template is an experiment in the works, feel free to modify/propose changes.
People and AgentStrings
This is version 0.0.1. All changes beyond grammar will result in an increment. Higher level increments reflect larger changes that may reflect new ways of doing things, or differences in user interfaces, etc.
You can ask for help and clarification live in person on Gitter!
Overview
This is a brief manual on curating People and references to people ("AgentStrings", i.e. data not yet formalized to People instances) in TaxonWorks.
Exercise target audience
Data curators.
Exercise goals
The goals are to describe:
Describe input patterns for common name variants
Describe mechanisms to add identifiers to people
Point to (but not fully describe) tools in TaxonWorks that facilitate the curation of People
Describe caveats for how People are rendered when displayed in various scenarios (e.g. Citations, Citation lists, as Taxon Name authors, etc.)
Describe how to link your user account to your representation as People data
At the end of the exercise you should:
Enter names for People like "Simon van Noort", "<TODO d', l', le, ben-> alternates
Understand how to add alternate values (character encodings, abbreviations, etc.) to People
Add ORCID ids (and other identifers) to people
Add an ORCID id to your User account (i.e. link yourself to your representation as a Person data element)
Assumptions
You have a User account in a TaxonWorks instance
Gotchas
TaxonWorks is only officially supported on Firefox and Chrome.
Tips
Tip 1
Tip 2
Tip 3
Related exercises
Related exercise 1 (link to other manual)
Exercise
Syntax
In the exercise bulleted points are actions you should take, non-bulleted tasks are comments or guiding questions.
Highlighted words refer to text or elements in the application, for example button or field names.
"Quoted words" are literal values to be input or noticed
People names
We acknowledge that globally the names of people follow many different patterns and idiosyncracies and that the present model employed in TaxonWorks is decidely Western/European scientific, this reflects the available libraries for things like parsing names, modelling sources, and rendering citation lists. This clear bias obviously isn't optimal. While we can not re-write large code-libraries that we depend on (e.g. CSL rendering, BibTeX standards), we can and do provide mechanisms (e.g. alternate values, translations, etc.) that can start to faciliate a more global perspective on how to represent the names of People.
It is important to remember, from a data modelling perspective, that a name is not the same as the Person. This is another way of saying, "your name matters to nobody but yourself, you matter to everyone".
Subsection title (1a)
Section title 2
...
Section title 3
...
Wrapping up
Reminder of what was taught/learned.
Addendum
Addendum topic 1
The text was updated successfully, but these errors were encountered:
This template is an experiment in the works, feel free to modify/propose changes.
People and AgentStrings
This is version 0.0.1. All changes beyond grammar will result in an increment. Higher level increments reflect larger changes that may reflect new ways of doing things, or differences in user interfaces, etc.
You can ask for help and clarification live in person on Gitter!
Overview
This is a brief manual on curating People and references to people ("AgentStrings", i.e. data not yet formalized to People instances) in TaxonWorks.
Exercise target audience
Data curators.
Exercise goals
The goals are to describe:
At the end of the exercise you should:
Assumptions
Gotchas
Tips
Related exercises
Exercise
Syntax
Highlighted words
refer to text or elements in the application, for example button or field names.People names
We acknowledge that globally the names of people follow many different patterns and idiosyncracies and that the present model employed in TaxonWorks is decidely Western/European scientific, this reflects the available libraries for things like parsing names, modelling sources, and rendering citation lists. This clear bias obviously isn't optimal. While we can not re-write large code-libraries that we depend on (e.g. CSL rendering, BibTeX standards), we can and do provide mechanisms (e.g. alternate values, translations, etc.) that can start to faciliate a more global perspective on how to represent the names of People.
It is important to remember, from a data modelling perspective, that a name is not the same as the Person. This is another way of saying, "your name matters to nobody but yourself, you matter to everyone".
Subsection title (1a)
Section title 2
...
Section title 3
...
Wrapping up
Reminder of what was taught/learned.
Addendum
Addendum topic 1
The text was updated successfully, but these errors were encountered: