Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  1. Fotoware Alto
    • 11.14 Schreckhorn
    • Terminology
    • Solutions
    • User Guide - Deutsch
    • User Guide - English
    • API Changelog
  2. Fotoware Veloz
    • Managing users and groups
    • Configuring archives
    • Configuring workflows
    • Configuring site behavior
    • Navigating and searching to find your assets
    • Working with your assets
    • Editing asset metadata
    • Uploading files
    • Version Control in Fotoware
    • Albums - Creating and sharing collections
    • Placing assets in a CMS
    • Working with the Fotoware Pro interface
    • Using the Fotoware plugins
    • Consent management
    • User guide to FotoWeb for iPad (Legacy)
    • Picture conferencing with FotoWeb Screens (Legacy)
    • What's what in Fotoware
    • GDPR
    • Fotoware Veloz releases
    • Activity Exports
    • Fotoware Example Workflows
  3. Fotostation
    • Getting started with Fotostation
    • Viewing, selecting and sorting files
    • Managing your assets with archives
    • Adding metadata to assets
    • Searching for assets
    • Working with your assets
    • Version Control in Fotostation
    • Automating tasks with Actions
    • Configuring metadata fields and editors
    • Configuring Fotostation
    • Configuring Fotostation for multi-user environments
    • Troubleshooting Fotostation
  4. Fotoware Flow
    • What is Flow?
    • Getting started
    • Flow dictionary
  5. Fotoware On-Premises
    • Getting started
    • Index Manager
    • FotoWeb
    • Color Factory
    • Connect
    • Operations Center Guide
  6. Integrations and APIs
    • The Fotoware API
    • Creating integrations using embeddable widgets
    • Authorizing applications using OAuth
    • Auto-tagging
    • FotoWeb Drag and Drop export
    • Integration using webhooks
    • Optimizely and Episerver plugin documentation
    • User Interface Integrations
  7. Fotoware Mobile
    • User guide for Fotoware Mobile for iPhone and Android
    • User guide to FotoWeb for iPad (Legacy)
    • User guide to FotoWeb for iPhone and Android (Legacy)

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Support

Table of Contents

Creating the QuickList content How the proxy QuickLists files work Setting the proxy file connection string for GET requests to the server Example Context-sensitive URLs Content caching and updating Providing cache header in the server response Setting the proxy file connection string for POST requests to the server POST request payload Replace method Insert method Add Child method Delete method
  • Home
  • Fotostation
  • Configuring metadata fields and editors

Configuring FotoStation to download QuickList content from a web server

29. March 2025

Elaine Foley

Table of Contents

Creating the QuickList content How the proxy QuickLists files work Setting the proxy file connection string for GET requests to the server Example Context-sensitive URLs Content caching and updating Providing cache header in the server response Setting the proxy file connection string for POST requests to the server POST request payload Replace method Insert method Add Child method Delete method

Note: This feature is only available in FotoStation Client.

When creating QuickLists (regular "flat" ones or hierarchical ones) with predefined metadata for FotoStation's editors, it is possible to store these on a central web server and configure "proxy" QuickLists files in the FotoStation configuration that tell the metadata editors to retrieve new content live from a centrally maintained QuickList repository via HTTP.
It is also possible to make edits to the QuickLists directly in FotoStation and have FotoStation update the QuickLists on the web server via POST requests to a server backend.

Creating the QuickList content

The Quicklists that contain the actual content that you will use in FotoStation can be created as described in the Creating QuickLists of Predefined Metadata topic. However, the naming conventions outlined there are not important, as it's the QuickList proxy files (see below) in the FotoStation configuration that need to be named correctly to map the metadata to the correct fields.

Having created QuickLists with content, put them on a web share so that FotoStation can reach them. 

How the proxy QuickLists files work

The proxy QuickLists follow the naming conventions of regular FotoStation QuickLists:

  • ql_<fieldnumber>.txt denotes a flat-structure QuickList, while 
  • <fieldnumber>.txt is used for thesaurus QuickLists, with hierarchically arranged entries.

They are stored in the default location for QuickLists; the actual location differs depending on the type of configuration used.

You can also create proxy files that link fields together and populate different fields with metadata from different levels in the hierarchical structure you've created. Make sure to include the connection string (as described in the paragraph below) to the first line of the file.

Setting the proxy file connection string for GET requests to the server

When creating a proxy QuickList file, it only needs to contain a single line of information - the string that tells FotoStation where to retrieve the QuickList content. This is in the form of a web URL, prefixed with http:// or https:// for secure connections.

Example

This is an example of the content in the proxy file that retrieves content in a flat structure for the Keywords field.

(Proxy file name: ql_025.txt)

