Your comments
Thanks, Romeo :-)
Yes, that's correct on both accounts. Locations don't matter and paper don't get duplicated. Papers are uniquely identified on bibbase by their "bibbaseid" which is constructed from author last names, title with whitespace removed, and year. Sure, every once in a while someone published the same paper with the same title and coauthors in the same year, so then there is a hash-collision, but I think that's not very good practice, so I'm OK with that.
Hi Romeo,
yes, it does. In your case, you are looking for these two pages:
http://bibbase.org/network/keyword/pisis
http://bibbase.org/all/keyword/pisis
You need to make sure that each of the individual bib files are being used with bibbase as well -- that is the mechanism by which the database is being kept up to date. Every time someone visits a bibbase page that uses one of these bib files as source, the database will be refreshed. So this is *not* as solution when you simply want to merge bib files. In that case, you should just manually merge them and use them as usual with bibbase. This is specifically a solution for showing an aggregate page from several already existing pages.
In your case, it seems that the second bib file in the drive (pubs_sara) had not yet been used with bibbase, so I just opened it once (http://bibbase.org/show?bib=https://d1055d4f3efc35...) in order to get it into the database. It won't stay up to date with changes to that bib file though unless the file is being used on a publications page where it is being visited somewhat regularly.
yes, it does. In your case, you are looking for these two pages:
http://bibbase.org/network/keyword/pisis
http://bibbase.org/all/keyword/pisis
You need to make sure that each of the individual bib files are being used with bibbase as well -- that is the mechanism by which the database is being kept up to date. Every time someone visits a bibbase page that uses one of these bib files as source, the database will be refreshed. So this is *not* as solution when you simply want to merge bib files. In that case, you should just manually merge them and use them as usual with bibbase. This is specifically a solution for showing an aggregate page from several already existing pages.
In your case, it seems that the second bib file in the drive (pubs_sara) had not yet been used with bibbase, so I just opened it once (http://bibbase.org/show?bib=https://d1055d4f3efc35...) in order to get it into the database. It won't stay up to date with changes to that bib file though unless the file is being used on a publications page where it is being visited somewhat regularly.
Hi Jorge,
I have not forgotten about this request. I always had in mind to solve this via a central database that simultaneously supports other functions as well. After long last, I've now implemented this. It is now possible to get bibbase pages for any keyword you use in a bibtex entry. For instance:
http://bibbase.org/network/keyword/golog
While this is mainly intended for use with areas of research, you can of course use it for other things as well, incl. the problem you are trying to solve: if everyone in your research group uses a specific term in their keywords, say "ing.puc", then you get a collected view of all of those publications in one page at the corresponding keyword page.
To embed a keyword page into another page, you can simply use URLs like
http://bibbase.org/all/keyword/golog in your page using the same mechanism as for regular bibbase pages (bib=http://bibbase.org/all/keyword/golog).
Please let me know if this works for you, and have fun at KR and/or AAAI if you are going!
I have not forgotten about this request. I always had in mind to solve this via a central database that simultaneously supports other functions as well. After long last, I've now implemented this. It is now possible to get bibbase pages for any keyword you use in a bibtex entry. For instance:
http://bibbase.org/network/keyword/golog
While this is mainly intended for use with areas of research, you can of course use it for other things as well, incl. the problem you are trying to solve: if everyone in your research group uses a specific term in their keywords, say "ing.puc", then you get a collected view of all of those publications in one page at the corresponding keyword page.
To embed a keyword page into another page, you can simply use URLs like
http://bibbase.org/all/keyword/golog in your page using the same mechanism as for regular bibbase pages (bib=http://bibbase.org/all/keyword/golog).
Please let me know if this works for you, and have fun at KR and/or AAAI if you are going!
Thanks! :-)
Hi Madhur,
I've dug a whole bunch deeper using tcpdump. I noticed that unlike wget and curl, bibbase was not sending a User-Agent header. It's a little picky of your server to deny requests without that header, but that's OK. BibBase is now sending this header as well and now your web server seems happy. This now works: http://bibbase.org/show?bib=http://www.seas.upenn....
I've dug a whole bunch deeper using tcpdump. I noticed that unlike wget and curl, bibbase was not sending a User-Agent header. It's a little picky of your server to deny requests without that header, but that's OK. BibBase is now sending this header as well and now your web server seems happy. This now works: http://bibbase.org/show?bib=http://www.seas.upenn....
BibBase isn't doing anything special. It just retrieves the file via an HTTP GET request issued from node.js using the regular HTTP module (http://nodejs.org/api/http.html#http_http_get_opti... The only header that is added is "If-Modified-Since" with the date of the last retrieval. This allows your server to respond with "304 Not Modified", which saves bandwidth and time to render your page as BibBase can then use its cache.
OK. Let me know what you find. I've also just pushed a small update that makes sure you get a proper error message now in the case you are encountering.
Customer support service by UserEcho
[blocked] The page at 'https://web.stanford.edu/group/fullergroup/cgi-bin...' was loaded over HTTPS, but ran insecure content from 'http://bibbase.org/show?bib=https%3A%2F%2Fweb.stan... this content should also be loaded over HTTPS.
Would embedding via PHP or CGI be an option. There are several benefits to those methods. This error would go away, but also you would wage better on SEO (search engine optimization) of your papers. It seems that you are already using cgi to render the page, so perhaps that method would be better suited? (see the second option for embedding on http://bibbase.org/help; you may be able to just use the CGI code within http://bibbase.org/help/bibbase_proxy2.cgi). Let me know if you need any help with that.
-- Christian