Skip to content
Prev 12344 / 21307 Next

[Bioc-devel] annotation data not updated?

On Wed, Nov 15, 2017 at 7:50 AM, Shepherd, Lori <
Lori.Shepherd at roswellpark.org> wrote:

            
Thanks. How are the OrgDb files for AnnotationHub built? I just made one
for Salmo salar using makeOrgPackageFromNCBI, and the GO IDs for that
package match those in GO.db. One of the GO IDs in the AnnotationHub OrgDb
for Salmo salar (that is not in GO.db) is GO:0044744, which was made a
secondary ID for GO:0034504 on 6/29/2017, which seems too far in the past
to have not been picked up by an update in November.

If I just pick another OrgDb at random, it has outdated GO IDs as well:
AnnotationHub with 3 records
# snapshotDate(): 2017-10-27
# $dataprovider: ftp://ftp.ncbi.nlm.nih.gov/gene/DATA/
# $species: Macaca cynomolgus, Macaca mulatta, Macaca nemestrina
# $rdataclass: OrgDb
# additional mcols(): taxonomyid, genome, description,
#   coordinate_1_based, maintainer, rdatadateadded, preparerclass, tags,
#   rdatapath, sourceurl, sourcetype
# retrieve records with, e.g., 'object[["AH57977"]]'

            title
  AH57977 | org.Mmu.eg.db.sqlite
  AH58035 | org.Macaca_nemestrina.eg.sqlite
  AH58053 | org.Macaca_cynomolgus.eg.sqlite
downloading from  https://annotationhub.bioconductor.org/fetch/64781
retrieving 1 resource
  |======================================================================|
100%
[1] 13
[1] "GO:0007067" "GO:0016337" "GO:0044699" "GO:0044700" "GO:0044702"
 [6] "GO:0044707" "GO:0044710" "GO:0044711" "GO:0044763" "GO:0044765"
[11] "GO:0044767" "GO:0098602" "GO:1902578"

So far as I can tell, all of these terms have been replaced, so it looks
like the GO source date were outdated?

Jim

  
    
Message-ID: <CAKO-U0o6Zy0FF2nyTgBus0wa8JMv42f1LJN09AUkX85mKmSbjA@mail.gmail.com>
In-Reply-To: <BN6PR12MB1731CBEFB5C9F24DBDC7EBD7F9290@BN6PR12MB1731.namprd12.prod.outlook.com>