\documentclass[11pt,twoside]{article}  % Leave intact
\usepackage{adassconf}


\begin{document}   % Leave intact


\paperID{P3-3}
%%%% ID=P3-3


\title{MMDSL: a Multi-Mission Data Server at LAEFF}
\titlemark{MMDSL: a Multi-Mission Data Server at LAEFF}

%-----------------------------------------------------------------------
%		          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{E.\ Solano, R.\ Guti\'{e}rrez, B.\ Montesinos\altaffilmark{1}, C.\ Morales and J.\ Garc\'{\i}a}
\affil{LAEFF. P.O. 50727, E-28080 Madrid, Spain}
\altaffiltext{1}{IAA-CSIC, PO Box 3004, E-18080 Granada, Spain}

%-----------------------------------------------------------------------
%			 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{Enrique Solano}
\email{esm@laeff.esa.es}

%-----------------------------------------------------------------------
%		      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{Solano, E.}
\aindex{Guti\'errez, R.}
\aindex{Montesinos, B.}
\aindex{Morales, C.}
\aindex{Garc\'\i a, J.}

%-----------------------------------------------------------------------
%                     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{Solano, Guti\'{e}rrez, Montesinos, Morales \& Garc\'{\i}a}

%-----------------------------------------------------------------------
%			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{archives: interoperability, data: mining, space missions: XMM, Infrared Space Observatory (ISO), MINISAT-01, surveys: 2MASS, INES}
%-----------------------------------------------------------------------
%			       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
We describe here the functionalities, contents and future implementations of the Multi-Mission Astronomical Data Server developed at LAEFF.
\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 acquisition rate of astronomical data, both from space and ground-based observatories, has increased enormously in the last years. The possibility of studying regions of the electromagnetic spectrum that could not be reached until very recently has led to a spectacular growth of the multi-wavelength astronomy. However, a negative aspect affecting this growth is the lack of homogeneity that astronomical archives currently show. Historically, astronomical archives have been built independently of each other and this has meant that their remote interoperability is neither easy nor efficient, as demonstrated by the fact that the queries to multiple databases are done, most of the times, by hand. Interoperability is, therefore, one of the fundamental aspects for the Virtual Observatory  (VO) and an essential requirement for the multi-wavelength astrophysical research. 

Since January 2002 LAEFF has been developing, in the framework of the VO, a multi-mission data server to provide easy, efficient and uniform access to astronomical databases. A primary goal of this project is the implementation of science-driven tools. In this context, MMDSL provides an excellent framework to check the performance of utilities before their inclusion in the VO structure. This is a fundamental step in order to manage properly the huge flow of data expected from the VO federation of archive centres.  

In this paper, the main functionalities and contents of the system are presented. The first version is foreseen to be released at the beginning of 2004 and will be available at http://sdc.laeff.inta.es


\section{Contents}

In the first phase, the system focuses on the integration of the ultraviolet
archives maintained at LAEFF (\htmladdnormallinkfoot{EURD}{http://laeff.esa.es}and \htmladdnormallinkfoot{INES}{http://ines.laeff.esa.es}) with the ESA astronomical archives hosted at VILSPA (\htmladdnormallinkfoot{XMM-Newton}{http://xmm.vilspa.esa.es/external/xmm_data_acc/xsa/index.shtml} and \htmladdnormallinkfoot{ISO}{http://www.iso.vilspa.esa.es/ida/index.html}). The coverage in the optical range is given by flux-calibrated Str\"omgren and Geneva photometry.

At the time of writing we are working on the implementation of the 2MASS Point-Source Catalogue. To give a coverage as complete as possible in the UV, future plans imply access to the ultraviolet missions available in MAST.


\begin{figure}
\epsscale{1.0}
\plotone{P3-3_f1.eps}
\caption{Example of an input query form.} \label{P3-3:fig-1}
\end{figure} 

\section{Functionalities}
\begin{itemize}
\item{ Archive search:} The query to the system is made by means of an HTML form (Figure~\ref{P3-3:fig-1}) allowing different types of search: by object, list of objects, object type as given in SIMBAD, coordinates, date and mission. Particularly interesting is the possibility of posing scientifically-driven queries by using the search by object type. A built-in name resolver has been implemented which permits queries using any of the object names provided by SIMBAD. \\

\item{ Results from searches:} \\

\begin{itemize}

\item[-]{Basic data information:} For each object, the system provides basic information retrieved from SIMBAD. This includes coordinates in different systems, magnitudes, spectral type, parallax, radial velocity and/or redshift. If Str\"omgren photometry is available, the dereddened indices as well as the physical parameters are also displayed. 

\item[-]{Data preview:} A browse plot can be generated by clicking on the corresponding link. The system also incorporates a multiplot utility with zooming capabilities designed to allow users to visualize a combined average spectrum of different missions/instruments. The browse plot can be saved as a PNG file. 

\item[-]{Links to publications:} For the IUE, ISO and XMM-Newton missions it is possible to access the publications which have made use of a given observation. By clicking on the link, the abstract and/or the full paper are obtained through the ADS facility.

\item[-]{FITS header display:} Links are provided to display the FITS header for the requested data. 

\item[-]{Data retrieval:} Data, delivered as FITS files, can be retrieved individually or in groups. Multiple retrieval generates a packed file in either tar or ZIP format. Compression of packed files is recommended for network efficiency, in particular when large data sets are downloaded. 

\item[-]{On-line help:} Help on a specific keyword can be obtained by simply clicking on it.

\item[-]{On-line access to missions: For accessing detailed project documentation, the system incorporates a link to the Home Pages of the different missions. }


\end{itemize}
\end{itemize}

\section{Interoperability}
To ensure  real interoperability it is compulsory to adapt the system to the standards and recommendations agreed within the International Virtual Observatory Alliance. MMDSL is being adapted to be compliant with one of these standards: Cone Search, a basic component of SIAP (Simple Image Access Protocol). In short, to be Cone Search-compliant, the web server must be able to respond to an http GET request containing the coordinates (right-ascension and declination) of the central position and the radius of the search. The service must respond with a table of the objects found within the cone.

\section{Analysis tools}

The development of analysis tools for their further implementation in the Data Server constitutes an important added-value to the system and is in agreement with the Virtual Observatory goal that Data Centres should not be simple data repositories but they must incorporate tools to help users in the analysis. This will permit to transfer only results and not pre-analyzed data, a non negligible aspect given the vast amount of data handled in the Virtual Observatory federation of Archives. Implemented in the Data Centre the analysis tools can be shared and re-used and the expertise requirements on the user's side greatly reduced. It is clear that a Data Centre cannot cope with all potential scientific cases but this situation can be alleviated if collaboration with scientists in universities or research centres, acting as software tools writers, are established. 

At present, MMDSL allows for comparisons between the observed spectral energy distribution of a stellar object and synthetic models. Another important facility implemented in the system is
the determination of the physical parameters of early and mid-type stars from the Str\"{o}mgren photometry using the most updated calibrations. Similarly, physical parameters of late-type stars will be derived from V-Johnson and 2MASS photometry following the method described in Ribas et al. (2003). Subsequent releases of the system will include the use of data mining tools for spectral classification and characterization of the observed spectral energy distributions. 

\begin{references}
\reference Ribas, I., Solano, E., Massana, E. \& Gim\'{e}nez, A., 1993, \aap, 411, L501
\end{references}


\end{document}  % Leave intact
