PubMan Func Spec Import/commons
CoNE[edit]
If the stylesheet parameter CoNE is set to true, the template misc:make_person-person invokes a alghorithm to enrich the person's data with informations from CoNE.
If the stylesheet parameter misc:use-CoNE-organizations-only is set to true, all person's organizations from the input document are replaced by organizations retrieved from CoNE
For retrieving matching CoNE records, the stylesheet perfoms some CoNE queries in descending order of accuracy:
- search CoNE by a persons CoNE ID (person:person/dc:identifier xsi:type="eterms:CONE")
- search CoNE by all given IDs
- search CoNE by family name, given name and organizations
- search CoNE by family name and given name.
Results are taken from the first query that have results which refer only to one single person. If the results of all queries refer to multiple persons, the CoNE enrichment is skipped.
CoNE records refer to the same person,
- if the persons CoNE IDs (rdf:RDF/rdf:Description/@rdf:about) are equal or
- if persons given names (rdf:RDF/rdf:Description/foaf:givenname), surnames (rdf:RDF/rdf:Description/foaf:family_name) and first organizations ID (rdf:RDF/rdf:Description/eterms:position[1]/rdf:Description[1]/dc:identifier[1]) or first organizations name (rdf:RDF//rdf:Description/eterms:position[1]/rdf:Description[1]/eprints:affiliatedInstitution[1]) are equal
| CoNE element | description | EScidoc/Pubman element | EScidoc/Pubman label | comment |
|---|---|---|---|---|
| cone | person:person | Person | This function enriches person:person records with informations retrieved from CoNE.
In general, original informations from person:person are not replaced, but additional informations from CoNE may be added. Affilations/organizations are handled in dependence of the stylesheet's parameter misc:use-CoNE-organizations-only
For more information about CoNE records see http://pubman.mpdl.mpg.de/cone/jquery/explain. | |
| cone/rdf:RDF/rdf:Description/@rdf:about | person:person/dc:identifier[xsi:type="eterms:CONE"] | Identifier | ||
| cone/rdf:RDF/rdf:Description/dc:identifier | person:person/dc:identifier | Identifier | ||
| cone/rdf:RDF/rdf:Description/dc:title | person:person/eterms:complete-name | Complete Name | Since eterms:complete-name must not be empty, this enrichment will never happen. | |
| cone/rdf:RDF/rdf:Description/dcterms:alternative | person:person/eterms:alternative-name | Alternative Name | ||
| cone/rdf:RDF/rdf:Description/eterms:degree | person:person/eterms:person-title | Title | ||
| cone/rdf:RDF/rdf:Description/eterms:position | person:person/organization:organization | Organization | ||
| cone/rdf:RDF/rdf:Description/eterms:position/ rdf:Description/dc:identifier | person:person/organization:organization/ dc:identifier | Identifier | ||
| cone/rdf:RDF/rdf:Description/eterms:position/ rdf:Description/eprints:affiliatedInstitution | person:person/organization:organization/ dc:title | Title | ||
| cone/rdf:RDF/rdf:Description/foaf:family_name | person:person/eterms:family-name | Family name | Since eterms:family-name must not be empty, this enrichment will never happen. | |
| cone/rdf:RDF/rdf:Description/foaf:givenname | person:person/eterms:given-name | Given name |
language codes[edit]
Pubman generally works with ISO 639-3 language codes. If a metadata formats needs or delivers ISO 639-2, the functions misc:iso-639-2_to_iso-639-3() and misc:iso-639-2_to_iso-639-3() are used to convert between the two standards. Essentially, the functions treat the different language codes, and return otherwise the ISO 639-2 value. Differences between ISO 639-2 and ISO 639-3 are listed in the table below. Language codes in ISO 639-3 that are not part of ISO 639-2 are not handled. Source: Wikipedia:List_of_ISO_639-2_codes
| ISO 639-2 code | n/a | ISO 639-3 code | n/a | comment |
|---|---|---|---|---|
| alb | sqi | |||
| arm | hye | |||
| baq | eus | |||
| bur | mya | |||
| chi | zho | |||
| cze | ces | |||
| dut | nld | |||
| fre | fra | |||
| geo | kat | |||
| ger | deu | |||
| gre | ell | |||
| ice | isl | |||
| mac | mkd | |||
| mao | mri | |||
| may | msa | |||
| per | fas | |||
| rum | ron | |||
| slo | slk | |||
| tib | bod | |||
| wel | cym |
Author Decoder[edit]
ESciDoc/Pubman provides a function called AuthorDecoder to parse complex author strings such as »Jang-Yen Wu, Stephen W Schaffer and Junichi Azuma«. This function takes a string and returns an XML tree with the results. The function has to be invoked explicitly.
| Author Decoder element | description | EScidoc/Pubman element | EScidoc/Pubman label | comment |
|---|---|---|---|---|
| Author/givenname | person:person/eterms:given-name | Given name | ||
| Author/prefix | person:person/eterms:complete-name | Complete Name | ||
| Author/familyname | ||||
| Author/givenname | ||||
| Author/prefix | person:person/eterms:family-name | Family name | ||
| Author/familyname | ||||
| Author/title | person:person/eterms:person-title | Title |
This page was automatically created from mapping_commons.xsl. It should not be changed. Please provide comments on the talk page.