Difference between revisions of "PubMan Func Spec Import/commons"

From MPDLMediaWiki
Jump to navigation Jump to search
(aktualisiert)
(aktualisiert)
 
Line 1: Line 1:
=== CoNE ===
=== CoNE ===
If the stylesheet parameter ''CoNE'' is set to true,  
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.  
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:
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 a persons CoNE ID (''person:person/dc:identifier xsi:type="eterms:CONE"'')
Line 20: Line 23:
{| style="width:100%" class="wikitable" border="1"
{| style="width:100%" class="wikitable" border="1"
|- style="vertical-align:top;"
|- style="vertical-align:top;"
! foreign
! CoNE element
! field description
! description
! EScidoc/Pubman
! EScidoc/Pubman element
! field description
! EScidoc/Pubman label
! comment
! comment
|- style="vertical-align:top;"
|- style="vertical-align:top;"
Line 29: Line 32:
|  
|  
| person:person
| person:person
|  
| Person
| ''person:person'' records are enriched with informations retrieved from CoNE.
| This function enriches ''person:person'' records with informations retrieved from CoNE.
This means that original informations from person:person are not replaced, but additional informations from CoNE may be added.
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''
 
* if ''$misc:use-CoNE-organizations-only'' is set to ''false()'', organizations retrieved from CoNE are added
* if ''$misc:use-CoNE-organizations-only'' is set to ''true()'', organizations from the source are replaced by organizations retrieved from CoNE.
 
For more information about CoNE records see [http://pubman.mpdl.mpg.de/cone/jquery/explain http://pubman.mpdl.mpg.de/cone/jquery/explain].
For more information about CoNE records see [http://pubman.mpdl.mpg.de/cone/jquery/explain http://pubman.mpdl.mpg.de/cone/jquery/explain].
|- style="vertical-align:top;"
|- style="vertical-align:top;"
Line 37: Line 45:
|  
|  
| person:person/dc:identifier[xsi:type="eterms:CONE"]
| person:person/dc:identifier[xsi:type="eterms:CONE"]
|  
| Identifier
|  
|  
|- style="vertical-align:top;"
|- style="vertical-align:top;"
Line 43: Line 51:
|  
|  
| person:person/dc:identifier
| person:person/dc:identifier
|  
| Identifier
|  
|  
|- style="vertical-align:top;"
|- style="vertical-align:top;"
Line 49: Line 57:
|  
|  
| person:person/eterms:complete-name
| person:person/eterms:complete-name
|  
| Complete Name
| Since eterms:complete-name must not be empty, this enrichment will never happen.
| Since eterms:complete-name must not be empty, this enrichment will never happen.
|- style="vertical-align:top;"
|- style="vertical-align:top;"
Line 55: Line 63:
|  
|  
| person:person/eterms:alternative-name
| person:person/eterms:alternative-name
|  
| Alternative Name
|  
|  
|- style="vertical-align:top;"
|- style="vertical-align:top;"
Line 61: Line 69:
|  
|  
| person:person/eterms:person-title
| person:person/eterms:person-title
|  
| Title
|  
|  
|- style="vertical-align:top;"
|- style="vertical-align:top;"
Line 67: Line 75:
|  
|  
| person:person/organization:organization
| person:person/organization:organization
|  
| Organization
|  
|  
|- style="vertical-align:top;"
|- style="vertical-align:top;"
Line 73: Line 81:
|  
|  
| person:person/organization:organization/
dc:identifier
| person:person/organization:organization/
dc:identifier
|  
| Identifier
|  
|  
|- style="vertical-align:top;"
|- style="vertical-align:top;"
Line 79: Line 87:
|  
|  
| person:person/organization:organization/
dc:title
| person:person/organization:organization/
dc:title
|  
| Title
|  
|  
|- style="vertical-align:top;"
|- style="vertical-align:top;"
Line 85: Line 93:
|  
|  
| person:person/eterms:family-name
| person:person/eterms:family-name
|  
| Family name
| Since eterms:family-name must not be empty, this enrichment will never happen.
| Since eterms:family-name must not be empty, this enrichment will never happen.
|- style="vertical-align:top;"
|- style="vertical-align:top;"
Line 91: Line 99:
|  
|  
| person:person/eterms:given-name
| person:person/eterms:given-name
|  
| Given name
|  
|  
|}
|}
Line 103: Line 111:
{| style="width:100%" class="wikitable" border="1"
{| style="width:100%" class="wikitable" border="1"
|- style="vertical-align:top;"
|- style="vertical-align:top;"
! foreign
! ISO 639-2 code
! field description
! n/a
! EScidoc/Pubman
! ISO 639-3 code
! field description
! n/a
! comment
! comment
|- style="vertical-align:top;"
|- style="vertical-align:top;"
Line 237: Line 245:
{| style="width:100%" class="wikitable" border="1"
{| style="width:100%" class="wikitable" border="1"
|- style="vertical-align:top;"
|- style="vertical-align:top;"
! foreign
! Author Decoder element
! field description
! description
! EScidoc/Pubman
! EScidoc/Pubman element
! field description
! EScidoc/Pubman label
! comment
! comment
|- style="vertical-align:top;"
|- style="vertical-align:top;"
Line 246: Line 254:
|  
|  
| person:person/eterms:given-name
| person:person/eterms:given-name
|  
| Given name
|  
|  
|- style="vertical-align:top;"
|- style="vertical-align:top;"
Line 252: Line 260:
|  
|  
| rowspan="3" | person:person/eterms:complete-name
| rowspan="3" | person:person/eterms:complete-name
| rowspan="3" |  
| rowspan="3" | Complete Name
| rowspan="3" |  
| rowspan="3" |  
|- style="vertical-align:top;"
|- style="vertical-align:top;"
Line 264: Line 272:
|  
|  
| rowspan="2" | person:person/eterms:family-name
| rowspan="2" | person:person/eterms:family-name
| rowspan="2" |  
| rowspan="2" | Family name
| rowspan="2" |  
| rowspan="2" |  
|- style="vertical-align:top;"
|- style="vertical-align:top;"
Line 273: Line 281:
|  
|  
| person:person/eterms:person-title
| person:person/eterms:person-title
|  
| Title
|  
|  
|}
|}

Latest revision as of 20:31, 29 July 2013

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:

  1. search CoNE by a persons CoNE ID (person:person/dc:identifier xsi:type="eterms:CONE")
  2. search CoNE by all given IDs
  3. search CoNE by family name, given name and organizations
  4. 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,

  1. if the persons CoNE IDs (rdf:RDF/rdf:Description/@rdf:about) are equal or
  2. 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

  • if $misc:use-CoNE-organizations-only is set to false(), organizations retrieved from CoNE are added
  • if $misc:use-CoNE-organizations-only is set to true(), organizations from the source are replaced by organizations retrieved from CoNE.

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.