Tus comentarios
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:
Sorry for the delay. I'm trying to debug this now, but it seems that the bib file is no longer there. Did you move it somewhere else? I found group_publications.bib instead, is that the one you want to use?
These two seem to both work fine:
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?
Could you give me a link to your page? Then I'll go have a look. Thanks.
I took a closer look at this and I'm a little puzzled. The latex escape sequences should have worked fine. For example, you can look at this publications and its corresponding bibtex: https://bibbase.org/network/publication/krstev-stankovi-obradovi-vitas-utvi-automaticconstructionofamorphologicaldictionaryofmultiwordunits-2010. There the escape sequences are translated fine.
BibBase handles a lot of latex but not everything. For instance, in your example of https://bibbase.org/network/publication/peressini-otviobuenoandstevenfrenchiapplyingmathematicsimmersioninferenceinterpretationi-2019, the textit is correctly handled. This morning I debugged the emdash and found a bug regarding it's parsing, which is fixed in development now and will be released soon. As for the single quotes, `...', those are not translated. But from what I recall you don't need to use them in latex anymore either. Modern versions of latex will handle ".." just fine.
For the ORBDE entry: the \url command is not translated by BibBase (at least yet -- seems like a good feature to add). But what you can do for now is to use url fields in your bibtex, e.g.:
@misc{peressiniORBDEv24,
Author = {Peressini, Anthony F. and Guastello, Stephen J.},
Date-Added = {2017-12-15 14:55:05 +0000},
Date-Modified = {2019-08-17 17:09:43 -0500},
url = {Software_(Menu_4,_fourth_item)_=http://www.societyforchaostheory.org/resources/ Software_(alternative)=http://academic.mu.edu/peressini/orbde/orbde.htm},
Title = {Orbital decomposition: A short user's guide to {ORBDE} v2.4},
Year = {2014}
}
All underscores will be replaced by spaces.
No, the bibtex file that your page uses is http://academic.mu.edu/peressini/MyPubsBibTex.bib and that one doesn't seem to be using Unicode characters, but latex escape sequences:
> curl http://academic.mu.edu/peressini/MyPubsBibTex.bib 2>/dev/null | grep Applying
Title = {{Ot{\'a}vio Bueno and Steven French. \textit{Applying Mathematics: Immersion, Inference, Interpretation}}},
Servicio de atención al cliente por UserEcho
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.