When updating an image in a Studio template the sorting isn’t persistent. For example, if I sort by person and add an image when I go back to change the image to a new one I need to sort for that person again. This lack of memory is pretty unproductive.
Solved
Studio: Persistent Search / Category Terms
Best answer by Marie Lunney
Hey
Use smart filters when you want to dynamically narrow down search results based on metadata, like region, asset type, or campaign. They're ideal for flexible, on-the-fly filtering without predefining a group of assets, and they sit at the top of the asset bank. For example, if you want to work from any images available for public use in France, set up a smart filter for that. Set this up in your DAM first and make sure the underlying metaproperties you're using have the setting 'API field' enabled so they show up in Universal Compact View (UCV) aka the image/asset picker in Studio.
Use collections when you need to group specific assets together. They're static and manually curated, so they're great for a predefined set you'll access repeatedly, like images from your most recent campaign photoshoot that you want to use in Studio.
So for a Studio project: if you're working from a fixed set of assets, build a collection first and pull from it as you go, updating or deleting it once the project's done. If you're working more broadly and want to keep filtering on the fly, a smart filter is the better fit.
Let me know if this helps!
Hi
Here’s a couple of screen shots. While updating a template I can sort my images to find the right one. This works well. Then I add that asset to see how it looks in the design.
If I then design that I don’t want to use this image, but want to use another image, perhaps of the same person, or from the same collection, or realistically that has all of the same filters applied I can’t because those filters aren’t persistent when I click back into the image edit.
Hey
Use smart filters when you want to dynamically narrow down search results based on metadata, like region, asset type, or campaign. They're ideal for flexible, on-the-fly filtering without predefining a group of assets, and they sit at the top of the asset bank. For example, if you want to work from any images available for public use in France, set up a smart filter for that. Set this up in your DAM first and make sure the underlying metaproperties you're using have the setting 'API field' enabled so they show up in Universal Compact View (UCV) aka the image/asset picker in Studio.
Use collections when you need to group specific assets together. They're static and manually curated, so they're great for a predefined set you'll access repeatedly, like images from your most recent campaign photoshoot that you want to use in Studio.
So for a Studio project: if you're working from a fixed set of assets, build a collection first and pull from it as you go, updating or deleting it once the project's done. If you're working more broadly and want to keep filtering on the fly, a smart filter is the better fit.
Let me know if this helps!
+2Hi
yes,my team is a big Studio user 😊 and during my work in Studio, I’ve made a lot of use of both collections and smart filters – they definitely help make the workflow more efficient.
One thing I would personally appreciate, though, is the option to somehow highlight or pin collections that are specifically intended for Studio. Some users can have quite a lot of collections – in my case, I share different types of content and information across multiple teams – so finding the right Studio collection can sometimes take a bit of time. Having a way to mark or prioritize those collections directly in the asset picker would make things even easier. So maybe a small tip for the Bynder crew 😊
We also use a “Studio” option within our metaproperties, which helps us filter and identify assets and different components intended for use in Studio. Combined with smart filters, this has been another useful way for us to keep things organized.
@Drew Unruh – would either of these approaches help with your workflow as well?
First, love the engagement here! Yay, community.
We’re already using Collections, and that’s certainly a win. These are great suggestions, but certainly still a work around for a persistent asset selection option. Even when using collections the selection resets every time you add a new image and therefore you have to go in, click collections, click the collection itself, find the new image and add asset.
None of this is ruining our days :) but persistent selection would certainly make the UX better and easier.
Login to the community
No account yet? Create an account here!
Bynder Employee SSO
Bynder Employee login hereor
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.