Your comments
Hi Kshitija,
HTTPS is not yet supported. An SSL certificate isn't actually free. The free ones that exist do not permit commercial use. However we are planning a "premium" subscription for BibBase that would have HTTPs as a feature (among others). Please let me know if that was an option you would consider. The way it is structured it is targeted at research groups rather then individuals, so it might make the most sense if others in your group also want to use BibBase, or if the group itself decided that they would like to use BibBase for its group site.
ps: if this is all you need, that's easy. We'll add it to our todo list.
Good idea. That should be possible. However we don't have much experience with the endnote format. I believe there are several different ones. It should be possible to generate the plain text format or the xml format. Is that what you are looking for? Could you send us some example files of the format you are hoping to see? Also, is the goal to import those files into another piece of software? if so, please let us know which (for testing). Thanks.
So no, you can't currently use BibBase on Google Sites. I recommend github pages as an alternative.
Sorry I misunderstood your intention. I certainly appreciate ideas on how the UX could be improved.
One question: are you describing the case where BibBase has been embedded using an iframe? I'm asking because you mention the situation where "the rest of the original website is still in view around it" If that is the case (iframe embedding), then I agree. That is very confusing. And there are a number of other reasons why I don't recommend the iframe method -- most importantly because search engines would not associate the terms/pdfs found to your web site, but would link to the embedded frame source directly.
Do you want to try the JSONP method of embedding instead and see whether you think that avoids some of the confusion for the user?
<script src="http://bibbase.org/show?bib=[URL-OF-BIBTEX-FILE]&jsonp=1"></script>
a[href^="http://arxiv.org"] .bibbase_icon { display: none; }
a[href^="http://arxiv.org"] .bibbase_icon_text { display: inline-block; }
Let me know if that doesn't work....
url_arXiv = {http://arxiv.org/abs/1503.06191},
...This will appear just the way you wanted, with "arXiv" as the link text.I know this is not quite the same as literally using the eprint field already in arXiv bibtex files, but it's only a very minor modification.
We implemented a special case for DOI because it is being used by dblp and we want that to be automatic (you can use dblp records for bibbase withough having to extract/update a bibtex file first). I don't think arXiv has an API for that yet. If or when they do, I'd be happy to interpret their bibtex entries fully as well.
Customer support service by UserEcho
Glad to see some pull for this feature. This is a feature we have been considering adding to BibBase. I don't think it's possible with the current styling capabilities alone (themes + CSS).