A Breakthrough in Astronomical Software Development
Inga Kamp\altaffilmark{1}
Randall Thompson\altaffilmark{1}
Alberto Conti\altaffilmark{1}
Dorothy Fraquelli\altaffilmark{1}
Tim Kimball\altaffilmark{1}
Karen Levay\altaffilmark{1}
Bernie Shiao\altaffilmark{1}
Myron Smith\altaffilmark{1}
Rachel Somerville\altaffilmark{1}
and Richard L. White\altaffilmark{1}
% and the start of your text. \begin{abstract} % Leave intact In the past year, the Multimission Archive at the Space Telescope Science Institute (MAST) has taken major steps in making MAST's holdings available using VO-defined protocols and standards, and in implementing VO-based tools. For example, MAST has implemented the Simple Cone Search protocol, and all MAST mission searches may be returned in the VOTable format, allowing other archives to use MAST data for their VO applications. We have made many of our popular High Level Science Products available through Simple Image Access Protocol (SIAP), and are implementing the VO Simple Spectral Access Protocol (SSAP). The cross correlation of VizieR catalogs with MAST missions is now possible, and illustrates the integration of VO services into MAST. The user can easily display the results from searches within MAST using the plotting tool VOPlot. MAST also participates in the NVO registry service. Thus, the user can harvest MAST holdings simultaneously with data from many other surveys and missions through the VO DataScope Data Inventory Service.
P1.1.8.tex
%ADASS_PROCEEDINGS_FORM%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%
% SAMPLE2.TEX -- ADASS XII (2002) ASP Conference Proceedings sample
% paper with complicated markup. Based on ADASS XI (01) version.
%
% This is a comprehensive example, meaning that we have made use of each
% of the capabilities of the LaTeX + the ASPCONF macro package that we think
% you may need to use.  If you want to see a "base-bones" sample paper,
% take a look at sample1.tex.
%
% Much of the input will be enclosed by braces (i.e., { }).  The
% percent sign, "%", denotes the start of a comment; text after it
% will be ignored by LaTeX.  You might also notice in some of the
% examples below the use of "\ " after a period; this prevents LaTeX
% from interpreting the period as the end of a sentence and putting
% extra space after it.   
% 
% You should check your paper by processing it with LaTeX.  For
% details about how to run LaTeX as well as how to print out the User
% Guide, consult the README file.  
%
% If you do not have access to the LaTeX software or a laser printer
% at your site, you can still prepare your paper following the
% instructions in the User Guide.  In such cases, the editors will
% process the file and make any necessary editorial adjustments.
% 
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% 
\documentclass[11pt,twoside]{article}  % Leave intact
\usepackage{adassconf}

% If you have the old LaTeX 2.09, and not the current LaTeX2e, comment
% out the \documentclass and \usepackage lines above and uncomment
% the following:

%\documentstyle[11pt,twoside,adassconf]{article}

\begin{document}   % Leave intact

%-----------------------------------------------------------------------
%			    Paper ID Code
%-----------------------------------------------------------------------
% Enter the proper paper identification code.  The ID code for your
% paper is the session number associated with your presentation as
% published in the official conference proceedings.  You can
% find this number locating your abstract in the printed proceedings
% that you received at the meeting or on-line at the conference web
% site; the ID code is the letter/number sequence proceeding the title
% of your presentation.
%
% This will not appear in your paper; however, it allows different
% papers in the proceedings to cross-reference each other.  Note that
% you should only have one \paperID, and it should not include a
% trailing period.
%

\paperID{P1.1.8}

%-----------------------------------------------------------------------
%		            Paper Title 
%-----------------------------------------------------------------------
% Enter the title of the paper.
%
% EXAMPLE: \title{A Breakthrough in Astronomical Software Development}
%
% If your title is so long as to fill the page header when you print it,
% then please supply a short form as a \titlemark.
%
% EXAMPLE:
%  \title{Rapid Development for Distributed Computing, with Implications
%         for the Virtual Observatory}
%  \titlemark{Rapid Development for Distributed Computing}
%

