Zeticon is proud to present version 21.1 of the Mediahaven platform. Please read more info about the new functionalities, improvements and fixed bugs below.
...
Evaluation flow of a collection
The evaluation flow has been extended. You can now also evaluate an entire collection. This means a user which has no rights to publish, can now submit a collection with its underlying children. Another user can evaluate the entire collection and publish it or he can decide to reject it for correction. During the correction task, the metadata and the content of the collection can be corrected and submitted again.
Introduction of ‘Albums’
We’ve introduced a new metadata field called “Album”. In this field, the system uses a metadata tag (the name of the album) to make items belong together to one or multiple folders or albums. The difference with a Mediahaven2.0 collection is that there is no inheritance of metadata and that an item can belong to multiple albums.
Support specific user controls
We’re now supporting a user control to define a list of values in one field, for example the metadata field ‘Album’. We’ve also improved the multi-select user control which is now a dropdownlist when there are a lot of values.
Notifications
Notifications provide the user with information about certain objects. They ensure that the user knows what has happened to a particular object, but do not mean that any action is required from the user. The most recent notifications are displayed on the dashboard, but the user can easily read all notifications in a seperate list.
Some new features during evaluation
The user can now see the previous motivations when evaluating an object. This helps the user to focus on the right things during a second or third evaluation round.
Also during the evaluation, the user who is doing the evaluation is now able to direclty directly modify some metadata fields.
Automatically generated tags/keywords
We’ve developed a proof of concept about automatically generating tags/keywords. For this proof of concept, we’ve chosen to integrate with a partner which is providing the software to generate the tags. In Mediahaven, you’re now able to see those automatically generated tags. You’re also able to accept or reject those automatically generated tags.
...
From release 21.1 the REST API 2.0 is the new reference. The Mediahaven REST API is self documented and always accessible (https://<Your MediaHaven URL>/mediahaven-rest-api/v2). The differences between v1 and v2 of the REST API can be found here.
...