On Apr 26, 2018, at 10:50 AM, Adrian Altenhoff <adrian.altenhoff at inf.ethz.ch> wrote:
Dear Lori,
thanks for helping with this. We appreciate your concern about the
ambiguity of the name. In our opinion the best option would be to rename
it to 'OmaDB' to emphases both OMA and the fact that it queries a database.
We would be very glad if you could initiate the process for rename then.
Best wishes & thanks for your help again!
Adrian
On 23/04/18 13:50, Shepherd, Lori wrote:
We can assist we renaming -
However - we would not recommend "oma" as that is also rather short
and ambiguous, especially considering that is the
exact abbreviated name of the database your package accesses -
Could you come up with perhaps a more unambigious and meaningful name?
for example here are some existing rest api for databases:
KEGGREST : Client-side REST access to KEGG
goTools: Functions for Gene Ontology database
IMPCdata: Retrieves data from IMPC database
InterMineR: R Interface with InterMine-Powered Databases
BgeeDB: Annotation and gene expression data retrieval from Bgee database
maybe something along those lines?
Lori Shepherd
Bioconductor Core Team
Roswell Park Cancer Institute
Department of Biostatistics & Bioinformatics
Elm & Carlton Streets
Buffalo, New York 14263
------------------------------------------------------------------------
*From:* Bioc-devel <bioc-devel-bounces at r-project.org> on behalf of
Adrian Altenhoff <adrian.altenhoff at inf.ethz.ch>
*Sent:* Thursday, April 19, 2018 4:37:07 PM
*To:* bioc-devel at r-project.org
*Subject:* [Bioc-devel] Process to rename a bioconductor package
Dear all,
we would like to rename or own bioconductor package 'roma' --> 'oma' (as
there exists another software tool with that name that could be
misleading). So far the package is only in the development version. Is
there a standard process how to proceed with such requests?
Thanks!
Adrian