Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Principles of operation of the waiting area

The waiting area will be available on your DAM objects as soon as these items will have the tag gallery_multi_upload on one of their file property.

...

  • mass upload new assets onto the system

  • insert the assets later into the destination DAM object

...

Upload assets

One click on the button Upload new asset will allow the user to send files to the system either via HTTP or FTP.

Access to asset download functionality is conditional on the result of a security rule on the insert action of the objectdata domain for the object damimport.
To be allowed to upload files on the system the user must have the right to insert new instances in the damimport object.

Sending assets via HTTP

This feature allows a user to upload one or more assets to the system from their workstation.

The user selects a set of assets from his workstation and sends them to the system.

Assets downloading via FTP

This feature allows the server to connect to an FTP server and retrieve all the files available to it.

Warning

Here it is the Wedia server that connects to an FTP server.

Indexation of the assets

Regardless of the upload method used each asset will be the source of a new instance in the damimport object in which the property having tag gallery_multi_upload will be feeded with the uploaded files and property name will be feeded with its name (ie: my_picture.png).

...

Note

Regardless of the selected mode, access to the functionalities indexing of assets is conditioned by the result of a safety rule on the insert action of the objectdata domain for the DAM object in which the user wants to create the assets.

Single indexing

During a single indexing the records are created one by one when the user clicks on the button Start indexing.

...

The checkboxes next to the properties allow you to keep the values properties to pre-fill the following records. Property values checked will have priority over the initial values of the card.

...

When a master record is created in the destination background it is automatically removed from the indexing basket (damimport).

Multiple indexing

During a multiple indexing all records will be created automatically. The values used to fill records depend on of the checkbox next to each property:

...

When the user clicks on the button Start indexing he will be able to choose either to index the files in the background by clicking on the button Index in background or index all files interactively.

...

When indexing in the background ends, the user is informed via a back-office notifications.

...

Pre-loading data into the system when uploading

The damimport object has two properties by default: name and file which allow you to store the name of the initial file and the downloaded file by the user.

...

It is possible to add to the damimport object as many properties as necessary.

Manual data preloading

The data can be pre-fed into the system in the damimport object by displaying an input form that will be presented to the user before downloading files to the system.

...

Note

The facets of the dam object will be played on this form. There must not be any facets on the damimport object because they are useless.

Automatic data preloading

The data of the damimport object properties can be fed to the damimport object via a trigger in the damimport object, for example by reading the IPTC metadata of images or by loading data via a third party API for each of the imported assets.

...