Curator Clip Link (3.5.1.176)

This hot-fix addresses three bug fixes and feature extensions:

• Folder permission editing will no longer close after an individual change is made.
• Fix for group removal in Advanced Search pop-up.
• Security fix removing the remaining reference to an old library (moment 2.24.0).

Curator Logger (2.5.1.33)

• This version provides a security update of the remaining outdated library to the latest secure version (moment).

Curator for Adobe (3.5.1.43 (PC) / 3.5.38 (Mac))

• As of this release, a few bug fixes have been made in order to improve right-click functionality when selecting a folder.

Curator File Service (1.4.1.143)

This update of File Service provides improvements and bug fixes to handling of File System stores and related records, including the following:

• When creating or editing a file system store, File Service no longer attempts to create the root directory on disk.
• Fixed a bug where multiple identical v1 files were being created.
• Fixed a bug where unnecessary new storages were created when moved files were synchronised.
• File paths stored as URLs now synchronise in the same way as network share paths matching appropriate store.
• When doing metadata synchronisation, File Service will now check to ensure subdirectories match existing stores before creating a new one. 
• File system stores (Windows file system) will now be made case insensitive by default when doing metadata synchronisation.
• Fixed a bug where duplicate messages were appearing in the Activity Log.

XFer Agent (2.15.1.21)

• A bug has been fixed where upload to Azure would fail in certain instances.

Curator Gateway (1.10.2.216)

Requirements

• On installing or upgrading to this release, you must upgrade this service to the version listed above or later.
• Please note that when upgrading to this release, you must ensure Microsoft ASP.NET Core Hosting Bundle is updated to version 7.0, followed by restarting IIS.
• As with version 1.9, RabbitMQ must be installed and connection details must be configured in Curator Gateway. Curator Gateway will now automatically go to the RabbitMQ configuration page when the System Administrator logs in and RabbitMQ was not configured.
• Two pre-requisite settings have now been added to the web.config file and no longer need to be set manually in IIS following this release:
  • <httpRuntime maxRequestLength="1048576" />
  • <requestLimits maxAllowedContentLength="4294967295" />

Updates

This release provides improvements and extensions for the External Identity Providers so that a wider range of the providers can be accepted:

• Improvements have been made to Open ID identity provider:
  • It is now possible to configure authorisation code flows and these can match the behaviour of different providers by selecting to either send of Authorisation Header or send Secret in the request. 
  • Users can receive additional claims from the identity provider when the Get Claims From User Info Endpoint is selected, and the name of the claim that contains group details can also be set.
• Improvements have been made when configuring a SAML2 identity provider.
  • In addition to the identity provider's Entity Id, the Curator Gateway Entity Id (Entity Id of the Service Provider / SP) will now also be configured and sent with any authentication requests. 
  • Minimum Incoming Signing Algorithm option can be set to a minimum strength of the acceptable incoming signing algorithm. 
  • Outgoing messages can be signed with a named certificate.
• A fix has been made for when enabling multiple LDAP providers simultaneously. Further small fixes have been made to the configuration of LDAP and SAML identity providers.

This release provides new features in user management:

• All passwords are now hidden when being typed in. There is a button provided to copy the password once set.
• When working with rows in lists the whole line over which the mouse is placed is highlighted.
• It is now possible to clone workgroups and permissions from an existing user when creating new invitations or to clone workgroups from one active user to another.
• It is also possible to select a workgroup and add users to it as well as to select a user and provide them with new workgroup memberships.
• It is also possible to set or modify the user(s) time-limited access, after which they will be automatically locked out.
• User's email, username and name can be modified for any active user
• Fixes an issue with temporary lock-out triggered after making more than the set number of allowed failed password attempts and manual user reactivation.

Navigating to Curator Gateway Client for the first time after deployment will generate all required client secrets. This serves the improved security of peer verification between Curator services which necessitates client secrets for all services.

