File and Data Ingest

BEFORE you begin importing files or data, read the section at the bottom of this article.

Import tools make it easy to transfer your assets and metadata into NetX.

In this article Ask your team
Learn about the different methods of importing assets and metadata. Discover how to prepare your files and data for import and ensure all required configurations are in place prior to migrating your content.

5 things to know about an initial ingest of files and data

Creating assets in NetX is more than just copying files from one place to another.
Thumbnails, previews, zooms, pages (and more) are generated at the time of import, so this could take longer than you might expect.
A small complex file can take longer to ingest than a larger simple file.
Complex files such as videos, layered TIFFs, multi-page PDF, and InDesign documents can take some time to process.
Metadata is indexed by the search engine.
System attributes, such as filenames, folder paths, and some embedded metadata are indexed at the time of file import. Custom attributes are indexed at the time of metadata upload or when edited in the UI.
Metadata from a previous DAM can be imported via .csv data upload.
Any data migrating from another system must be formatted correctly and align with your NetX Attributes.
Hydra can help in very large implementations by adding extra application servers to share the load.
Ask your Account Manager if this is the right approach for your ingest.

Best practices

Plan ahead.
Assign sufficient resources to prepare and deliver files and data. Migration preparation often takes a lot longer than you imagine. Prioritize popular assets and consider breaking up large or complex import projects into smaller batches.

Let it go.
Take the opportunity to filter out unnecessary files for a clean start in NetX. In most cases, storing only the highest resolution versions is sufficient as derivatives can be created on-demand instead of being stored. Plan carefully whether or not to store raw materials in NetX, such as unretouched photos or unedited HD video. NetX should store files that are of value to your organization, so resist storing everything!

Filenames are your friends.
Filenames are indexed by the search engine — take advantage of this. Descriptive, intuitive, consistent, and concise filename conventions are best. Avoid illegal characters and excessively long filenames (under 25 characters is good practice). Case and spelling matter: image.JPG, image.jpg, and image.jpeg are treated as distinct files in NetX. Use unique filenames to avoid collisions when moving or adding assets to folders or when uploading metadata via .csv.

Cataloging is better in bulk.
If you aren't migrating any existing metadata, attribute values can be batch-applied during import using the browser upload tool or the NetX I/O app. 

Import your way.
Choose to manage your own ingest using the NetX I/O desktop app or upload directly into NetX via a web browser. Hosted SaaS customers with repositories greater than 250 GB can ship us a drive and we'll manage the ingest for you. 

How-to articles

File import Data import

Tips and tricks

To increase indexing efficiency, all folder permissions should be configured prior to your initial import. Add all folders and sub-folders to which permissions apply, create user groups, then configure permissions.

For initial ingests via NetX I/O or a shipped hard drive, sub-folders will be automatically created during the ingest. Only the top-level structure needs to be created ahead of time in NetX. 

For initial ingests via the browser, all sub-folders need to be created before uploading files.

Duplicate Asset Detection can be configured if you have a large number of duplicate assets that need to be weeded out. See point 5 in the section below if you wish to use this feature.


1. Review our File Ingest Policy.

2. Provide these details to your Onboarding Specialist:

  • average file size
  • size (MB/GB) of your 10 largest files
  • pixel dimensions of your largest image file
  • approximate total number of files
  • approximate total size (GB/TB) of the import

3. Ensure the following essential configurations are in place:

  • all top-level folders
  • any sub-folders that have permissions
  • user groups
  • permissions
  • all properties that alter how files or data are processed
  • properties to optimize an initial ingest

4. If your site uses any optional configurations, these should be in place prior to import, along with all associated attribute fields, vocabularies, folders, and permissions:

  • attribute profiles
  • embedded metadata mappings triggered on import
  • autotask workflows triggered on import
  • autotasks that generate views or derivatives
  • indexing document content for basic keyword search
  • embedded color profiles for proxies
  • advanced configurations such as:
    • .jar files for custom jobs
    • MediaRich Zooms
    • InDesign Server
    • Hydra configuration
  • any other configurations that are impacted by the import of files or data

5. If you're using Duplicate Asset Detection:

  • turn on MD5 Checksums prior to the initial ingest, but DO NOT turn on the LinkDuplicatesJob. This ensures the asset count in NetX can be verified against the original ingest manifest.
  • once the ingest completes and has been verified, turn on the LinkDuplicatesJob and initiate an index-only resync to remove any duplicates (see Resyncing Assets). 
  • filenames are ignored by this system, so identical files with different filenames will still be detected as duplicates. Conversely, non-identical files with the same filenames will not be caught by Duplicate Asset Detection.
  • if a filename collision occurs, subsequent assets will be appended -1, -2, etc. which may impact data imports or other workflows dependent on accurate filenames. See the section on duplicate filenames in the Uploading Assets article for details.

Up next...

Launching your DAM

Was this article helpful?
0 out of 0 found this helpful