search

CDRH / api

Codenamed "Apium": An API to access all public Center for Digital Research in the Humanities resources
https://cdrhdev1.unl.edu/api_frontend
MIT License
3 stars 1 forks source link

build sorting assumptions into api_bridge not api #20

Closed jduss4 closed 6 years ago

jduss4 commented 7 years ago

the users should only get elasticsearch defaults when querying the API, but since we already know that if there is a q then we should sort by relevance descending, if not then title asc or date asc, etc, we should build those assumptions into api_bridge.

something else to consider: do blanks go at the top or bottom of search results? See: OSCYS project, which wants n.d. in a specific place

jduss4 commented 7 years ago

I ended up putting some of these into orchid to indicate assumptions through UI. For example, that if query and no sort, then must be relevance desc, etc. Should revisit these assumptions and make sure that they are perpetuated through bridge and any other places they might be showing up (like in elasticsearch's behavior itself).

jduss4 commented 6 years ago

I think that I disagree with my first statement about using Elasticsearch defaults, since if this is designed to be backend agnostic, we should communicate default behavior to the users clearly and not rely on elasticsearch fallbacks.