All the possible values for columns
and keytypes
are listed
below. Users will have to actually use these methods to learn which
of the following possible values actually apply in their case.
[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object] To get the latest information about the date stamps and source URLS
for the data used to make an annotation package, please use the
metadata method as shown in the example below.
Unless otherwise indicated above, the majority of the data for any one
package is taken from the source indicated by either it's name (if
it's an org package) OR from the name of it's associated org package.
So for example, org.Hs.eg.db is using "eg" in the name to indicate
that most of the data in that package comes from NCBI entrez gene
based data. And org.At.tair.db uses data that primarily comes from
tair. For chip packages, the relevant information is the organism
package that they depend on. So for example, hgu95av2.db depends on
org.Hs.eg.db, and is thus primarily based on NCBI entrez gene ID
information.