Review the affiliation mechanism
- Since version 0.8.14, the affiliation is based on the
short namedefined by
inspirehepfor each institute (
- The mechanism look for authors with a given affiliation using the institute
short name. Here, we assumed that the
short nameis used both by
cds.cern.chto define author's affiliation.
- Several exceptions have been found in
- as well as in
- In addition, we learned that
cds.cern.chwill change to use a CERN identifier related to their own database defining institutes.
- Finally, we have the case in which author come from different institute, i.e LPC CAEN, ENSICAE but belong to the same entity.
- In the author MARC fields, author's affiliation are defined by the field
(100)700__u. An other field exists,
(100)700__vwhich is left free to the cataloguer, but contains the full name (address) of the institute, in most of the case.
Add a new database table
affiliationscontaining two columns
full name. The first one would match the content of the field
700__uwhile the second one would match
700__v. One or the other can be undefined but not both.
For each authors build the affiliation as
Build a regular expression with the content of the
affiliationstable. Something like:
Scan authors list to find a match.
In order to facilitate the construction of the affiliations table, a wizard have to be developed. It will relies on:
- a list of authors belonging to the lab
The wizard will propose a list of
(full_name, long name)interrogating
inspirehep.net. Meaning pairs will selected by the user.
The wizard can be call at any time to add more values in the
In principle, this approach is very general and should cover all cases.