Your comments
This is already supported when just leaving groupby blank:
https://bibbase.org/show?bib=https://bibbase.org/bibs/knuth_selected.bib&groupby=&hidemenu=true
It's recommended to use that with the sort option. See "Customization options" in the documentation for more details.
Hi Pascal,
Thanks for following up on this! By now we actually support this. It's actually one of the most popular features of our group plans. In those plans, all users in your organization have their own data sources that they can maintain in whichever way they like -- bibtex file directly on BibBase, a URL to a bibtex file hosted elsewhere, Zotero, Mendeley, DBLP. All those sources are merged, with deduplication, at query time when a query for the organization's publications are made.
Could you point me to your site? Then I can have a look. I definitely think you are on the right track though, of adding more CSS that defined font-sizes for the currently unstyled items. The reason you can't find any mentioning of font-size for the titles is because our theme specifically doesn't want to overwrite the style suggested by the surrounding web page. This is so that it is consistent with the rest of the page. Usually this is a benefit, but it sounds like your page defined certain styles that don't make much sense. I've be curious to take a look and see why, but in the end the solution will almost certainly look something like:
.bibbase_paper {
font-size: 14px;
}
Or something like that.
By the way, if you are interested in more examples: all our themes have their own CSS file, e.g., https://bibbase.org/css/styles/dividers.css, and there is also a shared one that is common to all unless explicitly disabled: https://bibbase.org/css/styles/common.css .
Hi Adam,
Please help me understand your concern with those additional fields better. The BibBase-internal use of this bibtex is probably of no concern to you, so I suspect that you are just worried about the bibtex that BibBase displays with each publication and offers users to download from your page? If my understanding is correct, then yes, that's something we could implement -- a kind of filter that only hides from that display and download all those additional fields.
In terms of setting the right priority for this, what kind of page are you setting up, for an individual or for a group of people? are you a premium subscriber or will this all be done using the free plan? We have quite a bit of backlog of features needed by our premium subscribers that we need to focus on at the moment, so it might be a while until we get to this if it's under the free plan.
It might work if you add the required styles and libraries directly to your page, in the <head> section:
<link rel='stylesheet' href="https://bibbase.org/css/styles/default.css" />
<link rel='stylesheet' href="https://bibbase.org/css/bootstrap.min.css" />
<script src="https://bibbase.org/js/bootstrap.min.js"></script>
My first suspicion would be that it is related to the expiration of Let's Encrypt's root certificate:
https://techcrunch.com/2021/09/21/lets-encrypt-root-expiry/
If so, then I think updating drupal or it's certificates may help, but I'm not sure and don't use drupal or php. You can also use the script-tag embedding option instead of the php embedding and that should solve the problem as well.
You are pointing at a github page where, yes, the bib file is shown, but a whole lot more as well. You want the raw file:
https://raw.githubusercontent.com/Rian-Jo/home/master/_posts/publication/bibliography.bib
Use that for the bib argument, or just paste that into the BibTex field on our homepage and it will get you started (recommended).
Customer support service by UserEcho
Dear Benjamin,
Thanks for reporting this. The issue is (or was) that our new link uses the same CSS class name, "page", as already used by other elements on your page, with styling already applied. This is the style your page added to the "page" class:
This style was now also applied to the new links added by BibBase and that's what caused the layout issue.
Seeing your case made us realize that "page" is probably too generic of a class name for us to use, especially when we really mean "the bibbase page". So we've gone ahead and changed our class name to "bibbase_page" now. This fixes the layout issue you saw on your page.
Thanks again for reporting!
Best,
Christian