search

cedadev / search-futures

Future Search Architecture
BSD 2-Clause "Simplified" License
0 stars 0 forks source link

How to search properties with millions (!) of values #137

Closed agstephens closed 2 years ago

agstephens commented 2 years ago

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...

    "realm": {
      "title": "Realm",
      "type": "string",
      "enum": [
        "aerosol",
        "atmos",
        "land",
        "landIce",
        "ocean",
        "seaIce"
      ]
    },

Could we just remove the enum section?

agstephens commented 2 years ago

Initially, this is solved by the new and explicit 3-level collection description approach. Closing now as should not be a problem.