MySource Matrix has been superseded by Squiz Matrix. This site will remain available for archival purposes only; it is not intended as a current source of Matrix information. For all the latest on Matrix, including documentation and release information, visit the Squiz Matrix site.
[ Feature Request #4128 ]
A new function "setMetadataAllFields()" is now available in the JS API. This function takes a single array of field ids and their corresponding values to enable updating multiple fields for an asset in one request.
This provides performance gains over using multiple "setMetadata()" requests. Locks are acquired once and the Metadata Content is generated once for the asset instead of once per field. This function returns TRUE on success and FALSE on failure (eg; when failing to fill in a required field).
[ Feature Request #4130 ]
The command line script packages/search/scripts/reindexSearchIndex.php now allows multiple Root Nodes to be entered for reindexing.
The script can now be used as follows:
$ php packages/search/scripts/reindexSearchIndex.php `pwd` Enter the #IDs of the root nodes to reindex (space separated) or press ENTER to reindex the whole system: 123 456 789
A prompt will appear to confirm reindexing of each specified node.
[ Feature Request #4153 ]
A new option is available in Listing Engine assets such as Asset Listing and Search Page, to provide grouping by keywords.
Like existing grouping options, this can be configured from the Asset Grouping screen of these assets. The keyword used for the grouping is supplied without leading or training percentage (%) characters.
[ Feature Request #4155 ]
TRIM Saved Search assets now allow queries on custom TRIM metadata fields and allow boolean search logic between these terms to be defined.
A set of known metadata fields which is shipped with TRIM are provided in the TRIM Saved Search options by default. This can be expanded by requesting all available fields from the TRIM system, for use in search queries. A "Retrieve Now" button is available from the Details screen to retrieve these fields.
The Search Logic and Result Fields are expanded, and are configured from the Details screen. The layout is similar to that provided for Search Page assets. Fields may be grouped with a boolean operator, and each group is joined by another boolean operator.
For example:
Group 1: - Search field "AnyWord" for value "Fred" [ AND ] - Search field "Title" for value "Test" [ OR ] Group 2: - Search custom field "Status" for value "Yes"
Groups may be joined only by one common boolean operator, and "NOT" logic is unavailable.
Just like the Search Logic, Result Fields may be composed of standard or custom fields, or both.
[ Feature Request #4160 ]
A performance enhancement may be evident on systems with large asset trees and/or many links pointing to a particular asset.
[ Feature Request #4158 ]
Minor notices such as "file changed as we read it" are now suppressed, to avoid these being sent by email from backup routines scheduled by cron.