VidiCore 5.5 - New release
VidiCore version 5.5 is now live, and we have some new features and improvements we can’t wait to share with you. Find info on what's new, and how to upgrade to the latest version in this article.
Collection-to-collection joins
Collection hierarchy joins can be used to find collections based on their relationship with other collections. This can be used to find a collection based on it's `child`, `parent`, `ancestor` or `decendant` collections.
For example, to find collections that have a child collection with metadata `title=vidispine`.
```
PUT /collection
Content-Type: application/xml
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ItemSearchDocument version="2" xmlns="http://xml.vidispine.com/schema/vidispine">
<collection relation="child">
<field>
<name>title</name>
<value>vidispine</value>
</field>
</collection>
</ItemSearchDocument>
```
Collection improvements
In version 5.5, multiple relations between the same pair of collection and item, sub-collection or library are allowed. Each relation has a unique id (UUID), which can be used to reference relations
```
<CollectionDocument xmlns="http://xml.vidispine.com/schema/vidispine">
<id>VX-937</id>
<name>coll</name>
<content>
<id>VX-718</id>
<type>item</type>
<reference>bbd5adbb-4826-49cc-8f26-b87a266f09db</reference>
<metadata>
<field>
<key>myfield</key>
<value>somedata</value>
</field>
</metadata>
</content>
<content>
<id>VX-721</id>
<type>item</type>
<reference>9cf0a1ac-7c7b-49a7-acf9-33fce948e1aa</reference>
<metadata/>
</content>
<content>
<id>VX-718</id>
<type>item</type>
<reference>80eaad68-bcb7-4811-ada0-2fa1c366547c</reference>
<metadata/>
</content>
</CollectionDocument>
```
Other New features
Only return metadata in the timespans match the search query using the `interval=result` parameter.
Searching using cursors is now supported for non-generic timespans.
Upgrading from 5.4
Find information on how to upgrade from 5.4 to 5.5 here.
For a full list and more details on this release, see API Doc