Use HTTP_ACCEPT: application/json to get JSON only.
Usage
The list query interface is for fetching properties from dlexDB for a given list of lexical items, as far as they have matches in the dlexDB table that you are querying.
Add the list_eq URL parameter one or multiple times to define a list like so:
http://sr/dlexdb/kern/cc0/list/?list_eq=VAL1[&list_eq=VAL2...]
If you want the matching against dlexDB entries to be case-insensitive, use the list_eqi parameter instead:
http://sr/dlexdb/kern/cc0/list/?list_eqi=VAL1[&list_eqi=VAL2...]
The result set will always contain all of your input items, whether they have a match in dlexDB or not. For items without match, the properties will be NULL. The result set may be longer than your input list if
- you are using the case-insensitive matching with the
list_eqi parameter
- you are querying one of the tables based on annotated types, where a given orthographic form may occur multiple times with different POS tags.
The list query interface does not offer any filtering options. In order to retrieve lexical items from dlexDB by filtering, use the filter query interface.
Selecting columns
In list query mode, the result set contains three or more columns by default:
*_citlist_showlistid- Numeric id assigned to your input item
*_citlist_showlisttoken- Your input item
- one or more columns from dlexDB, e.g.
typ_cit
- Properties from dlexDB. By default, the orthographic column that matches your input is displayed.
To select more columns, use the select parameter:
http://sr/dlexdb/kern/cc0/list/?select=COL1[,COL2...]
If using select, the default columns are discarded
unless you include them manually.
The default column selection is subject to change. Don't rely on it in your application!
Sorting
http://sr/dlexdb/kern/cc0/list/?orderby=[-]COL
The default sort order is subject to change. Don't rely on it in your application!
Limit and offset
http://sr/dlexdb/kern/cc0/list/?top=N&skip=M
