Mailing-List: contact user-help@oodt.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@oodt.apache.org
Received-SPF: pass (athena.apache.org: local policy)
From: "Mattmann, Chris A (388J)" <chris.a.mattmann@jpl.nasa.gov>
To: "user@oodt.apache.org" <user@oodt.apache.org>
Date: Fri, 18 Mar 2011 12:43:30 -0700
Subject: Re: Component Documentation
Thread-Topic: Component Documentation
Thread-Index: AcvlpMLNLA/SEOB2ThuW35ru3Mc/Hw==
Message-ID: <527403B4-1B4E-47D3-B3BB-D59DC2320436@jpl.nasa.gov>
References: <AANLkTik=YdAG98kdKLubsxHnqZQADZjNO2ZTHG+BtJf5@mail.gmail.com>
In-Reply-To: <AANLkTik=YdAG98kdKLubsxHnqZQADZjNO2ZTHG+BtJf5@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Hi Tom,

Thanks for your questions, my replies inline below:

> I noticed that detailed documentation for some of the OODT components suc=
h as PCS Input and PCS PGE is not available on the website.
> I.E. http://oodt.apache.org/components/maven/pcs/input/ does not contain =
any user guides or advanced documentation like it does for most of the othe=
r components.

There aren't any advanced user guides for those components (though contribu=
tions are certainly welcome! :) ). In a way, the paper here [1] that I list=
ed for your assignment is sort of a specification/documentation for them at=
 the moment.=20

The two schools of thought on this are:

1. for your assignment -- you just make do with what you were handed and us=
e that to guide you architectural recovery and justification for your recor=
ded design decisions
2. beyond your assignment and if you're interested in contributing any of t=
hose docs after you gain an understand of the components, all of the xdocs =
for those guides are located in:

http://svn.apache.org/repos/asf/oodt/trunk/<component name>/src/site/xdoc

So, e.g.,=20

http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/site/xdoc/

>=20
> Is there anywhere I can look for additional information on these componen=
ts?

The best bet is the IEEE SMC-IT paper [1].

>=20
> Also, does the "opendapps" package in the source code map to any of the l=
isted components on the components section of the website?

It doesn't directly but I'd advise you that it's essentially a configurable=
 marriage of an OODT profile server, reading its information from OPeNDAP s=
ervers upstream of it, and delivering their information as OODT profile met=
adata.

HTH,
Chris

[1] http://sunset.usc.edu/~mattmann/pubs/SMCIT09.pdf

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW:   http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++