When upgrading Curator Gateway from a version older than 1.9, System Administrator will be redirected to the Organisation page if RabbitMQ connection details are not yet set and will have to set them to successfully save the details. If RabbitMQ details become invalid at any point, for example, the host to which RabbitMQ was deployed was changed, Curator Gateway will not start. Please see the Upgrade Guide for troubleshooting instructions. Curator Gateway is now a publisher of messages to RabbitMQ, so it is important to set it correctly before Curator Gateway comes into use. 

Curator API has been updated in line with using asset references and migrated blobs.

API routes can now have white- or blacklisted IP addresses.

Curator Server (4.3.2.92)

• On installing or upgrading to this release, you must upgrade this service to the version listed above or later.
• The Curator Server API for the delete has been altered. As a result of this, the old version will not work and workflows will need to move either to Remove (from Collection) or deliberately to use the new Delete API. This is so that the references can be removed on demand but delete can still stop if there are still references to the file to be deleted.
• As of this release, the Curator System Administrator link will no longer be available to ADMIN (READ ONLY) users from Gateway.
• As of this release, Clip Select has been de-supported and removed from Curator Server's database.
• Siphon Service and SVUtils clients and resources will now be removed out of the box and on upgrade.
• Client and API routes will now be created in an inactive state for Metadata Central admin, removing the need for these to be manually created via the execution of a manual script.
• Metadata and panel configuration improvements have been made in support of new IPV Curator For Adobe 3.5.1.39 (Win) \ 3.5.1.34 (Mac) (3.5.2) / IPV Curator For Adobe 3.5.1.37 (Win) \ 3.5.1.31 (Mac) (3.5) functionality.
• Routing has been added for Curator Connect updates in support of the auto updater functionality introduced in Curator Connect 2.0.1.279 (Win) \ 2.0.1.264 (Mac) (2.0) / Curator Connect 2.0.1.251 (Win) \ 2.0.1.259 (Mac).
• Folder improvements have been made in this release, including the addition of a search option to return assets in collections of subfolders; and the addition of a method to set a deletion date recursively for folders and their contents and assets and their clip marks, this is controlled by setting the Recursive option to True.
• This release provides support for Clip Link 3.5 download feature through the creation of a new download role.
• Provides support for Curator 3.7 and later's use of asset references where copies were used previously by renaming the Delete API, deprecating the previous version of the Delete API and substituting the new API to ensure the original asset will not be deleted.
• An option has been added to prevent deletion errors where assets are not found or are not available in a folder.
• Workflow support has been improved in cases where assets are no longer in a collection and another attempt is being made to remove it from the collection.
• In addition to this, a number of bug fixes have been made in this release to improve the searching and displaying of data across the Curator applications.

Curator System Administrator (2.2.1.82)

• The Metadata View filter will now match on a unique name, not only on the display name.
• Fixed an issue where an error was being returned when creating a new folder.
• A number of improvements have been made to the Configuration page for this release, improving the overall look and feel and security of the code. 
• The improvements in the display of the Metadata page have been made  to allow sorting on some columns. You can sort on Display Name, Unique Name, Data Type within Metadata Names table and on Workgroup Name within Permissions table.  Please note that you cannot sort on Asset Type, and Data Type sorts alphabetically.
• Some libraries have been updated to keep them free of vulnerabilities.
• As of this release, folder management functions which previously existed in Curator System Administrator can now be done in Clip Link. This functionality has now been removed from Curator System Administrator. For more information, please refer to the Clip Link guide.
• A few bug fixes have been made in this release including a fix for scrolling issues in the Configuration page, protection from inadvertently overwriting existing metadata names, a fix for view switching using the ‘Used in these Metadata Views’ buttons, a more appropriate error message when attempting to change multi-values and minor graphical fix in Mac Safari for the alignment of Metadata Names and Views.

Metadata Central (3.1.3)

