/alpha /sr /dlexdb /kern /typ /list

List query on table kern/typ

:
:
:
:
List items: (add or remove list items in the URL)
Reset all
typ_cit typ_freq_abs
Hans 11790
None None
Maria 6516

Use HTTP_ACCEPT: application/json to get JSON only.

48 columns in table /kern/typ

ColumnDescriptionData typeUser documentation
typ_cit String case-sensitive
typ_len int
typ_syls_cit String case-insensitive
typ_syls_cnt int
typ_freq_abs int
typ_freq_nor float
typ_freq_rank float
typ_div_con_abs int
typ_div_con_nor float
typ_div_con_rank float
typ_fam_abs int
typ_fam_nor float
typ_fam_rank float
typ_inf_abs int
typ_inf_nor float
typ_inf_rank float
typ_uniq_orth_strict_pos int
typ_uniq_orth_strict_neg int
typ_uniq_lemma_strict_pos int
typ_uniq_lemma_strict_neg int
typ_pia_avgcondprob_bigr float
typ_pia_avginfcont_bigr float
typ_pia_avgcondprob_trigr float
typ_pia_avginfcont_trigr float
typ_nei_col_hf_cumfreq_abs int
typ_nei_col_hf_cumfreq_nor float
typ_nei_col_hf_cumfreq_rank float
typ_nei_col_hf_cnt_abs int
typ_nei_col_hf_cnt_nor float
typ_nei_col_hf_cnt_rank float
typ_nei_col_all_cumfreq_abs int
typ_nei_col_all_cumfreq_nor float
typ_nei_col_all_cumfreq_rank float
typ_nei_col_all_cnt_abs int
typ_nei_col_all_cnt_nor float
typ_nei_col_all_cnt_rank float
typ_nei_lev_hf_cumfreq_abs int
typ_nei_lev_hf_cumfreq_nor float
typ_nei_lev_hf_cumfreq_rank float
typ_nei_lev_hf_cnt_abs int
typ_nei_lev_hf_cnt_nor float
typ_nei_lev_hf_cnt_rank float
typ_nei_lev_all_cumfreq_abs int
typ_nei_lev_all_cumfreq_nor float
typ_nei_lev_all_cumfreq_rank float
typ_nei_lev_all_cnt_abs int
typ_nei_lev_all_cnt_nor float
typ_nei_lev_all_cnt_rank float

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/typ/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/typ/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/typ/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/typ/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/typ/list/?top=N&skip=M