If we aggregate, for example, instance_id from the asset, to the item, to the collection then we list millions of possible values in the queryables options in the Collection record.
How can we avoid this whilst maintaining the existence of the queryable so that users/clients know it is an option?
If we aggregate, for example,
instance_id
from the asset, to the item, to the collection then we list millions of possible values in the queryables options in the Collection record.How can we avoid this whilst maintaining the existence of the queryable so that users/clients know it is an option?
Example collection content...
Could we just remove the
enum
section?