• This release should be paired with Curator Logger 2.4.1.33 or newer, but we recommend using it with Curator 3.7.2 suite and Curator Logger 2.5.1.32.
• As of this release, there is no longer a need to execute a separate deployment script for Metadata Central Administrator 2.0.1.86.
• This release provides an ETL update for compatibility to updated Opta Sports data streaming, and provides the ability to simultaneously deploy the Teragator to serve SKOS and Team Sports data. 
• This release also provides a set of test data to verify that the ETL ingest from the watch folder is working correctly.
• A number of improvements and bug fixes have been made for this release including provision of the version API call, removal of unnecessary logging that could cause a crash during startup and stopping the MDC Admin API createitem from being able to create records with insufficient parameters.
• When updating from before version 3.0, the Neo4J databases schema will be upgraded during startup of the Metadata Central. The Metadata Central Teragator service will start, but it will not be active until the Neo4J schema upgrade is completed and the cache loaded to memory. The Teragator is ready to work when the log file states "Finished system configuration. Service is now available." on a separate line of the log file.

Azure Video Indexer 

Using Microsoft Azure, Curator can now be configured to recognise celebrity faces, or to identify custom faces from a library of images as well as to label recognised objects and to create subtitling in Audio recognition process. It is now possible to analyse more than one set of insights (faces and labels) in the same video indexer workflow. For more information on installing the Azure video indexer, please refer to this article. For more information face and object recognition, including building an image library to recognise faces, please refer to this article. For more information on obtaining subtitles for videos, please refer to this article. 

Curator Connect 2.0.1.279 (Win) / 2.0.1.264 (Mac)

Windows-only operating system updates:

• Certificates placed into the “Intermediate Certification Authorities” store will now be picked up and used as a source of trusted certificates by default.
• From the local config file (com.IPV.CuratorConnect.config.json), you can now define extra certificate stores - if these are required, they will need to be added manually.
• Certificate stores can also now be defined via an environment variable that has also been added (for ease in controlling via group policy).

Configuration updates:

A number of configuration changes have been made independently to both the Curator Connect 1.6 and Curator Connect 2.0 code bases.

• This release allows you to configure new file2azure Transfer Type Destination Settings and Azure Blob Storage Settings via Curator System Administrator (com.IPV.Connect.config.json v2.2.12 included in this release),
• You can prevent uploading files with special characters via setting a RegEx in a new Curator System Administrator section, 
• It is possible to install and use a local PouchDB database in order to view historical activity information including ingest attempts and retry capabilities that are preserved between changes in the client version on disk (installation of PouchDB requires node.js).

Auto updater

Auto updates can now be configured for Curator Connect. For more information on this, please refer to this guide. 

Curator Clip Link (3.5.1.174)

• On installing or upgrading to Curator Suite 3.7, you must upgrade this service to the version listed above or later.
• This release provides compatibility with reference-based asset placements in Curator 3.7.2, and must replace any 3.4 version of Clip Link when working in a 3.7.2 environment.
• The layout of the video playback controls has been updated to allow for greater precision when viewing and editing video clips. You can now select sections of a video to create a sub-clip from by dragging in- and out-points directly within the video player, and are able to precisely control the playback speed.
• Additionally, plugin processes can now be added to the same Activity Log and icon as previously used in IPV Curator For Adobe and News Extension.
• Users will now be able to download single-source hi-res assets from Clip Link using the new Download role.
• Quick Search suggestion scan can also be expanded beyond the default Name metadata by configuring the following in the web.config: <add key="BasicSearchSuggestions" value="[MetadataViewContainingFields]" /
• For more information on Clip Link, please refer to this guide.

Additional improvements include:

• The ability to manually refresh individual tab contents.
• System Administrators can now edit metadata for assets contained within Trash.
• Changes have been made to Collections so that users can double-click them and see all the assets within like they would within a folder whilst preserving the right-click ability to Preview in a full screen window.
• Users can now drag and drop into a Collection provided that both assets are within the same window/tab.
• When confirming restoration from Trash of single items the restoration parent folder is now listed in the GUI, and the double-click Preview overlay window has now been replaced with a full-screen Preview under a new tab.
• Various bug fixes have now been made.

Curator Logger (2.5.1.32)

