You can batch import publication metadata to the Research Collection by uploading a BibTex or a RIS file.
The table below shows how the individual RIS and BibTex fields are imported and mapped into the Research Collection. Only fields mentioned in this table can be imported via the batch import process. Other fields not available in RIS or BibTex can be added later to the imported items (see Edit publications).
|RIS field||BibTex field||Research Collection field||Example content||required?|
|A1 / AU||author||Author or Creator||Smith, John; Doe, Jane||mandatory (depending on publication type)|
|A2 / ED||editor||Editor||Miller, Max||mandatory (depending on publication type)|
|T1 /TI / ST||title||Title||This would be the title||mandatory|
|DA / PY / Y1||year||Publication Date||2006 or 2006/05 or 2006/05/31||mandatory (at least year)|
978-3-86680-192-9 or 3-86680-192-0
|JF / T2||journal / series||Journal or Series Title||Human Nature||mandatory (depending on publication type)|
|booktitle||Book Title||This could be the Book Title||mandatory (depending on publication type)|
|IS / M1||number||Issue||23||optional|
|EP||- no value -||End Page||30||optional|
|pages||Start Page / End Page||14-30||optional|
|LA||language||Language||en or de or fr or it...||optional|
|AB / N2||abstract||Abstract||continuous text||optional|
|ET||edition||Edition / Version||2nd Edition|
3. rev. edition
We recommend to use the following formats when exporting publication lists from a reference management tool (the recommendation is based on the number of relevant fields exported by the tool):
- EndNote: BibTex (exported with "RefMan")
- Mendeley: BibTex
- Zotero: RIS or BibTex
Select the publications you want to import in your reference management software and export them as a RIS or BibTex file (see format recommendations above) and save the file.
Login to the Research Collection with your ETH user account.
In the left hand navigation, under the Publish heading, click on RIS/BibTex import.
Select your RIS or BibTex file from your computer and select the correct format from the dropdown.
Select an organisational unit. The selected unit will be assigned to all publications that are part of the imported file.
Click the Upload button.
The next page lists all publications that could be detected within your file. For each publication, information is displayed about potential duplicates and, if applicable, invalid metadata according to the following statuses:
|Status||Example||Explanation / How to proceed|
|no duplicate||This is a valid record without any potential duplicates. It has been pre-selected for import (checkbox is active). If you do not want to import it, please de-activate the checkbox.|
One ore more potential duplicates were detected for this record. You can check the potential duplicate by clicking on the Handle-ID displayed (e.g. 20.500.11859/13938).
If you determine that the potential duplicate is not a real duplicate, you can still select your record for import by activating the checkbox. If it is a real duplicate, please do not select this record for import.
|invalid metadata||This is a record with invalid or missing mandatory metadata, it cannot be selected for import. You will need to correct the record in the original RIS or BibTex file in order to be able to import it. See below what the individual error messages mean.|
By clicking the Import metadata button on the bottom of the page, all selected publiations are imported and your batch import is finished.
They will appear on your Submissions page (Publish → New Submission → Submissions under Review) and will be checked and edited by the ETH Library.
Instructions on how to add additional metadata and/or full text files to your publications can be found on the Edit publications pages.
Possible error messages
|Mandatory field ... is missing||You have not supplied any content in a field that is mandatory when submitting publications to the Research Collection.||Please add the field in your RIS or BibTex file. Mandatory fields are specified in the Mapping table above.|
|A value of field […] is not available in the value pairs||The content of the field mentioned has not been provided in the expected format, for example when the language field is not filled in with a correct language code.||Please correct the field content using the examples from the mapping table above.|