I've investigated this more. The fulltext feature Zotero describes in the link I posted doesn't seem to work very well. When I try it on a group with an item that has an attached PDF, I get "{}" (i.e., it doesn't find any). If I try it on your group I get:

> curl https://api.zotero.org/groups/4501563/fulltext

Forbidden

This is probably because your group is not public. We could try again after you make it "public closed", but so far this doesn't look promising.

Thanks. From the picture I was able to see that this is using a different account from the one under your name. Looking at that other account I found the problem. It was actually a bug on our end, regarding a corner-case in the zotero workflow. This is fixed now and your library now shows up:

https://bibbase.org/show?bib=https%3A%2F%2Fbibbase.org%2Fzotero%2Fmh_lenguyen&msg=embed#

(no need to use a collection)

Thanks for reporting this!

Christian

PS: link updated. (https://bibbase.org/service/zotero)

Hi Huong,

I've looked at your account but I don't see any Zotero credentials on it. What happens when you click this link: https://bibbase.org/service/zotero ? Could you send me a screenshot of what you see after you click that?

Thanks,

Christian

You somehow have "http://bibbase.org/show" repeated in your bibbase URLs:

https://bibbase.org/show?bib=http%3A%2F%2Fbibbase.org%2Fshow%3Fbib%3Dhttps%3A%2F%2Fdl.dropboxusercontent.com%2Fs%2F7hww6e1hho3lgha%2Fwp.bib%3Fdl%3D1&jsonp=1&theme=side&filter=type:article

It needs to be just:

https://bibbase.org/show?bib=https%3A%2F%2Fdl.dropboxusercontent.com%2Fs%2F7hww6e1hho3lgha%2Fwp.bib%3Fdl%3D1&jsonp=1&theme=side&filter=type:article

Here is the same without the jsonp=1 parameter so you can click on it and see that it's working:

https://bibbase.org/show?bib=https%3A%2F%2Fdl.dropboxusercontent.com%2Fs%2F7hww6e1hho3lgha%2Fwp.bib%3Fdl%3D1&theme=side&filter=type:article

You'll need to make that change to all places where you did that.

Url parameters, like the new noIndex one, need to come before the hash (#). They are started by a ? and separated by &. So you'll need: https://bibbase.org/service/mendeley/7a51828e-9782-3fa4-8bdb-357443954bfc/group/b49ab5c8-edb7-3544-9fc1-ebbc7f3ac750?noIndex=1

And yes, if there already are url parameters you can just append it with &noIndex=1.

And yes, to trigger an update from a new page, all you need to do is visit it in a browser. The update of the database happens asynchronously (the page itself is rendered from cache), but it should only take a few seconds to a minute depending on the data size.

Hi Adam,

Thanks for the elaborate message and attempts to debug. This helped me diagnose this pretty quickly.

Regarding the linked PDFs: You've found a bug! The issue was that we weren't yet handling filenames with spaces and special characters correctly in this context. This is fixed now and I've verified that the two papers you mentioned now download fine from the link on the page.

Regarding the per-publication pages on BibBase: yes, you are right. We deduplicate papers by their authors, title, and year and the database keeps getting updated by the last paper our servers saw with that combination. So while your other, Mendeley-based page is still live and being visited by people browsing the web, our database record for the paper keeps getting written by that old version. Once that page is removed from the web, or otherwise made inaccessible to people, the new page you are creating will be the one setting that record.

However, I recognize that this can be frustrating in some situations, like in your current migration. So we've just added a new option "noIndex=1" that you can use in the bibbase URL of your old (Mendeley-based) page to prevent it's data from being used to update the database.

Christian

Hi Adam,

Thanks for the contribution!

Regarding your question: Yes, exactly. In the bibtex file you upload (and which you can later edit directly on bibbase), you can include url fields that point to files you've also uploaded. You can specify absolute URLs in those fields, or, for convenience, you can also just list the filename, in which case they will resolve to URLs on the same host and same sub-path as the bib file itself. 

For example, if I have these files in my file manager on BibBase:

and the cf.bib file contains an entry with the field:

  url = {1909.11604.pdf}

then when I render that bib file it will resolve that filename to the file in my account.

Yes, confirmed, I saw that comment. We haven't yet found the time to investigate it more so I can't, at this point, make any promises. There are a number of issues that rank higher in priority right now, either because they are required by premium users, or because they affect more users. So I can't quite tell how long it will be until we get to it. If using straight-out bibtex files, hosted either on your own server, on github, or directly on bibbase, then I highly recommend that. They are best supported and give you the greatest level of control.

Hi Adam,

Awesome, thanks in advance for the shout on Twitter! In terms of donating: no, we don't have a mechanism for that, but you can sign up for one of our premium plans instead if you want. They start at $4/month and you can cancel any time.