• The asset player has been revamped in this version to match the player found in Clip Link, allowing for enhanced precision when editing video assets.
• In addition to this, some libraries have been updated to keep them free of vulnerabilities.
• Logging is now launched solely by searching for and selecting assets in Clip Link and selecting the 'Open with Curator Logger' menu option, providing a faster and more powerful search and select experience.
• For more information, refer to this guide.

IPV Curator For Adobe 3.5.1.41 (Win) / 3.5.36 (Mac)

• On installing or upgrading to this release, you must upgrade this service to the version listed above or later.
• The asset player has been revamped in line with Clip Link for this release, allowing for enhanced precision when editing video assets, including the ability to mark in- and out-points and directly import these as a sub-clip to the Premiere Pro project bin (this does not save a sub-clip in Curator).
• This update also provides fixes for locally exporting non-MOGRT graphics and, for AME-panel, correcting timecodes generated for some R3D media.
• For more information, refer to this guide.
• Xml files (such as blob metadata) can now be uploaded or fetched to use File Service.
• In order for Curator for Adobe version 3.5 to use Productions created in previous versions of the product, it is necessary to migrate blob metadata via Curator File Service as a one time event. For more information on this, please refer to the Migrating Blob Metadata tab within the Curator File Service Configuration section of the upgrade guide.
• The Curator Server API for the delete has been altered. As a result of this, the old version will not work and workflows will need to move either to Remove (from Collection) or deliberately to use the new Delete API. This is so that the references can be removed on demand but delete can stop if there are still references to the file to be deleted.
• You will need to check that the Curator Server provided configuration version 3.2.0.16 for Curator for Adobe is present in Curator Service Administrator. If this is not present, it will need to be manually imported and its configuration checked/amended.
• Once the above points are satisfied, it is necessary for Curator for Adobe 3.4 to be upgraded to IPV Curator For Adobe 3.5.1.37 (Win) / 3.5.1.31 (Mac) in order to prevent conflict within the Curator system. As a part of this:
• You must manually remove the previous version 3.2.0.15 of Curator For Adobe configuration com.IPV.Extension.config.json via Curator System Administrator.
• You must also manually remove any version 3.2.0.15 com.IPV.Extension.config.json files from any <Curator Server Installation path>\Config\<configuration group>\Premiere Pro\Extensions folders.
• Inspect all Config folders in the Curator Server installation path e.g. C:\Program Files\IPV\Curator\Server\Config\ for any configuration groups that may have the version 3.2.0.15 of the Premiere Pro\Extensions\com.IPV.Extension.config.json file present within it. You will typically find at least one in the configuration group w[]-u[]-win[]-m[] for all users
  • i.e. "C:\Program Files\IPV\Curator\Server\Config\w[]-u[]-win[]-m[]\Premiere Pro\Extensions\com.IPV.Extension.config.json".

Web Plugins (1.11.1.9)

A number of web plugins have been reviewed and updated for this release in order to improve security and ensure the compatibility with Clip Link forming part of this release.

Workflows

An improvement has been made so that the index ID will now be stored when Azure Audio analysis fails after analysis.

Curator File Service (1.4.0.110)

On installing or upgrading to this release, you must upgrade this service to the version listed above or later with a default Upload Store defined.

• Credentials can now be added and autoprovisioned from a new Credentials section in File Service for Azure and AWS S3 storage types. Credentials can be used to establish a connection to the storage system(s), and can be shared between several stores. For more information on credentials, please refer to the Managing Credentials tab in the Curator File Service Configuration section of the upgrade guide.
• SSL options for RabbitMQ can now be set directly from the File Service installer.
• Curator File Service can now be used to upload xml files and fetch files. As a result of this, it is now necessary to ensure that both an Upload and a Download selection is set specifying one of the Stores defined in File Service.
• As of Curator 3.7, blob metadata will no longer be created in the database, instead using File Service to access files previously stored in the database, reducing the database storage size and subsequently allowing for Curator system function response times to improve. As a result of this, it is necessary to fully migrate the Curator File Service including blob metadata when upgrading from any system earlier than Curator version 3.7 to 3.7 or later, in order for the Curator system to work. For more information on blob migration settings, please refer to the Migrating Blob Metadata tab in the Curator File Service Configuration section of the upgrade guide.