\title{The Multimission Archive at the Space Telescope 
Science Institute in the context of VO activities}
\titlemark{MAST in the context of VO activities}

%-----------------------------------------------------------------------
%		          Authors of Paper
%-----------------------------------------------------------------------
% Enter the authors followed by their affiliations.  The \author and
% \affil commands may appear multiple times as necessary.  List each
% author by giving the first name or initials first followed by the
% last name.  Authors with the same affiliations should grouped
% together. 
%
% Try to limit the front matter to no more than three \author
% commands.  Group authors with the same affiliations.  Too many
% \author commands fills the first page of the paper with little
% actual text.

\author{Inga Kamp\altaffilmark{1}, Randall Thompson\altaffilmark{1},
        Alberto Conti\altaffilmark{1}, Dorothy Fraquelli\altaffilmark{1}, 
        Tim Kimball\altaffilmark{1}, Karen Levay\altaffilmark{1}, 
        Bernie Shiao\altaffilmark{1}, Myron Smith\altaffilmark{1}, 
        Rachel Somerville\altaffilmark{1}, 
        and Richard L. White\altaffilmark{1}}
\affil{Space Telescope Science Institute, 3700 San Martin Drive, Baltimore,
       MD 21218}


% Notice that some of these authors have alternate affiliations, which
% are identified by the \altaffilmark after each name.  The actual alternate
% affiliation information is typeset in footnotes at the bottom of the
% first page, and the text itself is specified in \altaffiltext commands.
% There is a separate \altaffiltext for each alternate affiliation
% indicated above.


%-----------------------------------------------------------------------
%			 Contact Information
%-----------------------------------------------------------------------
% This information will not appear in the paper but will be used by
% the editors in case you need to be contacted concerning your
% submission.  Enter your name as the contact along with your email
% address.

\contact{Inga Kamp}
\email{kamp@stsci.edu}

%-----------------------------------------------------------------------
%		      Author Index Specification
%-----------------------------------------------------------------------
% Specify how each author name should appear in the author index.  The 
% \paindex{ } should be used to indicate the primary author, and the
% \aindex for all other co-authors.  You MUST use the following
% syntax: 
%
% SYNTAX:  \aindex{LASTNAME, F. M.}
% 
% where F is the first initial and M is the second initial (if
% used).  This guarantees that authors that appear in multiple papers
% will appear only once in the author index.  

\paindex{Kamp, I.}
\aindex{Thompson, R.}
\aindex{Conti, A.}
\aindex{Fraquelli, D.}
\aindex{Kimball, T.}
\aindex{Levay, K.}
\aindex{Shiao, B.}
\aindex{Smith, M.}
\aindex{Somerville, R.}
\aindex{White, R.L.}

%-----------------------------------------------------------------------
%                     Author list for page header
%-----------------------------------------------------------------------
% Please supply a list of author last names for the page header. in
% one of these formats:
%
% EXAMPLES:
% \authormark{LASTNAME}
% \authormark{LASTNAME1 \& LASTNAME2}
% \authormark{LASTNAME1, LASTNAME2, ... \& LASTNAMEn}
% \authormark{LASTNAME et al.}
%
% Use the "et al." form in the case of seven or more authors, or if
% the preferred form is too long to fit in the header.

\authormark{Kamp et al.}

