Translators are at the core of one of Zotero’s most popular features: its ability to import and export item metadata from and to a variety of formats. Below we describe how translators work, and how you can write your own.
Zotero translators are stored as individual JavaScript files in the “translators” subdirectory of the Zotero data directory.
https://www.zotero.org/support/zotero_data#locating_your_zotero_library
for example:
/Users/<username>/Library/Application Support/Firefox/Profiles/<randomstring>/zotero/Translators |
Each translator contains a JSON metadata header, followed by the translator’s JavaScript code.
https://www.zotero.org/support/dev/translators
https://github.com/zotero/translators
(à chaque mise à jour, cette liste de GitHub est mise dans le dossier “translators”
Data formats
list pf all import/export
https://www.zotero.org/support/dev/data_formatsThe main problem is the quality of the js code for the mapping.
https://www.zotero.org/support/kb/field_mappings
For example, the "Hal archive ouverte.js" does not import the Id of authors (and affiliation (in Hal it's an internal number; no Id of affiliation))
export file "TEI" in Hal (the other formats have no Id).
see ORCID
ORCID identifier
This element is used to record the ORCID iD of users. The ORCID iD is formed of a 16-digit number
Within <orcid-identifier> the iD will be recorded in the following child elements:
<uri> the full path to the ORCID record
<path> just the 16 digit ORCID identifier
<host> the domain of the uri
<orcid-identifier>
<uri>http://orcid.org/0000-0001-5727-2427</uri>
<path>0000-0001-5727-2427</path>
<host>orcid.org</host>
</orcid-identifier>
The affiliations section of an ORCID record in XML is recorded under <orcid-activities>. This area is separate from the <orcid-bio> fields.
XML for Affiliations for more information: http://members.orcid.org/api/xml-affiliations
Funding information
The Funding section of an ORCID record is recorded under <orcid-activities>. For information about adding funding via the API see XML for funding.
https://members.orcid.org/api/record-xml-structure
ORCID can be used in repository systems to clearly link authors – and all their name variants - with their research work, improving search and retrieval. Repository systems can also exchange data with the ORCID registry -for example, retreiving ORCID record information in order to populate author profiles and updating ORCID records with publication information each time repository deposit is made.
https://members.orcid.org/repositories
Import
https://www.zotero.org/support/getting_stuff_into_your_libraryZotero can import from various bibliographic formats:
- Zotero RDF, Bibliontology RDF
- MODS (Metadata Object Description Schema)
- BibTeX (rich format but lacks of standardization)
- CSL JSON
- Endnote XML (this is actually very similar to RIS in importing from Endnote, but may have some small advantages and is one of the few styles that will preserve italics across imports.)
- MAB2, MARC, MARCXML
- MEDLINE/nbib
- OVID Tagged
- PubMed XML
- RIS (this can be convenient for quick edits between export & import because of its simple structure)
- RefWorks Tagged (recommend for ReferenceWorks)
- Web of Science Tagged
- Refer/BibIX (discourage if any other option present)
- XML ContextObject
- Unqualified Dublin Core RDF
export via TEI.js
The tei-zotero-translator is a simple translator that seeks to bridge the gap between editing documents following the TEI Guidelines and maintaining the bibliographies with Zotero <http://www.zotero.org>.The translator exports items from the Zotero database to TEI biblStruct elements. It integrates with Zotero, such that it is possible to select TEI as a target export format. Initially, it has been developed to create bibliographies for papers written in TEI P5, but should as well be useful for other projects.
http://wiki.tei-c.org/index.php/TEIZoteroTranslator
Thanks for sharing this post. I'm very interested in this topic. here Check out this awesome useful online file converter that can come handy for use.
ReplyDelete