Page tree
Skip to end of metadata
Go to start of metadata

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

Upload window

  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. Remove all files from the queue using the trashcantrashcan button. 



  3. You can choose which physical location your assets will be stored in, 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 queue of files to upload. Each line displays the file's name and size, and a thumbnail which shows a preview of the asset when clicked. Assets can be removed individually using the X button.
  5. As your files are uploaded and become assets, attribute data can be applied.
  6. The Upload button initiates the upload action.

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.

Advanced settings

Duplicate asset detection checks each new asset as it is uploaded to see if its file name 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. 
PropertyValuesDescriptionRequires restart?

image.nameCollisionStrategy

or 1If 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 uploaded as usual but renamed with a numerical suffix: filename-1.jpg.No
import.duplicateActionreimport, checkin, rejectWhen the image.nameCollisionStrategy property is set to 0, the existing asset will be versioned via checkin. This property can be used to change that default behavior to reimport the asset or reject it altogether.No

Assets cannot be added or moved to a folder that contains an existing asset with a duplicate file name, regardless of the properties above.


In this article

  • No labels

1 Comment

  1. Leanne Dunn This line "If a file is uploaded into a folder that has an existing file with the same name, it will add the new file as a version of the existing one and not create a new asset. " is incorrect.  The default behaviour (ie: if this property is not configured), is to create a new asset and append the filename with  dash1 . Adding the property with a value of 1 leads to the same default behaviour.  Setting the value to 0 just deletes the new asset without versioning.