We are introducing Uplynk Search 3.0, which enables much more powerful search capabilities for assets. Uplynk Search 3.0 allows for sophisticated browser-like searches as well as providing for searching of metadata.
Uplynk Search 3.0 is optimized for full word searching. So, if you are searching for a partial string, you need to add * characters as wildcards. Partial searches will be slower than full word searches.
Here are some examples of the new schema:
Query: test beam
Result: assets that have the words test or beam in any of the indexed fields in order of the highest search score
Query: name: spiderman
Result: assets where the desc field contains the word spiderman
Query: *id: d3de**
Result: assets where the _id field starts with d3de
Query: external: m, name: +red -blue*
Result: assets that have an External ID that starts with m and must contain the word red but must not contain the word blue
Query: meta: foo=bar
Result: assets that contains value bar where the metadata key is foo
Query: meta: My Privacy=private
Result: assets that contain meta key of My Privacy with metadata value private. Note that metadata keys are case-sensitive.
Query: name: "the natural"
Result: assets where the desc field contains the phrase the natural
There is pop-up help with an “i†icon in the search box to help remember this new syntax.
Uplynk Search 3.0 works for all content searches (e.g. Playlist Builder), but the “i†pop-up help is only on the main content search.
When searching metadata, Uplynk Search 3.0 can only search for strings, not numerical values.
The backend for GET /api2/asset/list has been updated to use Search 3.0 so it will automatically do wildcard searches. This may impact the performance you are used to seeing, depending on your library size.
Documentation available below: * Content Management
Contact Support or your Technical Account Manager with any questions.