Good point. Yes, it would probably be better to only selectively remove titles. You can use

#group_article div span {
   display: none;
}

and similarly for all other titles you'd like to replace.

Yes and no. There is such a list, on every bibbase page out there, but there is no explicit documentation. CSS is sort of self-documenting, you just go into the page source and inspect the elements you care to change. On Chrome just right-click on the part of a page you want to change and select "Inspect Element".

Yes, this can be accomplished using CSS. Just drop the following into the CSS file on your page:

.bibbase_group span {
   display: none;
}

#group_article div i:after {
  content: " Journal Articles"
}

#group_inproceedings div i:after {
  content: " Conference Publications"
}

Similarly you would need to set new titles for the other groups (incollection, book, etc.).

Confirmed, and very strange. Not sure what was happening there, but after restarting the process it seems to now be working again.

Thanks for reporting this. This issue should now be resolved. Please try again and let me know if the issue persists.

Looks very nice.

Hi David,

Good catch. The order in which the css links are added to the header were indeed wrong. The one specified with the css parameter should indeed go last. This is fixed now. If you are extending the side theme then just make sure you use that as a theme, so that in your custom css you don't need to overwrite (respecify) too many things. Please let me know if that doesn't work for some reason.

I just restarted the server and the problem went away. I haven't yet dug deeper into the logs to see what may have caused it. I haven't seen a slow down like this in at least six month. But keeping it under control is not challenging. I might just restart the server automatically once a day, which is somewhat common practice. Another solution for this would be load balancers, which we'll probably put in place soon if bibbase keeps growing at the current pace.

Could you point me to the page in question so I can investigate what's happening?

Thanks for pointing this out, Chris. I believe I was able to fix it.

If this is the page in question, then I think it is much faster again: http://www.compbio.dundee.ac.uk/user/ccole/refs.html.

If that's no the one and it is still slow, please point me to your page for testing.

Thanks.