Data Types
Datatypes
This article describes the various data types in FYLR as well as their behaviour in im- and export situations. FYLR supports user datatypes and system datatypes.
User datatypes
text, text_oneline
l10ntext, l10ntext_oneline
date, datetime
daterange
bool
file
link
custom data
Metadata mapping
System datatypes
Field | Import | Export | Description |
---|---|---|---|
| - | ✓ | The attribute |
| - | ✓ |
User datatypes
Custom datatype
For custom datatype we support the import mapping for known fields. These known fields are fields for which a mapping is defined in the plugin's manifest.yml.
In this example the subfield mytext
and mynumber
are imported for metadata imports.
The full custom data is also supported if the full JSON is provided during the import.
For export mapping FYLR supports all import fields as well as the subfield _standard
to output the standard info of the custom data.
A list of all available subfield names for a specific instance can be found in
/inspect/datamodel
.
Export
System columns
T: Top Level
L: Linked Object
P: Path / Paths / Parents
F: FYLR only, not in easydb
Field | T | L | P | F | XML Name | XML |
---|---|---|---|---|---|---|
| + |
| ||||
| + | + | + |
| ||
| + |
| ||||
| + |
| ||||
| + | + | + |
| ||
| + | + | + |
| ||
| + |
| ||||
| + |
| ||||
| + | + | + | + | ||
| + | + | + |
|
| |
| + | + | + |
| ||
| + | + | + |
| ||
| + | + | + | + |
| |
| + | + | + |
| ||
| + |
| ||||
| + | + | + |
| ||
| + | + | + |
|
| |
| + | + | + | + |
|
|
| + | + | + |
|
| |
| + | + | + |
|
| |
| + | + | + |
|
| |
| + | + | + |
|
|
User column
Type | Field | CSV | XML |
---|---|---|---|
string |
| ||
text_oneline |
| ||
text_l10n |
| ||
text |
| ||
date |
| ||
datetime |
| ||
daterange |
| ||
number |
| ||
integer.2 |
| ||
bool |
| ||
file |
| ||
link |
| ||
reverse_hierarchical |
| ||
reverse |
| ||
custom | JSON |
| |
custom |
| All export languages standard XML, merges text + l10ntext into one language map | |
custom |
| Plain XML for mapped search fields, FYLR only |
Last updated