ZENODO
Zenodo puts only 4 bibliographic fields in metadata of each page!Then the import with Zotero (with metadata translator) is quite bad...
example:
https://zenodo.org/record/376087
This article was published with an input of 20 zenodo fields
(+2 : zenodo automatically add DOI field and 'zenodo id' field).
You can export in 7 formats:
- bibTeX
- CSL
- DataCite
- DublinCore
- JSON
- MarcXML
- Mendeley
bibTeX
@misc{frelat_joel_2011_376087, author = {Frelat, Joël}, title = {{Méthodes d éléments finis en calcul de structures élastiques}}, month = apr, year = 2011, note = {{Licence CC-BY-NC-ND. Ce volume (cet ISBN) est une 3ième édition. Collection -- Intégrations des savoirs et savoir faire -- dirigée par Stéphane MOTTIN. Lien: http://www.sudoc.fr/155436619 (voir SUDOC pour trouver cet ouvrage en bibliothèque). Ce PDF contient des metadata bibliographiques directement utilisables par exemple par Jabref (logiciel open source pour bibTeX). Ce PDF est structuré et balisé (voir en dessous de preview ci-dessous en haut à gauche). Le sommaire détaillé avec structure sur 2 niveaux est indiqué dans le champs résumé dans le but du (Linked Open DATA) et des citations croisées internes à l ouvrage.}}, doi = {10.5281/zenodo.376087}, url = {https://doi.org/10.5281/zenodo.376087} }
only 7 fields!!!
very bad.
CSL Citation Style Language JSON Export
only 13 fields
no contributors
no licence (i put in the "note" field")...
DataCite XML Export
Zenodo gives a DataCite DOI then he must provide clean datacite METADATA to DataCite.
with XML tree view:
It's a clean XML DataCite 3.1
<?xml version='1.0' encoding='utf-8'?>
<resource
xmlns:xsi= "http://www.w3.org/2001/XMLSchema-instance"
xmlns="http://datacite.org/schema/kernel-3"
xsi:schemaLocation="http://datacite.org/schema/kernel-3 http://schema.datacite.org/meta/kernel-3/metadata.xsd">
<!--
Revision history
2010-08-26 Complete revision according to new common specification by the metadata work group after review. AJH, DTIC
2010-11-17 Revised to current state of kernel review, FZ, TIB
2011-01-17 Complete revsion after community review. FZ, TIB
2011-03-17 Release of v2.1: added a namespace; mandatory properties got minLength; changes in the definitions of relationTypes
IsDocumentedBy/Documents and isCompiledBy/Compiles; changes type of property "Date" from xs:date to xs:string. FZ, TIB
2011-06-27 v2.2: namespace: kernel-2.2, additions to controlled lists "resourceType", "contributorType", "relatedIdentifierType", and "descriptionType". Removal of intermediate include-files.
2013-05 v3.0: namespace: kernel-3.0; delete LastMetadataUpdate & MetadateVersionNumber; additions to controlled lists "contributorType", "dateType", "descriptionType", "relationType", "relatedIdentifierType" & "resourceType"; deletion of "StartDate" & "EndDate" from list "dateType" and "Film" from "resourceType"; allow arbitrary order of elements; allow optional wrapper elements to be empty; include xml:lang attribute for title, subject & description; include attribute schemeURI for nameIdentifier of creator, contributor & subject; added new attributes "relatedMetadataScheme", "schemeURI" & "schemeType" to relatedIdentifier; included new property "geoLocation"
2014-08-20 v3.1: additions to controlled lists "relationType", contributorType" and "relatedIdentifierType"; introduction of new child element "affiliation" to "creator" and "contributor"
-->
only one field is empty:
no "CC-BY-NC-ND"
DublinCore (and OAI-PMH)
It's an XML with
http://www.openarchives.org/OAI/2.0/oai_dc.xsd"
<?xml version='1.0' encoding='utf-8'?>
<oai_dc:dc xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/ http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
The field "notes " is empty.
It's for OAI-PMH Open Archives Initiative Protocol for Metadata Harvesting
http://www.openarchives.org/pmh/
The Open Archives Initiative Protocol for Metadata Harvesting (OAI-PMH) is a low-barrier mechanism for repository interoperability. Data Providers are repositories that expose structured metadata via OAI-PMH. Service Providers then make OAI-PMH service requests to harvest that metadata. OAI-PMH is a set of six verbs or services that are invoked within HTTP.
and DublinCore
http://dublincore.org/documents/2012/06/14/dcmi-terms/?v=elements
JSON
It's the same METADATA JSON uploaded
1/ with unicode encoding /u (for example for "é" -> \u00e9)
2/ with a beautify/format transform of JSON
3-a/ with at the beginning
{"created": "2017-03-09T10:05:09.248886+00:00",
"doi": "10.5281/zenodo.376087",
"id": 376087,
"links": {
"badge": "https://zenodo.org/badge/doi/10.5281/zenodo.376087.svg",
"doi": "https://doi.org/10.5281/zenodo.376087",
"html": "https://zenodo.org/record/376087"
},
3-b/ and at the end
owners": [
2222
],
"revision": 0,
"updated": "2017-03-09T10:05:09.248893+00:00"
MarcXML
very good (all fields) but it's an old marc format (good for librarians)
and XML format
<record xmlns="http://www.loc.gov/MARC21/slim">
Mendeley
it's not an export but just a link to export
with only 3 METADATA {title, author and DOI}
and a web service of automatic upload of PDFs.
If you have already the reference in Mendeley, it could be OK.
(I import my bibTeX references (JabRef) with Desktop Mendeley app and sync but problem, many fields 'notes' 'editor' = 0...).
Conclusion
- Very good for JSON, DataCite XML and Marc21 XML.
- 'notes' lacks with the export DublinCore-OAI-PMH.
- Put your BibTeX reference in your PDF.
No comments:
Post a Comment