Documents may have associated numeric values, the most common of which would be timestamps (e.g. blog posts made on a certain date).
Morsels only indexes texts, but these can be mapped to integer values through some configuration (e.g. parsing a datetime string with a specific format into a 64bit unix timestamp).
On the API side, there could be support for:
less than, greater than, in between operations (1 < x < 1000)
sorting results by integer fields instead of BM25
On the UI side,
before/after dropdowns specifically for date times could be supported. (e.g. Any time vs After Dec 20 2005)
a sort-by dropdown could be supported. (e.g. by relevance, X field or Y field)
In terms of priority, timestamp fields should come first. The use case for generic numeric fields in static site search may be less common.
ang-zeyu
commented
1 year ago
This could be a generalisation of #4.
Documents may have associated numeric values, the most common of which would be timestamps (e.g. blog posts made on a certain date).
Morsels only indexes texts, but these can be mapped to integer values through some configuration (e.g. parsing a datetime string with a specific format into a 64bit unix timestamp).
On the API side, there could be support for:
1 < x < 1000)On the UI side,
In terms of priority, timestamp fields should come first. The use case for generic numeric fields in static site search may be less common.