...
We will see that it obeys specific rules in terms of updating and duplication of content.
...
Examples and naming conventions are applied to a DAM but these principles are applicable to any declinable object exploited on a layout-driven support.
Project’s content bin: principle of operation
Naming conventions
Group referential
Contains all the contents that must be shared between several projects of the same group. This group repository is also called media library. It can be an internal object in Wedia (instances of galleryelement) or a connection to a third party service.
...
Contains the contents specific to my project, not shared with other projects.
This project repository is called project content bin.
Contents of the project content-bin
The content elements in a project content bin can have several origins:
declination of an element of the group repository
direct import (page and emailing editor): for example, when I import an image file from my hard drive to a block of my document print (
monodoc)import from the Digital Asset Management repository (DAM)
Import kinematics
When content A stored in the project repository is imported into a project:
...
The principle of the single master and variants has been retained to link the blocks to a single instance, making it easier to synchronize and improves performance.
...
Unused elements of the content bin
If image A1' is deleted from the block and replaced by an image B1, it will remain in the content log. There is no automatic deletion of the variants called orphan.
This purge operation must be carried out by hand, by removing the elements concerned from the datalist.
Synchronizations - updates of the different elements
By multiplying versions of the same content on a medium, several processes have been put in place to synchronize the various elements (A to An or An').
...
| Warning |
|---|
On the page editor print, there is currently no automatic redial mechanism triggering an automatic redial after updating an element of the repository. |
...
In the case of an image without text data, the file is not a text file and no new variant is created.
The A1' file of the logger is not modified.
Technical requirements
The notion of a logger is managed by the support editor itself. It is he who, today, implements the logger using the tools and actions provided by the WXM_MediaCore plugin.
...
a functional page editor (
WXM_DTP_Managerfor print for example, with all its prerequisites)creation of multiple declinations within the same project (variations) requires the present of a variation field (type
integer) on the object of content to be used in the editor.
Easily parameterize the operation of the content bin
In the plugin parameters, you can intervene on the granularities of the projects content bin. For example, you can do this for particular object elements:
...