Autocomplete function on a field. Internally it is using the terms component in solr.
Autocomplete in advanced search forms
Show a list of facets. See source code for more information
This is used for the facetvalues popup when clicking on 'more' in the facet list.
Return instant search result. This method has only one option, `query`. Used for instant search results in the frontend.
NOTE: At this moment the instant search results are handled by the default per-database request handler. The solr config does have a per-database instant request hanlder, but it's use hasn't been implemented yet. This means that all options listed in method `search` can be used here, but this is not intended.
Instant results in `search in all databases`. Used fieldset is `searchlist`.
Returns a list of available databases in RKD Explore.
Note: Internally, `portraits` is not a database but a subset of `images`, (where field `isportrait` in `images` is `1`). Portraits has it's own request handler in solr.
Returns a list of configured facets per database.
For each database the facets have been configured. The configuration can be found in the source code. It is in the fashion of a solarium facetset. When providing facet parameters as an option in -ie the search method, the facet parameters are merged with the configuration.
NOTE : This method doesn't reveal details about the facet configuration, like their type. This can be found in the source code (database configuration).
Returns a list of fields in a database,as it is configured in the source code.
Note: it doesn't reveal details about each field. Look in the source code.
Returns a list of available fieldsets per database and the fields they return.
For each database, a number of `fieldsets` have been configured. This defines which fields should be returned in the response. This doesn't affect which fields are searched.
Note: fieldset `detail` has no fields defined, it will return all fields in the database.
Returns a single record. Parameter id is priref.
For content in permalinks and direct links to detail records. Always in html format and requested server side.
For all simple and advanced searches.
Note: The frontend is using an api call with fieldset=facets to retreive the facet list in html format (to show on the left side of the resultlist). This means that 2 api calls are done, one for the result list and one for the facet list.
Returns advanced search forms in html format.
Frontend gets advanced search forms.
Returns suggested searches based on a search query term. Internally it uses the `did-you-mean` request handler.
`Did you mean` suggestions when a simple search query doesn't return results.
Returns a single template
Returns Mustache templates for minimal, brief and searchlist views. (Searchlist is used in the instant search results in frontend). Detail views have no mustache templates, but are returned in html or json format.
The frontend loads the templates in the head. Search request in the result view are done with ajax, the response is in json. The template is rendered locally.
Rkd has a number of thesauri, stored in adlib databases. They can be requested using an adlib Api. This api is not reachable for the world, the rkd api provedes a port to it. The following methods can be used. Returns html. For thesauri `exhibitions` and `auctions` links to related results in the databases are added.:query (string/int) string value of term, or priref of term.
Thesaurus popups on clickable terms in detail view. The ajax calls in a detail page are done to the frontend, and the frontend does a server side call to the api.
For each field a label and description can be added, in multiple languages. These are stored in a mysql table (`fieldtags`) in the Rkd application. The fieldlabels and descriptions are used in the following places:
The frontend administrator section has an interface for editing these fieldlabels an descriptions. The frontend uses the api to store them. See also the FieldtagsController in the source code.