...
...
| Note |
|---|
The preview variations have been renamed to animated for clarity. We have not seen any project using it, but if that is the case, rename your “previewBig” variations to “animatedBig” for example. |
Table of contents for this release :
| Table of Contents | ||||
|---|---|---|---|---|
|
New Portal features
“Where is published my media?” tab
This new icon on the Portal opens a new screen where our DAM users can check where this media has been published on the web.
2 options are offered :
a reverse search options, that leverages the Tineye and Google Cloud APIs, and present a unified search result tab.
a DXM-based search, which scans the DXM logs to find which pages have been using this media for publishing using DXM urls coming from the content picker, the APIs, or direct links.
...
There is a back-office option for the reverse search also (not the DXM option).
This is enabled via the new PACKAGED_ReverseSearch plugin. Additional structures must be added to benefit from this feature, scroll down to the Added structures section for more information.
Sharing without download rights
When sharing a board that belongs to you, that was shared with you, or a public board, a new option offer to create a share link with no download options, only “view” options.
...
Customisable file names for exported assets
It is now easy to implement a Groovy script in the WXM_VARIATION_API to customize the exported filenames for downloaded files, board files names :
...
Wedia Baseline appearing in the menu
The Wedia Baseline is now always displayed in the menu :
...
New Content Picker features
Focus point definition when picking
In order to maintain the subject in focus even when cropping, it is now possible to define the focus point when picking an asset :
...
New Back-Office features
Dataview i18n language filtering
In order to give our users more flexibility about what they are seeing in the dataview, it’s now possible to show/hide all the i18n field from the dataview. A new button “Translations” is now displayed when i18n fields are present in the dataview. This is totally independant from the security and it’s working on what is already displayed.
...
New analytics display mode in the datalist
In the datalist, there is a new entry called “Analytic Dashboards”, it enables you to see all the left filters as graphics and therefore see how they are distributed in the current object.
...
To add a new graphic, just add the tag popinlist_search_group or popinlist_search_tree on any property you want to inspect, it will then be displayed on the left and a graphic will appear.
New dashboards and features on Analytics V2
List of the new features :
You can now select both “from” and “to” in the period filter.
A dashboard about search in the back-office has been added.
A dashboard about filters in the back-office has been added.
New filters are available for some dashboards.
On top of that, performances has been improved so dashboards loading is now noticeably faster.
New copy / paste values for multi-update
Previsouly, it was only possible to copy metadata from a given dataview and paste them to a new asset.
This copy/paste operation is now available in a multi-update.
A new button “Paste Values” appears when there are copied data in the clipboard.
...
All the non-empty metadata from copied asset are pasted to the selected assets, it then works as a classical multi-udpate.
The operation is automatically set to “Change”.
External video tracking
To keep track on where this video has been externally published, a new objet “externalvideo” that is linked to the default asset will now be filled by the MediaCloud API when the video is published on a YouTube channel :
...
Reverse Image Search
The plugin PACKAGED_ReverseSearch offer a new tab in the dataview of an asset, to trigger a Image Reverse search, powered by Tineye and Google Image search.
To trigger a new search, hit “register asset”.
...
When the search is complete, the list of the matches will be displayed with a line for each domain match :
...
Clicking on a domain opens a detailed list of matches for this domain :
...
New Admin features
Plugins list filterable and sorted by activation
...
Plugins can now expose errors that will be displayed in RED in the plugins list, and reported by the Status Page.
Structure changes
Added structures
Following structures were added to support asset reverse search feature.
reversesearch
reversesearchdomain
reversesearchmatch
reversesearchpage
Following structure were added to store external video IDs and status on Youtube.
externalvideo
Updated structures
massimportitem
itemisvalid (ADDED) Allows to store item validity against its target structure
child → activated
Not editable
default 1
Removed structures
Following structures were related to the Labs_Tineye plugin have been removed from the NAR:
tineyebacklink
tineyeresult
tineyesearch
wkftineyebacklink
wkftineyebacklinkaction
wkftineyeresult
wkftineyeresultaction
wkftineyesearch
wkftineyesearchaction
New operation of the API connection in session mode
...
This mode is called sessionful.
| Note |
|---|
Caution: note that there is a sessionful mode implemented in the WXM_RESTAPI plugin, which is also in session, but with the x-wedia-api-token cookie which is enabled by the sessionFul and allowSessionFul parameters. This is not the mode we are talking about here, which is enabled by the jsessionidcookie This mode is activated by default, with the sessionful plugin parameter. |
Cookies
The cookie used to maintain the session is JSESSIONID.
The x-wedia-api-token cookie is not used anymore. The , x-wedia-api-token-so and x-wedia-api-token-tk cookies are maintained.
A new cookie x-wedia-api-token-app is implemented to allow the return to the application connection in case of user disconnection.
Session sharing between Backoffice and Portal
The session (the JSESSIONID cookie) is shared between Portal and Backoffice. This means that logging into one connects to the other. And disconnecting from one, disconnects from the other.
Note that when a user disconnects from Portal as a user, he is automatically reconnected to the "Portal" as an application.
Compatibility
...
Normally, the server handles old cookies that may (especially x-wedia-api-token) interfere with the new system. There may be special unmanaged cases that require cleaning up the cookies in the browser.
Dataview personification
In the concern of giving to our users more flexibility about what they are seeing in the dataview, it’s now possible to show/hide all the i18n field from the dataview. A new button “Translations” is now displayed when i18n fields are present in the dataview. This is totally independant from the security and it’s working on what is already displayed.
...
New analytics entry in the datalist
In the datalist, there is a new entry called “Analytic Dashboards”, it enables you to see all the left filters as graphics and therefore see how they are distributed in the current object.
...
To add a new graphic, just add the tag popinlist_search_group or popinlist_search_tree on any property you want to inspect, it will then be displayed on the left and a graphic will appear.
Analytics V2
List of the new features :
You can now select both “from” and “to” in the period filter.
A dashboard about search in the back-office has been added.
A dashboard about filters in the back-office has been added.
New filters are available for some dashboards.
On top of that, performances has been improved so dashboards loading is now noticeably faster.
New multi-update operation
As now, it was only possible to copy metadata from a given dataview and paste them to a new asset.
This copy/paste operation is now available in a multi-update.
A new button “Paste Values” appears when there are copied data in the clipboard.
...
All the non-empty metadata from copied asset are pasted to the selected assets, it then works as a classical multi-udpate.
...
Changes to be made to the application tokens
| Warning |
|---|
It is imperative to associate an application token to a user. Application tokens with only a role cause an error when launching the Portal and block it. This problem will be corrected in 2021.5, version in which it will not be necessary to have a user associated with the application token. |