Process Engine (3.1.1.56)

• On installing or upgrading to this release, you must upgrade this service to the version listed above or later.
• Both Process Engine Service AND Process Engine Agent Service need to be configured with the Process Engine Service Client Secret.
• This release provides a major change to the Process Engine Monitor website in order to provide a dashboard experience in line with the Curator Gateway website design, as well as a number of other GUI improvements.
• Several new activities have been provided for use against Azure storage and Video Indexer device, including the ability to get captions and results from the new Microsoft Azure Indexer Device in Device Director 5.19.1.78. Additional new activities have also been added to improve handling of files in File Service that were previously stored as blob metadata in the Curator database, and improve handling of assets and metadata. In addition to this, a number of bugs have been fixed in this release.
• As a result of changes made for this release, you must deploy core and (if applicable) Edit & Publish modules manually on upgrade as a compulsory step. Without a newly deployed core the 3.7 system will not work correctly.

A number of additional enhancements have been made in this release, including:

• Changes have been made to the way pagination works, ensuring the results table in the dashboard accurately displays the number of results returned.
•  A date range has been added to the Process Engine dashboard search, replacing the date submitted search option.

Device Director (5.20.1.33)

• On installing or upgrading to this release, you must upgrade this service to the version listed above or later.
• A few stability fixes have been made for this release, including resilience to timeouts when communicating with SoDa device.
• This release provides a new Azure Video Indexer Device featuring the ability to set a personal model for face recognition other than the default and adding support for transcription and the generation of VTT files and matching sub-clips.
• As with previous 5.19 hot-fixes, this hot-fix supports SFTP including proper password support for initial submission. We have updated the Xfer Basic Profile to allow two new optional parameters (XFERBASICUSERNAME & XFERBASICPASSWORD) that are transmitted along with an Xfer Basic Job. When these are provided the password will be encrypted, and they will be used for all ftp, sftp and ftps interactions. These will not be used for file system interactions at this time. Default profiles for Siphon and SpectreView will no longer be created out of the box.
• Subtle yet important changes have been made to the AME Device (please pair this with the IPV AME Panel v3.4.1.2 contained within IPV Curator For Adobe 3.5.1.39 (Win) \ 3.5.1.34 (Mac) (3.5.2)) so that:
  • If Device Director thinks there is a job, but there is no current job, then the job will be Failed and the Status message will read Job was not found in AME.
  • If Device Director thinks there is a job, but the current job is a different job, then the job will be marked as Complete as has previously been the case, but with the status message of Job was assumed to have finished in AME.
• Handling of the NotFound state during the initial stages of the job has been added so that this is treated as a transient failure unless the job is past the job start timeout (as configured in the profile).
• This release provides MySQL8 compatibility and allows for the setting of the MySQL port number during the installation process.
• The website has been upgraded to remove any reference to jquery-migrate that otherwise causes slowdown on air-gapped installations, and the size of session cookies has now been minimised by using a memory cache so that only a short session cookie needs to be sent.

XCode (4.4.1.3)

This version is the final Curator Service that can have the firewall exceptions feature disabled during start up on systems where this is not appropriate. This version also fixes an audio drift in proxies derived from ProRes video.

Xfer (2.15.0.20)

The access control list (ACL) will now be removed when Xfer is moving files within the same volume so that the privileges of the destination folder are assigned after the move as is with moves between volumes.

The Azure Account name and Account key are no longer required in the Device Director profile.

Curator Media Agent (1.2.0.6)

An issue has been fixed so that thumbnail generation errors are now contained to a single asset and its sub-clips, and other assets will not be affected.

Curator Gateway (1.9.1.102)

A number of user management enhancements have been made including the following:

• Ability to edit a user's details directly via the Users section:
  username, display name, and email address are now editable fields - using the edit icon to the right of each field allows you to edit these fields, save them using the save button, or press x to cancel your changes.
  Please note that assets that already have the username saved in metadata during ingest or logging will not be updated to reflect changes made.
