Demo instance — all content is sample, fictional data.
TR
Help topics

Screens and settings

Import Columns

The columns of a bulk import file, which ones are required, how values are written and the rules that make a row invalid.

Permission needed
Bulk import (CSV, XLSX, JSON)
Changed in
1.9.9, 1.10.0

The first row of a bulk import file holds the column names. The file can contain only the columns below. An unknown column causes the whole file to be rejected. Upper and lower case in column names make no difference. Spaces and hyphens count as underscores, so a header "Title TR" is read as title_tr.

Columns

Column Required Contents
type Yes Record type. book, chapter, journal, article, proceedings, thesis, children, or the Turkish kitap, bölüm, dergi, makale, bildiri, tez, çocuk
source_id Recommended The record's ID in the old system
title_tr, title_en At least one Turkish and English title, between 2 and 500 characters
subtitle_tr, subtitle_en No Subtitles
abstract_tr, abstract_en No Abstracts, at most 5000 characters
keywords_tr, keywords_en No Keywords, separated by semicolons
language No Language of the work (tr, en …). If empty, the language of the first title is used
year No Four-digit publication year, between 1500 and next year
published_at No Publication date
contributors No Contributors, in the format given below
isbn No ISBN-10 or ISBN-13. The check digit is verified
doi No A DOI starting with 10. or a https://doi.org/… link
issn, eissn No ISSN and e-ISSN. For journal rows they are written to the journal profile; on other rows they are not read
categories No The slugs of the categories, separated by semicolons
publisher, rights_holder No Publisher and rights holder
access_status No open, metadata_only, embargoed, restricted, or the Turkish açık, yalnız üstveri, ambargolu, kısıtlı. If empty, metadata only
license No The code of a licence active in the system, for example CC-BY-4.0
embargo_until If embargoed The date the embargo ends
details No Type-specific fields, as a JSON object

The file must have the type column and one of the title_tr or title_en columns. If one of these is missing, the file is not read.

Writing the values

  • Dates are written as YYYY-MM-DD. DD.MM.YYYY and DD/MM/YYYY are read too.
  • In lists, values are separated by semicolons. If a value has no semicolon, a comma counts as the separator.
  • Categories are written with their Slug (URL) value, not with the category name.
  • Type-specific fields are given as a JSON object such as {"edition": "1", "pages": 240} and are checked with the rules of the record form.
  • On thesis rows, the level value in the type-specific fields is written as its code (ms, phd, art, medical, other) or its Turkish or English name, for example {"level": "Medical specialty"}. A "tezi" or "thesis" at the end of the name makes no difference.
  • On rows that are not journals, the issn and eissn columns are not read. These numbers belong to the article's journal or to the book's series and are not stored on the record. A file that repeats the journal's ISSN on every article row is therefore imported without problems.
  • In a CSV file the separator can be a semicolon, a comma or a tab, and is taken from the first row. If the file is not UTF-8, it is read with the Turkish Windows encoding and the report notes this.
  • In an XLSX file the sheet named publications is read, or the first sheet if there is none.
  • A JSON file is a list of objects, or an object that holds such a list in its rows field. Lists can also be written as JSON arrays.

Contributors

In the contributors column, contributors are separated by vertical bars. Each contributor is written as "Family name, Given name". If the role is not author, put the role and a colon before the name. An ORCID iD goes after the name in square brackets. For example:

Aksoy, Deniz | editor: Yalçın, Ece [0000-0002-1825-0097]

As the role, write author, editor, translator, illustrator, advisor or contributor. The Turkish equivalents yazar, editör, çevirmen, resimleyen, danışman and katkıda bulunan are accepted too. A contributor without a role counts as an author.

Cases that make a row invalid

A row is invalid and is not imported in these cases:

  • A required value is missing or a value has the wrong format.
  • A subtitle, abstract or keywords are given in a language that has no title.
  • A category slug or licence code in the row does not exist in the system.
  • The row is embargoed, but no embargo end date is given.
  • The same ISBN, DOI or source_id value also appears in an earlier row of the file.
  • The ISBN or DOI value is used in another record in the catalogue.
  • The ISSN or e-ISSN value of a journal row also appears in an earlier row of the file or is used in another record in the catalogue.
  • The existing record that matches the row is of another type.

Warnings

Warnings do not make a row invalid, but they are shown in the report:

  • The row has no source_id value. If this row is uploaded again, a second record is created.
  • The catalogue has another record with the same title, type and year.
  • The row is open access but has no licence. This record cannot be published until a licence is selected.

Was this page helpful?