DOCUMENTATION
  • Welcome
  • Releases
    • 2025
      • Release v6.20.2 (2025-05-07)
      • Release v6.20.1 (2025-05-06)
      • Release v6.20.0 (2025-04-30)
      • Release v6.19.2 (2025-04-11)
      • Release v6.19.1 (2025-03-31)
      • Release v6.19.0 (2025-03-27)
      • Release v6.18.2 (2025-03-11)
      • Release v6.18.1 (2025-03-07)
      • Release v6.18.0 (2025-02-26)
      • Release v6.17.3 (2025-02-14)
      • Release v6.17.2 (2025-02-07)
      • Release v6.17.1 (2025-02-06)
      • Release v6.17.0 (2025-01-30)
    • 2024
      • Release v6.16.0 (2024-12-12)
      • Release v6.15.0 (2024-11-27)
      • Release v6.14.2 (2024-11-05)
      • Release v6.14.1 (2024-11-01)
      • Release v6.14.0 (2024-10-31)
      • Release v6.13.3 (2024-10-16)
      • Release v6.13.2 (2024-10-10)
      • Release v6.13.1 (2024-10-02)
      • Release v6.13.0 (2024-09-25)
      • Release v6.12.2 (2024-09-18)
      • Release v6.12.1 (2024-08-01)
      • Release v6.12.0 (2024-07-25)
      • Release v6.11.5 (2024-07-09)
      • Release v6.11.4 (2024-07-05)
      • Release v6.11.3 (2024-07-03)
      • Release v6.11.2 (2024-06-21)
      • Release v6.11.1 (2024-06-14)
      • Release v6.11.0 (2024-06-05)
      • Release v6.10.2 (2024-05-15)
      • Release v6.10.1 (2024-05-08)
      • Release v6.10.0 (2024-04-30)
      • Release v6.9.3 (2024-03-19)
      • Release v6.9.2 (2024-03-15)
      • Release v6.9.1 (2024-03-06)
      • Release v6.9.0 (2024-02-28)
      • Release v6.8.5 (2024-02-02)
      • Release v6.8.4 (2024-02-01)
      • Release v6.8.3 (2024-01-12)
      • Release v6.8.2 (2024-01-05)
    • 2023
      • Release v6.8.1 (2023-12-22)
      • Release v6.8.0 (2023-12-14)
      • Release v6.7.4 (2023-11-15)
      • Release v6.7.3 (2023-11-14)
      • Release v6.7.2 (2023-11-03)
      • Release v6.7.1 (2023-10-17)
      • Release v6.7.0 (2023-10-13)
      • Release v6.6.4 (2023-09-29)
      • Release v6.6.3 (2023-09-28)
      • Release 6.6.2 (2023-09-14)
      • Release v6.6.1 (2023-08-10)
      • Release v6.6.0 (2023-08-03)
      • Release v6.5.1 (2023-06-23)
      • Release v6.5.0 (2023-06-22)
      • Release v6.4.0 (2023-05-31)
      • Release v6.3.1 (2023-04-28)
      • Release v6.3.0 (2023-04-05)
      • Release v6.2.5 (2023-03-16)
      • Release v6.2.4 (2023-02-01)
      • Release v6.2.3 (2023-01-12)
      • Release v6.2.2 (2023-01-12)
      • Release v6.2.1 (2023-01-05)
    • 2022
      • fylr first Production Ready Release 🎉 (2022-12-22)
  • License
  • Help
    • FAQs
    • Tutorials
      • For Users
      • For Administrators
        • Exporting & Importing Hierarchical Lists
        • Regenerating preview images
        • Search Text in images or office files
      • For System Administrators
        • How to setup and use IIIF
        • External access: Sharing collections with anonymous users
    • Glossary
  • FOR USERS
    • Getting Started
    • Asset / Records Management
      • Creating Records
      • Editing Records
        • Input Fields
        • Group Editor
      • Deleting Records
    • Quick Access
      • Collections (& Presentations)
      • Saved Searches (& Lists)
    • Lists
    • Plugins
      • Plugin Overview
  • FOR ADMINISTRATORS
    • Permissions
      • User
      • Groups
      • Object Types
      • Pools
      • Tags & Workflows
      • Presets
    • Tools
      • CSV Importer
        • General Information
        • Options
        • Examples
          • All Data Types
          • Lists
          • Hierarchies
          • Files
      • JSON Importer
        • Step-by-Step Tutorial
          • Write Import Manifest
          • Create Basetype Payloads
          • Create Object Payloads
          • Collection Payloads
          • Optional: Update links between Objects
          • Start Import
      • Permissions Download & Upload
    • Base Configuration
      • General
      • Access
      • User Management
      • Languages
      • Email
      • Export & Deep Links
      • Workflow Webhooks
      • Publications
      • File Worker
        • Preview Configuration
        • Location Defaults
        • Custom .icc Color Profiles
      • Objectstore
      • Services
      • License Management
      • Development
      • Plugins
    • Plugin Manager
    • Location Manager
    • Messages
    • Events
    • Backup Manager
    • Additional Features
      • IIIF
      • Connector
      • Wordpress
      • Zooniverse
      • Protocols
        • OAI/PMH
  • FOR SYSTEM ADMINISTRATORS
    • Installation
      • Linux
        • multiple fylrs in one Linux
        • proxy and fylr
      • Windows
      • Kubernetes
    • Configuration
      • fylr.example.yml
      • fylr.default.yml
      • performance tuning
      • pre-load frontend config
      • Load Custom Plugins
      • HTTP and HTTPS
      • DNS Domains
    • Backups & Restore
    • Migration Tool
      • Create payloads (fylr backup)
      • Insert payloads (fylr restore)
      • Best Practice
      • Using the fylr inspect page
    • Integration
      • Authentication
      • Hotfolder
    • Symptom & Solution
      • Log messages that can be ignored
      • too many clients are connected
      • too many nested clauses
      • context canceled
      • ContainerConfig error
      • Purge objects
    • PostgreSQL versions
  • Tutorials
    • Project Workflow
    • Hotfolder & File System Connect
      • Preparations Before Usage
      • Setting Up An Upload Collection
      • Importing Files
    • PDF Creator
    • Extracting File Metadata Later On
    • Overlay Resource
    • Authentication
      • LDAP
      • SAML
    • Data Model Sync
    • Purge a fylr instance
    • typo3 plugin
    • Use fylr in Google docs via CI HUB
  • FOR DEVELOPERS
    • API
      • OAuth2
      • Endpoints
        • /api/collection
        • /api/config
        • /api/db_info
        • /api/db
        • /api/eas
        • /api/event
        • /api/export
        • /api/group
        • /api/l10n
        • /api/mask
        • /api/message
        • /api/oaipmh
        • /api/objects
        • /api/objecttype
        • /api/plugin
        • /api/pool
        • /api/publish
        • /api/right
        • /api/schema
        • /api/search
        • /api/settings
        • /api/suggest
        • /api/system
        • /api/tags
        • /api/transitions
        • /api/user
        • /api/webdav
        • /api/xmlmapping
        • /api/task
    • System Data Types
      • pool
      • file
      • user
      • group
      • pool
      • collection
      • message
      • publish
      • event
    • User Data Types
      • text, text_oneline
      • string
      • text_l10n, text_l10n_oneline
      • boolean
      • number
      • integer.2
      • double
      • date, datetime
      • daterange
      • geojson
    • Custom Data
    • Emails
    • Export
    • Exec server
    • File versions
    • WebDAV
    • Plugin
    • Collection Pin Code
    • easydb 5
    • Localization
    • Access private Repositories
