Search Mailing List Archives

Limit search to: Subject & Body Subject Author
Sort by: Reverse Sort
Limit to: All This Week Last Week This Month Last Month
Select Date Range     through    

[bioontology-support] looking for the right BioPortal version

Vyacheslav Zholudev vyacheslav.zholudev at
Thu Sep 9 01:56:03 PDT 2010

Dear Paul,

thanks for looking into this. I have a couple of comments. 

> I looked into your report of problems with the HTTP PUT and DELETE methods. We do support these, in fact it's exactly how the reads and writes to our persistent store work, but it does look like the "raw" HTTP methods weren't being detected properly. Most of our calls use "tunneled" methods where you add a parameter to the query string to indicate which method you're using. For example, adding "method=PUT" when doing a POST will allow a PUT method to be detected. This is to support clients that don't implement the HTTP methods fully (most browsers support GET and POST only).

But that kills the purpose of RESTful interface where certain type of actions are supposed to be done by certain types of HTTP requests, e.g. delete actions should be done by DELETE requests. Yes, that's true that most browsers do support only GET and POST, but for browsers you have the BioPOrtal GUI, or one can use RESTful plugins for browsers. Anyway, it's rather a thought ...

> I've fixed the improper detection in /bioportal/src/java/org/ncbo/stanford/view/rest/restlet/ rev2735.


> If there's anything else I can help out with, please let me know. We're happy to accept bug reports, you can submit them at our tracker:

I'm not sure whether this is a bug. But I guess when you set up a new version of BioPortal, new Lucene indexes are not created automatically, that leads that BioPOrtal can't start. On my local machine I have a small patch that checks whether indexes exist at all, and if not bioportl creates an initial version. This patch is useful upon initialization only. Can you recall something like this, or should I rather provide a detailed report in the bug tracker?


> Paul R Alexander
> Web / UI Developer
> NCBO BioPortal
> Stanford Center for Biomedical Informatics Research
> On 9/8/10 4:23 AM, Immanuel Normann wrote:
>> Dear BioPortal support team,
>> We have installed an instance of BioPortal to store ontologies for our
>> own project:
>> Unfortunately, the BioPortal revision we have taken (revision 1875,
>> path /tags/1014) turned out to be buggy. We considered to upgrade to
>> BioPortal 2.5, but deferred that for three reason: 1) the content
>> migration seems to be not that straightforward (according to a mail by
>> Paul Alexander) and thus currently to risky for us. 2) The REST API has
>> changed in BioPortal 2.5, but our partners rely on the REST API of our
>> current BioPortal. 3) Our main developer, Slava, who takes care for the
>> BioPortal installation figured out that some (for us fundamental) bug
>> apparently hasn't been fixed in the latest version: RESTful DELETE and
>> PUT does not work.
>> Slava says that to fix this bug is very easy and so he did it on a local
>> installation. But there are some other bugs that we haven't yet
>> identified. We came to the decision that the best solution for us is to
>> check out the stablest BioPortal revision that is still close enough to
>> our current revision (1875, /tags/1014) so that we do not need to
>> migrate content and that uses still the same REST API.
>> Our problem is that we cannot figure out from the revision logs which
>> revision satisfies our needs. Appearently, it is even unclear to figure
>> out to what release a certain revision belongs.
>> We would be very grateful for any clarification!
>> Thanks in advance,
>> Immanuel Normann
>> _______________________________________________
>> bioontology-support mailing list
>> bioontology-support at


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the bioontology-support mailing list