Change Details

Media search will search for wikidata entities that match the search term, and then include those entities in its search for files. When a users scroll down the page to load more, it'll use those same entities to find the next set of results. Right now, this will cause that same search for wikidata entities (api call & search query) to happen, when we actually already knew the answer. These results should be stored in, and retrieved from, cache to reduce load & latency of follow-up searches (or next batch) with the same search term.

Media search will search for wikidata entities that match the search term, and then include those entities in its search for files. When a users scroll down the page to load more, it'll use those same entities to find the next set of results. Right now, this will cause that same search for wikidata entities (api call & search query) to happen, when we actually already knew the answer. These results should be stored in, and retrieved from, cache (whatever key-value store - probably redis?) to reduce load & latency of follow-up searches (or next batch) with the same search term.

Media search will search for wikidata entities that match the search term, and then include those entities in its search for files. When a users scroll down the page to load more, it'll use those same entities to find the next set of results. Right now, this will cause that same search for wikidata entities (api call & search query) to happen, when we actually already knew the answer. These results should be stored in, and retrieved from, cache (whatever key-value store - probably redis?) to reduce load & latency of follow-up searches (or next batch) with the same search term.