Search Mailing List Archives
[bioontology-support] [BioPortal] Feedback from Benjamin Leinfelder
leinfelder at nceas.ucsb.edu
Wed Dec 10 11:00:15 PST 2014
I'm inclined to start with the first option and just keep our ontology private.
I don't expect our UI development work to overload the services, but we are also looking at using the recommender service for automated classification
If we end up doing too many queries, please let us know.
I assume my API key will still allow me to interact with private ontologies (find concept matches, navigate classes, etc)?
On Dec 9, 2014, at 5:46 PM, Ray Fergerson <ray.fergerson at stanford.edu> wrote:
> There are two ways forward here. First you can load your ontology as
> "private". Then only you and those you specify will be able to see it. The
> second way is to set you your own virtual machine instance of BioPortal.
> If you are going to be (1) doing lots of queries or (2) making lots of
> modification (notes & mappings) then the second method is preferable. If
> not then you can use the first.
> When the ontology is complete you can change it over to public if you
> -----Original Message-----
> From: bioontology-support
> [mailto:bioontology-support-bounces at lists.stanford.edu] On Behalf Of
> support at bioontology.org
> Sent: Monday, December 8, 2014 2:32 PM
> To: support at bioontology.org; leinfelder at nceas.ucsb.edu
> Subject: [bioontology-support] [BioPortal] Feedback from Benjamin
> Name: Benjamin Leinfelder
> Email: leinfelder at nceas.ucsb.edu
> Location: http://bioportal.bioontology.org/
> I'm wondering if there's a development instance of BioPortal that could be
> used for testing the API with some not-yet-finished ontologies. We really
> like BioPortal and don't want to pollute the holdings with
> NCEAS software development
> bioontology-support mailing list
> bioontology-support at lists.stanford.edu
More information about the bioontology-support