Open WolfgangFahl opened 2 years ago
Should the filter be added to the event series endpoint as e.g. ?bk=50
and only apply for the tibkat datasource ?
for a start yes
bk filter is now added
To filter for multiple bks separate them with ,
the filter is currently implemented as OR i.e. one of the given bk must fit a record.
The filter allows to search for the main class e.g. 54
or with subclass e.g. 54.75
/eventseries/AAAI?format=json&bk=54
for all tibkat records with at least one bk 54.*
/eventseries/AAAI?format=json&bk=54.75
for all tibkat records with at least one bk equal to 54.75
/eventseries/AAAI?format=json&bk=54,85.20
for all tibkat records with at least one bk 54.*
or one equal to 85.20
If the logic for the filter should change let me know
Great - how is a bk null value handled? It looks by default they are ignored - then it would be good to allow null values actively in the query - is that possible?
null values can now be included by adding null
or none
to the filter clause e.g.
/eventseries/AAAI?format=json&bk=54,null
for bk null values and bk=54.*/eventseries/AAAI?format=json&bk=null
for bk null values
allow to specify a basisklassifkation when searching for event series.