Twoje komentarze

Yes, BibBase doesn't understand Latex completely, only some of it's commands. Links to papers should be out in a url field (for details see here). For to-be-published papers we recommend using the to-be-correct bibtex entry type, in your case @article, and making the note read "To appear." or similar. Does that work for you?

OK, so after a lot of digging and testing with different tools I found that your server requires its requestors to send a 

'Connection': 'keep-alive'

header. Without it, it will drop the connection after some TCP packets manifesting in errors like "ConnectionResetError: [Errno 104] Connection reset by peer". So the abstracts only really matter in so much as they increased the file size beyond that limit.

I've just pushed an update to bibbase.org that makes sure that header is no included in all bibtex file requests and your original URL with the abstracts (papers.bib) is working now.

Thanks a lot for reporting. While most servers don't just hang up on requests, it is possible that some other users have been affected by this issue as well. Much appreciated!

For some reason, when BibBase retrieves your bibtex file, the content abruptly ends like this:

@inproceedings{saad2018trcrpm,
author          = {Saad, Feras A. and Mansinghka, Vikash K.},
title           = {Temporally-reweighted {C}hinese restaurant process mixtures for clustering, imputing, and forecasting multivariate time series},
booktitle       = {AISTATS 2018: Proceedings of the 21st International Conference on Artificial Intelligence and Statistics},
series          = {Proceedings of Machine Learning Research},
volume          = {84},
pages           = {755--764},
publisher       = {PMLR},
address         = {Playa Blanca, Lanzarote, Canary Islands},
year            = {2018},
keywords        = {probabilistic inference, multivariate time series, nonparametric Bayes, structure learning},
url_paper       = {http://

This doesn't happen when retrieving the file via wget or curl, so I'm debugging what is causing the difference. Stay tuned.

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"

Hm, yes, it seems that your site uses some CSS that conflicts with the one used by Bootstrap (which in turn is used by BibBase). The easiest way to avoid this issue would be to add the following to your CSS stylesheet:

#bibbase_header li.dropdown {
  display: none;
}

This will simply hide the drop-down menus. This would remove the ability to change the grouping, but the alternative would be a lot more difficult, because one would need to figure out which CSS rules conflict, and there is a lot to be checked.


It is on our roadmap to remove the use of Bootstrap on user pages. So this problem will go away in the near future. Perhaps it's best to just hide these menus until then as described?