• Ability to clone workgroups and permissions across from one user to another when adding new users via a new Add workgroups and permissions from an existing user option - this allows you to select a user to copy permissions and workgroups across from. 
• Improved UI for individual additions of workgroups to User's settings and adding users to Workgroups, it provides longer listings of possible values to choose from and is not showing the already assigned options.
• A fix has been made for when enabling multiple LDAP providers simultaneously.
• Further small fixes have been made to the configuration of LDAP and SAML identity providers.

Curator Server (4.2.1.82) Hotfix which replaces 4.2.1.78

• This update removes the Files tab in Curator System Administrator, completing the move of file permissions to Clip Link.

Curator System Administrator (2.2.1.82)

• Folder management functionality has been removed from Curator System Administrator as of this version and is now available in Curator Clip Link. 
• Some libraries have been updated to keep them free of vulnerabilities.

NOTE: This version requires the use of at minimum Curator Server 4.2.1.61 and Curator Gateway 1.9.1.50, but as usual should be paired with the latest versions of Curator Server and Curator Gateway that form part of the same suite.

Curator Clip Link (3.4.1.264)

• The layout of the video playback controls has been updated to allow for greater precision when viewing and editing video clips. You can now select sections of a video to create a sub-clip from by dragging in- and out-points directly within the video player, and are able to precisely control the playback speed.
• A number of display fixes have been made for this release.
• In addition to this, some libraries have been updated to keep them free of vulnerabilities.

Curator Logger (2.4.1.79)

• The asset player has been revamped in this version to match the player found in Clip Link, allowing for enhanced precision when editing video assets.
• In addition to this, some libraries have been updated to keep them free of vulnerabilities.
• Logging is now launched solely by searching for and selecting assets in Clip Link and selecting the 'Open with Curator Logger' menu option, providing a faster and more powerful search and select experience.

Curator for Adobe (3.4.1.38 (Win) / 3.4.60 (Mac))

• The asset player has been revamped in line with Clip Link for this release, allowing for enhanced precision when editing video assets, including the ability to mark in- and out-points and directly import these as a sub-clip to the Premiere Pro project bin (this does not save a sub-clip in Curator).
• This update also provides fixes for locally exporting non-MOGRT graphics and, for AME-panel, correcting timecodes generated for some R3D media.

Web Plugins (1.11.1.9)

A number of web plugins have been reviewed and updated for this release in order to improve security and ensure the compatibility with Clip Link forming part of this release.

Device Director (5.19.1.84)

A few stability fixes have been made for this release, including resilience to timeouts when communicating with SoDa device.

Xfer (2.14.1.61)

The access control list (ACL) will now be removed when Xfer is moving files within the same volume so that the privileges of the destination folder are assigned after the move as is with moves between volumes.

Curator Gateway (1.9.1.78) HotFix which replaces 1.9.1.58

• Curator is now compatible with MySQL version 8 as well as version 5.7.
• You can now configure alternate MySQL ports instead of just the default during installation.
• A number of security improvements have been made for this release.
• This 1.9 Hot-Fix release, as any from Curator Gateway 1.9.1.64 onwards, requires installation (if not done previously) of the Microsoft ASP.NET Core Hosting Bundle version 7.0 (with version 6.0 still installed) followed by an IIS Restart.

Curator Server (4.2.1.78) HotFix which replaces 4.2.1.70

• As of this release, Curator is now compatible with MySQL version 8 as well as version 5.7.
• You can now configure alternate MySQL ports instead of just the default during installation.
• You can now opt not to set firewall options during the installation process.
• A user agent can now be added to resource requests.
• Fixed Solr query generation issue where there are nested negative terms.
• If you have not already done so as part of upgrading to Curator Server 4.2.1.68 or beyond, you MUST delete and recreate the Solr curator and curator_activity cores when upgrading to this Curator Server version (even if the Solr core was already curator_2_6).

