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
    • End-User Manual
    • User Guides
    • Solutions
    • Terminology
    • 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
    • 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 (Fotoware Veloz & On-Premises)
    • 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

What this workflow does Setting it up
  • Home
  • Fotoware On-Premises
  • Color Factory
  • Building workflows using Color Factory (On-Premises)

Filtering out files that have insufficient metadata

This topic explains how Color Factory can be configured to filter out files with insufficient metadata from workflows for manual metadata entry.

04. March 2025

Elaine Foley

Table of Contents

What this workflow does Setting it up

What this workflow does

When submitting files to an archive, you need some level of metadata governance to make sure that the files can be successfully found later. Color Factory helps you do this, for example using routing by required metadata. This allows you to create a workflow where assets that have sufficient metadata will pass right on through the workflow and be stored in the location you've configured, while assets that don't contain enough metadata will be routed elsewhere to allow you to review and edit those files.

Note: There a plethora of levels at which you can enforce metadata governance in the Fotoware system - for example you can configure clients so a user must add metadata to certain required fields before a file is submitted. However, this topic only deals with the Color Factory side of things, and we'll leave it up to you to choose where this is best enforced in your asset management system.

Setting it up

  1. Start by creating a channel with the AutoRouting feature enabled.
  2. Expand the channel tree and go to the AutoRouting node and click on Add to create a new routing method.
  3. Choose the Required Fields routing type, then name the routing and click Select.

     
  4. Now choose which folder file file should be routed to if the required fields are not filled in. By default, they will be stored in a folder called Required text missing inside the channel's output folder, but you can choose to store these files in any folder on the network. Asset that have content in the required fields are be default stored in the channel's output folder, but you can override that too if you like by choosing another folder.

     
  5. Tick off the fields that are required - i.e. have to be filled in before the file is approved.
  6. If you want to make sure that users have not simply inserted a space character in the required fields to avoid having to type anything in, you can tick the corresponding option to ignore white spaces. Any file with a blank space in the required field is then routed as a file that does not contain the required metadata.
  7. Click OK to store the routing preferences and make sure you save the Color Factory configuration (File | Save in the program menu) to incorporate the changes.
screening files inadequate data

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • Mapping of metadata category codes
  • Defining metadata requirements for uploaded assets
  • Preserving metadata on upload
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