Powered by GitBook
On this page
  • Fields
  • Technical Metadata
  • File Versions
  1. FOR DEVELOPERS
  2. System Data Types

file

PreviouspoolNextuser

Last updated 5 months ago

The system data type file stores all files used throughout the fylr system:

  • Objects

  • Plugins

  • Logo & Background, XSLT files in the base configuration

  • User picture and custom data

  • Pool watermark and custom data

  • Objecttype custom data

Files are generally uploaded to the endpoint . fylr can also upload files by copying from remote URLs when using the endpoint . Files can also be uploaded via WebDAV or by the for plugins with type url.

Files are stored in configurable locations, like S3 or disk storage.

fylr can also manage purley remote stored files. In that case only the URL is stored for the file.

fylr runs programs to discover metadata for each file. Plugins can extend the list of programs run to find metadata.

Fields

Technical Metadata

File Versions

Henk

Horst s3ioj osqjwo ijojsqwi

/api/eas/put
/api/eas/rput
/api/plugin/manage
Field
Format
Description

_download_allowed

string

_id

string

aspect_ratio

string

blurhash

string

class

string

class_extension

string

date_created

string

deep_link_url

string

delete_url

string

dpi

string

extension

string

filesize

string

hash

string

height

string

iiif_url

string

last_status_at

string

orientation

string

path

string

percent_done

string

status

string

technical_metadata

string

url

string

watermark

string

width

string

zoom_url

string

Field
Format
Description

aspect_ratio

float64

audio_codec

array

blurhash

string

camera_scanner

string

colordepth

int

colorprofile

string

colorspace

string

create_date

string

date_time_original

string

dimensions

object

height

float64

unit

string

width

float64

dpi

int

duration

int

