locdb / locdb-frend

Fr(ont-)end for the Linked Open Citation Database.
https://locdb.github.io
GNU General Public License v3.0
6 stars 2 forks source link

How to input names? #204

Closed zuphilip closed 6 years ago

zuphilip commented 6 years ago

Currently we see sometimes familyName givenName which seems unusal. The OC model suggest as one possibility givenName familyName or to split these parts up. When we begin to input these names manually we should also have a clear guideline.

lgalke commented 6 years ago

Currently, we only use the more generic nameString property, since the OCR component also does not detect which is the first and which is the lastname.

lgalke commented 6 years ago

In #58 we also figured out, that seperating between first and last names is difficult in principle.

zuphilip commented 6 years ago

Sorry, I should be more specific. I am aware of the problems with automatically splitting a name string into first and last name. That is not what I suggest here.

But sometimes we already have first and last names e.g. from Crossref. OpenCitations seem to save them then also into two different fields. Moreover, when we have to input them manually, then we want to do that consistent, e.g.

However, the currently used lastName firstName is very uncommon, or do I miss the point here?

author-names

Picture shows our captured data vs. the original data from Crossref for http://api.crossref.org/works/10.2307/2757850

lgalke commented 6 years ago

Alright, I can check when the data is present and display it accordingly. Would you prefer <firstname> <lastname> over <lastname>, <firstname> ?

In any case I would need to default to <namestring>, whenever there is no structure.

zuphilip commented 6 years ago

For inputing lastName, firstName is more accurate and allows to split the name string into parts. However, we should according to the OpenCitation model save this either as two parts or in the form firstName lastName.

lgalke commented 6 years ago

Just to remember later:

For editing:

  1. When input string contains ,:
    • Assume string before , as lastname, the remainder as firstname
    • Store both structured (firstname and lastname) and unstructured variant (namestring) for safety
  2. When displaying prefer structured <lastname>, <firstname> format, if possible else fallback to nameString
lgalke commented 6 years ago

252

lgalke commented 6 years ago

What if some organization name contains a , Guess we wont get around putting separate fields into the form.

lgalke commented 6 years ago

190d0fc