Regarding the 1540 entry, the issues seems to be the dot in "Theatra.de_PDF" used in the url field. This trips up our database, since dots are not allowed in keys.

@book{la_perriere_theatre_1540,
    address = {Paris},
    title = {Le théatre des bons engins: auquel sont contenuz cent emblemes moraulx},
    shorttitle = {Le théatre des bons engins},
    url = {Virginia_IIIF=https://v3.lib.virginia.edu/catalog/uva-lib:830320/iiif/manifest.json Theatra.de_PDF=http://www.theatra.de/repertorium/ed000134.pdf}},
    language = {French},
    urldate = {2020-07-21},
    publisher = {Denis Janot},
    author = {La Perrière, Guillaume de},
    year = {1540},
    note = {OCLC: 889853146},
    keywords = {43AA42 triumphal entry, 49M3213 emblem book, Moral education},
}

I took a look but unfortunately it doesn't look like the Zotero API is exporting those fields. This item (from my hometown Cologne!) has IIIF manifests in the library, but all the Zotero API gives us in the bibtex is:

@book{adrichem_theatrum_1582,
 address = {Cologne},
 title = {Theatrum {Terrae} {Sanctae} et {Biblicarum} {Historiarum} cum tabulis geographicis aere expressis},
 url = {Paper=mypdfs/gau-hum-1830.pdf Link=http://example.com/1830/measurements-of-the-world.html Slides=talks/gau-hum-1830.ppt}},
 language = {Latin},
 urldate = {2020-08-28},
 publisher = {Birckmannica officina, Arnold Mylius},
 author = {Adrichem, Christiaan van},
 year = {1582},
 note = {OCLC: 778667079},
}

So no, I'm afraid this won't be possible until they change their API. They might though if you ask.

Hi Oscar,

Can you point me to the page where you are embedding BibBase? Then I can take a look and see whether these Link to URI fields are already exported by the Zotero API and show up in the data we are getting from them. If that is the case then it should be pretty easy for us to support that.

Thanks,

Christian

Not per se, no, but I actually don't think that that's the best approach for accomplishing what you have in mind. Since you don't seem to want to use the abstract as an abstract but rather to provide additional information (annotations), you can just use the bibbase_note field instead. See this example. That field accepts HTML and is always rendered. So in your case you may be able to just rename all those abstract fields to bibbase_note. You may also want to use a div rather than a span, so that it rendered on a new line (like the abstract now) instead of inline.

Does that work for you?

It's not directly supported, but I think you can get it done using an additional field, with values 1_preprint, 2_misc, 3_..., grouping by that, and then using CSS to hide the group headers and show custom headers instead:

div.bibbase_group > span:nth-child(2) {
  display: none;
}

#group_1_preprint .bibbase_group_count:before {
      content: 'Pre-prints';
}
#group_2_misc .bibbase_group_count:before {
   content: 'Other Publications';
}

I know it's not ideal, but it should work.

Sorry for this interruption. The issue has been resolved this morning. Thanks for reporting.

Thanks for the suggestion. Are you thinking of giving the option to show their donut next to each paper? I think some tracking like this might be a good option for those who want it, some might find this donut too obtrusive though. We have a similar feature (counts of downloads), but most of our users don't seem to care much for this and are hiding that count instead. 

We recently upgraded to a newer version of Bootstrap. I suspect their CSS is a little different and is interacting with your own in a different way.

I've poked around and found that it seems to be related to the font-size you set on `li` tags in your style.css file. When I disable that, then the drop-downs look OK again. See below. Is that an option?