The metadata exchanged via ORCID’s BibTeX import/export features is limited in comparison to that which is exchanged through the normal machine-to-machine connections built by our member organizations. We therefore recommend that you only use BibTeX to import/export works if there is no other option.
These are some known issues when using BibTeX files with your ORCID record:
Non-standard BibTeX: Not every system uses the same BibTeX standard; some systems also accept modified BibTeX. If you experience any import issues, try isolating the problematic citation by splitting the file in half and importing again. If you are unable to find the error, contact us and include the BibTeX file and the system you used to generate it.
Limited grouping: Works are grouped in your ORCID record based on unique identifiers. Since BibTeX only supports a limited number of identifiers (DOI, ISBN, ISSN), if your imported work does not include an identifier, it may not group on your record.
Encoding issues: Our BibTeX tool imports data as it is encoded in the BibTeX. Special characters may not import properly. Please contact us if you experience any issues, as we may need to update our parser.
We export existing BibTeX and metadata: The ORCID tool exports the existing BibTeX citation for a work; if one doesn’t exist, it generates BibTeX from the work’s metadata. If the original BibTeX added by you or a trusted party had errors, they will be reproduced in the export.
Encoding issues: Our BibTeX tool exports data in the same character encoding as was added to our Registry. These may not be ready properly by the systems you import your BibTeX citations into.
Limited metadata: BibTeX does not support all metadata available on the ORCID record, such as the data’s source, multiple URLs, and additional identifiers, so this information will not be exported.
Help make our BibTeX parser better
ORCID is an open-source project that relies strongly on community support. We welcome your contributions to the improvement of our BibTeX parser – submit them in our Github repository.
Article is closed for comments.