\Header{getSYMBOL}{Functions to deal with Data Packages}
\alias{getGO}{getSYMBOL}
\alias{getGOdesc}{getSYMBOL}
\alias{getLL}{getSYMBOL}
\alias{getPMID}{getSYMBOL}
\keyword{manip}{getSYMBOL}
\begin{Description}\relax
The functions documented here are intended to make it easier to map
from a set of manufacturers identifiers (such as you will get from the
chips etc) to other identifiers.\end{Description}
\begin{Usage}
\begin{verbatim}
getSYMBOL(x, data = "hgu95a")
getLL(x, data = "hgu95a")
getGO(x, data = "hgu95a")
getPMID(x, data = "hgu95a")
getGOdesc(x, which=c("MF","BP","CC") )
\end{verbatim}
\end{Usage}
\begin{Arguments}
\begin{ldescription}
\item[\code{x}] The identifiers to be mapped (usually manufacturer)
\item[\code{data}] A character string identifying the data source 
\item[\code{which}] For \code{getGOdesc} indicates which GO hierarchy to use.
\end{ldescription}
\end{Arguments}
\begin{Details}\relax
Appropriate translations are done. In some cases such as \code{getLL}
and \code{getSYMBOL} there will only be one match and a vector is
returned. In other cases such as \code{getPMID} and \code{getGO} there
may be multiple matches and a list is returned.
For \code{getGOdesc} the input vector is GO identifiers (not
manufacturer identifiers) and in the output any identifier that does
not have a description in the selected GO hierarchy (MF, BP or CC) is
dropped.\end{Details}
\begin{Value}
Either a vector or a list depending on whether multiple values per
input are possible.\end{Value}
\begin{Author}\relax
R. Gentleman\end{Author}
\begin{SeeAlso}\relax
\code{\Link{multiget}}\end{SeeAlso}
\begin{Examples}
\begin{ExampleCode}
  data(eset)
  gN <- geneNames(eset)[100:105]
  getSYMBOL(gN)
  gg<- getGO(gN)
  getGOdesc(gg[[2]], "MF")
  getLL(gN)
  getPMID(gN)
\end{ExampleCode}
\end{Examples}

