Uploading Assets

Users with sufficient privileges can upload assets to NetX as well as apply attribute data to the new assets. 

Upload window

Upload_queue_round_two.png

  1. The Upload button along the header of the application launches the upload window. You can also initiate an upload by dragging files into the browser. 
  2. Use the plus + button along the header of the upload window to add assets to your upload queue. You can also add assets by dragging files to the upload window. To remove all files from the queue, use the trashcan button.
  3. Choose the server storage location where your assets will be kept and the folder where they will be displayed in the application. The Storage location, by default, is the Internal repository — though there may be other options if your site's administrators have configured other storage locations.
    The Upload folder is the folder where the assets are located in NetX and can be changed using a folder-picker by clicking this field. 
  4. Your upload queue. Each line displays the file's name and size, and each asset will receive a thumbnail as it is successfully uploaded to the system. Assets can be removed individually using the X button.
  5. Check this box to apply attribute data to every file uploaded in the current queue. Note that even if this checkbox is not marked, mandatory attributes will still be enforced. 
  6. The Upload button initiates the upload action. As assets are successfully uploaded, they will remain in the queue (unless explicitly removed) with a new preview thumbnail icon. 

Drag to upload

Drag files into the browser window to begin an upload. If an upload is in progress, dragging additional assets into NetX adds them to the queue. If you are initiating an upload from a folder context, the folder field is automatically filled with that folder.

Editing attributes

  1. To edit attributes during an upload, check the box marked Edit attributes before clicking the Upload button.
  2. Once you click the Upload button, a window will appear containing editable attribute fields. If an attribute is mandatory, it will be separated at the top from any other attributes and will require a value to be entered. Attribute sets can be chosen from the topmost dropdown so that you can narrow your attribute options to those you need at the moment.
  3. Click Save when finished, and the upload will begin.

uploadingthethings.gif

Duplicate filenames

NetX checks each new asset as it is uploaded to see if its filename matches an existing asset in the same folder. If a duplicate name is found, NetX will either:

  • Version the existing asset with the new asset; the existing asset will be retained as a prior version. If this setting is used, no new asset is created.
  • Rename the new asset with a numerical suffix, e.g. filename-1.jpgfilename-2.jpg, etc. If this setting is used, the asset is still uploaded to the folder as usual.
  • Assets cannot be added or moved to a folder that contains an existing asset with a duplicate file name, regardless of the properties above.
  • Duplicate filename behavior is not to be confused with the Duplicate Asset Detection feature, which detects duplicates based on file content (MD5 checksum) rather than filename.
Property Description

image.nameCollisionStrategy

If the value of this property is and an asset is uploaded to a folder with a file name conflict, the existing asset will be versioned. If the value of this property is 1, the new asset will be uploaded as usual but renamed with a numerical suffix: filename-1.jpg.

Value options: or 1

Requires restart: No

import.duplicateAction

When the image.nameCollisionStrategy property is set to 0, the existing asset will be versioned via check-in. This property can be used to change that default behavior to reimport the asset or reject it altogether.

Value options: reimport, checkin, reject

Requires restart: No

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