Curator System Administrator (2.2.1.74) Hotfix which replaces 2.1.1.29

• A number of back end improvements have been made to the Configuration page for this release, improving the overall look and feel.

Curator File Service (1.2.1.96) Hotfix which replaces 1.2.1.88

• As of this release, Curator is now compatible with MySQL version 8 as well as version 5.7.
• You can now configure alternate MySQL ports instead of just the default during installation.

Process Engine (2.19.1.70) HotFix which replaces 2.19.1.60

• As of this release, Curator is now compatible with MySQL version 8 as well as version 5.7.
• You can now configure alternate MySQL ports instead of just the default during installation.
• You can now opt not to set firewall options during the installation process.
• It is now required to enter a Client Secret when installing Process Engine in order to connect to Curator Gateway and Curator File Service APIs.
• Support for Azure Transcription Service when combined with new workflow module ‘Azure Video Indexer’
• Ability to delete from an Azure container, extending previous support for Azure Blob Storage (uploading and downloading)
• A number of security and bug fixes have been made for this release.

Device Director (5.19.1.82) Hotfix which replaces 5.19.1.61

• As of this release, Curator is now compatible with MySQL version 8 as well as version 5.7.
• You can now configure alternate MySQL ports instead of just the default during installation.
• You can now opt not to set firewall options during the installation process.
• Support for Azure Video Indexer, where combined with Xfer 2.14.1.58 and the new Azure Video Indexer workflow module.
• Extension of support for Azure Blob Storage, where combined with Xfer 2.14.1.58

Curator Connect (1.6.1.109 (Win) \ 1.6.1.113 (Mac))  which replaces 1.6.1.109 (Win)\1.6.1.106 (Mac) 

• This release is now certified for use with Mac OS Sonoma
• The 1.6 release requires the use of minimum Curator Server 4.0.1.131 and Curator Gateway 1.5.1.151.

Curator Clip Link (3.4.1.171) HotFix which replaces 3.4.1.132

• As of this release, folders and their permissions can now be edited and managed directly from within Clip Link itself by right-clicking on a folder tree or folder asset in the search results, offering the same functionality as previously found within Curator System Administrator. For more information on this, please refer to the Curator Clip Link Guide.
• NOTE: When upgrading to 3.6.8, to prevent searches potentially returning no results when running the search and report plugin, you may need to manually import the latest version of the Spawn - Search and Report workflow (this can be found in the "Curator Arrival 3.6.8\Additional items for Partners" folder in Dropbox) and add it to Process Engine. To do this, from Process Engine Monitor, go to Process Definitions, click Choose Files and select the latest version of the "Spawn - Search and Report" in the File browser pop-up. Once selected, select Import Definitions to update this workflow to version 1.4.0.

Curator for Adobe (3.4.1.34 (Win)\3.4.56 (Mac)) HotFix which replaces Curator for Adobe (3.4.1.30 (Win)\3.4.52 (Mac))

• This release of Curator for Adobe is fully compatible with Adobe 2024 applications.
• With a fix for importing assets from the Curator to set metadata on imported assets metadata
• Fix for fallback proxy import when Source Extension is not set on an asset
• Fix for importing sequences from within productions on Mac OS 
• Fix the management of import, the failed imports now offer a restore option.
• Updated Edit and Publish - Adobe module version 1.12.0.0 is included.

Curator Media Agent (1.1.1.13) HotFix which replaces 1.1.1.9

• You can now opt not to set firewall options during installation by manually setting the option in the service's configuration file before starting the service for the first time. 

XChange Manager (2.7.1.21) HotFix which replaces 2.7.1.11

• As of this version, AWS S3 devices can now be configured without the need to provide credentials (via the use of EC2 instance roles if the service is running within AWS)
• As of this release, Curator is now compatible with MySQL version 8 as well as version 5.7.
• You can now opt not to set firewall options during the installation process.

Xfer (2.14.1.58) Hotfix which replaces 2.14.1.57