#! HTTP_DOWNLOAD_URL=http://yourserver.com/QuickLists/keywords.txt

If the file referenced above is a hierarchical structure of keywords (a thesaurus QuickList) name the proxy file 025.txt, omitting the ql_ prefix.

Context-sensitive URLs

When configuring a proxy file with a connection string, you have the option to create a connection string that uses dynamically inserted content from your metadata to query a backend server.

A connection string can look like the following example:

#! HTTP_DOWNLOAD_URL=http://myserver.com/QuickLists?title=#005&keyword=#025

The above request sends the query string to the server and inserts the content of fields #005 (Title field) and #025 (Keywords field).

Note that in the case of bag fields, such as Keywords (#025), FotoStation inserts the value of the currently selected keyword on the page in the metadata editor. If no entry is selected in the bag field, the first value in the bag is inserted into the query.

Content caching and updating

When a user opens the metadata editor, FotoStation downloads the content from the referenced URL. To avoid unnecessary downloads we recommend setting up caching on the web server - see the instructions below.

FotoStation stores the downloaded content in the proxy file and updates it with new content when available. Consequently, FotoStation will be able to use the locally cached QuickLists even when it does not have a network connection to the server.

Providing cache header in the server response

Configure your web server with a HTTP response header to enable caching of the QuickLists:

Property: Cache-control

Value: public; max-age=<seconds>

Setting the proxy file connection string for POST requests to the server

A QuickList file can also contain a string for POST requests. This way, users can update QuickLists using the tools in the FotoStation metadata editor and the new data is sent to the web server immediately.

The POST statement in the QuickList is in the form of a web URL prefixed with http or HTTPS and reads as follows:

#! HTTP_EDIT_URL=http://www.myserver.com/QuickListbackendservice

POST request payload

Four different methods are used in the JSON payload delivered to the web server.

Replace method

Used when an entry in the QuickList is replaced with a new value.

1
 POST http://www.myserver.com:7009/backend HTTP/1.1
2
 Host: www.ovensen.com:7009
3
 Content-Type: application/json
4
 Content-Length: 117
5
 Connection: Keep-Alive
6
 Accept-Encoding: gzip, deflate
7
 Accept-Language: nb-NO,en,*
8
 User-Agent: Mozilla/5.0{"method": "replace", "path":["Architecture", "Building", "agricultural building"], "value": "Agricultural Building"}

Insert method

Used when a new item is created in the QuickList at the same level as an existing item (sibling).

1
 POST http://www.myserver.com:7009/backend HTTP/1.1
2
 Host: www.ovensen.com:7009
3
 Content-Type: application/json
4
 Content-Length: 120
5
 Connection: Keep-Alive
6
 Accept-Encoding: gzip, deflate
7
 Accept-Language: nb-NO,en,*
8
 User-Agent: Mozilla/5.0{"method": "insert", "path":["Architecture", "Building", "Agricultural Building"], "value": "Agricultural Machine"}

Add Child method

Used when a new item is created as a child item below an existing item.

1
 POST http://www.myserver.com:7009/backend HTTP/1.1
2
 Host: www.ovensen.com:7009
3
 Content-Type: application/json
4
 Content-Length: 103
5
 Connection: Keep-Alive
6
 Accept-Encoding: gzip, deflate
7
 Accept-Language: nb-NO,en,*
8
 User-Agent: Mozilla/5.0{"method": "addChild", "path":["Architecture", "Building", "Agricultural Machine"], "value": "Tractor"}

Delete method

Used to delete an item in the QuickList.

1
 POST http://www.myserver.com:7009/backend HTTP/1.1
2
 Host: www.ovensen.com:7009
3
 Content-Type: application/json
4
 Content-Length: 92
5
 Connection: Keep-Alive
6
 Accept-Encoding: gzip, deflate
7
 Accept-Language: nb-NO,en,*
8
 User-Agent: Mozilla/5.0{"method": "delete", "path":["Architecture", "Building", "Agricultural Machine", "Tractor"]}

 

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • Application registration using OAuth 2.0
  • Get started with OAuth
  • Refreshing tokens
eco-lighthouse-miljøfyrtårn

Company

  • About us
  • Resellers
  • Careers
  • Contact us

Help & support

  • Support center
  • Consultancy
  • Tech partners
  • Fotostation
  • System status

Trust Center

  • Legal
  • Security
  • Sustainability & ESG

Locations

Fotoware AS (HQ)
Tollbugata 35
0157 OSLO
Norway
FotoWare Switzerland AG
Industriestrasse 25
5033 Buchs (AG)
Switzerland

Copyright 2025 Fotoware All rights reserved.

  • Terms of service
  • Privacy policy
  • Cookie policy

Knowledge Base Software powered by Helpjuice

Expand