file_type_extension

string

filesize

int64

format

string

The format of the file: landscape, portrait or square.

gps_location

object

altitude

float64

latitude

float64

longitude

float64

has_clipping_path

boolean

height

int

max_dimension

int

mime_type

string

num_glyphs

int

orientation

string

pages

int

sha256_hash

string

video_codec

array

width

int

Field
Format
Description

_duplicates

array

If set, this attribute can hold an array of duplicates.

_id

int64

The _id is created when a file is uploaded into the fylr server.

_linked_objects

array

_mapped_metadata

object

A rendered version of the object data retrived and mapped from this file's metadata. It can be used to create objects based on a pre-configured metadata mapping.

best_date

timestamp

Best date is a compiled UTC timestamp from the technical metadata. fylr uses the first set date from technical_metadata.date_time_original, technical_metadata.create_date, date_uploaded.

children

array

For originals which use a pageable format, like PDF, this attribute contains the pages available underneath the original. The format is string and the value is using the file's _id and the page number (starting at 0) separated by /.

class

string

The compiled class of the file. The classes are set by the recipe. Standard recipes of fylr include image, audio, office, video. The fylr frontend uses the class to pick the general player to view the file. A class unknown is assigned if no matching recipe was found but the upload accepts unknown types.

class_extension

string

A compiled concatenation of class, version, joined by .. This is used for aggregations of files

class_version_status

string

A compiled concatenation of class, version and status, joined by .. This is used for aggregations of file status.

compiled

string

A compiled version of the metadata for this file. For images this looks like this: JPG, 1920 x 1285 px, 569.5 kB.

compiled_props

object

A fielded version of compiled. Frontends can use this to beatify the compiled output of the metadata.

. dimensions

string

The rendered dimensions for this file. This may include a unit. For page sizes European paper sizes like A4 will be recognised.

. duration

string

Runtime of the audio or video file.

extension

string

The upper cased version of the extension.

pages

string

The number of pages followed by a p.. Frontends may localize this manually.

date_uploaded

timestamp

The UTC timestamp when this file was uploaded.

eas_parent_id

int64

The eas_parent_id is the id of the file this file is derived from. When using /api/produce, the newly produced files will get the parent id set to the file they are produced from.

extension

string

The compiled extension of the file. This is matched by parsing available recipes at the time of the metadata generation. Extensions are matched by longer length first. So for a file flower.webdvd.zip the extension matched would be .webdvd.zip and not .zip if there is an available recipe.

filesize

int64

The file size in bytes.

frontend_prefs

object

Set only in relation to an object. This map can contain custom attributes and values.

hash

string

is_original

boolean

Set to true if the file is an original. It is false if the file is a generated or uploaded rendition. Produced files are registered as originals underneath the original they are produced from.

last_status_at

timestamp

The UTC timestamp when the last status change was last written to the database.

lookup:_id

object

reference

string

The reference of the file to look up.

metadata

object

groupnames

array

Sorted list of metadata group names found in groups.

groups

object

name

string

original_filename

string

The filename as set by original_filepath minus the path.

original_filename_basename

string

The filename as set by original_filepath minus the path and the detected extension.

original_filepath

string

Filename of the file as set during the upload. On Windows, this can contain drive letters and backslashes.

pages_allowed

boolean

Indicates that the file has pages.

preferred

boolean

This may be set if the file is in the context of an object. If set, preferred indicates that this version is the preferred one in a list of other versions.

reference

string

If set, this reference string is a unique string identifying the file. If the reference contains a sha244:<hash> or sha256:<hash>, the provided hash can be checked against the file's checksum using an action triggerable in /inspect/files. Other parts of the reference can be added but must be separated by :.

status

string

The status of the file. Known states are: pending, processing, sync, done, failed. Files and renditions can be accessed in status sync and done. Only files in state done can be exported.

technical_metadata

object

upload_user

object

The user who uploaded this file into the system. If the upload happens via Hotfolder, the uploader is the owner of the upload collection.

_basetype

string

user

object

versions

object

versions contains a map with renditions for the file. Depending on the users permissions, not all versions might be accessible.

When a file is uploaded and linked to a collection via , the attribute contains a list of objects created based on the upload settings of that collection.

The hash is a non unique identifier of the file. For remote files, it is the of the URL, for local files it is the of the binary file data. It is calculated together with the metadata for the file and a copy of technical_metadata.sha256_hash. The hash is used for duplicate detection.

Custom name of the file. This is set in the relation to the object. When retrieving the file via .

An object to describe technical aspects of the file. See for details.

"user". More info can be found

This will show a short representation of .

/api/eas
md5sum
SHA-256
/api/eas
Technical Metadata
here
here2
here3
here4
user