Difference between revisions of "PubMan Func Spec Dublin Core Mapping"

From MPDLMediaWiki
Jump to navigation Jump to search
(removed genre mapping, as the types are not "allowed" within simple DC)
 
(22 intermediate revisions by 4 users not shown)
Line 32: Line 32:
! eSciDoc !! DC !! Comment/Condition(s)
! eSciDoc !! DC !! Comment/Condition(s)
|-
|-
| Genre || dc:type || -
| Genre || dc:type || in addition create 2nd dc:type with DCMI Type = Text (to be discussed with Traugott Koch or KIM --[[User:Makarenko|Makarenko]] 15:07, 4 June 2009 (UTC): DCMI Type has own namespace, can it be used in the mapping?
|-
|-
|-
|-
Line 87: Line 87:
|-
|-
|-
|-
| Identifier.Id || dc:identifier || -
| Identifier.Id || dc:identifier || please write value of Identifier.IdType: value of Identifier.Id, e.g. ISBN: 3-454-567-X; to be discussed with Traugott Koch or KIM
|-
|-
|-
|-
| Identifier.IdType || - || Unfortunately, some ID types are hard to recognize without their explicit Id.Type information (e.g. PMID), but qualifiers are only supported in Qualified Dublin Core.
| Identifier.IdType || dc:identifier || see above
|-
|-
|-
|-
Line 96: Line 96:
|-
|-
|-
|-
| PublishingInfo.Place || - || Could be used in a citation - maybe as OpenURL? - in dc:identifier (similar to Source identifiers, see below, see also http://dublincore.org/documents/dc-citation-guidelines/).
| PublishingInfo.Place || dc:source || will be included into the bibliographic citation (dc:source), the topic "dc:source" is in general to be discussed with Traugott/KIM --[[User:Makarenko|Makarenko]] 15:07, 4 June 2009 (UTC): Not clear, it means that citationmanager should be called for citation creation?
|-
|-
|-
|-
| PublishingInfo.Edition || dc:relation || Since the qualifier hasVersion cannot be used in Simple Dublin Core, it might be useful to add the prefix "Edition: ".
| PublishingInfo.Edition || dc:source || will be included into the bibliographic citation (dc:source)
|-
|-
|-
|-
Line 108: Line 108:
|-
|-
|-
|-
| ReviewMethod || - || -
| ReviewMethod || - ||  
|-
|-
|-
|-
Line 114: Line 114:
|-
|-
|-
|-
| Source.Title || dc:identifier || together with other Source information (see below). DCMI suggests dcterms:bibliographicCitation for this kind of data, which is a Qualified Dublin Core refinement of dc:identifier. Additionally, Source information may be stored in dc:identifier in OpenURL format. See http://dublincore.org/documents/dc-citation-guidelines/
| Source.Title || dc:source || together with other Source information (see below). DCMI suggests dcterms:bibliographicCitation for this kind of data, which is a Qualified Dublin Core refinement of dc:identifier. Additionally, Source information may be stored in dc:identifier in OpenURL format. See http://dublincore.org/documents/dc-citation-guidelines/ --[[User:Makarenko|Makarenko]] 15:21, 4 June 2009 (UTC): dcterms has own namespace different from dc, can it be used in the mapping?
|-
|-
|-
|-
Line 126: Line 126:
|-
|-
|-
|-
| Source.Creator.Person.CompleteName || dc:identifier || together with other Source data (see above). Map only if Source.Genre = Book, Proceedings, Issue, or Other.
| Source.Creator.Person.CompleteName || dc:source || together with other Source data (see above). Map only if Source.Genre = Book, Proceedings, Issue, or Other.
|-
|-
|-
|-
| Source.Creator.Person.GivenName || dc:identifier || if there is no Source.Creator.Person.CompleteName. See above.
| Source.Creator.Person.GivenName || dc:source || if there is no Source.Creator.Person.CompleteName. See above.
|-
|-
|-
|-
| Source.Creator.Person.FamilyName || dc:identifier || if there is no Source.Creator.Person.CompleteName. See above.
| Source.Creator.Person.FamilyName || dc:source || if there is no Source.Creator.Person.CompleteName. See above.
|-
|-
|-
|-
Line 147: Line 147:
|-
|-
|-
|-
| Source.Creator.Organization.Name || dc:identifier || together with other Source data (see above). Map only if Source.Genre = Book, Proceedings, Issue, or Other.
| Source.Creator.Organization.Name || dc:source || together with other Source data (see above). Map only if Source.Genre = Book, Proceedings, Issue, or Other.
|-
|-
|-
|-
Line 156: Line 156:
|-
|-
|-
|-
| Source.Volume || dc:identifier || together with other Source data (see above).
| Source.Volume || dc:source || together with other Source data (see above).
|-
|-
|-
|-
| Source.Issue || dc:identifier || together with other Source data (see above).
| Source.Issue || dc:source || together with other Source data (see above).
|-
|-
|-
|-
| Source.StartPage || dc:identifier || together with other Source data (see above).
| Source.StartPage || dc:format ||  
|-
|-
|-
|-
| Source.EndPage || dc:identifier || together with other Source data (see above).
| Source.EndPage || dc:format ||  
|-
|-
|-
|-
Line 171: Line 171:
|-
|-
|-
|-
| Source.PublishingInfo.Publisher || dc:identifier || together with other Source data (see above). If Source.Genre = Journal or Series, ignore Source.PublishingInfo.Publisher instead.
| Source.PublishingInfo.Publisher || dc:source || together with other Source data (see above). If Source.Genre = Journal or Series, ignore Source.PublishingInfo.Publisher instead.
|-
|-
|-
|-
| Source.PublishingInfo.Place || dc:identifier || together with other Source data (see above). If Source.Genre = Journal or Series, ignore Source.PublishingInfo.Place instead.
| Source.PublishingInfo.Place || dc:source || together with other Source data (see above). If Source.Genre = Journal or Series, ignore Source.PublishingInfo.Place instead.
|-
|-
|-
|-
| Source.PublishingInfo.Edition || dc:identifier || together with other Source data (see above). If Source.Genre = Journal or Series, ignore Source.PublishingInfo.Edition instead.
| Source.PublishingInfo.Edition || dc:source || together with other Source data (see above). If Source.Genre = Journal or Series, ignore Source.PublishingInfo.Edition instead.
|-
|-
|-
|-
Line 189: Line 189:
|-
|-
|-
|-
| Event || dc:relation || export all Event.* fields to a single dc:relation field and separate the values with a comma. (In Qualified Dublin Core, the refinement would be dcterms:isPartOf.)
| Event || dc:relation || export all Event.* fields to a single dc:relation field and separate the values with a comma. (In Qualified Dublin Core, the refinement would be dcterms:isPartOf.) Event.Title, Event.Place, Event.StartDate - Event.EndDate.
|-
|-
|-
|-
| TotalNumberOfPages || dc:format || add suffix " pages".
| TotalNumberOfPages || dc:format ||  
|-
|-
|-
|-
| Degree || - || -
| Degree || dc:type || -
|-
|-
|-
|-
Line 201: Line 201:
|-
|-
|-
|-
| Subject || dc:subject || Map each keyword to a dc:subject field of its own. Dublin Core also allows using a single dc:subject field and delimiters to separate the keywords, but it will probably be easier to use multiple fields once the changes to the Subject field ([[Talk:PubMan_Metadata_Sets#Subject_once]]) are implemented.
| Subject || dc:subject || -
|-
|-
|-
|-
Line 207: Line 207:
|-
|-
|}
|}
===Problems===
* Usage of the dcterms and dcmitype namespaces (not dc namespace)
:Sorry, I don't see the problem here. http://dublincore.org/documents/dces/ says: "Recommended best practice is to use a controlled vocabulary such as the DCMI Type Vocabulary [DCMITYPE].", so why shouldn't they be used? --[[User:Martin de la Iglesia|Martin de la Iglesia]] 09:27, 8 June 2009 (UTC)
* Please, revise dc:source creation. It is not clear, whether the mapping assumes creation of the separate dc:source elements per each mapped item above or the items should be somehow concatenated and put in one dc:source.
:By "together with", we mean the items are concatenated and written into a single dc:source field. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 09:23, 8 June 2009 (UTC)
* Not clear how to handle source and details metadata to be included into dcterms:bibliographicCitation
:After a long discussion, we decided not to use this field and to put the metadata into dc:source instead. --[[User:Martin de la Iglesia|Martin de la Iglesia]] 09:31, 8 June 2009 (UTC)


=Links, further reading=
=Links, further reading=
Line 215: Line 222:
*DCMI Type Vocabulary - http://dublincore.org/documents/dcmi-type-vocabulary/
*DCMI Type Vocabulary - http://dublincore.org/documents/dcmi-type-vocabulary/


[[Category:PubMan|DC Mapping ]]
[[Category:PubMan_Functional_Specification|DC Mapping ]]
[[Category:ESciDoc Mappings|DC Mapping]]
[[Category:ESciDoc Mappings|DC Mapping]]
[[Category:Functional specification]]

Latest revision as of 09:48, 4 August 2009

Dublin Core[edit]

This mapping uses Simple/unqualified Dublin Core.

Dublin Core elements[edit]

The following elements are specified in the Dublin Core Metadata Element Set (DCMES) version 1.1 (http://dublincore.org/documents/dces/). The order of the elements is arbitrary (alphabetical in this list), but a meaningful order can be implemented locally.

  • contributor
  • coverage
  • creator
  • date
  • description
  • format
  • identifier
  • language
  • publisher
  • relation
  • rights
  • source
  • subject
  • title
  • type

See also Dublin Core Metadata Element Set.

eSciDoc Metadata Set for Publication[edit]

PubMan Metadata Sets#eSciDoc Metadata Set for Publication

Mapping eSciDoc Metadata Set for Publications to Dublin Core (for DC Export)[edit]

Mapping of eSciDoc Standard Entries[edit]

eSciDoc DC Comment/Condition(s)
Genre dc:type in addition create 2nd dc:type with DCMI Type = Text (to be discussed with Traugott Koch or KIM --Makarenko 15:07, 4 June 2009 (UTC): DCMI Type has own namespace, can it be used in the mapping?
Creator.CreatorType - -
Creator.CreatorRole - determines whether the Creator is mapped to dc:contributor or to dc:creator (see below).
Creator.Person.CompleteName dc:creator if Creator.CreatorRole = Author. Otherwise, if Creator.CreatorRole is Advisor, Contributor, Transcriber, Translator, or Honoree, map Creator.Person.CompleteName to dc:contributor. For other Creator.CreatorRoles, map Creator.Person.CompleteName to dc:creator if there is no Creator.CreatorRole = Author, or map to dc:contributor if there is already a Creator.CreatorRole = Author.
Creator.Person.GivenName dc:creator if there's no CompleteName. See above
Creator.Person.FamilyName dc:creator if there's no CompleteName. See above
Creator.Person.AlternativeName - -
Creator.Person.Title - -
Creator.Person.Organization.Name dc:contributor -
Creator.Person.Organization.Address - -
Creator.Person.Organization.Identifier - -
Creator.Person.Identifier - -
Creator.Organization.Name dc:creator if Creator.CreatorRole = Author. Otherwise, if Creator.CreatorRole is Advisor, Contributor, Transcriber, Translator, or Honoree, map Creator.Organization.Name to dc:contributor. For other Creator.CreatorRoles, map Creator.Organization.Name to dc:creator if there is no Creator.CreatorRole = Author, or map to dc:contributor if there is already a Creator.CreatorRole = Author.
Creator.Organization.Address - -
Creator.Organization.Identifier - -
Title dc:title -
Language dc:language ISO 639 is also proposed by DCMI, so no transformation is necessary.
AlternativeTitle dc:title It should be made clear by the order of the dc:title fields which is the main title and which is the alternative title (e.g. 1st dc:title = main title, 2nd dc:title = alternative title).
Identifier.Id dc:identifier please write value of Identifier.IdType: value of Identifier.Id, e.g. ISBN: 3-454-567-X; to be discussed with Traugott Koch or KIM
Identifier.IdType dc:identifier see above
PublishingInfo.Publisher dc:publisher -
PublishingInfo.Place dc:source will be included into the bibliographic citation (dc:source), the topic "dc:source" is in general to be discussed with Traugott/KIM --Makarenko 15:07, 4 June 2009 (UTC): Not clear, it means that citationmanager should be called for citation creation?
PublishingInfo.Edition dc:source will be included into the bibliographic citation (dc:source)
Date.Date dc:date ISO 8601 is also proposed by DCMI, so no transformation is necessary. Since no qualifiers are used to express the Date.DateType, only the first Date.Date according to PubMan_Func_Spec_OpenURL_Mapping is mapped to dc:date and all others are ignored.
Date.DateType - is used to determine which Date.Date is mapped to dc:date (see above).
ReviewMethod -
Source.Genre - -
Source.Title dc:source together with other Source information (see below). DCMI suggests dcterms:bibliographicCitation for this kind of data, which is a Qualified Dublin Core refinement of dc:identifier. Additionally, Source information may be stored in dc:identifier in OpenURL format. See http://dublincore.org/documents/dc-citation-guidelines/ --Makarenko 15:21, 4 June 2009 (UTC): dcterms has own namespace different from dc, can it be used in the mapping?
Source.AlternativeTitle - -
Source.Creator.CreatorType - -
Source.Creator.CreatorRole - -
Source.Creator.Person.CompleteName dc:source together with other Source data (see above). Map only if Source.Genre = Book, Proceedings, Issue, or Other.
Source.Creator.Person.GivenName dc:source if there is no Source.Creator.Person.CompleteName. See above.
Source.Creator.Person.FamilyName dc:source if there is no Source.Creator.Person.CompleteName. See above.
Source.Creator.Person.AlternativeName - -
Source.Creator.Person.Title - -
Source.Creator.Person.Organization - -
Source.Creator.Person.Identifier - -
Source.Creator.Organization.Name dc:source together with other Source data (see above). Map only if Source.Genre = Book, Proceedings, Issue, or Other.
Source.Creator.Organization.Address - -
Source.Creator.Organization.Identifier - -
Source.Volume dc:source together with other Source data (see above).
Source.Issue dc:source together with other Source data (see above).
Source.StartPage dc:format
Source.EndPage dc:format
Source.SequenceNumber - -
Source.PublishingInfo.Publisher dc:source together with other Source data (see above). If Source.Genre = Journal or Series, ignore Source.PublishingInfo.Publisher instead.
Source.PublishingInfo.Place dc:source together with other Source data (see above). If Source.Genre = Journal or Series, ignore Source.PublishingInfo.Place instead.
Source.PublishingInfo.Edition dc:source together with other Source data (see above). If Source.Genre = Journal or Series, ignore Source.PublishingInfo.Edition instead.
Source.Identifier.Id - -
Source.Identifier.IdType - -
2nd Source - -
Event dc:relation export all Event.* fields to a single dc:relation field and separate the values with a comma. (In Qualified Dublin Core, the refinement would be dcterms:isPartOf.) Event.Title, Event.Place, Event.StartDate - Event.EndDate.
TotalNumberOfPages dc:format
Degree dc:type -
Abstract dc:description -
Subject dc:subject -
TableOfContents dc:description -

Problems[edit]

  • Usage of the dcterms and dcmitype namespaces (not dc namespace)
Sorry, I don't see the problem here. http://dublincore.org/documents/dces/ says: "Recommended best practice is to use a controlled vocabulary such as the DCMI Type Vocabulary [DCMITYPE].", so why shouldn't they be used? --Martin de la Iglesia 09:27, 8 June 2009 (UTC)
  • Please, revise dc:source creation. It is not clear, whether the mapping assumes creation of the separate dc:source elements per each mapped item above or the items should be somehow concatenated and put in one dc:source.
By "together with", we mean the items are concatenated and written into a single dc:source field. --Martin de la Iglesia 09:23, 8 June 2009 (UTC)
  • Not clear how to handle source and details metadata to be included into dcterms:bibliographicCitation
After a long discussion, we decided not to use this field and to put the metadata into dc:source instead. --Martin de la Iglesia 09:31, 8 June 2009 (UTC)

Links, further reading[edit]

References[edit]

Enhanced Scientific Documentation

Dublin Core

Dublin Core Metadata Initiative

Kompetenzzentrum Interoperable Metadaten

Coordinated Universal Time

International Organization for Standardization

International Standard Book Number

Open Uniform Resource Locator

Retrieved from "https://colab.mpdl.mpg.de/mw010/index.php?title=PubMan_Func_Spec_Dublin_Core_Mapping&oldid=40791"