All Data Types
At this point you will find an example of data preparation in CSV format for each data type that is available in FYLR.
Pools
If you only want to import records into one pool, you do not have to enter the pool in the CSV file, but simply select it in the import settings. However, if you have records that should go in different pools or if you want to change the pool for records that already exist in the system, you must add the pool in the CSV file. You can use the ID, short name or reference of the pool in the CSV file. If no pool is specified for a record in the CSV file, the pool from the import settings is used.
| ID | TITLE | POOL |
|---|---|---|
1 | Berlin by Night | Pool A |
2 | Berliner Fernsehturm | |
3 | Berliner Dom | Pool B |
In the import mapping, select “_pool” for the column containing the pool and the “ID”, “Short name” or “Reference” field, depending on what you used in your CSV file.
Tags
If you want to import tags, please make sure, that the tags are available in your system. You can use the ID or the display name of the tags in the CSV file.
| ID | TITLE | TAG |
|---|---|---|
1 | Berlin by Night | TAG A |
3 | Berliner Dom | TAG B |
In the import mapping, select “_tags” for the column containing the tag and the “ID” or “Display Name” field, depending on what you used in your CSV file. On the "Import Settings" tab choose, if the tags should be added to existing tags or should replace them when updating existing records.
Single Line & Multi Line Text, Simple Text (String)
It is recommended to enclose the texts in double quotation marks. If a text contains a comma, semicolon, backslash, tab or a break, double quotes must be used so that they are not interpreted as column separators.
| ID | TITLE (single line text) | DESCRIPTION (multiline text) | SIGNATURE (string) |
|---|---|---|---|
1 | Berlin by Night | The image shows the illuminated Alexanderplatz at night. | signature_2019_001 |
2 | Berlin Cathedral | “The Berlin Cathedral in the midday sun. Many people lie on the lawn in front of the Berlin Cathedral.” | SIgnature_2018_002 |
3 | Berlin from above | Signature_2017_003 |
In the mapping, only the corresponding target fields have to be selected in each case. There are no further options.
Single Line & Multiline Text (multilingual)
For multilingual fields, the contents for the different languages are stored internally in separate fields. Therefore, the languages must also be written in different columns in the CSV file.
| ID | TITLE DE | TITLE EN | TITLE ES |
|---|---|---|---|
1 | German title | English title | Título en español |
2 | Only a German title is available here | ||
3 | Titel in Deutsch und Englisch | Title in German and English |
In the mapping, the same target field must first be selected for both columns (i.e. "TITLE"). Then the corresponding language can be selected. If a language is not displayed in the pulldown, it must first be activated by the administrator in the base configuration.
Date, Date + Time
When importing dates, both the German and American formats are supported.
| ID | CREATE DATE (date) | CREATE DATE (date + time) |
|---|---|---|
1 | 2019-12-06 | 2019-12-09 13:39:00 |
2 | 24.12.2019 | |
3 | 2018-11 | 2019-12-09 |
4 | 2017 |
In the mapping, only the corresponding target fields have to be selected in each case (i.e. "CREATE DATE"). There are no further options.
Date (Range)
The date range field is characterized by the fact that the values are stored internally in two fields. There is a “from” and “to” field. Therefore, the start and end date must also be written in two columns in the CSV file. Again, the German as well as the American format are accepted.
| ID | DATE FROM | DATE TO |
|---|---|---|
1 | 2019-10-01 | 2019-10-08 |
2 | 2016-01 | 2018-12 |
3 | 2009 | 2019-12-31 |
In the mapping, the same target field must first be selected for both columns. Then it can be selected whether the data should be written in “from” or “to”.
Number (integer), Decimal Number (2 digits), Double
When importing decimal numbers, both the period and the comma are supported. Thousands separators (point or comma) may not be used currently.
| ID | NUMBER (number) | VALUE (decimal number) |
|---|---|---|
1 | 1 | 1.40 |
2 | 2 | 5,80 |
3 | 3 | 35 |
In the mapping, only the corresponding target fields have to be selected in each case. There are no further options.
Yes/No Field (Boolean)
Fields of type “Yes/No field (Boolean)” are displayed as checkbox in the FYLR frontend. The two states “enabled” and “disabled” can be set by “true” or “1” and “false” or “0” during import. Empty fields in the CSV correspond to “false”.
| ID | VALUE |
|---|---|
1 | true |
2 | false |
3 |
Only the corresponding target field has to be selected in the mapping. There are no further options.
Simple Linking to Flat Lists
If a field connects to a list, these links can also be imported via CSV. The record you want to link can, but does not have to exist in the list in FYLR.
| ID | CATEGORY |
|---|---|
1 | Persons |
2 | Buildings |
3 | Events |
In the mapping, first select the corresponding target field. Then select the field from the linked object type. FYLR uses this field to check whether the record already exists in the list. If yes, the existing record will be linked. If not, a new record will be created in the list and linked (provided that the checkbox “Create Linked Records” is activated on the “Import Settings” tab during CSV import).
Simple Linking to Hierarchical Lists
If a field connects to a hierarchical list, these links can also be imported via CSV. The record you want to link can, but does not have to exist in the list in FYLR.
| ID | LOCATION |
|---|---|
1 | Germany > Berlin |
2 | Ireland > Dublin |
3 | United Kingdom > Scotland > Glasgow |
In the mapping, first select the corresponding target field. Then select the field from the linked object type. FYLR uses this field to check whether the record already exists in the list. If yes, the existing record will be linked. If not, a new record will be created in the list and linked (provided that the checkbox “Create Linked Records” is activated on the “Import Settings” tab during CSV import). When importing hierarchical lists, the separator used can be selected (">" or “/”) to build a hierarchy.
Repeatable Text Fields
If the target field is a so-called nested field (i.e. several entries can be made per record), all records in the CSV file must be written in one cell and separated with a break. Use double quotes to import texts that contain a break.
| ID | REPEATABLE TEXT |
|---|---|
1 | First text Second text Third text |
2 | “Text that contains a break. Continued after the break." “Text without a break, but with a comma.” |
Only the corresponding target field has to be selected in the mapping. There are no further options.
Alternatively, each entry of the repeatable field can also be written into a separate column. When importing, however, it should be noted that this must be done in several stages, since the target field may only ever be selected once during mapping. In the first run, the first column is mapped and imported. In the second run, only the second, etc. It is important that in this case the option “Append Nested Fields” is activated under “Import Settings”, so that the entries in the multiple field are added and not overwritten each time.
Nested Fields
If the target field is a so-called nested field in which another object type is referenced, all records to be linked in the CSV file must be written in one cell and separated with a break. Use double quotes to import entries that contain a break or separator.
| ID | KEYWORDS |
|---|---|
1 | Sun Moon Stars |
2 | “City, Country, River Game” “Children’s Games” |
This works even if the linked object type is hierarchical:
| ID | FORMER LOCATIONS |
|---|---|
1 | Germany > Berlin Ireland > Dublin United Kingdom > Scotland > Glasgow |
In the mapping, first select the corresponding target field. Then select the field from the linked object type. FYLR uses this field to check whether the record already exists in the list. If yes, the existing record will be linked. If not, a new record will be created in the list and linked (provided that the checkbox “Create Linked Records” is activated on the “Import Settings” tab during CSV import). When importing hierarchical lists, the separator used can still be selected (">” or “/”) to build a hierarchy.
Alternatively, each entry of the repeatable field can also be written into a separate column. When importing, however, it should be noted that this must be done in several stages, since the target field may only ever be selected once during mapping. In the first run, the first column is mapped and imported. In the second run, only the second, etc. It is important that in this case the option “Append Nested Fields” is activated under “Import Settings”, so that the entries in the multiple field are added and not overwritten each time.
Nested Fields with Multiple Fields
If the target field is a so-called nested field, which contains more than one field, these fields must be divided into individual columns. If more than one record is to be linked to a record, these must again be entered in a cell and separated by a break.
| ID | OTHER IDS | ID TYPES |
|---|---|---|
1 | IDA123 ID1XYZ IDA1B2C3 | Altsystem XY Portal XY |
Alternatively, each record of the repeatable field can also be written into its own column. In our example, there would be a total of 6 columns for the three entries (“OTHER ID 1”, “OTHER ID 1 TYPE”, “OTHER ID 2”, “OTHER ID 2 TYPE”, “OTHER ID 3”, “OTHER ID 3 TYPE”). When importing, however, it should be noted that this must be done in multiple steps, since you may only ever select the target field once during the mapping. So in the first run you map and import the first two columns. In the second run, only the third and fourth, etc. It is important that in this case the option “Append Nested Records” is activated under “Import settings”, so that the entries in the multiple field are supplemented and not overwritten each time.
Files
The import of files is explained in the examples.
Plugins
To import content into Custom Data Fields, it is best to first manually create a record in FYLR and export it as CSV. There you can have a look at the structure of the content. This varies depending on the plugin. Sometimes not all information is needed for the import, but can be added automatically by the Custom-Data-Updater. You can find more information at the respective Plugins.
The following information is sufficient for the GND custom data type:
The following information is sufficient for the GVK custom data type:
Only the corresponding target field has to be selected in the mapping. There are no further options.
Last updated