When WoodWing Enterprise is integrated with Elvis it is important that metadata information is shared between the two systems so that information about how and where assets are used in Enterprise can be verified and searched on.
For this purpose, various metadata fields are mapped, thereby making it possible for metadata changes in Elvis to appear in Enterprise and the other way round.
This article provides an overview of the fields that are mapped.
Fields that are mapped when importing assets from Enterprise
The following table shows which fields are mapped and if they are read from Elvis and written back to Elvis.
Enterprise name | Elvis name | Read | Write 1 |
---|---|---|---|
Aspect ratio Internal name: |
Aspect ratio Internal name: |
x |
|
Author Internal name: |
Name Internal name: |
x | x |
Character count Internal name: |
Character count Internal name: |
x | |
Color space Internal name: |
Color space Internal name: |
x | |
Comment Internal name: |
Version comment Internal name: |
x | x |
Copyright (c) Internal name: |
Copyright Internal name: |
x | x |
Copyright Marked Internal name: |
- |
x4 |
|
Copyright URL Internal name: |
Website Internal name: |
x | x |
Created By Internal name: |
Importer Internal name: |
x | |
Created On Internal name: |
Imported in Elvis Internal name: |
x | |
Credit Internal name: |
Credit Internal name: |
x | x |
Description Internal name: Description |
Description Internal name: description |
x | x |
Description author Internal name: |
Caption writer Internal name: |
x | x |
Dpi Internal name: |
Resolution Internal name: |
x | |
Encoding Internal name: |
Video codec Internal name: |
x | |
Format Internal name: |
MIME type Internal name: |
x3 |
|
Height Internal name: |
Height (pixels) Internal name: |
x | |
Modified By Internal name: |
Checked in by Internal name: |
x | |
Modified On Internal name: |
Checked in Internal name: |
x | |
Publication Channels Internal name: |
Channel Internal name: |
x |
|
Source Internal name: |
Source Internal name: |
x | x |
In Use By Internal name: |
Checked out by Internal name: |
x | |
Keywords Internal name: |
Tags Internal name: |
x | x |
Line count Internal name: |
Line count Internal name: |
x | |
Name Internal name: |
Name Internal name: |
x | x2 |
Paragraph count Internal name: |
Paragraph count Internal name: |
x | |
Rating Internal name: |
Rating Internal name: |
x | x |
Size Internal name: |
File size Internal name: |
x | |
Type Internal name: |
Kind Internal name: |
x | |
Version Internal name: |
Version number Internal name: |
x | |
Width Internal name: |
Width (pixels) Internal name: |
x | |
Word count Internal name: |
Word count Internal name: |
x |
1 Content Source users must have edit permissions in Elvis for all fields that are marked as 'write'.
2 Changing the name of a file in Enterprise will rename the file in Elvis. The file extension will not be changed.
3 The MIME type is mapped to the corresponding MIME type Enterprise format.
4 Copyright marked is derived from the copyright field in Elvis.
Fields that are mapped when linking an asset
When an asset is linked to Enterprise (for example by adding it to a Dossier in Content Station), the following Elvis fields are mapped to corresponding Enterprise fields.
The Elvis fields are read-only and are updated automatically when the data in Enterprise changes.
Name | Description |
---|---|
Archived from Enterprise Internal name: |
A boolean value that represents if an asset is archived from Enterprise. |
Category Internal name: |
The name of the Category in Enterprise that the asset belongs to. |
Category ID Internal name: |
The ID of the Category in Enterprise that the asset belongs to. |
Enterprise created Internal name: |
The date and time when the link was created. |
Enterprise creator Internal name: |
The Enterprise user who created the link. |
Enterprise ID Internal name: |
The object ID of the asset in Enterprise. |
Enterprise System ID Internal name: |
The GUID of the Enterprise Server where this asset is used.1 |
Enterprise modified Internal name: |
The date and time when the metadata was modified. |
Enterprise modifier Internal name: |
The Enterprise user who modified the metadata. |
Publication Internal name: |
The name of the Publication (Brand) in Enterprise that the asset belongs to. |
Publication ID Internal name: |
The ID of the Publication (Brand) in Enterprise that the asset belongs to. |
Used in Enterprise Internal name: |
A boolean value that represents if an asset is used in Enterprise. |
1 An asset can only be used on one Enterprise Server at a time.
Fields that are mapped when placing an asset
When a linked asset is placed on a layout, various relations are established between the asset and the layout and the publication of which the layout is part.
The following fields are populated during this process.
Name | Description |
---|---|
Channel Internal name: sceChannel |
The name of the Publication Channel in Enterprise that the asset belongs to. |
Channel ID Internal name: sceChannelId |
The ID of the Publication Channel in Enterprise that the asset belongs to. |
Edition Internal name: sceEdition |
The name of the Edition in Enterprise that the asset belongs to. |
Edition ID Internal name: sceEditionId |
The ID of the Edition in Enterprise that the asset belongs to. |
Enterprise relations Internal name: sceRelations |
A JSON structure with relations of this asset as shadow object to Enterprise entities such as layout, Category, Publication Channel, Issue, page and On pasteboard.1 |
Issue Internal name: |
The name of the I issue in Enterprise that the asset belongs to. |
Issue ID Internal name: sceIssueId |
The ID of the Issue in Enterprise that the asset belongs to. |
Layout Internal name: sceLayout |
The name of the layout on which the asset is placed. |
Layout ID Internal name: sceLayoutId |
The ID of the layout on which the asset is placed. |
Page Internal name: |
The page number of the page on which the asset is placed. |
Placed on page Internal name: scePlaced |
A boolean value that represents if an asset is placed on an InDesign page in Enterprise. |
1 The equally named fields in this table are based on this JSON structure.
Enterprise fields without mapping
The Enterprise metadata property 'State" is deliberately not mapped because it is Enterprise specific and will be stored in Elvis when archiving files from Enterprise to Elvis.
Mapping custom Enterprise fields
Mapping an Enterprise custom metadata property to an Elvis metadata field can be done by configuring the configuration file of the Integrating Elvis 5 in Enterprise Server 10.
Mapping on Brand level
Info: This feature requires Enterprise Server 10.0.6 (or any higher version of Enterprise Server 10.0.x).
By default, the mapped field is available across all Brands in Enterprise. To make it available to specific Brands only, add the Brand ID to the mapping (see examples below).
Step 1. Open a Web browser and log in to Enterprise Server.
Step 2. In the Maintenance menu or on the Home page, click Brands. A page showing a list of all Brands appears.
Step 3. Click on the Brand for which you need the ID.
The Brand Maintenance page appears. The Brand ID is shown at the end of the URL in the address bar of the browser.
Example: Here, the Brand ID is 1:
|
Note: The mapping applies to all object types; it is not possible to map the custom field to a specific object type (meaning: not on Dossiers only, articles only, and so on).
Examples
More example mappings can be found in the configuration file.
Example 1 Here, the custom Enterprise metadata property 'C_MyCustomField' is mapped to the custom Elvis metadata field 'cf_myCustomField' for all Brands:
Example 2 Here, the custom Enterprise metadata property 'C_MyCustomField' is mapped to the custom Elvis metadata field 'cf_myCustomField', but only for Brand with ID = 1:
Example 3 Here, the custom Enterprise metadata property 'C_Instructions' is mapped to the default Elvis metadata field 'instructions' for all Brands:
|
Document history
- 25 September 2017: Added section 'Mapping on Brand level'.
- 25 September 2017: Updated section 'Examples' with an example showing how to map a field to an Enterprise Brand.
Comment
Do you have corrections or additional information about this article? Leave a comment! Do you have a question about what is described in this article? Please contact Support.
0 comments
Please sign in to leave a comment.