Your comments
Hi Adam,
Thanks for the detailed report with links and sorry for the delay. We found the bug that causes this and fix it, and I think I've checked all the cases you mentioned, please double check.
Best,
Christian
Hi Howcanoe,
Thanks for reporting this and for the suggestion. Do you have a page where I can see this problem in action?
Christian
Hi Frédérique,
You need to use the
https://bibbase.org/zotero-group/:userID/:groupID
URL. In your case, your zotero id seems to be Sordello, so:
https://bibbase.org/show?bib=https://bibbase.org/zotero-group/Sordello/4622315
and
https://bibbase.org/show?bib=https://bibbase.org/zotero-group/Sordello/2233096
Hi Adam,
I've looked into this and unfortunately the solution we had in mind is a lot more involved then we thought. The issue is that the current bibbaseid (authors-title-year), is used for indexing in the database and is assumed to be unique. This doesn't mean that this solution won't work, but it will require a lot more time to implement and test than anticipated. As a result we don't currently know when we'll have the time to address this, sorry.
For now, I think the only option is to add something to the title like "(working paper)".
Our plan is to use the bibtex key in addition to the bibbaseid, just for disambiguation when necessary. I'll keep you posted.
That's not currently possible, no, unless you are willing to change the title of course. In computer science, e.g., it is not uncommon to have such papers with more information, but they usually indicate this in their title, e.g., by adding "Extended Version" or similar to avoid confusion.
I think we can add support for this, though, by using the bibtex key for disambiguation.
Glad it worked! For finding .bib files, try bib$. The filter, again, uses regular expressions and the dollar sign is a special character in regular expressions indicating the end of the string.
Customer support service by UserEcho
Hi Baran,
I've checked the server log. It says:
It seems that the signing authority that issued your server's SSL certification (DFN-Verein Global, Verein zur Foerderung eines Deutschen Forschungsnetzes e. V.) is not recognized by the http library we use, which is just the built-in http library of node.js. Indeed, curl says the same:
I recommend getting a new SSL certificate from an authority that is widely accepted, e.g., a free one from Let's Encrypt.