Filtering based on custom field (not author name or year)

Ali Nasseri 4 years ago updated by Christian Fritz 4 years ago 6

I am trying to filter a bibbase generated bibliography based on a "keywords" or "supported" field. This is the custom script I use: 

Specifically, I append something like "filter=support:D3M" or "filter=keywords:D3M". Unfortunately, the filtering does not work and nothing is shown in the final output.

I noticed that my script was not posted, so here is the full code:
<script src="https://bibbase.org/show?bib=https://raw.githubusercontent.com/plai-group/bibliography/master/lab_publications.bib&jsonp=1&theme=dividers&group0=year&group1=type&folding=1&filter=Keyword:D3M&">

Hi Christian,
Thanks a lot for looking into this.
Yes, it seems that the link itself works, but when put in as a script to embed the bibbase output, it does not show up on our page. I am using the script tag mentioned on the bibbase documentation. As an example, check this page where at the bottom I am using the script: https://cs-plai-2019.sites.olt.ubc.ca/research/data-driven-discover-models-d3m/
The script works without the keyword (like this page: https://cs-plai-2019.sites.olt.ubc.ca/publications/) but does not display anything on the page where we include the keyword entry.

In https://cs-plai-2019.sites.olt.ubc.ca/research/data-driven-discover-models-d3m/ it seems you are missing the &jsonp=1 argument. Can you try adding that? Without that it won't work for sure. Once it's added we can debug further.

Testing using curl gives a response that seems to contain data, so that's promising:

curl "https://bibbase.org/show?bib=https://raw.githubusercontent.com/plai-group/bibliography/master/group_publications.bib&theme=dividers&group0=year&group1=type&folding=1&filter=keywords:D3M&jsonp=1"

So it seems that my original implementation had some semicolons after each & (Considering I copied the original from the documentation, I think this was added by my CMS); the code works in that situation generally, but it would not work when filter is added (I assume it messes up the parsing somehow).

Thanks a lot for taking the time for looking into this. All resolved! :)