1 Mar 2012 01:17
Re: problem creating own org.Ss.eg.db
Hi Guido, I am not surprised by any of that. Annotations change more than most people expect. And the pig org package is made (special) here along with all the other major organism packages that we support. It is not generated by the method you used because that method has to work for ALL organisms that are at NCBI. That means that when you use that method, you don't get any of the extras that we add for you here. The auto-generated version is just generated by using information from NCBI with the help of some external GO mappings. And it is really not meant to be a way to get a newer package. It is meant to allow people who are using non-model organisms to get annotations. So it is expected that some things are definitely going to be missing unless you want to do the extra work of finding those things and adding them back in manually. And it is really not possible to keep the "too new" GO terms when you generate the package either, because that would break a lot of software that depends on GO.db being in sync with the organism packages. The only way around that would be if you also generated a new GO.db package from scratch. I suppose that you could do that, and if you did (and installed it) the method would stop trying to drop those "too new" GO terms, but it would be a lot of work to generate that package from scratch. And even if you used it you would lose some of the benefits of using versioned annotation packages. Personally, I would never recommend that strategy, I only mention it so that you can understand what is happening here (and why). A new release of Bioconductor should drop in about a month and with it will be an update to org.Ss.eg.db. If you are feeling impatient, there should be a new package in devel even sooner than that..(Continue reading)
RSS Feed