• Identically named objects already stored in Azure Blob Storage will now be overwritten. operations are extended to allow the deleting of the objects, which requires Device Director 5.19.1.78 or greater.
• Xfer Agent is now capable of using FTP, SFTP and FTPS protocols when invoked as a job for Xfer Basic in Device Director 5.19.1.58, with authentication where appropriate which can be set in Xfer Basic profile or in the input details.

Curator Gateway (1.9.1.69) HotFix which replaces 1.9.1.58

This version provides a security update. This HotFix requires .Net Core Runtime Hosting Bundle 7.0 to be installed in order to resolve an unexpected error when checking out a Production within Curator For Adobe. .Net Core Runtime Hosting Bundle 6.0 must also be installed in order for File Service to run correctly. 

Curator Server (4.2.1.70) which replaces 4.2.1.68

This version fixes two issues. One with nested advanced searches with negative terms, and another where in resource API calls a userAgent field is required.

Curator Clip Link (3.4.1.132) HotFix which replaces 3.4.1.115

This HotFix fixes issues and provides a few extensions to the function of sub-clip/bookmark creation.

Curator Connect (1.6.1.109 (Windows)/1.6.1.106 (Mac)) Hotfix which replaces 1.6.1.102 (Windows)/1.6.1.106 (Mac)

This HotFix is for Windows only and fixes a number of operating system and configuration issues.

Note: The Curator Connect client app MUST HAVE WRITE ACCESS to the Mezzanine and Higher fidelity source material locations when using the Associate Mezzanines functionality. 

Curator Logger (2.4.1.33) which replaces 2.4.1.30 

This HotFix addresses an issue with rosters sometimes not being loaded when logging in Sports mode, as well as updating an optional deployment script necessary for logging in Sports mode, removing a bug affecting use of resource API for loading rosters in the "1. Team Sports Generic.sql" script.

Device Director (5.19.1.61) which replaces 5.19.1.34 

This version provides a security improvement. This HotFix makes changes only to the Device Director website.

Metadata Central (3.0.11)

This release provides API support for the newly redesigned Metadata Central Administrator 2.0.1.86 and speeds up the API used by Curator Logger in Sports mode, allowing operation with large databases of historical games and rosters.

Metadata Central Administrator (2.0.1.86)

This release provides a completely new application with the ability to review and alter the rosters present in Metadata Teragator's database.

Process Engine (2.19.1.60) which replaces 2.19.1.53 

This version provides a security improvement. This HotFix makes changes only to the Process Engine Monitor website.

XFer (2.14.1.51)

This new release provides a number of AWS S3 improvements, extends support for AW S3 VPC interface and fixes a bug affecting the copying of assets between S3 buckets.

Curator Logger (2.4.1.30) HotFix which replaces 2.4.1.27

• As of this HotFix, incorrect metadata will no longer be displayed when switching assets in media logging. The correct metadata will now display when switching assets.
• An issue has been fixed whereby when entering batch mode, asset metadata would be loaded into the controls (including when switching between assets in the batch).

Curator for Adobe (3.4.1.30/3.4.52) HotFix which replaces 3.4.1.27/3.4.47

• Latest checked in Production will no longer incorrectly display as checked out from the Productions menu.
• Users can now configure and manage multiple instances of Curator Gateway from within the Curator for Adobe extension and switch between different Gateways without having to log out and back in again using the Curator Gateway menu. Where multiple Gateways have been configured, a Gateway icon will be displayed from the Curator for Adobe menu from within the menu, showing the name of the active/in-use Gateway and allowing for different instances of Gateway to be viewed and selected when the icon is clicked. Using the Manage gateways section of the Curator Gateway menu, new Gateways can be configured, and existing instances of Gateway can be updated or deleted. 
  Where you use very little space to operate Curator for Adobe (less than half of the menu can be seen without scrolling) please expand horizontally before using the Manage gateways menu.

Curator Clip Link (3.4.1.115) HotFix which replaces 3.4.1.108

• An issue has been fixed whereby thumbnails would suddenly disappear during use until a user logs in again.
• As of this release, it is no longer possible to add duplicate instances of an identical asset to a collection.