URL query param searching on fields
For example being able to pass ?search_name=Ben
is a common feature in applications and would be useful to provide within the core
Stretch goals
- There are different ways to search a field, we could ideally provide a way to override that (e.g. defaulting to basic search, but a package developer might want to use full-text search)
- Providing search on "virtual" fields (e.g. annotated columns), could be useful, too. We should consider where in the process the search is applied, for example to give package developers an easy place to prepare the queryset. Another common way to provide behavioural fields is during serialization via Rest Framework's
MethodSerializerField
. This would be much harder to support, because it would be more efficient to apply basic search to a (db-level) queryset than to serialized JSON-LD
Future developments
- More complex queries than this, directed by the client-side, are moving into the territory of tools such as GraphQL. There has been some interest in the community in using GraphQL with RDF graphs