Open arildm opened 1 year ago
Tested the API. It doesn't support not-matches-<egenskap> but it works with not-<egenskap>, for instance: https://libris.kb.se/find?q=*&and-matches-instanceOf.subject.%40id=https%3A%2F%2Fqueerlit.dh.gu.se%2Fqlit%2Fv1%2Fua71em06¬-instanceOf.subject.%40id=https%3A%2F%2Fqueerlit.dh.gu.se%2Fqlit%2Fv1%2Fdk34ho21&%40reverse.itemOf.heldBy.%40id=https%3A%2F%2Flibris.kb.se%2Flibrary%2FQLIT&_sort=-meta.modified&_offset=0&_limit=20 It means that the NOT'ed term is matched exactly, not hierarchically. I'm not sure if this covers most usecases, or if we need to ask KB to support not-matches-<egenskap> as well.
not-matches-<egenskap>
not-<egenskap>
Tested the API. It doesn't support
not-matches-<egenskap>but it works withnot-<egenskap>, for instance: https://libris.kb.se/find?q=*&and-matches-instanceOf.subject.%40id=https%3A%2F%2Fqueerlit.dh.gu.se%2Fqlit%2Fv1%2Fua71em06¬-instanceOf.subject.%40id=https%3A%2F%2Fqueerlit.dh.gu.se%2Fqlit%2Fv1%2Fdk34ho21&%40reverse.itemOf.heldBy.%40id=https%3A%2F%2Flibris.kb.se%2Flibrary%2FQLIT&_sort=-meta.modified&_offset=0&_limit=20 It means that the NOT'ed term is matched exactly, not hierarchically. I'm not sure if this covers most usecases, or if we need to ask KB to supportnot-matches-<egenskap>as well.