%-----------------------------------------------------------------------
%			Subject Index keywords
%-----------------------------------------------------------------------
% Enter up to 6 keywords describing your paper.  These will NOT be
% printed as part of your paper; however, they will be used to
% generate the subject index for the proceedings.  There is no
% standard list; however, you can consult the indices for past ADASS
% proceedings (http://iraf.noao.edu/ADASS/adass.html). 

\keywords{Virtual Observatory, webservice, HST, VizieR, Archive: MAST}

%-----------------------------------------------------------------------
%			       Abstract
%-----------------------------------------------------------------------
% Type abstract in the space below.  Consult the User Guide and Latex
% Information file for a list of supported macros (e.g. for typesetting 
% special symbols). Do not leave a blank line between \begin{abstract} 
% and the start of your text.

\begin{abstract}          % Leave intact
In the past year, the Multimission Archive at the Space Telescope 
Science Institute (MAST) has taken major steps in making MAST's holdings 
available using VO-defined protocols and standards, and in implementing 
VO-based tools. For example, MAST has implemented the Simple Cone 
Search protocol, and all MAST mission searches may be returned in the 
VOTable format, allowing other archives to use MAST data for their VO 
applications. We have made many of our popular High Level Science 
Products available through Simple Image Access Protocol (SIAP), and are 
implementing the VO Simple Spectral Access Protocol (SSAP). The cross 
correlation of VizieR catalogs with MAST missions is now possible, and 
illustrates the integration of VO services into MAST. The user can 
easily display the results from searches within MAST using the 
plotting tool VOPlot. MAST also participates in the NVO registry service. 
Thus, the user can harvest MAST holdings simultaneously with data from 
many other surveys and missions through the VO DataScope Data Inventory 
Service.


\end{abstract}

%-----------------------------------------------------------------------
%			      Main Body
%-----------------------------------------------------------------------
% Place the text for the main body of the paper here.  You should use
% the \section command to label the various sections; use of
% \subsection is optional.  Significant words in section titles should
% be capitalized.  Sections and subsections will be numbered
% automatically. 

\section{Introduction}

The Multimission Archive at Space Telescope Science Institute is NASA's 
UV-optical science archive center. It contains the Hubble Space Telescope archive 
plus more than a dozen additional active, planned, and legacy mission datasets. 
The total MAST data volume exceeds 20 Terabytes, making it one of the most 
significant astronomical collections available on-line.  

MAST is an important node in the upcoming virtual observatory and we are 
continually improving our data discovery and retrieval abilities. MAST has 
taken major steps in making its holdings available using VO-defined protocols 
and standards, and in implementing VO-based tools. All MAST mission searches 
may be returned in the VOTable format, allowing other archives to use MAST 
data for their VO applications.


\section{MAST Webservices}

Currently, MAST provides three different  forms of webservices, HTTP GET 
Requests, an RSS news service and dataset verifier SOAP service. 
Additional information can be found at 
{\bf \sl http://archive.stsci.edu/vo/mast\_services.html}.
HTTP GET Requests allow search parameters to be included in the URL. 
As such, they can be called from within programs to automate data searches. 
Currently, MAST provides this service for Mission Searches, Simple Cone 
Searches and the Simple Image Access Protocol. The results are returned 
in VOTable XML format. The result of the Mission Searches can also be
returned as excel spreadsheet, and comma-separated values which can 
simplify ingesting results into user-written programs. 
Fig.~\ref{SIAP} shows the VOTable returned
for a positional search in the archived NICMOS images: the search radius
is 0.5 arcsec and the search is restricted to data in gif-format.

\begin{figure}
\epsscale{0.72}
\plotone{P1.1.8_1a.ps}
\caption{Example of the Simple Image Access Protocol: the command 
{\bf \sl http://archive.stsci.edu/siap/search.php?POS=6.0,-72.0\&SIZE=0.5\&format=gif\&ID=nicmos}
returns the above VOTable containing the information on all matching datasets.} \label{SIAP}
\end{figure}

The RSS news service offers to search a list of MASTs most recent news items and returns
the result in RSS XML-format. The output can also be displayed in HTML.

MAST has one SOAP-based web service, which is accessed via the ADS. The web service allows 
users to enter a data set name and obtain a verification and link to the archival website
of this dataset. More information about the ADEC naming conventions can be found at
{\bf \sl http://archive.stsci.edu/pub\_dsn.html}. The service can be accessed from the 
web form at:\\
{\bf \sl http://ads.harvard.edu/ws/DataVerifier},
or, using the latest ADEC naming conventions:\\
{\bf \sl http://vo.ads.harvard.edu/dv/DataVerifier.cgi} (Fig.~\ref{SOAP})\,\,.

\begin{figure}[ht]
\vspace*{3mm}
\epsscale{1.0}
\plotone{P1.1.8_2a.ps}
\caption{Example of the SOAP-based web service: enter the dataset names in
the verification form and submit the request. The result contains the verification
of the dataset name as well as links to these datasets.} \label{SOAP}
\end{figure}

\section{VOPlot at MAST}

Users may plot search results from any MAST mission or VizieR catalog search with 
the new JAVA-based graphical display tool called VOPlot (developed within the Indian 
VO project in collaboration with CDS). The example in Fig.~\ref{VOPlot} shows the 
galactic distribution of STIS UV observations with the Echelle gratings.

\begin{figure}
\epsscale{.60}
\plotone{P1.1.8_3a.ps}
\caption{The galactic distribution of STIS high-resolution UV observations: the
graphical display tool VOPlot is called from the result page of a 
MAST archive query.} \label{VOPlot}
\end{figure}

\section{MAST and VizieR}

Users may now search the entire set of 4\,000 VizieR catalogs and cross correlate 
the results with any MAST mission. This uses a VizieR web service which communicates 
using the VOTable standard. The example shows the result of a cross correlation between 
the Vega-type star catalogue and archived FUSE observations. Enter the catalog information 
at {\bf \sl http://archive.stsci.edu/vizier.php} and cross correlate
it with the FUSE data in MAST. Fig.~\ref{VizieR} shows how to navigate through
the cross correlation. In addition, it provides a cutout of the returned 
information on the available FUSE datasets for Vega-type stars from the 
specified catalog.

\begin{figure}
\epsscale{0.9}
\plotone{P1.1.8_4a.ps}
\caption{Provide the catalog information for the cross correlation at
{\bf \sl http://archive.stsci.edu/vizier.php}. After choosing the cross 
correlation option for the catalog of Vega-type stars, the FUSE mission 
was selected and the last page shows a pane of the resulting web table.} \label{VizieR}
\end{figure}



% That's the end of the main body of the paper.  Now we will have some
% back matter.
%
%-----------------------------------------------------------------------
%			      References
%-----------------------------------------------------------------------
% Now comes the reference list.  Since we typed out the citations ourselves,
% the reference list is enclosed in a "references" environment.  Each
% new reference begins with a \reference command which sets up the proper
% indentation.  Typography that may be required in the reference list by
% the editorial staff must be included by the author.
%
% Observe the "standard" order for bibliographic material: author name(s),
% publication year, journal name, volume, and page number for articles.
% Some journal names are available as macros; see the package
% instructions for a listing of which ones have been "macro-ized".
%
% There is no need to engage in any other typographic manipulation.
%
% List your references below within the reference environment
% (i.e. between the \begin{references} and \end{references} tags).
% Each new reference should begin with a \reference command which sets
% up the proper indentation.  Observe the following order when listing
% bibliographical information for each reference:  author name(s),
% publication year, journal name, volume, and page number for
% articles.  Note that many journal names are available as macros; see
% the User Guide for a listing "macro-ized" journals.   
%
% Note the following are some of the tricks that can be used:
%
%   o  \& is used to format an ampersand symbol (&).
%   o  \'e and \`e puts an accent agu and accent grave, respectively,
%      over the letter e.  See the User Guide for details on
%      formatting special characters.
%   o  "\ " after a period prevents LaTeX from interpreting the period 
%      as an end of a sentence.
%   o  \aj is a macro that expands to "Astron. J."  See the User Guide
%      for a full list of journal macros
%   o  \adassviii is a macro that expands to the full title, editor,
%      and publishing information for the ADASS VIII conference
%      proceedings.  Such macros are defined for ADASS conferences I
%      through X.
%   o  When referencing a paper in the current volume, use the
%      \adassviii and \paperref macros.  The argument to \paperref is
%      the paper ID code for the paper you are referencing.  See the 
%      note in the "Paper ID Code" section above for details on how to 
%      determine the paper ID code for the paper you reference.  
%
%\begin{references}
%\reference Auri\`ere, M.\  1995, \adassiv, 109
%\end{references}

% Do not place any material after the references section

\end{document}  % Leave intact
