Skip to content

global: uniform the handling of names #2273

Open
@jacquerie

Description

@jacquerie

According to the schema names:

Should be of the form 'family names, first names'
(https://github.com/inspirehep/inspire-schemas/blob/1db9777634844724c522728521ab1f876b25ca8e/inspire_schemas/records/hep.yml#L328-L339)

Logic to deal with this, either by normalizing some input we get (legacy, forms, harvesting) or producing the output other services expect (ORCID, HAL) is scattered all over the codebase. Often it is wrong. For example:

{'full_name': 'Guerra, A.Del'}, # XXX: wrong.

It should be centralized, and we should probably something semi-smart like https://pypi.python.org/pypi/nameparser to handle the parsing for us, instead of directly monkeying with strings.

Metadata

Metadata

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions