You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oodt.apache.org by Ross Laidlaw <rl...@gmail.com> on 2012/03/22 05:34:39 UTC
OODT-402 progress update
Hi Chris,
I'm writing to give an update on my progress on OODT-402 and getting
up to speed with the OODT project.
I've been reading through the documentation from
http://oodt.apache.org/components/maven/filemgr and the wiki pages
http://cwiki.apache.org/oodt. I've also read up on the GeoRSS format
at http://georss.org and http://en.wikipedia.org/wiki/GeoRSS.
By following the user guides (which are awesome by the way!) I have
built OODT with maven v2.2.1 on my laptop (macbook running OSX Lion)
and set up the File Manager program (I've ingested my first 'blah.txt'
file with meta data! And also tested out some queries).
As a next step, I'd like to install the File Manager webapp. Are
there any recent guides for installing? I watched both of your Apache
OODT Curation tutorials on YouTube (very cool) and also found some
info about webapps from one of your replies on the
user@oodt.apache.org mailing list (with link to slides
http://oodt.apache.org/components/maven/grid/slides.pdf). I have my
webapp target folders and war files from the build and I have Tomcat
set up on my machine, so hopefully I'm not far off being up and
running! Apologies if this is something obvious that I should know
already (e.g. by learning more about Tomcat).
I built the 0.3 release of OODT on my machine. But I also had a look
through the latest webapp source code and noted your comments in the
following file:
https://svn.apache.org/repos/asf/oodt/trunk/webapp/fmprod/src/main/resources/rssconf.xml
<!--
If you want to turn your CAS File Manager into a GeoRSS
simple service (see http://georss.org/simple), add the
following block, assuming that you have indexed met fields
named Latitude and Longitude for your product (update as
appropriate otherwise).
<tag name="georss:point" source="[Latitude] [Longitude]"/>
-->
Am I right in thinking that this is the starting point for OODT-402?
I saw from georss.org that there are a few different GeoRSS formats
(Simple, GML and W3C). But I read that the W3C format is a bit older
and the GML format is quite extensive, so it's a great plan to use the
simple format and work from there.
I'd like to set up a similar development environment to the OODT
developers. Is Eclipse the IDE of choice? I noticed you using it on
the youtube tutorials and also there's an 'OODT Eclipse Developer
Help' guide on the wiki. I have version 3.7.2 (Indigo) installed on
my machine but please let me know if there are any incompatibility
problems.
Regarding OODT-402, do you have a feel for how long you'd expect me to
take in completing the project? I'd like to put together a plan of
action for my GSoC proposal. I have the three step outline from the
OODT-402 JIRA page as the basis for the plan. I feel that I have a
good knowledge of XML and core Java, for example I have passed the
Oracle Certified Java Programmer exam. Hopefully I also have a good
grounding in some of the design principles used in OODT, for example
factory design patterns and coding to interfaces for extensibility, as
I have taken several OO classes so far in my studies.
I'm hoping to have some more specific questions about the steps for
OODT-402 as I start using the webapp and examining the source code in
more detail.
Many thanks again for your time,
Ross
Fwd: OODT-402 progress update
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
FYI, of interest to the SIS community...
Begin forwarded message:
> From: Ross Laidlaw <rl...@gmail.com>
> Date: March 31, 2012 4:04:10 AM PDT
> To: "dev@oodt.apache.org" <de...@oodt.apache.org>
> Subject: Re: OODT-402 progress update
> Reply-To: "dev@oodt.apache.org" <de...@oodt.apache.org>
>
> Hi Chris,
>
> Many thanks for your comments and advice. I have now installed SIS on
> my system and I have the demo up and running. I've also been
> experimenting with the connection between File Manager and SIS and I
> have a basic connection working. Here are the steps I have carried so
> far:
>
> Firstly, I added elements for 'Latitude' and 'Longitude' to the
> GenericFile policy. Then I created a set of test files (simple text
> files) with corresponding '.met' metadata files. I added 'Latitude'
> and 'Longitude' metadata to the '.met' files. I then ingested these
> into my File Manager repository.
>
> After that, I enabled the 'georss' tags in the 'rssconf.xml'
> configuration file (I added tags for geo:lat and geo:long to start
> with) and viewed the RSS output from the CAS REST API in my browser.
>
> I then added the URL
> ('http://localhost:8080/fmprod/viewRecent?channel=ALL') as an RSS feed
> to the 'sis-location-config.xml' config in my SIS webapp.
>
> Next, I ran a bounding box query from the SIS demo.jsp and my file
> manager files appeared on the map! Awesome!
>
> I have uploaded a set of screenshots showing my progress, hopefully
> they're accessible and make sense (I'm new to flickr, so apologies if
> things look a bit disorganised!):
>
> http://www.flickr.com/photos/rlaidlaw/sets/72157629342438940/with/7031581313/
>
> I tried to order the screenshots to follow the steps I outlined above,
> with the final screenshot being the output from the SIS demo showing
> the File Manager files on the map.
>
> For next steps, I could start to formalize some of my experimental
> code and begin to address the key points you have outlined on the
> OODT-402 jira page (i.e. writing a default GeoRSS config and a default
> file manager policy for a 'LocationAwareProduct' type). I will follow
> up with specific questions about both of these, but for now I just
> wanted to give you an update on my progress and to check that I'm
> heading in the right direction.
>
> Speak to you soon,
>
> Ross
>
>
>
>
>
> On 22 March 2012 05:48, Mattmann, Chris A (388J)
> <ch...@jpl.nasa.gov> wrote:
>> Hi Ross,
>>
>> On Mar 22, 2012, at 5:34 AM, Ross Laidlaw wrote:
>>
>>> Hi Chris,
>>>
>>> I'm writing to give an update on my progress on OODT-402 and getting
>>> up to speed with the OODT project.
>>>
>>> I've been reading through the documentation from
>>> http://oodt.apache.org/components/maven/filemgr and the wiki pages
>>> http://cwiki.apache.org/oodt. I've also read up on the GeoRSS format
>>> at http://georss.org and http://en.wikipedia.org/wiki/GeoRSS.
>>
>> Awesome, that's the right place to start!
>>
>>>
>>> By following the user guides (which are awesome by the way!)
>>
>> * thanks * Many folks have been really updating those lately (Tom Bennett, Cameron
>> Goodale, Sheryl John, and others) so thanks to them for that!
>>
>>> I have
>>> built OODT with maven v2.2.1 on my laptop (macbook running OSX Lion)
>>> and set up the File Manager program (I've ingested my first 'blah.txt'
>>> file with meta data! And also tested out some queries).
>>
>> You ROCK, nice!
>>
>>>
>>> As a next step, I'd like to install the File Manager webapp. Are
>>> there any recent guides for installing? I watched both of your Apache
>>> OODT Curation tutorials on YouTube (very cool) and also found some
>>> info about webapps from one of your replies on the
>>> user@oodt.apache.org mailing list (with link to slides
>>> http://oodt.apache.org/components/maven/grid/slides.pdf). I have my
>>> webapp target folders and war files from the build and I have Tomcat
>>> set up on my machine, so hopefully I'm not far off being up and
>>> running! Apologies if this is something obvious that I should know
>>> already (e.g. by learning more about Tomcat).
>>
>> Great, that's the right starting point.
>>
>>>
>>> I built the 0.3 release of OODT on my machine. But I also had a look
>>> through the latest webapp source code and noted your comments in the
>>> following file:
>>> https://svn.apache.org/repos/asf/oodt/trunk/webapp/fmprod/src/main/resources/rssconf.xml
>>>
>>> <!--
>>>
>>> If you want to turn your CAS File Manager into a GeoRSS
>>> simple service (see http://georss.org/simple), add the
>>> following block, assuming that you have indexed met fields
>>> named Latitude and Longitude for your product (update as
>>> appropriate otherwise).
>>>
>>> <tag name="georss:point" source="[Latitude] [Longitude]"/>
>>> -->
>>
>> Yep, the above is assuming that you index 2 met fields along with your
>> products, the Latitude met field, and the Longitude. If you indexed them
>> differently (e.g., a field named "geolat" or "geolng", then you would update
>> the above accordingly).
>>
>>>
>>>
>>> Am I right in thinking that this is the starting point for OODT-402?
>>
>> Absolutely that's the right starting point for getting GeoRSS out of the
>> File Manager, then the next step is to move onto SIS and read about its
>> GeoRSS data loader and Quad Tree. Admittedly over in SIS ville there's
>> a lot less documentation, but it would be great because there is also
>> as an Incubator project a lot more ability to easily contribute and get started
>> being part of the community.
>>
>>> I saw from georss.org that there are a few different GeoRSS formats
>>> (Simple, GML and W3C). But I read that the W3C format is a bit older
>>> and the GML format is quite extensive, so it's a great plan to use the
>>> simple format and work from there.
>>
>> It would be great to support the Simple to start out with and if there is
>> time to look at the GML and W3C versions (but only as it makes sense
>> and if there is time).
>>
>>>
>>> I'd like to set up a similar development environment to the OODT
>>> developers. Is Eclipse the IDE of choice?
>>
>> Yep most of the OODT devs use Eclipse and there are a wealth of
>> folks that could help you here on list if you have any trouble.
>>
>>> I noticed you using it on
>>> the youtube tutorials and also there's an 'OODT Eclipse Developer
>>> Help' guide on the wiki. I have version 3.7.2 (Indigo) installed on
>>> my machine but please let me know if there are any incompatibility
>>> problems.
>>
>> That sounds fine, should work great.
>>
>>>
>>> Regarding OODT-402, do you have a feel for how long you'd expect me to
>>> take in completing the project?
>>
>> I'm hoping that in a month you could have the whole thing running end, to
>> end, but even if it took 2 months or 3 months that would be great too. There's
>> a lot of room to grow in both projects, OODT and SIS, and you can really
>> take it where you want to go from there.
>>
>>> I'd like to put together a plan of
>>> action for my GSoC proposal. I have the three step outline from the
>>> OODT-402 JIRA page as the basis for the plan. I feel that I have a
>>> good knowledge of XML and core Java, for example I have passed the
>>> Oracle Certified Java Programmer exam. Hopefully I also have a good
>>> grounding in some of the design principles used in OODT, for example
>>> factory design patterns and coding to interfaces for extensibility, as
>>> I have taken several OO classes so far in my studies.
>>
>> Yeah I think you are perfect for the project and you will do great. The next
>> step is probably to start learning about SIS as you get closer to getting
>> the FM to spit out GeoRSS. Feel free to engage the SIS community
>> (sis-dev@incubator.apache.org) as you move forward there too and if
>> you have any questions let us know and we'll all try and help out.
>>
>>>
>>> I'm hoping to have some more specific questions about the steps for
>>> OODT-402 as I start using the webapp and examining the source code in
>>> more detail.
>>
>> Awesome happy to help!
>>
>>>
>>>
>>> Many thanks again for your time,
>>>
>>
>> And to yours! I'm super excited, great work so far Ross...
>>
>> Cheers,
>> Chris
>>
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> 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
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
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
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Re: OODT-402 progress update
Posted by "Ramirez, Paul M (388J)" <pa...@jpl.nasa.gov>.
Hey Ross,
Yep that should be changed.
--Paul
Sent from my iPhone
On May 10, 2012, at 9:05 PM, "Ross Laidlaw" <rl...@gmail.com> wrote:
> Hi Chris,
>
> I noticed the following commented code in the rssconf.xml file for the
> fmprod webapp:
>
> <!-- FIXME: adjust namespace URI? -->
> <cas:rssconf xmlns:cas="http://oodt.jpl.nasa.gov/1.0/cas">
>
>
> Since the work on OODT-402 is based on that file, would it be ok if I
> include an update for the URI in the patch? Would the following be
> correct?
>
> <cas:rssconf xmlns:cas="http://oodt.apache.org/1.0/cas">
>
>
> I'd also like to use the updated URI for the georss-config.xml as well.
>
>
> Ross
>
>
>
> On 28 April 2012 17:24, Mattmann, Chris A (388J)
> <ch...@jpl.nasa.gov> wrote:
>> Anytime, Ross!
>>
>> Cheers,
>> Chris
>>
>> On Apr 27, 2012, at 9:51 AM, Ross Laidlaw wrote:
>>
>>> Hi Chris!
>>>
>>> Thanks for responding so quickly and for the guidance. I'll set up
>>> the JIRA issues and add some specific info and questions to each item.
>>>
>>> Ross
>>>
>>>
>>>
>>>
>>> On 26 April 2012 16:25, Mattmann, Chris A (388J)
>>> <ch...@jpl.nasa.gov> wrote:
>>>> Hi Ross,
>>>>
>>>> No problem at all! Read on below and keep the questions coming!
>>>>
>>>> On Apr 26, 2012, at 5:27 AM, Ross Laidlaw wrote:
>>>>
>>>>> Hi Chris,
>>>>>
>>>>> I'm planning my next steps for working on OODT-402. The first task is
>>>>> to create a default GeoRSS config in the File Manager RSS service. Do
>>>>> you have a preference for where this file should be stored and
>>>>> accessed?
>>>>
>>>> Yep. I think we should ship it with the File Manager inside of:
>>>>
>>>> http://svn.apache.org/repos/asf/oodt/trunk/webapp/fmprod/src/main/resources/georss-config.xml
>>>>
>>>>> As a first step, in the demo that I set up recently I used
>>>>> the default 'rssconfig.xml' file for the fmprod webapp and followed
>>>>> your comments to add latitude and longitude tags to this.
>>>>>
>>>>
>>>> Yep in the georss-config.xml I would copy through the default RSS and config
>>>> and then just expose lat/lon with the comments/documentation.
>>>>
>>>> This could be a JIRA issue in itself.
>>>>
>>>>> For the 'LocationAwareProduct' definition, I was wondering if we could
>>>>> make this a virtual type that could then be inherited by concrete
>>>>> vendor types.
>>>>
>>>> +1, this sounds like a good strategy, and I would do it as a full
>>>> specced product-types.xml, elements.xml and product-type-element-map.xml
>>>> combination. A home for it could be:
>>>>
>>>> http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/main/resources/examples/geo
>>>>
>>>> As part of this, we should move the current contents of:
>>>>
>>>> http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/main/resources/examples/
>>>>
>>>> To:
>>>>
>>>> http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/main/resources/examples/core
>>>>
>>>> This would be 2 separate JIRA issues (for default geo policy, and then a separate
>>>> to move core, and make sure assembly.xml still works, and the unit tests, etc.)
>>>>
>>>>>
>>>>> Just a few questions and thoughts to get going! Apologies if I'm off track...
>>>>
>>>> HTH and rock on!
>>>>
>>>> Cheers,
>>>> Chris
>>>>
>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>> 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
>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>
>>
>>
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> 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
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>
Re: OODT-402 progress update
Posted by Ross Laidlaw <rl...@gmail.com>.
Cool, thanks guys! I'll include it in the patch for 449 (sub-task of 402)
On 11 May 2012 05:16, Mattmann, Chris A (388J)
<ch...@jpl.nasa.gov> wrote:
> +1, sounds great Ross.
>
> Cheers,
> Chris
>
On 11 May 2012 05:11, Ramirez, Paul M (388J)
<pa...@jpl.nasa.gov> wrote:
> Hey Ross,
>
> Yep that should be changed.
>
> --Paul
>
> Sent from my iPhone
>
>> On May 10, 2012, at 8:38 PM, Ross Laidlaw wrote:
>> Hi Chris,
>>
>> I noticed the following commented code in the rssconf.xml file for the
>> fmprod webapp:
>>
>> <!-- FIXME: adjust namespace URI? -->
>> <cas:rssconf xmlns:cas="http://oodt.jpl.nasa.gov/1.0/cas">
>>
>>
>> Since the work on OODT-402 is based on that file, would it be ok if I
>> include an update for the URI in the patch? Would the following be
>> correct?
>>
>> <cas:rssconf xmlns:cas="http://oodt.apache.org/1.0/cas">
>>
>>
>> I'd also like to use the updated URI for the georss-config.xml as well.
>>
>>
>> Ross
>>
>>
>>
>> On 28 April 2012 17:24, Mattmann, Chris A (388J)
>> <ch...@jpl.nasa.gov> wrote:
>>> Anytime, Ross!
>>>
>>> Cheers,
>>> Chris
>>>
>>> On Apr 27, 2012, at 9:51 AM, Ross Laidlaw wrote:
>>>
>>>> Hi Chris!
>>>>
>>>> Thanks for responding so quickly and for the guidance. I'll set up
>>>> the JIRA issues and add some specific info and questions to each item.
>>>>
>>>> Ross
>>>>
>>>>
>>>>
>>>>
>>>> On 26 April 2012 16:25, Mattmann, Chris A (388J)
>>>> <ch...@jpl.nasa.gov> wrote:
>>>>> Hi Ross,
>>>>>
>>>>> No problem at all! Read on below and keep the questions coming!
>>>>>
>>>>> On Apr 26, 2012, at 5:27 AM, Ross Laidlaw wrote:
>>>>>
>>>>>> Hi Chris,
>>>>>>
>>>>>> I'm planning my next steps for working on OODT-402. The first task is
>>>>>> to create a default GeoRSS config in the File Manager RSS service. Do
>>>>>> you have a preference for where this file should be stored and
>>>>>> accessed?
>>>>>
>>>>> Yep. I think we should ship it with the File Manager inside of:
>>>>>
>>>>> http://svn.apache.org/repos/asf/oodt/trunk/webapp/fmprod/src/main/resources/georss-config.xml
>>>>>
>>>>>> As a first step, in the demo that I set up recently I used
>>>>>> the default 'rssconfig.xml' file for the fmprod webapp and followed
>>>>>> your comments to add latitude and longitude tags to this.
>>>>>>
>>>>>
>>>>> Yep in the georss-config.xml I would copy through the default RSS and config
>>>>> and then just expose lat/lon with the comments/documentation.
>>>>>
>>>>> This could be a JIRA issue in itself.
>>>>>
>>>>>> For the 'LocationAwareProduct' definition, I was wondering if we could
>>>>>> make this a virtual type that could then be inherited by concrete
>>>>>> vendor types.
>>>>>
>>>>> +1, this sounds like a good strategy, and I would do it as a full
>>>>> specced product-types.xml, elements.xml and product-type-element-map.xml
>>>>> combination. A home for it could be:
>>>>>
>>>>> http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/main/resources/examples/geo
>>>>>
>>>>> As part of this, we should move the current contents of:
>>>>>
>>>>> http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/main/resources/examples/
>>>>>
>>>>> To:
>>>>>
>>>>> http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/main/resources/examples/core
>>>>>
>>>>> This would be 2 separate JIRA issues (for default geo policy, and then a separate
>>>>> to move core, and make sure assembly.xml still works, and the unit tests, etc.)
>>>>>
>>>>>>
>>>>>> Just a few questions and thoughts to get going! Apologies if I'm off track...
>>>>>
>>>>> HTH and rock on!
>>>>>
>>>>> Cheers,
>>>>> Chris
>>>>>
>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>> 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
>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>>
>>>
>>>
>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>> 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
>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 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
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
Re: OODT-402 progress update
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
+1, sounds great Ross.
Cheers,
Chris
On May 10, 2012, at 8:38 PM, Ross Laidlaw wrote:
> Hi Chris,
>
> I noticed the following commented code in the rssconf.xml file for the
> fmprod webapp:
>
> <!-- FIXME: adjust namespace URI? -->
> <cas:rssconf xmlns:cas="http://oodt.jpl.nasa.gov/1.0/cas">
>
>
> Since the work on OODT-402 is based on that file, would it be ok if I
> include an update for the URI in the patch? Would the following be
> correct?
>
> <cas:rssconf xmlns:cas="http://oodt.apache.org/1.0/cas">
>
>
> I'd also like to use the updated URI for the georss-config.xml as well.
>
>
> Ross
>
>
>
> On 28 April 2012 17:24, Mattmann, Chris A (388J)
> <ch...@jpl.nasa.gov> wrote:
>> Anytime, Ross!
>>
>> Cheers,
>> Chris
>>
>> On Apr 27, 2012, at 9:51 AM, Ross Laidlaw wrote:
>>
>>> Hi Chris!
>>>
>>> Thanks for responding so quickly and for the guidance. I'll set up
>>> the JIRA issues and add some specific info and questions to each item.
>>>
>>> Ross
>>>
>>>
>>>
>>>
>>> On 26 April 2012 16:25, Mattmann, Chris A (388J)
>>> <ch...@jpl.nasa.gov> wrote:
>>>> Hi Ross,
>>>>
>>>> No problem at all! Read on below and keep the questions coming!
>>>>
>>>> On Apr 26, 2012, at 5:27 AM, Ross Laidlaw wrote:
>>>>
>>>>> Hi Chris,
>>>>>
>>>>> I'm planning my next steps for working on OODT-402. The first task is
>>>>> to create a default GeoRSS config in the File Manager RSS service. Do
>>>>> you have a preference for where this file should be stored and
>>>>> accessed?
>>>>
>>>> Yep. I think we should ship it with the File Manager inside of:
>>>>
>>>> http://svn.apache.org/repos/asf/oodt/trunk/webapp/fmprod/src/main/resources/georss-config.xml
>>>>
>>>>> As a first step, in the demo that I set up recently I used
>>>>> the default 'rssconfig.xml' file for the fmprod webapp and followed
>>>>> your comments to add latitude and longitude tags to this.
>>>>>
>>>>
>>>> Yep in the georss-config.xml I would copy through the default RSS and config
>>>> and then just expose lat/lon with the comments/documentation.
>>>>
>>>> This could be a JIRA issue in itself.
>>>>
>>>>> For the 'LocationAwareProduct' definition, I was wondering if we could
>>>>> make this a virtual type that could then be inherited by concrete
>>>>> vendor types.
>>>>
>>>> +1, this sounds like a good strategy, and I would do it as a full
>>>> specced product-types.xml, elements.xml and product-type-element-map.xml
>>>> combination. A home for it could be:
>>>>
>>>> http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/main/resources/examples/geo
>>>>
>>>> As part of this, we should move the current contents of:
>>>>
>>>> http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/main/resources/examples/
>>>>
>>>> To:
>>>>
>>>> http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/main/resources/examples/core
>>>>
>>>> This would be 2 separate JIRA issues (for default geo policy, and then a separate
>>>> to move core, and make sure assembly.xml still works, and the unit tests, etc.)
>>>>
>>>>>
>>>>> Just a few questions and thoughts to get going! Apologies if I'm off track...
>>>>
>>>> HTH and rock on!
>>>>
>>>> Cheers,
>>>> Chris
>>>>
>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>> 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
>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>
>>
>>
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> 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
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
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
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Re: OODT-402 progress update
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Thanks Ross, as usual, great progress!
Cheers,
Chris
On May 14, 2012, at 4:48 PM, Ross Laidlaw wrote:
> Hi Chris!
>
> On 12 May 2012 18:13, Mattmann, Chris A (388J)
> <ch...@jpl.nasa.gov> wrote:
>>
>> Yep, +1 to creating a separate task and this sounds like great progress!
>
> I've recently created OODT-458 and transferred the namespace info over
> from OODT-449.
>
>
>> I would like to keep the cas namespace since it's really cas config and
>> to me, declaring the namespace there solidified that for me. Is there any
>> specific reason to remove it?
>
> I see what you mean and completely agree - no reason to remove it and
> makes sense to have it there in the config.
>
>
>> +1 to make it use RSSConfig in both the ProductServlet and the TransferServlet.
>
> I'll try to include this in OODT-458.
>
>
>> Also if you're feeling ambitious, a separate issue is to turn those 2 services
>> into JAX-RS services using CXF :) You can find examples of how to do that
>> in CAS curator (see its services) but it's really a separate issue. I just
>> wanted to whet your whistle b/c you are doing so great! :)
>
> Definitely! Sounds very interesting! I'd like to contribute to this
> work. Ricky Nguyen has replied with some info on this, so I'll follow
> up on his comments as well.
>
>
> Ross
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
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
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Re: OODT-402 progress update
Posted by Ross Laidlaw <rl...@gmail.com>.
Hi Chris!
On 12 May 2012 18:13, Mattmann, Chris A (388J)
<ch...@jpl.nasa.gov> wrote:
>
> Yep, +1 to creating a separate task and this sounds like great progress!
I've recently created OODT-458 and transferred the namespace info over
from OODT-449.
> I would like to keep the cas namespace since it's really cas config and
> to me, declaring the namespace there solidified that for me. Is there any
> specific reason to remove it?
I see what you mean and completely agree - no reason to remove it and
makes sense to have it there in the config.
> +1 to make it use RSSConfig in both the ProductServlet and the TransferServlet.
I'll try to include this in OODT-458.
> Also if you're feeling ambitious, a separate issue is to turn those 2 services
> into JAX-RS services using CXF :) You can find examples of how to do that
> in CAS curator (see its services) but it's really a separate issue. I just
> wanted to whet your whistle b/c you are doing so great! :)
Definitely! Sounds very interesting! I'd like to contribute to this
work. Ricky Nguyen has replied with some info on this, so I'll follow
up on his comments as well.
Ross
Re: OODT-402 progress update
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hey Ricky,
On May 25, 2012, at 1:58 PM, Nguyen, Ricky wrote:
> Nice work Ross! It's not even summer yet and you've finished your GSoC project!
Super +1, I know crazy huh.
>
> Chris,
> I too can't assign issues to myself. Unless I'm the one who filed it. Could you please fix my perms too? Thanks.
Fixed!
Cheers,
Chris
>
>
>
> On May 25, 2012, at 1:53 PM, Mattmann, Chris A (388J) wrote:
>
>> Hey Ross,
>>
>> You're set I set the JIRA perms for ya.
>>
>> We're fine on the fix version since 0.4 hasn't
>> shipped yet so your fixes will be in 0.4. Hackathon time! :)
>>
>> Cheers,
>> Chris
>>
>> On May 25, 2012, at 11:58 AM, Ross Laidlaw wrote:
>>
>>> Hi Chris,
>>>
>>> Ah! I knew I'd forgotten something! Thanks for the info - I've
>>> updated CHANGES.txt and uploaded patch to JIRA OODT-402 for reference.
>>> I have a couple more questions:
>>>
>>> i) I'd like to add myself as the assignee for all four tickets, but at
>>> the moment I can't. Is it a JIRA permissions thing or am I missing
>>> something obvious?
>>>
>>> ii) Shall we change the fix version for these tickets from 0.5 to 0.4?
>>>
>>>
>>> Ross
>>>
>>>
>>>
>>> On 25 May 2012 15:50, Mattmann, Chris A (388J)
>>> <ch...@jpl.nasa.gov> wrote:
>>>> Hey Ross,
>>>>
>>>> One thing I forgot -- please remember to update CHANGES.txt at the top level OODT
>>>> dir will the results of your changes.
>>>>
>>>> t's an ASCII readable light-weight change log that we ship with Apache OODT.
>>>>
>>>> Thanks!
>>>>
>>>> Cheers,
>>>> Chris
>>>>
>>>> On May 25, 2012, at 6:49 AM, Ross Laidlaw wrote:
>>>>
>>>>> Hi Chris,
>>>>>
>>>>> I've committed the patches for OODT-449, 452 and 453 and set the JIRA
>>>>> issues to 'resolved' (hope this is ok!).
>>>>>
>>>>> Would you like me to do anything more for the main issue 402? Or if
>>>>> everything is ok, I could close it if all of the basic steps are
>>>>> complete.
>>>>>
>>>>> Regards,
>>>>>
>>>>> Ross
>>>>>
>>>>>
>>>>>
>>>>> On 24 May 2012 12:12, Ross Laidlaw <rl...@gmail.com> wrote:
>>>>>> Thanks Chris! :) I'll go ahead with the commits and will let you know if I have any questions or info to report.
>>>>>>
>>>>>>
>>>>>>
>>>>>> On 24 May 2012, at 04:54, "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov> wrote:
>>>>>>
>>>>>>> Hi Ross,
>>>>>>>
>>>>>>> Patches look good to me, no worries about committing directly. You are now a full
>>>>>>> PMC member and OODT committer, so use the force :)
>>>>>>>
>>>>>>> Review Board is great because me, Ricky, Thomas B., Paul R., Sheryl, BFost,
>>>>>>> and others are actively leveraging it and love it. If you put your patches there
>>>>>>> you are bound to get tons of feedback (more so than JIRA atm). But I think you are
>>>>>>> fine with OODT-449, 452 and 453, we've discussed them plenty and there are
>>>>>>> no objections so +1 to move forward go for it!
>>>>>>>
>>>>>>> Cheers,
>>>>>>> Chris
>>>>>>>
>>>>>>> On May 23, 2012, at 7:11 PM, Ross Laidlaw wrote:
>>>>>>>
>>>>>>>> Hi Chris,
>>>>>>>>
>>>>>>>> I've uploaded patches for each sub-task for OODT-402 (these are
>>>>>>>> OODT-449, 452 and 453). I noted your comments and I wanted to ask
>>>>>>>> about the next steps. Would you like me to post the patches to review
>>>>>>>> board for a formal review? Or are you satisfied that everything's
>>>>>>>> looking good and covered in JIRA? If everything's fine and you're ok
>>>>>>>> for me to commit the changes I'd be happy to go ahead.
>>>>>>>>
>>>>>>>> Ross
>>>>>>>>
>>>>>>>>
>>>>>>>> On 15 May 2012 19:46, Mattmann, Chris A (388J)
>>>>>>>> <ch...@jpl.nasa.gov> wrote:
>>>>>>>>> +1 for RB!
>>>>>>>>>
>>>>>>>>> #win!
>>>>>>>>>
>>>>>>>>> Cheers,
>>>>>>>>> Chris
>>>>>>>>>
>>>>>>>>> On May 15, 2012, at 3:34 AM, Ramirez, Paul M (388J) wrote:
>>>>>>>>>
>>>>>>>>>> Hey Ricky,
>>>>>>>>>>
>>>>>>>>>> Sounds good. You can always just implement it as a patch and then when its
>>>>>>>>>> done commit it to the repo. That would make it easy to push through review
>>>>>>>>>> board too.
>>>>>>>>>>
>>>>>>>>>> --Paul
>>>>>>>>>>
>>>>>>>>>> On 5/14/12 9:16 PM, "Mattmann, Chris A (388J)"
>>>>>>>>>> <ch...@jpl.nasa.gov> wrote:
>>>>>>>>>>
>>>>>>>>>>> Hey Ricky,
>>>>>>>>>>>
>>>>>>>>>>> That's awesome, glad that you started those and hope you can
>>>>>>>>>>> dig them up!
>>>>>>>>>>>
>>>>>>>>>>> Cheers,
>>>>>>>>>>> Chris
>>>>>>>>>>>
>>>>>>>>>>> On May 14, 2012, at 5:03 PM, Ross Laidlaw wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Hi Ricky,
>>>>>>>>>>>>
>>>>>>>>>>>> On 14 May 2012 21:26, Nguyen, Ricky <rn...@chla.usc.edu> wrote:
>>>>>>>>>>>>> FYI, I've got some code lying around that ports the DataDeliverServlet
>>>>>>>>>>>>> and DatasetDeliveryServlet to JAX-RS using CXF. The reason I started it
>>>>>>>>>>>>> was because I thought we might be able to make use of CXF's oauth
>>>>>>>>>>>>> providers to secure this RESTful web service. But I hadn't figured out
>>>>>>>>>>>>> the oauth part (nor how to port the RDF/RSS servlets).
>>>>>>>>>>>>>
>>>>>>>>>>>>> If I find time, maybe I'll start a branch...
>>>>>>>>>>>>>
>>>>>>>>>>>>> -Ricky
>>>>>>>>>>>>
>>>>>>>>>>>> Sounds good. I'll try to close out OODT-402 and OODT-458 first, but
>>>>>>>>>>>> after that I'd be happy to contribute to this work if there's anything
>>>>>>>>>>>> I can do to help out. By the way, I found your emails with Chris and
>>>>>>>>>>>> Andrew about the various ways of serving files from File Manager very
>>>>>>>>>>>> informative! Really helped me to learn about all of the different
>>>>>>>>>>>> services available.
>>>>>>>>>>>>
>>>>>>>>>>>> Ross
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>>>>>>>> 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
>>>>>>>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>>>>>> 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
>>>>>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>>>> 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
>>>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>>>>
>>>>
>>
>>
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> 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
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>
>
>
>
>
> ---------------------------------------------------------------------
> CONFIDENTIALITY NOTICE: This e-mail message, including any attachments,
> is for the sole use of the intended recipient(s) and may contain confidential
> or legally privileged information. Any unauthorized review, use, disclosure
> or distribution is prohibited. If you are not the intended recipient, please
> contact the sender by reply e-mail and destroy all copies of this original message.
>
> ---------------------------------------------------------------------
>
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
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
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Re: OODT-402 progress update
Posted by "Nguyen, Ricky" <rn...@chla.usc.edu>.
Nice work Ross! It's not even summer yet and you've finished your GSoC project!
Chris,
I too can't assign issues to myself. Unless I'm the one who filed it. Could you please fix my perms too? Thanks.
-Ricky
On May 25, 2012, at 1:53 PM, Mattmann, Chris A (388J) wrote:
> Hey Ross,
>
> You're set I set the JIRA perms for ya.
>
> We're fine on the fix version since 0.4 hasn't
> shipped yet so your fixes will be in 0.4. Hackathon time! :)
>
> Cheers,
> Chris
>
> On May 25, 2012, at 11:58 AM, Ross Laidlaw wrote:
>
>> Hi Chris,
>>
>> Ah! I knew I'd forgotten something! Thanks for the info - I've
>> updated CHANGES.txt and uploaded patch to JIRA OODT-402 for reference.
>> I have a couple more questions:
>>
>> i) I'd like to add myself as the assignee for all four tickets, but at
>> the moment I can't. Is it a JIRA permissions thing or am I missing
>> something obvious?
>>
>> ii) Shall we change the fix version for these tickets from 0.5 to 0.4?
>>
>>
>> Ross
>>
>>
>>
>> On 25 May 2012 15:50, Mattmann, Chris A (388J)
>> <ch...@jpl.nasa.gov> wrote:
>>> Hey Ross,
>>>
>>> One thing I forgot -- please remember to update CHANGES.txt at the top level OODT
>>> dir will the results of your changes.
>>>
>>> t's an ASCII readable light-weight change log that we ship with Apache OODT.
>>>
>>> Thanks!
>>>
>>> Cheers,
>>> Chris
>>>
>>> On May 25, 2012, at 6:49 AM, Ross Laidlaw wrote:
>>>
>>>> Hi Chris,
>>>>
>>>> I've committed the patches for OODT-449, 452 and 453 and set the JIRA
>>>> issues to 'resolved' (hope this is ok!).
>>>>
>>>> Would you like me to do anything more for the main issue 402? Or if
>>>> everything is ok, I could close it if all of the basic steps are
>>>> complete.
>>>>
>>>> Regards,
>>>>
>>>> Ross
>>>>
>>>>
>>>>
>>>> On 24 May 2012 12:12, Ross Laidlaw <rl...@gmail.com> wrote:
>>>>> Thanks Chris! :) I'll go ahead with the commits and will let you know if I have any questions or info to report.
>>>>>
>>>>>
>>>>>
>>>>> On 24 May 2012, at 04:54, "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov> wrote:
>>>>>
>>>>>> Hi Ross,
>>>>>>
>>>>>> Patches look good to me, no worries about committing directly. You are now a full
>>>>>> PMC member and OODT committer, so use the force :)
>>>>>>
>>>>>> Review Board is great because me, Ricky, Thomas B., Paul R., Sheryl, BFost,
>>>>>> and others are actively leveraging it and love it. If you put your patches there
>>>>>> you are bound to get tons of feedback (more so than JIRA atm). But I think you are
>>>>>> fine with OODT-449, 452 and 453, we've discussed them plenty and there are
>>>>>> no objections so +1 to move forward go for it!
>>>>>>
>>>>>> Cheers,
>>>>>> Chris
>>>>>>
>>>>>> On May 23, 2012, at 7:11 PM, Ross Laidlaw wrote:
>>>>>>
>>>>>>> Hi Chris,
>>>>>>>
>>>>>>> I've uploaded patches for each sub-task for OODT-402 (these are
>>>>>>> OODT-449, 452 and 453). I noted your comments and I wanted to ask
>>>>>>> about the next steps. Would you like me to post the patches to review
>>>>>>> board for a formal review? Or are you satisfied that everything's
>>>>>>> looking good and covered in JIRA? If everything's fine and you're ok
>>>>>>> for me to commit the changes I'd be happy to go ahead.
>>>>>>>
>>>>>>> Ross
>>>>>>>
>>>>>>>
>>>>>>> On 15 May 2012 19:46, Mattmann, Chris A (388J)
>>>>>>> <ch...@jpl.nasa.gov> wrote:
>>>>>>>> +1 for RB!
>>>>>>>>
>>>>>>>> #win!
>>>>>>>>
>>>>>>>> Cheers,
>>>>>>>> Chris
>>>>>>>>
>>>>>>>> On May 15, 2012, at 3:34 AM, Ramirez, Paul M (388J) wrote:
>>>>>>>>
>>>>>>>>> Hey Ricky,
>>>>>>>>>
>>>>>>>>> Sounds good. You can always just implement it as a patch and then when its
>>>>>>>>> done commit it to the repo. That would make it easy to push through review
>>>>>>>>> board too.
>>>>>>>>>
>>>>>>>>> --Paul
>>>>>>>>>
>>>>>>>>> On 5/14/12 9:16 PM, "Mattmann, Chris A (388J)"
>>>>>>>>> <ch...@jpl.nasa.gov> wrote:
>>>>>>>>>
>>>>>>>>>> Hey Ricky,
>>>>>>>>>>
>>>>>>>>>> That's awesome, glad that you started those and hope you can
>>>>>>>>>> dig them up!
>>>>>>>>>>
>>>>>>>>>> Cheers,
>>>>>>>>>> Chris
>>>>>>>>>>
>>>>>>>>>> On May 14, 2012, at 5:03 PM, Ross Laidlaw wrote:
>>>>>>>>>>
>>>>>>>>>>> Hi Ricky,
>>>>>>>>>>>
>>>>>>>>>>> On 14 May 2012 21:26, Nguyen, Ricky <rn...@chla.usc.edu> wrote:
>>>>>>>>>>>> FYI, I've got some code lying around that ports the DataDeliverServlet
>>>>>>>>>>>> and DatasetDeliveryServlet to JAX-RS using CXF. The reason I started it
>>>>>>>>>>>> was because I thought we might be able to make use of CXF's oauth
>>>>>>>>>>>> providers to secure this RESTful web service. But I hadn't figured out
>>>>>>>>>>>> the oauth part (nor how to port the RDF/RSS servlets).
>>>>>>>>>>>>
>>>>>>>>>>>> If I find time, maybe I'll start a branch...
>>>>>>>>>>>>
>>>>>>>>>>>> -Ricky
>>>>>>>>>>>
>>>>>>>>>>> Sounds good. I'll try to close out OODT-402 and OODT-458 first, but
>>>>>>>>>>> after that I'd be happy to contribute to this work if there's anything
>>>>>>>>>>> I can do to help out. By the way, I found your emails with Chris and
>>>>>>>>>>> Andrew about the various ways of serving files from File Manager very
>>>>>>>>>>> informative! Really helped me to learn about all of the different
>>>>>>>>>>> services available.
>>>>>>>>>>>
>>>>>>>>>>> Ross
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>>>>>>> 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
>>>>>>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>>>>> 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
>>>>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>>>>>
>>>>>>
>>>>>>
>>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>>> 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
>>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>>>
>>>
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 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
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
---------------------------------------------------------------------
CONFIDENTIALITY NOTICE: This e-mail message, including any attachments,
is for the sole use of the intended recipient(s) and may contain confidential
or legally privileged information. Any unauthorized review, use, disclosure
or distribution is prohibited. If you are not the intended recipient, please
contact the sender by reply e-mail and destroy all copies of this original message.
---------------------------------------------------------------------
Re: OODT-402 progress update
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hey Ross,
You're set I set the JIRA perms for ya.
We're fine on the fix version since 0.4 hasn't
shipped yet so your fixes will be in 0.4. Hackathon time! :)
Cheers,
Chris
On May 25, 2012, at 11:58 AM, Ross Laidlaw wrote:
> Hi Chris,
>
> Ah! I knew I'd forgotten something! Thanks for the info - I've
> updated CHANGES.txt and uploaded patch to JIRA OODT-402 for reference.
> I have a couple more questions:
>
> i) I'd like to add myself as the assignee for all four tickets, but at
> the moment I can't. Is it a JIRA permissions thing or am I missing
> something obvious?
>
> ii) Shall we change the fix version for these tickets from 0.5 to 0.4?
>
>
> Ross
>
>
>
> On 25 May 2012 15:50, Mattmann, Chris A (388J)
> <ch...@jpl.nasa.gov> wrote:
>> Hey Ross,
>>
>> One thing I forgot -- please remember to update CHANGES.txt at the top level OODT
>> dir will the results of your changes.
>>
>> t's an ASCII readable light-weight change log that we ship with Apache OODT.
>>
>> Thanks!
>>
>> Cheers,
>> Chris
>>
>> On May 25, 2012, at 6:49 AM, Ross Laidlaw wrote:
>>
>>> Hi Chris,
>>>
>>> I've committed the patches for OODT-449, 452 and 453 and set the JIRA
>>> issues to 'resolved' (hope this is ok!).
>>>
>>> Would you like me to do anything more for the main issue 402? Or if
>>> everything is ok, I could close it if all of the basic steps are
>>> complete.
>>>
>>> Regards,
>>>
>>> Ross
>>>
>>>
>>>
>>> On 24 May 2012 12:12, Ross Laidlaw <rl...@gmail.com> wrote:
>>>> Thanks Chris! :) I'll go ahead with the commits and will let you know if I have any questions or info to report.
>>>>
>>>>
>>>>
>>>> On 24 May 2012, at 04:54, "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov> wrote:
>>>>
>>>>> Hi Ross,
>>>>>
>>>>> Patches look good to me, no worries about committing directly. You are now a full
>>>>> PMC member and OODT committer, so use the force :)
>>>>>
>>>>> Review Board is great because me, Ricky, Thomas B., Paul R., Sheryl, BFost,
>>>>> and others are actively leveraging it and love it. If you put your patches there
>>>>> you are bound to get tons of feedback (more so than JIRA atm). But I think you are
>>>>> fine with OODT-449, 452 and 453, we've discussed them plenty and there are
>>>>> no objections so +1 to move forward go for it!
>>>>>
>>>>> Cheers,
>>>>> Chris
>>>>>
>>>>> On May 23, 2012, at 7:11 PM, Ross Laidlaw wrote:
>>>>>
>>>>>> Hi Chris,
>>>>>>
>>>>>> I've uploaded patches for each sub-task for OODT-402 (these are
>>>>>> OODT-449, 452 and 453). I noted your comments and I wanted to ask
>>>>>> about the next steps. Would you like me to post the patches to review
>>>>>> board for a formal review? Or are you satisfied that everything's
>>>>>> looking good and covered in JIRA? If everything's fine and you're ok
>>>>>> for me to commit the changes I'd be happy to go ahead.
>>>>>>
>>>>>> Ross
>>>>>>
>>>>>>
>>>>>> On 15 May 2012 19:46, Mattmann, Chris A (388J)
>>>>>> <ch...@jpl.nasa.gov> wrote:
>>>>>>> +1 for RB!
>>>>>>>
>>>>>>> #win!
>>>>>>>
>>>>>>> Cheers,
>>>>>>> Chris
>>>>>>>
>>>>>>> On May 15, 2012, at 3:34 AM, Ramirez, Paul M (388J) wrote:
>>>>>>>
>>>>>>>> Hey Ricky,
>>>>>>>>
>>>>>>>> Sounds good. You can always just implement it as a patch and then when its
>>>>>>>> done commit it to the repo. That would make it easy to push through review
>>>>>>>> board too.
>>>>>>>>
>>>>>>>> --Paul
>>>>>>>>
>>>>>>>> On 5/14/12 9:16 PM, "Mattmann, Chris A (388J)"
>>>>>>>> <ch...@jpl.nasa.gov> wrote:
>>>>>>>>
>>>>>>>>> Hey Ricky,
>>>>>>>>>
>>>>>>>>> That's awesome, glad that you started those and hope you can
>>>>>>>>> dig them up!
>>>>>>>>>
>>>>>>>>> Cheers,
>>>>>>>>> Chris
>>>>>>>>>
>>>>>>>>> On May 14, 2012, at 5:03 PM, Ross Laidlaw wrote:
>>>>>>>>>
>>>>>>>>>> Hi Ricky,
>>>>>>>>>>
>>>>>>>>>> On 14 May 2012 21:26, Nguyen, Ricky <rn...@chla.usc.edu> wrote:
>>>>>>>>>>> FYI, I've got some code lying around that ports the DataDeliverServlet
>>>>>>>>>>> and DatasetDeliveryServlet to JAX-RS using CXF. The reason I started it
>>>>>>>>>>> was because I thought we might be able to make use of CXF's oauth
>>>>>>>>>>> providers to secure this RESTful web service. But I hadn't figured out
>>>>>>>>>>> the oauth part (nor how to port the RDF/RSS servlets).
>>>>>>>>>>>
>>>>>>>>>>> If I find time, maybe I'll start a branch...
>>>>>>>>>>>
>>>>>>>>>>> -Ricky
>>>>>>>>>>
>>>>>>>>>> Sounds good. I'll try to close out OODT-402 and OODT-458 first, but
>>>>>>>>>> after that I'd be happy to contribute to this work if there's anything
>>>>>>>>>> I can do to help out. By the way, I found your emails with Chris and
>>>>>>>>>> Andrew about the various ways of serving files from File Manager very
>>>>>>>>>> informative! Really helped me to learn about all of the different
>>>>>>>>>> services available.
>>>>>>>>>>
>>>>>>>>>> Ross
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>>>>>> 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
>>>>>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>>>> 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
>>>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>>>>
>>>>>
>>>>>
>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>> 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
>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>>
>>
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
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
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Re: OODT-402 progress update
Posted by Ross Laidlaw <rl...@gmail.com>.
Hi Chris,
Ah! I knew I'd forgotten something! Thanks for the info - I've
updated CHANGES.txt and uploaded patch to JIRA OODT-402 for reference.
I have a couple more questions:
i) I'd like to add myself as the assignee for all four tickets, but at
the moment I can't. Is it a JIRA permissions thing or am I missing
something obvious?
ii) Shall we change the fix version for these tickets from 0.5 to 0.4?
Ross
On 25 May 2012 15:50, Mattmann, Chris A (388J)
<ch...@jpl.nasa.gov> wrote:
> Hey Ross,
>
> One thing I forgot -- please remember to update CHANGES.txt at the top level OODT
> dir will the results of your changes.
>
> t's an ASCII readable light-weight change log that we ship with Apache OODT.
>
> Thanks!
>
> Cheers,
> Chris
>
> On May 25, 2012, at 6:49 AM, Ross Laidlaw wrote:
>
>> Hi Chris,
>>
>> I've committed the patches for OODT-449, 452 and 453 and set the JIRA
>> issues to 'resolved' (hope this is ok!).
>>
>> Would you like me to do anything more for the main issue 402? Or if
>> everything is ok, I could close it if all of the basic steps are
>> complete.
>>
>> Regards,
>>
>> Ross
>>
>>
>>
>> On 24 May 2012 12:12, Ross Laidlaw <rl...@gmail.com> wrote:
>>> Thanks Chris! :) I'll go ahead with the commits and will let you know if I have any questions or info to report.
>>>
>>>
>>>
>>> On 24 May 2012, at 04:54, "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov> wrote:
>>>
>>>> Hi Ross,
>>>>
>>>> Patches look good to me, no worries about committing directly. You are now a full
>>>> PMC member and OODT committer, so use the force :)
>>>>
>>>> Review Board is great because me, Ricky, Thomas B., Paul R., Sheryl, BFost,
>>>> and others are actively leveraging it and love it. If you put your patches there
>>>> you are bound to get tons of feedback (more so than JIRA atm). But I think you are
>>>> fine with OODT-449, 452 and 453, we've discussed them plenty and there are
>>>> no objections so +1 to move forward go for it!
>>>>
>>>> Cheers,
>>>> Chris
>>>>
>>>> On May 23, 2012, at 7:11 PM, Ross Laidlaw wrote:
>>>>
>>>>> Hi Chris,
>>>>>
>>>>> I've uploaded patches for each sub-task for OODT-402 (these are
>>>>> OODT-449, 452 and 453). I noted your comments and I wanted to ask
>>>>> about the next steps. Would you like me to post the patches to review
>>>>> board for a formal review? Or are you satisfied that everything's
>>>>> looking good and covered in JIRA? If everything's fine and you're ok
>>>>> for me to commit the changes I'd be happy to go ahead.
>>>>>
>>>>> Ross
>>>>>
>>>>>
>>>>> On 15 May 2012 19:46, Mattmann, Chris A (388J)
>>>>> <ch...@jpl.nasa.gov> wrote:
>>>>>> +1 for RB!
>>>>>>
>>>>>> #win!
>>>>>>
>>>>>> Cheers,
>>>>>> Chris
>>>>>>
>>>>>> On May 15, 2012, at 3:34 AM, Ramirez, Paul M (388J) wrote:
>>>>>>
>>>>>>> Hey Ricky,
>>>>>>>
>>>>>>> Sounds good. You can always just implement it as a patch and then when its
>>>>>>> done commit it to the repo. That would make it easy to push through review
>>>>>>> board too.
>>>>>>>
>>>>>>> --Paul
>>>>>>>
>>>>>>> On 5/14/12 9:16 PM, "Mattmann, Chris A (388J)"
>>>>>>> <ch...@jpl.nasa.gov> wrote:
>>>>>>>
>>>>>>>> Hey Ricky,
>>>>>>>>
>>>>>>>> That's awesome, glad that you started those and hope you can
>>>>>>>> dig them up!
>>>>>>>>
>>>>>>>> Cheers,
>>>>>>>> Chris
>>>>>>>>
>>>>>>>> On May 14, 2012, at 5:03 PM, Ross Laidlaw wrote:
>>>>>>>>
>>>>>>>>> Hi Ricky,
>>>>>>>>>
>>>>>>>>> On 14 May 2012 21:26, Nguyen, Ricky <rn...@chla.usc.edu> wrote:
>>>>>>>>>> FYI, I've got some code lying around that ports the DataDeliverServlet
>>>>>>>>>> and DatasetDeliveryServlet to JAX-RS using CXF. The reason I started it
>>>>>>>>>> was because I thought we might be able to make use of CXF's oauth
>>>>>>>>>> providers to secure this RESTful web service. But I hadn't figured out
>>>>>>>>>> the oauth part (nor how to port the RDF/RSS servlets).
>>>>>>>>>>
>>>>>>>>>> If I find time, maybe I'll start a branch...
>>>>>>>>>>
>>>>>>>>>> -Ricky
>>>>>>>>>
>>>>>>>>> Sounds good. I'll try to close out OODT-402 and OODT-458 first, but
>>>>>>>>> after that I'd be happy to contribute to this work if there's anything
>>>>>>>>> I can do to help out. By the way, I found your emails with Chris and
>>>>>>>>> Andrew about the various ways of serving files from File Manager very
>>>>>>>>> informative! Really helped me to learn about all of the different
>>>>>>>>> services available.
>>>>>>>>>
>>>>>>>>> Ross
>>>>>>>>
>>>>>>>>
>>>>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>>>>> 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
>>>>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>>> 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
>>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>>>
>>>>
>>>>
>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>> 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
>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>
>
Re: OODT-402 progress update
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hey Ross,
One thing I forgot -- please remember to update CHANGES.txt at the top level OODT
dir will the results of your changes.
t's an ASCII readable light-weight change log that we ship with Apache OODT.
Thanks!
Cheers,
Chris
On May 25, 2012, at 6:49 AM, Ross Laidlaw wrote:
> Hi Chris,
>
> I've committed the patches for OODT-449, 452 and 453 and set the JIRA
> issues to 'resolved' (hope this is ok!).
>
> Would you like me to do anything more for the main issue 402? Or if
> everything is ok, I could close it if all of the basic steps are
> complete.
>
> Regards,
>
> Ross
>
>
>
> On 24 May 2012 12:12, Ross Laidlaw <rl...@gmail.com> wrote:
>> Thanks Chris! :) I'll go ahead with the commits and will let you know if I have any questions or info to report.
>>
>>
>>
>> On 24 May 2012, at 04:54, "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov> wrote:
>>
>>> Hi Ross,
>>>
>>> Patches look good to me, no worries about committing directly. You are now a full
>>> PMC member and OODT committer, so use the force :)
>>>
>>> Review Board is great because me, Ricky, Thomas B., Paul R., Sheryl, BFost,
>>> and others are actively leveraging it and love it. If you put your patches there
>>> you are bound to get tons of feedback (more so than JIRA atm). But I think you are
>>> fine with OODT-449, 452 and 453, we've discussed them plenty and there are
>>> no objections so +1 to move forward go for it!
>>>
>>> Cheers,
>>> Chris
>>>
>>> On May 23, 2012, at 7:11 PM, Ross Laidlaw wrote:
>>>
>>>> Hi Chris,
>>>>
>>>> I've uploaded patches for each sub-task for OODT-402 (these are
>>>> OODT-449, 452 and 453). I noted your comments and I wanted to ask
>>>> about the next steps. Would you like me to post the patches to review
>>>> board for a formal review? Or are you satisfied that everything's
>>>> looking good and covered in JIRA? If everything's fine and you're ok
>>>> for me to commit the changes I'd be happy to go ahead.
>>>>
>>>> Ross
>>>>
>>>>
>>>> On 15 May 2012 19:46, Mattmann, Chris A (388J)
>>>> <ch...@jpl.nasa.gov> wrote:
>>>>> +1 for RB!
>>>>>
>>>>> #win!
>>>>>
>>>>> Cheers,
>>>>> Chris
>>>>>
>>>>> On May 15, 2012, at 3:34 AM, Ramirez, Paul M (388J) wrote:
>>>>>
>>>>>> Hey Ricky,
>>>>>>
>>>>>> Sounds good. You can always just implement it as a patch and then when its
>>>>>> done commit it to the repo. That would make it easy to push through review
>>>>>> board too.
>>>>>>
>>>>>> --Paul
>>>>>>
>>>>>> On 5/14/12 9:16 PM, "Mattmann, Chris A (388J)"
>>>>>> <ch...@jpl.nasa.gov> wrote:
>>>>>>
>>>>>>> Hey Ricky,
>>>>>>>
>>>>>>> That's awesome, glad that you started those and hope you can
>>>>>>> dig them up!
>>>>>>>
>>>>>>> Cheers,
>>>>>>> Chris
>>>>>>>
>>>>>>> On May 14, 2012, at 5:03 PM, Ross Laidlaw wrote:
>>>>>>>
>>>>>>>> Hi Ricky,
>>>>>>>>
>>>>>>>> On 14 May 2012 21:26, Nguyen, Ricky <rn...@chla.usc.edu> wrote:
>>>>>>>>> FYI, I've got some code lying around that ports the DataDeliverServlet
>>>>>>>>> and DatasetDeliveryServlet to JAX-RS using CXF. The reason I started it
>>>>>>>>> was because I thought we might be able to make use of CXF's oauth
>>>>>>>>> providers to secure this RESTful web service. But I hadn't figured out
>>>>>>>>> the oauth part (nor how to port the RDF/RSS servlets).
>>>>>>>>>
>>>>>>>>> If I find time, maybe I'll start a branch...
>>>>>>>>>
>>>>>>>>> -Ricky
>>>>>>>>
>>>>>>>> Sounds good. I'll try to close out OODT-402 and OODT-458 first, but
>>>>>>>> after that I'd be happy to contribute to this work if there's anything
>>>>>>>> I can do to help out. By the way, I found your emails with Chris and
>>>>>>>> Andrew about the various ways of serving files from File Manager very
>>>>>>>> informative! Really helped me to learn about all of the different
>>>>>>>> services available.
>>>>>>>>
>>>>>>>> Ross
>>>>>>>
>>>>>>>
>>>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>>>> 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
>>>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>> 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
>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>>
>>>
>>>
>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>> 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
>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>
Re: OODT-402 progress update
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hey Ross,
+1 to close out 402 looks awesome and you did great! Keep #winning...
Cheers,
Chris
On May 25, 2012, at 6:49 AM, Ross Laidlaw wrote:
> Hi Chris,
>
> I've committed the patches for OODT-449, 452 and 453 and set the JIRA
> issues to 'resolved' (hope this is ok!).
>
> Would you like me to do anything more for the main issue 402? Or if
> everything is ok, I could close it if all of the basic steps are
> complete.
>
> Regards,
>
> Ross
>
>
>
> On 24 May 2012 12:12, Ross Laidlaw <rl...@gmail.com> wrote:
>> Thanks Chris! :) I'll go ahead with the commits and will let you know if I have any questions or info to report.
>>
>>
>>
>> On 24 May 2012, at 04:54, "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov> wrote:
>>
>>> Hi Ross,
>>>
>>> Patches look good to me, no worries about committing directly. You are now a full
>>> PMC member and OODT committer, so use the force :)
>>>
>>> Review Board is great because me, Ricky, Thomas B., Paul R., Sheryl, BFost,
>>> and others are actively leveraging it and love it. If you put your patches there
>>> you are bound to get tons of feedback (more so than JIRA atm). But I think you are
>>> fine with OODT-449, 452 and 453, we've discussed them plenty and there are
>>> no objections so +1 to move forward go for it!
>>>
>>> Cheers,
>>> Chris
>>>
>>> On May 23, 2012, at 7:11 PM, Ross Laidlaw wrote:
>>>
>>>> Hi Chris,
>>>>
>>>> I've uploaded patches for each sub-task for OODT-402 (these are
>>>> OODT-449, 452 and 453). I noted your comments and I wanted to ask
>>>> about the next steps. Would you like me to post the patches to review
>>>> board for a formal review? Or are you satisfied that everything's
>>>> looking good and covered in JIRA? If everything's fine and you're ok
>>>> for me to commit the changes I'd be happy to go ahead.
>>>>
>>>> Ross
>>>>
>>>>
>>>> On 15 May 2012 19:46, Mattmann, Chris A (388J)
>>>> <ch...@jpl.nasa.gov> wrote:
>>>>> +1 for RB!
>>>>>
>>>>> #win!
>>>>>
>>>>> Cheers,
>>>>> Chris
>>>>>
>>>>> On May 15, 2012, at 3:34 AM, Ramirez, Paul M (388J) wrote:
>>>>>
>>>>>> Hey Ricky,
>>>>>>
>>>>>> Sounds good. You can always just implement it as a patch and then when its
>>>>>> done commit it to the repo. That would make it easy to push through review
>>>>>> board too.
>>>>>>
>>>>>> --Paul
>>>>>>
>>>>>> On 5/14/12 9:16 PM, "Mattmann, Chris A (388J)"
>>>>>> <ch...@jpl.nasa.gov> wrote:
>>>>>>
>>>>>>> Hey Ricky,
>>>>>>>
>>>>>>> That's awesome, glad that you started those and hope you can
>>>>>>> dig them up!
>>>>>>>
>>>>>>> Cheers,
>>>>>>> Chris
>>>>>>>
>>>>>>> On May 14, 2012, at 5:03 PM, Ross Laidlaw wrote:
>>>>>>>
>>>>>>>> Hi Ricky,
>>>>>>>>
>>>>>>>> On 14 May 2012 21:26, Nguyen, Ricky <rn...@chla.usc.edu> wrote:
>>>>>>>>> FYI, I've got some code lying around that ports the DataDeliverServlet
>>>>>>>>> and DatasetDeliveryServlet to JAX-RS using CXF. The reason I started it
>>>>>>>>> was because I thought we might be able to make use of CXF's oauth
>>>>>>>>> providers to secure this RESTful web service. But I hadn't figured out
>>>>>>>>> the oauth part (nor how to port the RDF/RSS servlets).
>>>>>>>>>
>>>>>>>>> If I find time, maybe I'll start a branch...
>>>>>>>>>
>>>>>>>>> -Ricky
>>>>>>>>
>>>>>>>> Sounds good. I'll try to close out OODT-402 and OODT-458 first, but
>>>>>>>> after that I'd be happy to contribute to this work if there's anything
>>>>>>>> I can do to help out. By the way, I found your emails with Chris and
>>>>>>>> Andrew about the various ways of serving files from File Manager very
>>>>>>>> informative! Really helped me to learn about all of the different
>>>>>>>> services available.
>>>>>>>>
>>>>>>>> Ross
>>>>>>>
>>>>>>>
>>>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>>>> 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
>>>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>> 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
>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>>
>>>
>>>
>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>> 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
>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>
Re: OODT-402 progress update
Posted by Ross Laidlaw <rl...@gmail.com>.
Hi Chris,
I've committed the patches for OODT-449, 452 and 453 and set the JIRA
issues to 'resolved' (hope this is ok!).
Would you like me to do anything more for the main issue 402? Or if
everything is ok, I could close it if all of the basic steps are
complete.
Regards,
Ross
On 24 May 2012 12:12, Ross Laidlaw <rl...@gmail.com> wrote:
> Thanks Chris! :) I'll go ahead with the commits and will let you know if I have any questions or info to report.
>
>
>
> On 24 May 2012, at 04:54, "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov> wrote:
>
>> Hi Ross,
>>
>> Patches look good to me, no worries about committing directly. You are now a full
>> PMC member and OODT committer, so use the force :)
>>
>> Review Board is great because me, Ricky, Thomas B., Paul R., Sheryl, BFost,
>> and others are actively leveraging it and love it. If you put your patches there
>> you are bound to get tons of feedback (more so than JIRA atm). But I think you are
>> fine with OODT-449, 452 and 453, we've discussed them plenty and there are
>> no objections so +1 to move forward go for it!
>>
>> Cheers,
>> Chris
>>
>> On May 23, 2012, at 7:11 PM, Ross Laidlaw wrote:
>>
>>> Hi Chris,
>>>
>>> I've uploaded patches for each sub-task for OODT-402 (these are
>>> OODT-449, 452 and 453). I noted your comments and I wanted to ask
>>> about the next steps. Would you like me to post the patches to review
>>> board for a formal review? Or are you satisfied that everything's
>>> looking good and covered in JIRA? If everything's fine and you're ok
>>> for me to commit the changes I'd be happy to go ahead.
>>>
>>> Ross
>>>
>>>
>>> On 15 May 2012 19:46, Mattmann, Chris A (388J)
>>> <ch...@jpl.nasa.gov> wrote:
>>>> +1 for RB!
>>>>
>>>> #win!
>>>>
>>>> Cheers,
>>>> Chris
>>>>
>>>> On May 15, 2012, at 3:34 AM, Ramirez, Paul M (388J) wrote:
>>>>
>>>>> Hey Ricky,
>>>>>
>>>>> Sounds good. You can always just implement it as a patch and then when its
>>>>> done commit it to the repo. That would make it easy to push through review
>>>>> board too.
>>>>>
>>>>> --Paul
>>>>>
>>>>> On 5/14/12 9:16 PM, "Mattmann, Chris A (388J)"
>>>>> <ch...@jpl.nasa.gov> wrote:
>>>>>
>>>>>> Hey Ricky,
>>>>>>
>>>>>> That's awesome, glad that you started those and hope you can
>>>>>> dig them up!
>>>>>>
>>>>>> Cheers,
>>>>>> Chris
>>>>>>
>>>>>> On May 14, 2012, at 5:03 PM, Ross Laidlaw wrote:
>>>>>>
>>>>>>> Hi Ricky,
>>>>>>>
>>>>>>> On 14 May 2012 21:26, Nguyen, Ricky <rn...@chla.usc.edu> wrote:
>>>>>>>> FYI, I've got some code lying around that ports the DataDeliverServlet
>>>>>>>> and DatasetDeliveryServlet to JAX-RS using CXF. The reason I started it
>>>>>>>> was because I thought we might be able to make use of CXF's oauth
>>>>>>>> providers to secure this RESTful web service. But I hadn't figured out
>>>>>>>> the oauth part (nor how to port the RDF/RSS servlets).
>>>>>>>>
>>>>>>>> If I find time, maybe I'll start a branch...
>>>>>>>>
>>>>>>>> -Ricky
>>>>>>>
>>>>>>> Sounds good. I'll try to close out OODT-402 and OODT-458 first, but
>>>>>>> after that I'd be happy to contribute to this work if there's anything
>>>>>>> I can do to help out. By the way, I found your emails with Chris and
>>>>>>> Andrew about the various ways of serving files from File Manager very
>>>>>>> informative! Really helped me to learn about all of the different
>>>>>>> services available.
>>>>>>>
>>>>>>> Ross
>>>>>>
>>>>>>
>>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>>> 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
>>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>>>
>>>>>
>>>>
>>>>
>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>> 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
>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>
>>
>>
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> 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
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>
Re: OODT-402 progress update
Posted by Ross Laidlaw <rl...@gmail.com>.
Thanks Chris! :) I'll go ahead with the commits and will let you know if I have any questions or info to report.
On 24 May 2012, at 04:54, "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov> wrote:
> Hi Ross,
>
> Patches look good to me, no worries about committing directly. You are now a full
> PMC member and OODT committer, so use the force :)
>
> Review Board is great because me, Ricky, Thomas B., Paul R., Sheryl, BFost,
> and others are actively leveraging it and love it. If you put your patches there
> you are bound to get tons of feedback (more so than JIRA atm). But I think you are
> fine with OODT-449, 452 and 453, we've discussed them plenty and there are
> no objections so +1 to move forward go for it!
>
> Cheers,
> Chris
>
> On May 23, 2012, at 7:11 PM, Ross Laidlaw wrote:
>
>> Hi Chris,
>>
>> I've uploaded patches for each sub-task for OODT-402 (these are
>> OODT-449, 452 and 453). I noted your comments and I wanted to ask
>> about the next steps. Would you like me to post the patches to review
>> board for a formal review? Or are you satisfied that everything's
>> looking good and covered in JIRA? If everything's fine and you're ok
>> for me to commit the changes I'd be happy to go ahead.
>>
>> Ross
>>
>>
>> On 15 May 2012 19:46, Mattmann, Chris A (388J)
>> <ch...@jpl.nasa.gov> wrote:
>>> +1 for RB!
>>>
>>> #win!
>>>
>>> Cheers,
>>> Chris
>>>
>>> On May 15, 2012, at 3:34 AM, Ramirez, Paul M (388J) wrote:
>>>
>>>> Hey Ricky,
>>>>
>>>> Sounds good. You can always just implement it as a patch and then when its
>>>> done commit it to the repo. That would make it easy to push through review
>>>> board too.
>>>>
>>>> --Paul
>>>>
>>>> On 5/14/12 9:16 PM, "Mattmann, Chris A (388J)"
>>>> <ch...@jpl.nasa.gov> wrote:
>>>>
>>>>> Hey Ricky,
>>>>>
>>>>> That's awesome, glad that you started those and hope you can
>>>>> dig them up!
>>>>>
>>>>> Cheers,
>>>>> Chris
>>>>>
>>>>> On May 14, 2012, at 5:03 PM, Ross Laidlaw wrote:
>>>>>
>>>>>> Hi Ricky,
>>>>>>
>>>>>> On 14 May 2012 21:26, Nguyen, Ricky <rn...@chla.usc.edu> wrote:
>>>>>>> FYI, I've got some code lying around that ports the DataDeliverServlet
>>>>>>> and DatasetDeliveryServlet to JAX-RS using CXF. The reason I started it
>>>>>>> was because I thought we might be able to make use of CXF's oauth
>>>>>>> providers to secure this RESTful web service. But I hadn't figured out
>>>>>>> the oauth part (nor how to port the RDF/RSS servlets).
>>>>>>>
>>>>>>> If I find time, maybe I'll start a branch...
>>>>>>>
>>>>>>> -Ricky
>>>>>>
>>>>>> Sounds good. I'll try to close out OODT-402 and OODT-458 first, but
>>>>>> after that I'd be happy to contribute to this work if there's anything
>>>>>> I can do to help out. By the way, I found your emails with Chris and
>>>>>> Andrew about the various ways of serving files from File Manager very
>>>>>> informative! Really helped me to learn about all of the different
>>>>>> services available.
>>>>>>
>>>>>> Ross
>>>>>
>>>>>
>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>> 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
>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>>
>>>>
>>>
>>>
>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>> 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
>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 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
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
Re: OODT-402 progress update
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hi Ross,
Patches look good to me, no worries about committing directly. You are now a full
PMC member and OODT committer, so use the force :)
Review Board is great because me, Ricky, Thomas B., Paul R., Sheryl, BFost,
and others are actively leveraging it and love it. If you put your patches there
you are bound to get tons of feedback (more so than JIRA atm). But I think you are
fine with OODT-449, 452 and 453, we've discussed them plenty and there are
no objections so +1 to move forward go for it!
Cheers,
Chris
On May 23, 2012, at 7:11 PM, Ross Laidlaw wrote:
> Hi Chris,
>
> I've uploaded patches for each sub-task for OODT-402 (these are
> OODT-449, 452 and 453). I noted your comments and I wanted to ask
> about the next steps. Would you like me to post the patches to review
> board for a formal review? Or are you satisfied that everything's
> looking good and covered in JIRA? If everything's fine and you're ok
> for me to commit the changes I'd be happy to go ahead.
>
> Ross
>
>
> On 15 May 2012 19:46, Mattmann, Chris A (388J)
> <ch...@jpl.nasa.gov> wrote:
>> +1 for RB!
>>
>> #win!
>>
>> Cheers,
>> Chris
>>
>> On May 15, 2012, at 3:34 AM, Ramirez, Paul M (388J) wrote:
>>
>>> Hey Ricky,
>>>
>>> Sounds good. You can always just implement it as a patch and then when its
>>> done commit it to the repo. That would make it easy to push through review
>>> board too.
>>>
>>> --Paul
>>>
>>> On 5/14/12 9:16 PM, "Mattmann, Chris A (388J)"
>>> <ch...@jpl.nasa.gov> wrote:
>>>
>>>> Hey Ricky,
>>>>
>>>> That's awesome, glad that you started those and hope you can
>>>> dig them up!
>>>>
>>>> Cheers,
>>>> Chris
>>>>
>>>> On May 14, 2012, at 5:03 PM, Ross Laidlaw wrote:
>>>>
>>>>> Hi Ricky,
>>>>>
>>>>> On 14 May 2012 21:26, Nguyen, Ricky <rn...@chla.usc.edu> wrote:
>>>>>> FYI, I've got some code lying around that ports the DataDeliverServlet
>>>>>> and DatasetDeliveryServlet to JAX-RS using CXF. The reason I started it
>>>>>> was because I thought we might be able to make use of CXF's oauth
>>>>>> providers to secure this RESTful web service. But I hadn't figured out
>>>>>> the oauth part (nor how to port the RDF/RSS servlets).
>>>>>>
>>>>>> If I find time, maybe I'll start a branch...
>>>>>>
>>>>>> -Ricky
>>>>>
>>>>> Sounds good. I'll try to close out OODT-402 and OODT-458 first, but
>>>>> after that I'd be happy to contribute to this work if there's anything
>>>>> I can do to help out. By the way, I found your emails with Chris and
>>>>> Andrew about the various ways of serving files from File Manager very
>>>>> informative! Really helped me to learn about all of the different
>>>>> services available.
>>>>>
>>>>> Ross
>>>>
>>>>
>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>> 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
>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>
>>>
>>
>>
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> 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
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
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
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Re: OODT-402 progress update
Posted by Ross Laidlaw <rl...@gmail.com>.
Hi Chris,
I've uploaded patches for each sub-task for OODT-402 (these are
OODT-449, 452 and 453). I noted your comments and I wanted to ask
about the next steps. Would you like me to post the patches to review
board for a formal review? Or are you satisfied that everything's
looking good and covered in JIRA? If everything's fine and you're ok
for me to commit the changes I'd be happy to go ahead.
Ross
On 15 May 2012 19:46, Mattmann, Chris A (388J)
<ch...@jpl.nasa.gov> wrote:
> +1 for RB!
>
> #win!
>
> Cheers,
> Chris
>
> On May 15, 2012, at 3:34 AM, Ramirez, Paul M (388J) wrote:
>
>> Hey Ricky,
>>
>> Sounds good. You can always just implement it as a patch and then when its
>> done commit it to the repo. That would make it easy to push through review
>> board too.
>>
>> --Paul
>>
>> On 5/14/12 9:16 PM, "Mattmann, Chris A (388J)"
>> <ch...@jpl.nasa.gov> wrote:
>>
>>> Hey Ricky,
>>>
>>> That's awesome, glad that you started those and hope you can
>>> dig them up!
>>>
>>> Cheers,
>>> Chris
>>>
>>> On May 14, 2012, at 5:03 PM, Ross Laidlaw wrote:
>>>
>>>> Hi Ricky,
>>>>
>>>> On 14 May 2012 21:26, Nguyen, Ricky <rn...@chla.usc.edu> wrote:
>>>>> FYI, I've got some code lying around that ports the DataDeliverServlet
>>>>> and DatasetDeliveryServlet to JAX-RS using CXF. The reason I started it
>>>>> was because I thought we might be able to make use of CXF's oauth
>>>>> providers to secure this RESTful web service. But I hadn't figured out
>>>>> the oauth part (nor how to port the RDF/RSS servlets).
>>>>>
>>>>> If I find time, maybe I'll start a branch...
>>>>>
>>>>> -Ricky
>>>>
>>>> Sounds good. I'll try to close out OODT-402 and OODT-458 first, but
>>>> after that I'd be happy to contribute to this work if there's anything
>>>> I can do to help out. By the way, I found your emails with Chris and
>>>> Andrew about the various ways of serving files from File Manager very
>>>> informative! Really helped me to learn about all of the different
>>>> services available.
>>>>
>>>> Ross
>>>
>>>
>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>> 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
>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>
>>
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 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
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
Re: OODT-402 progress update
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
+1 for RB!
#win!
Cheers,
Chris
On May 15, 2012, at 3:34 AM, Ramirez, Paul M (388J) wrote:
> Hey Ricky,
>
> Sounds good. You can always just implement it as a patch and then when its
> done commit it to the repo. That would make it easy to push through review
> board too.
>
> --Paul
>
> On 5/14/12 9:16 PM, "Mattmann, Chris A (388J)"
> <ch...@jpl.nasa.gov> wrote:
>
>> Hey Ricky,
>>
>> That's awesome, glad that you started those and hope you can
>> dig them up!
>>
>> Cheers,
>> Chris
>>
>> On May 14, 2012, at 5:03 PM, Ross Laidlaw wrote:
>>
>>> Hi Ricky,
>>>
>>> On 14 May 2012 21:26, Nguyen, Ricky <rn...@chla.usc.edu> wrote:
>>>> FYI, I've got some code lying around that ports the DataDeliverServlet
>>>> and DatasetDeliveryServlet to JAX-RS using CXF. The reason I started it
>>>> was because I thought we might be able to make use of CXF's oauth
>>>> providers to secure this RESTful web service. But I hadn't figured out
>>>> the oauth part (nor how to port the RDF/RSS servlets).
>>>>
>>>> If I find time, maybe I'll start a branch...
>>>>
>>>> -Ricky
>>>
>>> Sounds good. I'll try to close out OODT-402 and OODT-458 first, but
>>> after that I'd be happy to contribute to this work if there's anything
>>> I can do to help out. By the way, I found your emails with Chris and
>>> Andrew about the various ways of serving files from File Manager very
>>> informative! Really helped me to learn about all of the different
>>> services available.
>>>
>>> Ross
>>
>>
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> 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
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>
>
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
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
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Re: OODT-402 progress update
Posted by "Ramirez, Paul M (388J)" <pa...@jpl.nasa.gov>.
Hey Ricky,
Sounds good. You can always just implement it as a patch and then when its
done commit it to the repo. That would make it easy to push through review
board too.
--Paul
On 5/14/12 9:16 PM, "Mattmann, Chris A (388J)"
<ch...@jpl.nasa.gov> wrote:
>Hey Ricky,
>
>That's awesome, glad that you started those and hope you can
>dig them up!
>
>Cheers,
>Chris
>
>On May 14, 2012, at 5:03 PM, Ross Laidlaw wrote:
>
>> Hi Ricky,
>>
>> On 14 May 2012 21:26, Nguyen, Ricky <rn...@chla.usc.edu> wrote:
>>> FYI, I've got some code lying around that ports the DataDeliverServlet
>>>and DatasetDeliveryServlet to JAX-RS using CXF. The reason I started it
>>>was because I thought we might be able to make use of CXF's oauth
>>>providers to secure this RESTful web service. But I hadn't figured out
>>>the oauth part (nor how to port the RDF/RSS servlets).
>>>
>>> If I find time, maybe I'll start a branch...
>>>
>>> -Ricky
>>
>> Sounds good. I'll try to close out OODT-402 and OODT-458 first, but
>> after that I'd be happy to contribute to this work if there's anything
>> I can do to help out. By the way, I found your emails with Chris and
>> Andrew about the various ways of serving files from File Manager very
>> informative! Really helped me to learn about all of the different
>> services available.
>>
>> Ross
>
>
>++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>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
>++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
Re: OODT-402 progress update
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hey Ricky,
That's awesome, glad that you started those and hope you can
dig them up!
Cheers,
Chris
On May 14, 2012, at 5:03 PM, Ross Laidlaw wrote:
> Hi Ricky,
>
> On 14 May 2012 21:26, Nguyen, Ricky <rn...@chla.usc.edu> wrote:
>> FYI, I've got some code lying around that ports the DataDeliverServlet and DatasetDeliveryServlet to JAX-RS using CXF. The reason I started it was because I thought we might be able to make use of CXF's oauth providers to secure this RESTful web service. But I hadn't figured out the oauth part (nor how to port the RDF/RSS servlets).
>>
>> If I find time, maybe I'll start a branch...
>>
>> -Ricky
>
> Sounds good. I'll try to close out OODT-402 and OODT-458 first, but
> after that I'd be happy to contribute to this work if there's anything
> I can do to help out. By the way, I found your emails with Chris and
> Andrew about the various ways of serving files from File Manager very
> informative! Really helped me to learn about all of the different
> services available.
>
> Ross
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
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
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Re: OODT-402 progress update
Posted by Ross Laidlaw <rl...@gmail.com>.
Hi Ricky,
On 14 May 2012 21:26, Nguyen, Ricky <rn...@chla.usc.edu> wrote:
> FYI, I've got some code lying around that ports the DataDeliverServlet and DatasetDeliveryServlet to JAX-RS using CXF. The reason I started it was because I thought we might be able to make use of CXF's oauth providers to secure this RESTful web service. But I hadn't figured out the oauth part (nor how to port the RDF/RSS servlets).
>
> If I find time, maybe I'll start a branch...
>
> -Ricky
Sounds good. I'll try to close out OODT-402 and OODT-458 first, but
after that I'd be happy to contribute to this work if there's anything
I can do to help out. By the way, I found your emails with Chris and
Andrew about the various ways of serving files from File Manager very
informative! Really helped me to learn about all of the different
services available.
Ross
Re: OODT-402 progress update
Posted by "Nguyen, Ricky" <rn...@chla.usc.edu>.
FYI, I've got some code lying around that ports the DataDeliverServlet and DatasetDeliveryServlet to JAX-RS using CXF. The reason I started it was because I thought we might be able to make use of CXF's oauth providers to secure this RESTful web service. But I hadn't figured out the oauth part (nor how to port the RDF/RSS servlets).
If I find time, maybe I'll start a branch...
-Ricky
On May 12, 2012, at 10:13 AM, Mattmann, Chris A (388J) wrote:
Also if you're feeling ambitious, a separate issue is to turn those 2 services
into JAX-RS services using CXF :) You can find examples of how to do that
in CAS curator (see its services) but it's really a separate issue. I just
wanted to whet your whistle b/c you are doing so great! :)
---------------------------------------------------------------------
CONFIDENTIALITY NOTICE: This e-mail message, including any attachments,
is for the sole use of the intended recipient(s) and may contain confidential
or legally privileged information. Any unauthorized review, use, disclosure
or distribution is prohibited. If you are not the intended recipient, please
contact the sender by reply e-mail and destroy all copies of this original message.
---------------------------------------------------------------------
Re: OODT-402 progress update
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hey Ross,
On May 11, 2012, at 12:29 AM, Ross Laidlaw wrote:
> Hi Chris,
>
>
> On 11 May 2012 06:01, Mattmann, Chris A (388J)
> <ch...@jpl.nasa.gov> wrote:
>> Hey Ross,
>>
>> Either one would be +1 for me -- if you make it easily configurable, and changeable,
>> that would be even better!
>>
>> Cheers,
>> Chris
>
>
> I had a go at implementing the configurable namespaces idea and I have
> something that seems to be working! I added a comment to OODT-449
> with a draft implementation that processes namespace tags in the RSS
> config. If you like, I could move the comment over to a separate task
> and upload a patch to it.
Yep, +1 to creating a separate task and this sounds like great progress!
>
> With the implementation, it would be possible to add the cas namespace
> as well to the RSS config file and this will be picked up in the <rss>
> tag of the output. For example, as follows:
>
> <namespace prefix="cas" uri="http://oodt.apache.org/components/cas" />
Gotcha.
>
>
> In theory, this means that the cas namespace wouldn't have to be
> hard-coded in the RSS java classes. But there might be a couple of
> related things to tidy up:
>
> 1) Do we still need the cas namespace definition at the top of the RSS
> config file? This one is an inline definition for the cas:rssconf tag
> itself and not for the output tags:
>
> <cas:rssconf xmlns:cas="http://oodt.apache.org/components/cas">
I would like to keep the cas namespace since it's really cas config and
to me, declaring the namespace there solidified that for me. Is there any
specific reason to remove it?
>
>
> 2) Two RSS java classes have hard-coded 'cas' namespace info:
> RSSProductServlet.java and RSSProductTransferServlet.java. These
> classes both use a class variable to store namespaces and write them
> to the output:
>
> private static final Map NS_MAP = new HashMap();
> static { NS_MAP.put("cas", "http://oodt.jpl.nasa.gov/1.0/cas"); }
> ...
> XMLUtils.addAttribute(doc, rss, "xmlns:cas", (String) NS_MAP.get("cas"));
>
> I think in RSSProductServlet.java, we could remove this and read it
> from the RSS config instead, but how about
> RSSProductTransferServlet.java? I'm not sure about that one because
> it doesn't appear to access the RSS config file.
+1 to make it use RSSConfig in both the ProductServlet and the TransferServlet.
Also if you're feeling ambitious, a separate issue is to turn those 2 services
into JAX-RS services using CXF :) You can find examples of how to do that
in CAS curator (see its services) but it's really a separate issue. I just
wanted to whet your whistle b/c you are doing so great! :)
> Many thanks again for your time and guidance!
Anytime Ross! You are super full of win!
Cheers,
Chris
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
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
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Re: OODT-402 progress update
Posted by Ross Laidlaw <rl...@gmail.com>.
(Correction to my previous message: I should have written that NS_MAP
is a constant, not a class variable!)
On 11 May 2012, at 11:29, Ross Laidlaw <rl...@gmail.com> wrote:
> These classes both use a class variable to store namespaces and write them
> to the output:
>
> private static final Map NS_MAP = new HashMap();
> static { NS_MAP.put("cas", "http://oodt.jpl.nasa.gov/1.0/cas"); }
Re: OODT-402 progress update
Posted by Ross Laidlaw <rl...@gmail.com>.
Hi Chris,
On 11 May 2012 06:01, Mattmann, Chris A (388J)
<ch...@jpl.nasa.gov> wrote:
> Hey Ross,
>
> Either one would be +1 for me -- if you make it easily configurable, and changeable,
> that would be even better!
>
> Cheers,
> Chris
I had a go at implementing the configurable namespaces idea and I have
something that seems to be working! I added a comment to OODT-449
with a draft implementation that processes namespace tags in the RSS
config. If you like, I could move the comment over to a separate task
and upload a patch to it.
With the implementation, it would be possible to add the cas namespace
as well to the RSS config file and this will be picked up in the <rss>
tag of the output. For example, as follows:
<namespace prefix="cas" uri="http://oodt.apache.org/components/cas" />
In theory, this means that the cas namespace wouldn't have to be
hard-coded in the RSS java classes. But there might be a couple of
related things to tidy up:
1) Do we still need the cas namespace definition at the top of the RSS
config file? This one is an inline definition for the cas:rssconf tag
itself and not for the output tags:
<cas:rssconf xmlns:cas="http://oodt.apache.org/components/cas">
2) Two RSS java classes have hard-coded 'cas' namespace info:
RSSProductServlet.java and RSSProductTransferServlet.java. These
classes both use a class variable to store namespaces and write them
to the output:
private static final Map NS_MAP = new HashMap();
static { NS_MAP.put("cas", "http://oodt.jpl.nasa.gov/1.0/cas"); }
...
XMLUtils.addAttribute(doc, rss, "xmlns:cas", (String) NS_MAP.get("cas"));
I think in RSSProductServlet.java, we could remove this and read it
from the RSS config instead, but how about
RSSProductTransferServlet.java? I'm not sure about that one because
it doesn't appear to access the RSS config file.
Many thanks again for your time and guidance!
Ross
Re: OODT-402 progress update
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hey Ross,
Either one would be +1 for me -- if you make it easily configurable, and changeable,
that would be even better!
Cheers,
Chris
On May 10, 2012, at 8:54 PM, Ross Laidlaw wrote:
> ... or maybe it could be: <cas:rssconf
> xmlns:cas="http://oodt.apache.org/components/cas">
>
>
> On 11 May 2012 04:38, Ross Laidlaw <rl...@gmail.com> wrote:
>> Hi Chris,
>>
>> I noticed the following commented code in the rssconf.xml file for the
>> fmprod webapp:
>>
>> <!-- FIXME: adjust namespace URI? -->
>> <cas:rssconf xmlns:cas="http://oodt.jpl.nasa.gov/1.0/cas">
>>
>>
>> Since the work on OODT-402 is based on that file, would it be ok if I
>> include an update for the URI in the patch? Would the following be
>> correct?
>>
>> <cas:rssconf xmlns:cas="http://oodt.apache.org/1.0/cas">
>>
>>
>> I'd also like to use the updated URI for the georss-config.xml as well.
>>
>>
>> Ross
>>
>>
>>
>> On 28 April 2012 17:24, Mattmann, Chris A (388J)
>> <ch...@jpl.nasa.gov> wrote:
>>> Anytime, Ross!
>>>
>>> Cheers,
>>> Chris
>>>
>>> On Apr 27, 2012, at 9:51 AM, Ross Laidlaw wrote:
>>>
>>>> Hi Chris!
>>>>
>>>> Thanks for responding so quickly and for the guidance. I'll set up
>>>> the JIRA issues and add some specific info and questions to each item.
>>>>
>>>> Ross
>>>>
>>>>
>>>>
>>>>
>>>> On 26 April 2012 16:25, Mattmann, Chris A (388J)
>>>> <ch...@jpl.nasa.gov> wrote:
>>>>> Hi Ross,
>>>>>
>>>>> No problem at all! Read on below and keep the questions coming!
>>>>>
>>>>> On Apr 26, 2012, at 5:27 AM, Ross Laidlaw wrote:
>>>>>
>>>>>> Hi Chris,
>>>>>>
>>>>>> I'm planning my next steps for working on OODT-402. The first task is
>>>>>> to create a default GeoRSS config in the File Manager RSS service. Do
>>>>>> you have a preference for where this file should be stored and
>>>>>> accessed?
>>>>>
>>>>> Yep. I think we should ship it with the File Manager inside of:
>>>>>
>>>>> http://svn.apache.org/repos/asf/oodt/trunk/webapp/fmprod/src/main/resources/georss-config.xml
>>>>>
>>>>>> As a first step, in the demo that I set up recently I used
>>>>>> the default 'rssconfig.xml' file for the fmprod webapp and followed
>>>>>> your comments to add latitude and longitude tags to this.
>>>>>>
>>>>>
>>>>> Yep in the georss-config.xml I would copy through the default RSS and config
>>>>> and then just expose lat/lon with the comments/documentation.
>>>>>
>>>>> This could be a JIRA issue in itself.
>>>>>
>>>>>> For the 'LocationAwareProduct' definition, I was wondering if we could
>>>>>> make this a virtual type that could then be inherited by concrete
>>>>>> vendor types.
>>>>>
>>>>> +1, this sounds like a good strategy, and I would do it as a full
>>>>> specced product-types.xml, elements.xml and product-type-element-map.xml
>>>>> combination. A home for it could be:
>>>>>
>>>>> http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/main/resources/examples/geo
>>>>>
>>>>> As part of this, we should move the current contents of:
>>>>>
>>>>> http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/main/resources/examples/
>>>>>
>>>>> To:
>>>>>
>>>>> http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/main/resources/examples/core
>>>>>
>>>>> This would be 2 separate JIRA issues (for default geo policy, and then a separate
>>>>> to move core, and make sure assembly.xml still works, and the unit tests, etc.)
>>>>>
>>>>>>
>>>>>> Just a few questions and thoughts to get going! Apologies if I'm off track...
>>>>>
>>>>> HTH and rock on!
>>>>>
>>>>> Cheers,
>>>>> Chris
>>>>>
>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>> 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
>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>>
>>>
>>>
>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>> 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
>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
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
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Re: OODT-402 progress update
Posted by Ross Laidlaw <rl...@gmail.com>.
... or maybe it could be: <cas:rssconf
xmlns:cas="http://oodt.apache.org/components/cas">
On 11 May 2012 04:38, Ross Laidlaw <rl...@gmail.com> wrote:
> Hi Chris,
>
> I noticed the following commented code in the rssconf.xml file for the
> fmprod webapp:
>
> <!-- FIXME: adjust namespace URI? -->
> <cas:rssconf xmlns:cas="http://oodt.jpl.nasa.gov/1.0/cas">
>
>
> Since the work on OODT-402 is based on that file, would it be ok if I
> include an update for the URI in the patch? Would the following be
> correct?
>
> <cas:rssconf xmlns:cas="http://oodt.apache.org/1.0/cas">
>
>
> I'd also like to use the updated URI for the georss-config.xml as well.
>
>
> Ross
>
>
>
> On 28 April 2012 17:24, Mattmann, Chris A (388J)
> <ch...@jpl.nasa.gov> wrote:
>> Anytime, Ross!
>>
>> Cheers,
>> Chris
>>
>> On Apr 27, 2012, at 9:51 AM, Ross Laidlaw wrote:
>>
>>> Hi Chris!
>>>
>>> Thanks for responding so quickly and for the guidance. I'll set up
>>> the JIRA issues and add some specific info and questions to each item.
>>>
>>> Ross
>>>
>>>
>>>
>>>
>>> On 26 April 2012 16:25, Mattmann, Chris A (388J)
>>> <ch...@jpl.nasa.gov> wrote:
>>>> Hi Ross,
>>>>
>>>> No problem at all! Read on below and keep the questions coming!
>>>>
>>>> On Apr 26, 2012, at 5:27 AM, Ross Laidlaw wrote:
>>>>
>>>>> Hi Chris,
>>>>>
>>>>> I'm planning my next steps for working on OODT-402. The first task is
>>>>> to create a default GeoRSS config in the File Manager RSS service. Do
>>>>> you have a preference for where this file should be stored and
>>>>> accessed?
>>>>
>>>> Yep. I think we should ship it with the File Manager inside of:
>>>>
>>>> http://svn.apache.org/repos/asf/oodt/trunk/webapp/fmprod/src/main/resources/georss-config.xml
>>>>
>>>>> As a first step, in the demo that I set up recently I used
>>>>> the default 'rssconfig.xml' file for the fmprod webapp and followed
>>>>> your comments to add latitude and longitude tags to this.
>>>>>
>>>>
>>>> Yep in the georss-config.xml I would copy through the default RSS and config
>>>> and then just expose lat/lon with the comments/documentation.
>>>>
>>>> This could be a JIRA issue in itself.
>>>>
>>>>> For the 'LocationAwareProduct' definition, I was wondering if we could
>>>>> make this a virtual type that could then be inherited by concrete
>>>>> vendor types.
>>>>
>>>> +1, this sounds like a good strategy, and I would do it as a full
>>>> specced product-types.xml, elements.xml and product-type-element-map.xml
>>>> combination. A home for it could be:
>>>>
>>>> http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/main/resources/examples/geo
>>>>
>>>> As part of this, we should move the current contents of:
>>>>
>>>> http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/main/resources/examples/
>>>>
>>>> To:
>>>>
>>>> http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/main/resources/examples/core
>>>>
>>>> This would be 2 separate JIRA issues (for default geo policy, and then a separate
>>>> to move core, and make sure assembly.xml still works, and the unit tests, etc.)
>>>>
>>>>>
>>>>> Just a few questions and thoughts to get going! Apologies if I'm off track...
>>>>
>>>> HTH and rock on!
>>>>
>>>> Cheers,
>>>> Chris
>>>>
>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>> 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
>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>
>>
>>
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> 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
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>
Re: OODT-402 progress update
Posted by Ross Laidlaw <rl...@gmail.com>.
Hi Chris,
I noticed the following commented code in the rssconf.xml file for the
fmprod webapp:
<!-- FIXME: adjust namespace URI? -->
<cas:rssconf xmlns:cas="http://oodt.jpl.nasa.gov/1.0/cas">
Since the work on OODT-402 is based on that file, would it be ok if I
include an update for the URI in the patch? Would the following be
correct?
<cas:rssconf xmlns:cas="http://oodt.apache.org/1.0/cas">
I'd also like to use the updated URI for the georss-config.xml as well.
Ross
On 28 April 2012 17:24, Mattmann, Chris A (388J)
<ch...@jpl.nasa.gov> wrote:
> Anytime, Ross!
>
> Cheers,
> Chris
>
> On Apr 27, 2012, at 9:51 AM, Ross Laidlaw wrote:
>
>> Hi Chris!
>>
>> Thanks for responding so quickly and for the guidance. I'll set up
>> the JIRA issues and add some specific info and questions to each item.
>>
>> Ross
>>
>>
>>
>>
>> On 26 April 2012 16:25, Mattmann, Chris A (388J)
>> <ch...@jpl.nasa.gov> wrote:
>>> Hi Ross,
>>>
>>> No problem at all! Read on below and keep the questions coming!
>>>
>>> On Apr 26, 2012, at 5:27 AM, Ross Laidlaw wrote:
>>>
>>>> Hi Chris,
>>>>
>>>> I'm planning my next steps for working on OODT-402. The first task is
>>>> to create a default GeoRSS config in the File Manager RSS service. Do
>>>> you have a preference for where this file should be stored and
>>>> accessed?
>>>
>>> Yep. I think we should ship it with the File Manager inside of:
>>>
>>> http://svn.apache.org/repos/asf/oodt/trunk/webapp/fmprod/src/main/resources/georss-config.xml
>>>
>>>> As a first step, in the demo that I set up recently I used
>>>> the default 'rssconfig.xml' file for the fmprod webapp and followed
>>>> your comments to add latitude and longitude tags to this.
>>>>
>>>
>>> Yep in the georss-config.xml I would copy through the default RSS and config
>>> and then just expose lat/lon with the comments/documentation.
>>>
>>> This could be a JIRA issue in itself.
>>>
>>>> For the 'LocationAwareProduct' definition, I was wondering if we could
>>>> make this a virtual type that could then be inherited by concrete
>>>> vendor types.
>>>
>>> +1, this sounds like a good strategy, and I would do it as a full
>>> specced product-types.xml, elements.xml and product-type-element-map.xml
>>> combination. A home for it could be:
>>>
>>> http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/main/resources/examples/geo
>>>
>>> As part of this, we should move the current contents of:
>>>
>>> http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/main/resources/examples/
>>>
>>> To:
>>>
>>> http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/main/resources/examples/core
>>>
>>> This would be 2 separate JIRA issues (for default geo policy, and then a separate
>>> to move core, and make sure assembly.xml still works, and the unit tests, etc.)
>>>
>>>>
>>>> Just a few questions and thoughts to get going! Apologies if I'm off track...
>>>
>>> HTH and rock on!
>>>
>>> Cheers,
>>> Chris
>>>
>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>> 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
>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 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
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
Re: OODT-402 progress update
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Anytime, Ross!
Cheers,
Chris
On Apr 27, 2012, at 9:51 AM, Ross Laidlaw wrote:
> Hi Chris!
>
> Thanks for responding so quickly and for the guidance. I'll set up
> the JIRA issues and add some specific info and questions to each item.
>
> Ross
>
>
>
>
> On 26 April 2012 16:25, Mattmann, Chris A (388J)
> <ch...@jpl.nasa.gov> wrote:
>> Hi Ross,
>>
>> No problem at all! Read on below and keep the questions coming!
>>
>> On Apr 26, 2012, at 5:27 AM, Ross Laidlaw wrote:
>>
>>> Hi Chris,
>>>
>>> I'm planning my next steps for working on OODT-402. The first task is
>>> to create a default GeoRSS config in the File Manager RSS service. Do
>>> you have a preference for where this file should be stored and
>>> accessed?
>>
>> Yep. I think we should ship it with the File Manager inside of:
>>
>> http://svn.apache.org/repos/asf/oodt/trunk/webapp/fmprod/src/main/resources/georss-config.xml
>>
>>> As a first step, in the demo that I set up recently I used
>>> the default 'rssconfig.xml' file for the fmprod webapp and followed
>>> your comments to add latitude and longitude tags to this.
>>>
>>
>> Yep in the georss-config.xml I would copy through the default RSS and config
>> and then just expose lat/lon with the comments/documentation.
>>
>> This could be a JIRA issue in itself.
>>
>>> For the 'LocationAwareProduct' definition, I was wondering if we could
>>> make this a virtual type that could then be inherited by concrete
>>> vendor types.
>>
>> +1, this sounds like a good strategy, and I would do it as a full
>> specced product-types.xml, elements.xml and product-type-element-map.xml
>> combination. A home for it could be:
>>
>> http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/main/resources/examples/geo
>>
>> As part of this, we should move the current contents of:
>>
>> http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/main/resources/examples/
>>
>> To:
>>
>> http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/main/resources/examples/core
>>
>> This would be 2 separate JIRA issues (for default geo policy, and then a separate
>> to move core, and make sure assembly.xml still works, and the unit tests, etc.)
>>
>>>
>>> Just a few questions and thoughts to get going! Apologies if I'm off track...
>>
>> HTH and rock on!
>>
>> Cheers,
>> Chris
>>
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> 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
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
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
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Re: OODT-402 progress update
Posted by Ross Laidlaw <rl...@gmail.com>.
Hi Chris!
Thanks for responding so quickly and for the guidance. I'll set up
the JIRA issues and add some specific info and questions to each item.
Ross
On 26 April 2012 16:25, Mattmann, Chris A (388J)
<ch...@jpl.nasa.gov> wrote:
> Hi Ross,
>
> No problem at all! Read on below and keep the questions coming!
>
> On Apr 26, 2012, at 5:27 AM, Ross Laidlaw wrote:
>
>> Hi Chris,
>>
>> I'm planning my next steps for working on OODT-402. The first task is
>> to create a default GeoRSS config in the File Manager RSS service. Do
>> you have a preference for where this file should be stored and
>> accessed?
>
> Yep. I think we should ship it with the File Manager inside of:
>
> http://svn.apache.org/repos/asf/oodt/trunk/webapp/fmprod/src/main/resources/georss-config.xml
>
>> As a first step, in the demo that I set up recently I used
>> the default 'rssconfig.xml' file for the fmprod webapp and followed
>> your comments to add latitude and longitude tags to this.
>>
>
> Yep in the georss-config.xml I would copy through the default RSS and config
> and then just expose lat/lon with the comments/documentation.
>
> This could be a JIRA issue in itself.
>
>> For the 'LocationAwareProduct' definition, I was wondering if we could
>> make this a virtual type that could then be inherited by concrete
>> vendor types.
>
> +1, this sounds like a good strategy, and I would do it as a full
> specced product-types.xml, elements.xml and product-type-element-map.xml
> combination. A home for it could be:
>
> http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/main/resources/examples/geo
>
> As part of this, we should move the current contents of:
>
> http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/main/resources/examples/
>
> To:
>
> http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/main/resources/examples/core
>
> This would be 2 separate JIRA issues (for default geo policy, and then a separate
> to move core, and make sure assembly.xml still works, and the unit tests, etc.)
>
>>
>> Just a few questions and thoughts to get going! Apologies if I'm off track...
>
> HTH and rock on!
>
> Cheers,
> Chris
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 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
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
Re: OODT-402 progress update
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hi Ross,
No problem at all! Read on below and keep the questions coming!
On Apr 26, 2012, at 5:27 AM, Ross Laidlaw wrote:
> Hi Chris,
>
> I'm planning my next steps for working on OODT-402. The first task is
> to create a default GeoRSS config in the File Manager RSS service. Do
> you have a preference for where this file should be stored and
> accessed?
Yep. I think we should ship it with the File Manager inside of:
http://svn.apache.org/repos/asf/oodt/trunk/webapp/fmprod/src/main/resources/georss-config.xml
> As a first step, in the demo that I set up recently I used
> the default 'rssconfig.xml' file for the fmprod webapp and followed
> your comments to add latitude and longitude tags to this.
>
Yep in the georss-config.xml I would copy through the default RSS and config
and then just expose lat/lon with the comments/documentation.
This could be a JIRA issue in itself.
> For the 'LocationAwareProduct' definition, I was wondering if we could
> make this a virtual type that could then be inherited by concrete
> vendor types.
+1, this sounds like a good strategy, and I would do it as a full
specced product-types.xml, elements.xml and product-type-element-map.xml
combination. A home for it could be:
http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/main/resources/examples/geo
As part of this, we should move the current contents of:
http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/main/resources/examples/
To:
http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/main/resources/examples/core
This would be 2 separate JIRA issues (for default geo policy, and then a separate
to move core, and make sure assembly.xml still works, and the unit tests, etc.)
>
> Just a few questions and thoughts to get going! Apologies if I'm off track...
HTH and rock on!
Cheers,
Chris
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
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
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Re: OODT-402 progress update
Posted by Ross Laidlaw <rl...@gmail.com>.
Hi Chris,
I'm planning my next steps for working on OODT-402. The first task is
to create a default GeoRSS config in the File Manager RSS service. Do
you have a preference for where this file should be stored and
accessed? As a first step, in the demo that I set up recently I used
the default 'rssconfig.xml' file for the fmprod webapp and followed
your comments to add latitude and longitude tags to this.
For the 'LocationAwareProduct' definition, I was wondering if we could
make this a virtual type that could then be inherited by concrete
vendor types.
Just a few questions and thoughts to get going! Apologies if I'm off track...
Ross :)
On 6 April 2012 19:34, Mattmann, Chris A (388J)
<ch...@jpl.nasa.gov> wrote:
> Awesome, thanks Ross!
>
> Cheers,
> Chris
>
> On Apr 6, 2012, at 3:51 AM, Ross Laidlaw wrote:
>
>> Thanks Chris! It's working now :)
>>
>> On 6 April 2012 07:33, Mattmann, Chris A (388J)
>> <ch...@jpl.nasa.gov> wrote:
>>> KK, got it. I made some changes in the SIS wiki. Can you try again?
>>>
>>> Cheers,
>>> Chris
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 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
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
Re: OODT-402 progress update
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Awesome, thanks Ross!
Cheers,
Chris
On Apr 6, 2012, at 3:51 AM, Ross Laidlaw wrote:
> Thanks Chris! It's working now :)
>
> On 6 April 2012 07:33, Mattmann, Chris A (388J)
> <ch...@jpl.nasa.gov> wrote:
>> KK, got it. I made some changes in the SIS wiki. Can you try again?
>>
>> Cheers,
>> Chris
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
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
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Re: OODT-402 progress update
Posted by Ross Laidlaw <rl...@gmail.com>.
Thanks Chris! It's working now :)
On 6 April 2012 07:33, Mattmann, Chris A (388J)
<ch...@jpl.nasa.gov> wrote:
> KK, got it. I made some changes in the SIS wiki. Can you try again?
>
> Cheers,
> Chris
Re: OODT-402 progress update
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hey Ross,
On Apr 5, 2012, at 6:33 PM, Ross Laidlaw wrote:
> Hi Chris,
>
> On 5 April 2012 04:15, Mattmann, Chris A (388J)
> <ch...@jpl.nasa.gov> wrote:
>> OK, on the OODT wiki, I clicked to this screen and got the
>> following:
>>
>> http://minus.com/mUOo4Prhu/
>>
>> Is this what you are seeing?
>
>
> Thanks for looking into this. I checked on the OODT wiki site and I
> can see exactly the same screen and I can attach files there. But
> over on the SIS wiki site I can't attach files. Are the permissions
> set up the same way there? On the SIS wiki, my screen looks like
> this:
>
> http://minus.com/mQgZL8TJI/
KK, got it. I made some changes in the SIS wiki. Can you try again?
Cheers,
Chris
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
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
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Re: OODT-402 progress update
Posted by Ross Laidlaw <rl...@gmail.com>.
Hi Chris,
On 5 April 2012 04:15, Mattmann, Chris A (388J)
<ch...@jpl.nasa.gov> wrote:
> OK, on the OODT wiki, I clicked to this screen and got the
> following:
>
> http://minus.com/mUOo4Prhu/
>
> Is this what you are seeing?
Thanks for looking into this. I checked on the OODT wiki site and I
can see exactly the same screen and I can attach files there. But
over on the SIS wiki site I can't attach files. Are the permissions
set up the same way there? On the SIS wiki, my screen looks like
this:
http://minus.com/mQgZL8TJI/
Ross
Re: OODT-402 progress update
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hi Ross,
On Apr 3, 2012, at 5:59 AM, Ross Laidlaw wrote:
>
>
>> I will see if I can modify
>> the confluence wiki to let you upload images. It looks
>> like it is set to allow logged in users to add
>> attachments -- is it a different permission
>> than that? If so let me know and I or someone else
>> can update it.
>
> These sound like the correct permissions. I'm new to confluence so
> it's probably something on my side that I haven't figured out yet!
> When I select 'Tools -> Attachments' I can view attached files but I
> couldn't see any options to browse for files to add new attachments.
> Apologies if it's something obvious that I missed.
OK, on the OODT wiki, I clicked to this screen and got the
following:
http://minus.com/mUOo4Prhu/
Is this what you are seeing? If you don't see that, can you please
send an email to infrastructure@apache.org, (or in IRC hit up #asfinfra) and ask them
what's up? Feel free to CC me -- I'd be happy to set the permissions
differently than they are already set up. Here is what I see
in the Confluence permissions for the OODT space:
http://minus.com/mUOo4Prhu/2
Thanks!
Cheers,
Chris
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
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
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Re: OODT-402 progress update
Posted by Ross Laidlaw <rl...@gmail.com>.
Hi Chris!
On 3 April 2012 04:21, Mattmann, Chris A (388J)
<ch...@jpl.nasa.gov> wrote:
> Hi Ross,
>
> I checked it out. Did I mention you are amazing??! :)
>
> Keep up the awesome work!
Thanks Chris! I'm glad things are going well. This is a really great
community and I'm very grateful to have the opportunity to contribute.
> I will see if I can modify
> the confluence wiki to let you upload images. It looks
> like it is set to allow logged in users to add
> attachments -- is it a different permission
> than that? If so let me know and I or someone else
> can update it.
These sound like the correct permissions. I'm new to confluence so
it's probably something on my side that I haven't figured out yet!
When I select 'Tools -> Attachments' I can view attached files but I
couldn't see any options to browse for files to add new attachments.
Apologies if it's something obvious that I missed.
Ross
Re: OODT-402 progress update
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hi Ross,
I checked it out. Did I mention you are amazing??! :)
Keep up the awesome work! I will see if I can modify
the confluence wiki to let you upload images. It looks
like it is set to allow logged in users to add
attachments -- is it a different permission
than that? If so let me know and I or someone else
can update it.
Thanks again keep it up!
Cheers,
Chris
On Apr 2, 2012, at 4:24 PM, Ross Laidlaw wrote:
> Hi Chris,
>
> I've uploaded a first draft for the tutorial on the SIS wiki and
> linked to it from the OODT and SIS home pages as requested. I didn't
> have permissions to attach images directly to the wiki page, so I
> added the screenshot to OODT-402 first and then transferred it over
> from there. Apologies if this caused a lot of notifications. As I
> make progress on OODT-402 I'll keep updating the tutorial to reflect
> the latest work.
>
>
> Ross
>
>
>
>
>
> On 2 April 2012 13:11, Ross Laidlaw <rl...@gmail.com> wrote:
>> Hi Chris, definitely, I'd be happy to do that. I've started work on
>> it - hoping to have a draft up by end of today (April 2nd). Will send
>> you a message as soon as I've uploaded it :)
>>
>>
>> On 31 March 2012 22:47, Mattmann, Chris A (388J)
>> <ch...@jpl.nasa.gov> wrote:
>>> They look great, I checked them out. Would you be willing to do the following?
>>>
>>> 1. Log onto the SIS wiki and add a little tutorial (small) based on the above email
>>> and screenshots?
>>>
>>> wiki here: https://cwiki.apache.org/confluence/display/SIS/Home
>>>
>>> 2. Link the SIS tutorial via the OODT wiki, here:
>>>
>>> https://cwiki.apache.org/confluence/display/OODT/Home
>>>
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
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
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Re: OODT-402 progress update
Posted by Ross Laidlaw <rl...@gmail.com>.
Hi Chris,
I've uploaded a first draft for the tutorial on the SIS wiki and
linked to it from the OODT and SIS home pages as requested. I didn't
have permissions to attach images directly to the wiki page, so I
added the screenshot to OODT-402 first and then transferred it over
from there. Apologies if this caused a lot of notifications. As I
make progress on OODT-402 I'll keep updating the tutorial to reflect
the latest work.
Ross
On 2 April 2012 13:11, Ross Laidlaw <rl...@gmail.com> wrote:
> Hi Chris, definitely, I'd be happy to do that. I've started work on
> it - hoping to have a draft up by end of today (April 2nd). Will send
> you a message as soon as I've uploaded it :)
>
>
> On 31 March 2012 22:47, Mattmann, Chris A (388J)
> <ch...@jpl.nasa.gov> wrote:
>> They look great, I checked them out. Would you be willing to do the following?
>>
>> 1. Log onto the SIS wiki and add a little tutorial (small) based on the above email
>> and screenshots?
>>
>> wiki here: https://cwiki.apache.org/confluence/display/SIS/Home
>>
>> 2. Link the SIS tutorial via the OODT wiki, here:
>>
>> https://cwiki.apache.org/confluence/display/OODT/Home
>>
Re: OODT-402 progress update
Posted by Ross Laidlaw <rl...@gmail.com>.
Hi Chris, definitely, I'd be happy to do that. I've started work on
it - hoping to have a draft up by end of today (April 2nd). Will send
you a message as soon as I've uploaded it :)
On 31 March 2012 22:47, Mattmann, Chris A (388J)
<ch...@jpl.nasa.gov> wrote:
> They look great, I checked them out. Would you be willing to do the following?
>
> 1. Log onto the SIS wiki and add a little tutorial (small) based on the above email
> and screenshots?
>
> wiki here: https://cwiki.apache.org/confluence/display/SIS/Home
>
> 2. Link the SIS tutorial via the OODT wiki, here:
>
> https://cwiki.apache.org/confluence/display/OODT/Home
>
Re: OODT-402 progress update
Posted by Ross Laidlaw <rl...@gmail.com>.
Hi Tom!
Thanks for your encouraging words. It means a lot to me that the OODT
team are happy with my work so far. I hope I can deliver something
useful that will be of benefit to you guys.
Regards,
Ross
On 2 April 2012 07:24, Thomas Bennett <lm...@gmail.com> wrote:
> Hey Ross,
>
> I also wanted to say great work so far, looks very promising!
>
> Regards,
> Tom
>
> On 1 April 2012 18:59, Cameron Goodale <go...@apache.org> wrote:
>
>> Ross,
>>
>> I agree with Chris that you are doing a great job on this. Thank you for
>> all the hard work in setting this up. Having a standard geospatial
>> interface from the FileManager to SIS will prove extremely helpful to
>> several JPL/NASA Earth Science Missions in the future.
>>
>> Just wanted to say thanks!
>>
>>
>>
>> Cameron
>>
>> On Sat, Mar 31, 2012 at 2:47 PM, Mattmann, Chris A (388J) <
>> chris.a.mattmann@jpl.nasa.gov> wrote:
>>
>> > (sorry for the cross post, but of interest to both communities)
>> >
>> > Hey Ross,
>> >
>> > That is awesome to hear! Comments below:
>> >
>> > On Mar 31, 2012, at 4:04 AM, Ross Laidlaw wrote:
>> >
>> > > Hi Chris,
>> > >
>> > > Many thanks for your comments and advice. I have now installed SIS on
>> > > my system and I have the demo up and running. I've also been
>> > > experimenting with the connection between File Manager and SIS and I
>> > > have a basic connection working. Here are the steps I have carried so
>> > > far:
>> > >
>> > > Firstly, I added elements for 'Latitude' and 'Longitude' to the
>> > > GenericFile policy. Then I created a set of test files (simple text
>> > > files) with corresponding '.met' metadata files. I added 'Latitude'
>> > > and 'Longitude' metadata to the '.met' files. I then ingested these
>> > > into my File Manager repository.
>> >
>> > That's perfect.
>> >
>> > >
>> > > After that, I enabled the 'georss' tags in the 'rssconf.xml'
>> > > configuration file (I added tags for geo:lat and geo:long to start
>> > > with) and viewed the RSS output from the CAS REST API in my browser.
>> > >
>> > > I then added the URL
>> > > ('http://localhost:8080/fmprod/viewRecent?channel=ALL') as an RSS feed
>> > > to the 'sis-location-config.xml' config in my SIS webapp.
>> > >
>> > > Next, I ran a bounding box query from the SIS demo.jsp and my file
>> > > manager files appeared on the map! Awesome!
>> >
>> > That is SWEET!
>> >
>> > >
>> > > I have uploaded a set of screenshots showing my progress, hopefully
>> > > they're accessible and make sense (I'm new to flickr, so apologies if
>> > > things look a bit disorganised!):
>> > >
>> > >
>> >
>> http://www.flickr.com/photos/rlaidlaw/sets/72157629342438940/with/7031581313/
>> >
>> > They look great, I checked them out. Would you be willing to do the
>> > following?
>> >
>> > 1. Log onto the SIS wiki and add a little tutorial (small) based on the
>> > above email
>> > and screenshots?
>> >
>> > wiki here: https://cwiki.apache.org/confluence/display/SIS/Home
>> >
>> > 2. Link the SIS tutorial via the OODT wiki, here:
>> >
>> > https://cwiki.apache.org/confluence/display/OODT/Home
>> >
>> > >
>> > > I tried to order the screenshots to follow the steps I outlined above,
>> > > with the final screenshot being the output from the SIS demo showing
>> > > the File Manager files on the map.
>> >
>> > That's awesome.
>> >
>> > >
>> > > For next steps, I could start to formalize some of my experimental
>> > > code and begin to address the key points you have outlined on the
>> > > OODT-402 jira page (i.e. writing a default GeoRSS config and a default
>> > > file manager policy for a 'LocationAwareProduct' type).
>> >
>> > That would be perfect!
>> >
>> > > I will follow
>> > > up with specific questions about both of these, but for now I just
>> > > wanted to give you an update on my progress and to check that I'm
>> > > heading in the right direction.
>> >
>> > You are definitely heading in the right direction that's precisely what I
>> > was
>> > hoping you would figure out how to do. Thank you Ross for the update
>> > and your results look VERY promising, great job so far!
>> >
>> > Cheers,
>> > Chris
>> >
>> > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> > 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
>> > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> >
>> >
>>
Re: OODT-402 progress update
Posted by Thomas Bennett <lm...@gmail.com>.
Hey Ross,
I also wanted to say great work so far, looks very promising!
Regards,
Tom
On 1 April 2012 18:59, Cameron Goodale <go...@apache.org> wrote:
> Ross,
>
> I agree with Chris that you are doing a great job on this. Thank you for
> all the hard work in setting this up. Having a standard geospatial
> interface from the FileManager to SIS will prove extremely helpful to
> several JPL/NASA Earth Science Missions in the future.
>
> Just wanted to say thanks!
>
>
>
> Cameron
>
> On Sat, Mar 31, 2012 at 2:47 PM, Mattmann, Chris A (388J) <
> chris.a.mattmann@jpl.nasa.gov> wrote:
>
> > (sorry for the cross post, but of interest to both communities)
> >
> > Hey Ross,
> >
> > That is awesome to hear! Comments below:
> >
> > On Mar 31, 2012, at 4:04 AM, Ross Laidlaw wrote:
> >
> > > Hi Chris,
> > >
> > > Many thanks for your comments and advice. I have now installed SIS on
> > > my system and I have the demo up and running. I've also been
> > > experimenting with the connection between File Manager and SIS and I
> > > have a basic connection working. Here are the steps I have carried so
> > > far:
> > >
> > > Firstly, I added elements for 'Latitude' and 'Longitude' to the
> > > GenericFile policy. Then I created a set of test files (simple text
> > > files) with corresponding '.met' metadata files. I added 'Latitude'
> > > and 'Longitude' metadata to the '.met' files. I then ingested these
> > > into my File Manager repository.
> >
> > That's perfect.
> >
> > >
> > > After that, I enabled the 'georss' tags in the 'rssconf.xml'
> > > configuration file (I added tags for geo:lat and geo:long to start
> > > with) and viewed the RSS output from the CAS REST API in my browser.
> > >
> > > I then added the URL
> > > ('http://localhost:8080/fmprod/viewRecent?channel=ALL') as an RSS feed
> > > to the 'sis-location-config.xml' config in my SIS webapp.
> > >
> > > Next, I ran a bounding box query from the SIS demo.jsp and my file
> > > manager files appeared on the map! Awesome!
> >
> > That is SWEET!
> >
> > >
> > > I have uploaded a set of screenshots showing my progress, hopefully
> > > they're accessible and make sense (I'm new to flickr, so apologies if
> > > things look a bit disorganised!):
> > >
> > >
> >
> http://www.flickr.com/photos/rlaidlaw/sets/72157629342438940/with/7031581313/
> >
> > They look great, I checked them out. Would you be willing to do the
> > following?
> >
> > 1. Log onto the SIS wiki and add a little tutorial (small) based on the
> > above email
> > and screenshots?
> >
> > wiki here: https://cwiki.apache.org/confluence/display/SIS/Home
> >
> > 2. Link the SIS tutorial via the OODT wiki, here:
> >
> > https://cwiki.apache.org/confluence/display/OODT/Home
> >
> > >
> > > I tried to order the screenshots to follow the steps I outlined above,
> > > with the final screenshot being the output from the SIS demo showing
> > > the File Manager files on the map.
> >
> > That's awesome.
> >
> > >
> > > For next steps, I could start to formalize some of my experimental
> > > code and begin to address the key points you have outlined on the
> > > OODT-402 jira page (i.e. writing a default GeoRSS config and a default
> > > file manager policy for a 'LocationAwareProduct' type).
> >
> > That would be perfect!
> >
> > > I will follow
> > > up with specific questions about both of these, but for now I just
> > > wanted to give you an update on my progress and to check that I'm
> > > heading in the right direction.
> >
> > You are definitely heading in the right direction that's precisely what I
> > was
> > hoping you would figure out how to do. Thank you Ross for the update
> > and your results look VERY promising, great job so far!
> >
> > Cheers,
> > Chris
> >
> > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > 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
> > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >
> >
>
Re: OODT-402 progress update
Posted by Ross Laidlaw <rl...@gmail.com>.
Hi Chris & Cameron,
Thank you for your kind words. I'm honoured to have the opportunity
to contribute to these projects and to work with and learn from superb
mentors. I very much like the fact that both OODT and SIS are
developed and used by NASA. It will be a great feeling and sense of
achievement for me if I can make a positive contribution and therefore
benefit these projects.
Regards,
Ross
On 1 April 2012 17:59, Cameron Goodale <go...@apache.org> wrote:
> Ross,
>
> I agree with Chris that you are doing a great job on this. Thank you for
> all the hard work in setting this up. Having a standard geospatial
> interface from the FileManager to SIS will prove extremely helpful to
> several JPL/NASA Earth Science Missions in the future.
>
> Just wanted to say thanks!
>
>
>
> Cameron
>
> On Sat, Mar 31, 2012 at 2:47 PM, Mattmann, Chris A (388J) <
> chris.a.mattmann@jpl.nasa.gov> wrote:
>
>> (sorry for the cross post, but of interest to both communities)
>>
>> Hey Ross,
>>
>> That is awesome to hear! Comments below:
>>
>> On Mar 31, 2012, at 4:04 AM, Ross Laidlaw wrote:
>>
>> > Hi Chris,
>> >
>> > Many thanks for your comments and advice. I have now installed SIS on
>> > my system and I have the demo up and running. I've also been
>> > experimenting with the connection between File Manager and SIS and I
>> > have a basic connection working. Here are the steps I have carried so
>> > far:
>> >
>> > Firstly, I added elements for 'Latitude' and 'Longitude' to the
>> > GenericFile policy. Then I created a set of test files (simple text
>> > files) with corresponding '.met' metadata files. I added 'Latitude'
>> > and 'Longitude' metadata to the '.met' files. I then ingested these
>> > into my File Manager repository.
>>
>> That's perfect.
>>
>> >
>> > After that, I enabled the 'georss' tags in the 'rssconf.xml'
>> > configuration file (I added tags for geo:lat and geo:long to start
>> > with) and viewed the RSS output from the CAS REST API in my browser.
>> >
>> > I then added the URL
>> > ('http://localhost:8080/fmprod/viewRecent?channel=ALL') as an RSS feed
>> > to the 'sis-location-config.xml' config in my SIS webapp.
>> >
>> > Next, I ran a bounding box query from the SIS demo.jsp and my file
>> > manager files appeared on the map! Awesome!
>>
>> That is SWEET!
>>
>> >
>> > I have uploaded a set of screenshots showing my progress, hopefully
>> > they're accessible and make sense (I'm new to flickr, so apologies if
>> > things look a bit disorganised!):
>> >
>> >
>> http://www.flickr.com/photos/rlaidlaw/sets/72157629342438940/with/7031581313/
>>
>> They look great, I checked them out. Would you be willing to do the
>> following?
>>
>> 1. Log onto the SIS wiki and add a little tutorial (small) based on the
>> above email
>> and screenshots?
>>
>> wiki here: https://cwiki.apache.org/confluence/display/SIS/Home
>>
>> 2. Link the SIS tutorial via the OODT wiki, here:
>>
>> https://cwiki.apache.org/confluence/display/OODT/Home
>>
>> >
>> > I tried to order the screenshots to follow the steps I outlined above,
>> > with the final screenshot being the output from the SIS demo showing
>> > the File Manager files on the map.
>>
>> That's awesome.
>>
>> >
>> > For next steps, I could start to formalize some of my experimental
>> > code and begin to address the key points you have outlined on the
>> > OODT-402 jira page (i.e. writing a default GeoRSS config and a default
>> > file manager policy for a 'LocationAwareProduct' type).
>>
>> That would be perfect!
>>
>> > I will follow
>> > up with specific questions about both of these, but for now I just
>> > wanted to give you an update on my progress and to check that I'm
>> > heading in the right direction.
>>
>> You are definitely heading in the right direction that's precisely what I
>> was
>> hoping you would figure out how to do. Thank you Ross for the update
>> and your results look VERY promising, great job so far!
>>
>> Cheers,
>> Chris
>>
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> 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
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>
>>
Re: OODT-402 progress update
Posted by Cameron Goodale <go...@apache.org>.
Ross,
I agree with Chris that you are doing a great job on this. Thank you for
all the hard work in setting this up. Having a standard geospatial
interface from the FileManager to SIS will prove extremely helpful to
several JPL/NASA Earth Science Missions in the future.
Just wanted to say thanks!
Cameron
On Sat, Mar 31, 2012 at 2:47 PM, Mattmann, Chris A (388J) <
chris.a.mattmann@jpl.nasa.gov> wrote:
> (sorry for the cross post, but of interest to both communities)
>
> Hey Ross,
>
> That is awesome to hear! Comments below:
>
> On Mar 31, 2012, at 4:04 AM, Ross Laidlaw wrote:
>
> > Hi Chris,
> >
> > Many thanks for your comments and advice. I have now installed SIS on
> > my system and I have the demo up and running. I've also been
> > experimenting with the connection between File Manager and SIS and I
> > have a basic connection working. Here are the steps I have carried so
> > far:
> >
> > Firstly, I added elements for 'Latitude' and 'Longitude' to the
> > GenericFile policy. Then I created a set of test files (simple text
> > files) with corresponding '.met' metadata files. I added 'Latitude'
> > and 'Longitude' metadata to the '.met' files. I then ingested these
> > into my File Manager repository.
>
> That's perfect.
>
> >
> > After that, I enabled the 'georss' tags in the 'rssconf.xml'
> > configuration file (I added tags for geo:lat and geo:long to start
> > with) and viewed the RSS output from the CAS REST API in my browser.
> >
> > I then added the URL
> > ('http://localhost:8080/fmprod/viewRecent?channel=ALL') as an RSS feed
> > to the 'sis-location-config.xml' config in my SIS webapp.
> >
> > Next, I ran a bounding box query from the SIS demo.jsp and my file
> > manager files appeared on the map! Awesome!
>
> That is SWEET!
>
> >
> > I have uploaded a set of screenshots showing my progress, hopefully
> > they're accessible and make sense (I'm new to flickr, so apologies if
> > things look a bit disorganised!):
> >
> >
> http://www.flickr.com/photos/rlaidlaw/sets/72157629342438940/with/7031581313/
>
> They look great, I checked them out. Would you be willing to do the
> following?
>
> 1. Log onto the SIS wiki and add a little tutorial (small) based on the
> above email
> and screenshots?
>
> wiki here: https://cwiki.apache.org/confluence/display/SIS/Home
>
> 2. Link the SIS tutorial via the OODT wiki, here:
>
> https://cwiki.apache.org/confluence/display/OODT/Home
>
> >
> > I tried to order the screenshots to follow the steps I outlined above,
> > with the final screenshot being the output from the SIS demo showing
> > the File Manager files on the map.
>
> That's awesome.
>
> >
> > For next steps, I could start to formalize some of my experimental
> > code and begin to address the key points you have outlined on the
> > OODT-402 jira page (i.e. writing a default GeoRSS config and a default
> > file manager policy for a 'LocationAwareProduct' type).
>
> That would be perfect!
>
> > I will follow
> > up with specific questions about both of these, but for now I just
> > wanted to give you an update on my progress and to check that I'm
> > heading in the right direction.
>
> You are definitely heading in the right direction that's precisely what I
> was
> hoping you would figure out how to do. Thank you Ross for the update
> and your results look VERY promising, great job so far!
>
> Cheers,
> Chris
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 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
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
Re: OODT-402 progress update
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
(sorry for the cross post, but of interest to both communities)
Hey Ross,
That is awesome to hear! Comments below:
On Mar 31, 2012, at 4:04 AM, Ross Laidlaw wrote:
> Hi Chris,
>
> Many thanks for your comments and advice. I have now installed SIS on
> my system and I have the demo up and running. I've also been
> experimenting with the connection between File Manager and SIS and I
> have a basic connection working. Here are the steps I have carried so
> far:
>
> Firstly, I added elements for 'Latitude' and 'Longitude' to the
> GenericFile policy. Then I created a set of test files (simple text
> files) with corresponding '.met' metadata files. I added 'Latitude'
> and 'Longitude' metadata to the '.met' files. I then ingested these
> into my File Manager repository.
That's perfect.
>
> After that, I enabled the 'georss' tags in the 'rssconf.xml'
> configuration file (I added tags for geo:lat and geo:long to start
> with) and viewed the RSS output from the CAS REST API in my browser.
>
> I then added the URL
> ('http://localhost:8080/fmprod/viewRecent?channel=ALL') as an RSS feed
> to the 'sis-location-config.xml' config in my SIS webapp.
>
> Next, I ran a bounding box query from the SIS demo.jsp and my file
> manager files appeared on the map! Awesome!
That is SWEET!
>
> I have uploaded a set of screenshots showing my progress, hopefully
> they're accessible and make sense (I'm new to flickr, so apologies if
> things look a bit disorganised!):
>
> http://www.flickr.com/photos/rlaidlaw/sets/72157629342438940/with/7031581313/
They look great, I checked them out. Would you be willing to do the following?
1. Log onto the SIS wiki and add a little tutorial (small) based on the above email
and screenshots?
wiki here: https://cwiki.apache.org/confluence/display/SIS/Home
2. Link the SIS tutorial via the OODT wiki, here:
https://cwiki.apache.org/confluence/display/OODT/Home
>
> I tried to order the screenshots to follow the steps I outlined above,
> with the final screenshot being the output from the SIS demo showing
> the File Manager files on the map.
That's awesome.
>
> For next steps, I could start to formalize some of my experimental
> code and begin to address the key points you have outlined on the
> OODT-402 jira page (i.e. writing a default GeoRSS config and a default
> file manager policy for a 'LocationAwareProduct' type).
That would be perfect!
> I will follow
> up with specific questions about both of these, but for now I just
> wanted to give you an update on my progress and to check that I'm
> heading in the right direction.
You are definitely heading in the right direction that's precisely what I was
hoping you would figure out how to do. Thank you Ross for the update
and your results look VERY promising, great job so far!
Cheers,
Chris
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
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
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Re: OODT-402 progress update
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
(sorry for the cross post, but of interest to both communities)
Hey Ross,
That is awesome to hear! Comments below:
On Mar 31, 2012, at 4:04 AM, Ross Laidlaw wrote:
> Hi Chris,
>
> Many thanks for your comments and advice. I have now installed SIS on
> my system and I have the demo up and running. I've also been
> experimenting with the connection between File Manager and SIS and I
> have a basic connection working. Here are the steps I have carried so
> far:
>
> Firstly, I added elements for 'Latitude' and 'Longitude' to the
> GenericFile policy. Then I created a set of test files (simple text
> files) with corresponding '.met' metadata files. I added 'Latitude'
> and 'Longitude' metadata to the '.met' files. I then ingested these
> into my File Manager repository.
That's perfect.
>
> After that, I enabled the 'georss' tags in the 'rssconf.xml'
> configuration file (I added tags for geo:lat and geo:long to start
> with) and viewed the RSS output from the CAS REST API in my browser.
>
> I then added the URL
> ('http://localhost:8080/fmprod/viewRecent?channel=ALL') as an RSS feed
> to the 'sis-location-config.xml' config in my SIS webapp.
>
> Next, I ran a bounding box query from the SIS demo.jsp and my file
> manager files appeared on the map! Awesome!
That is SWEET!
>
> I have uploaded a set of screenshots showing my progress, hopefully
> they're accessible and make sense (I'm new to flickr, so apologies if
> things look a bit disorganised!):
>
> http://www.flickr.com/photos/rlaidlaw/sets/72157629342438940/with/7031581313/
They look great, I checked them out. Would you be willing to do the following?
1. Log onto the SIS wiki and add a little tutorial (small) based on the above email
and screenshots?
wiki here: https://cwiki.apache.org/confluence/display/SIS/Home
2. Link the SIS tutorial via the OODT wiki, here:
https://cwiki.apache.org/confluence/display/OODT/Home
>
> I tried to order the screenshots to follow the steps I outlined above,
> with the final screenshot being the output from the SIS demo showing
> the File Manager files on the map.
That's awesome.
>
> For next steps, I could start to formalize some of my experimental
> code and begin to address the key points you have outlined on the
> OODT-402 jira page (i.e. writing a default GeoRSS config and a default
> file manager policy for a 'LocationAwareProduct' type).
That would be perfect!
> I will follow
> up with specific questions about both of these, but for now I just
> wanted to give you an update on my progress and to check that I'm
> heading in the right direction.
You are definitely heading in the right direction that's precisely what I was
hoping you would figure out how to do. Thank you Ross for the update
and your results look VERY promising, great job so far!
Cheers,
Chris
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
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
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Re: OODT-402 progress update
Posted by Ross Laidlaw <rl...@gmail.com>.
Hi Chris,
Many thanks for your comments and advice. I have now installed SIS on
my system and I have the demo up and running. I've also been
experimenting with the connection between File Manager and SIS and I
have a basic connection working. Here are the steps I have carried so
far:
Firstly, I added elements for 'Latitude' and 'Longitude' to the
GenericFile policy. Then I created a set of test files (simple text
files) with corresponding '.met' metadata files. I added 'Latitude'
and 'Longitude' metadata to the '.met' files. I then ingested these
into my File Manager repository.
After that, I enabled the 'georss' tags in the 'rssconf.xml'
configuration file (I added tags for geo:lat and geo:long to start
with) and viewed the RSS output from the CAS REST API in my browser.
I then added the URL
('http://localhost:8080/fmprod/viewRecent?channel=ALL') as an RSS feed
to the 'sis-location-config.xml' config in my SIS webapp.
Next, I ran a bounding box query from the SIS demo.jsp and my file
manager files appeared on the map! Awesome!
I have uploaded a set of screenshots showing my progress, hopefully
they're accessible and make sense (I'm new to flickr, so apologies if
things look a bit disorganised!):
http://www.flickr.com/photos/rlaidlaw/sets/72157629342438940/with/7031581313/
I tried to order the screenshots to follow the steps I outlined above,
with the final screenshot being the output from the SIS demo showing
the File Manager files on the map.
For next steps, I could start to formalize some of my experimental
code and begin to address the key points you have outlined on the
OODT-402 jira page (i.e. writing a default GeoRSS config and a default
file manager policy for a 'LocationAwareProduct' type). I will follow
up with specific questions about both of these, but for now I just
wanted to give you an update on my progress and to check that I'm
heading in the right direction.
Speak to you soon,
Ross
On 22 March 2012 05:48, Mattmann, Chris A (388J)
<ch...@jpl.nasa.gov> wrote:
> Hi Ross,
>
> On Mar 22, 2012, at 5:34 AM, Ross Laidlaw wrote:
>
>> Hi Chris,
>>
>> I'm writing to give an update on my progress on OODT-402 and getting
>> up to speed with the OODT project.
>>
>> I've been reading through the documentation from
>> http://oodt.apache.org/components/maven/filemgr and the wiki pages
>> http://cwiki.apache.org/oodt. I've also read up on the GeoRSS format
>> at http://georss.org and http://en.wikipedia.org/wiki/GeoRSS.
>
> Awesome, that's the right place to start!
>
>>
>> By following the user guides (which are awesome by the way!)
>
> * thanks * Many folks have been really updating those lately (Tom Bennett, Cameron
> Goodale, Sheryl John, and others) so thanks to them for that!
>
>> I have
>> built OODT with maven v2.2.1 on my laptop (macbook running OSX Lion)
>> and set up the File Manager program (I've ingested my first 'blah.txt'
>> file with meta data! And also tested out some queries).
>
> You ROCK, nice!
>
>>
>> As a next step, I'd like to install the File Manager webapp. Are
>> there any recent guides for installing? I watched both of your Apache
>> OODT Curation tutorials on YouTube (very cool) and also found some
>> info about webapps from one of your replies on the
>> user@oodt.apache.org mailing list (with link to slides
>> http://oodt.apache.org/components/maven/grid/slides.pdf). I have my
>> webapp target folders and war files from the build and I have Tomcat
>> set up on my machine, so hopefully I'm not far off being up and
>> running! Apologies if this is something obvious that I should know
>> already (e.g. by learning more about Tomcat).
>
> Great, that's the right starting point.
>
>>
>> I built the 0.3 release of OODT on my machine. But I also had a look
>> through the latest webapp source code and noted your comments in the
>> following file:
>> https://svn.apache.org/repos/asf/oodt/trunk/webapp/fmprod/src/main/resources/rssconf.xml
>>
>> <!--
>>
>> If you want to turn your CAS File Manager into a GeoRSS
>> simple service (see http://georss.org/simple), add the
>> following block, assuming that you have indexed met fields
>> named Latitude and Longitude for your product (update as
>> appropriate otherwise).
>>
>> <tag name="georss:point" source="[Latitude] [Longitude]"/>
>> -->
>
> Yep, the above is assuming that you index 2 met fields along with your
> products, the Latitude met field, and the Longitude. If you indexed them
> differently (e.g., a field named "geolat" or "geolng", then you would update
> the above accordingly).
>
>>
>>
>> Am I right in thinking that this is the starting point for OODT-402?
>
> Absolutely that's the right starting point for getting GeoRSS out of the
> File Manager, then the next step is to move onto SIS and read about its
> GeoRSS data loader and Quad Tree. Admittedly over in SIS ville there's
> a lot less documentation, but it would be great because there is also
> as an Incubator project a lot more ability to easily contribute and get started
> being part of the community.
>
>> I saw from georss.org that there are a few different GeoRSS formats
>> (Simple, GML and W3C). But I read that the W3C format is a bit older
>> and the GML format is quite extensive, so it's a great plan to use the
>> simple format and work from there.
>
> It would be great to support the Simple to start out with and if there is
> time to look at the GML and W3C versions (but only as it makes sense
> and if there is time).
>
>>
>> I'd like to set up a similar development environment to the OODT
>> developers. Is Eclipse the IDE of choice?
>
> Yep most of the OODT devs use Eclipse and there are a wealth of
> folks that could help you here on list if you have any trouble.
>
>> I noticed you using it on
>> the youtube tutorials and also there's an 'OODT Eclipse Developer
>> Help' guide on the wiki. I have version 3.7.2 (Indigo) installed on
>> my machine but please let me know if there are any incompatibility
>> problems.
>
> That sounds fine, should work great.
>
>>
>> Regarding OODT-402, do you have a feel for how long you'd expect me to
>> take in completing the project?
>
> I'm hoping that in a month you could have the whole thing running end, to
> end, but even if it took 2 months or 3 months that would be great too. There's
> a lot of room to grow in both projects, OODT and SIS, and you can really
> take it where you want to go from there.
>
>> I'd like to put together a plan of
>> action for my GSoC proposal. I have the three step outline from the
>> OODT-402 JIRA page as the basis for the plan. I feel that I have a
>> good knowledge of XML and core Java, for example I have passed the
>> Oracle Certified Java Programmer exam. Hopefully I also have a good
>> grounding in some of the design principles used in OODT, for example
>> factory design patterns and coding to interfaces for extensibility, as
>> I have taken several OO classes so far in my studies.
>
> Yeah I think you are perfect for the project and you will do great. The next
> step is probably to start learning about SIS as you get closer to getting
> the FM to spit out GeoRSS. Feel free to engage the SIS community
> (sis-dev@incubator.apache.org) as you move forward there too and if
> you have any questions let us know and we'll all try and help out.
>
>>
>> I'm hoping to have some more specific questions about the steps for
>> OODT-402 as I start using the webapp and examining the source code in
>> more detail.
>
> Awesome happy to help!
>
>>
>>
>> Many thanks again for your time,
>>
>
> And to yours! I'm super excited, great work so far Ross...
>
> Cheers,
> Chris
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 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
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
Re: OODT-402 progress update
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hi Ross,
On Mar 22, 2012, at 5:34 AM, Ross Laidlaw wrote:
> Hi Chris,
>
> I'm writing to give an update on my progress on OODT-402 and getting
> up to speed with the OODT project.
>
> I've been reading through the documentation from
> http://oodt.apache.org/components/maven/filemgr and the wiki pages
> http://cwiki.apache.org/oodt. I've also read up on the GeoRSS format
> at http://georss.org and http://en.wikipedia.org/wiki/GeoRSS.
Awesome, that's the right place to start!
>
> By following the user guides (which are awesome by the way!)
* thanks * Many folks have been really updating those lately (Tom Bennett, Cameron
Goodale, Sheryl John, and others) so thanks to them for that!
> I have
> built OODT with maven v2.2.1 on my laptop (macbook running OSX Lion)
> and set up the File Manager program (I've ingested my first 'blah.txt'
> file with meta data! And also tested out some queries).
You ROCK, nice!
>
> As a next step, I'd like to install the File Manager webapp. Are
> there any recent guides for installing? I watched both of your Apache
> OODT Curation tutorials on YouTube (very cool) and also found some
> info about webapps from one of your replies on the
> user@oodt.apache.org mailing list (with link to slides
> http://oodt.apache.org/components/maven/grid/slides.pdf). I have my
> webapp target folders and war files from the build and I have Tomcat
> set up on my machine, so hopefully I'm not far off being up and
> running! Apologies if this is something obvious that I should know
> already (e.g. by learning more about Tomcat).
Great, that's the right starting point.
>
> I built the 0.3 release of OODT on my machine. But I also had a look
> through the latest webapp source code and noted your comments in the
> following file:
> https://svn.apache.org/repos/asf/oodt/trunk/webapp/fmprod/src/main/resources/rssconf.xml
>
> <!--
>
> If you want to turn your CAS File Manager into a GeoRSS
> simple service (see http://georss.org/simple), add the
> following block, assuming that you have indexed met fields
> named Latitude and Longitude for your product (update as
> appropriate otherwise).
>
> <tag name="georss:point" source="[Latitude] [Longitude]"/>
> -->
Yep, the above is assuming that you index 2 met fields along with your
products, the Latitude met field, and the Longitude. If you indexed them
differently (e.g., a field named "geolat" or "geolng", then you would update
the above accordingly).
>
>
> Am I right in thinking that this is the starting point for OODT-402?
Absolutely that's the right starting point for getting GeoRSS out of the
File Manager, then the next step is to move onto SIS and read about its
GeoRSS data loader and Quad Tree. Admittedly over in SIS ville there's
a lot less documentation, but it would be great because there is also
as an Incubator project a lot more ability to easily contribute and get started
being part of the community.
> I saw from georss.org that there are a few different GeoRSS formats
> (Simple, GML and W3C). But I read that the W3C format is a bit older
> and the GML format is quite extensive, so it's a great plan to use the
> simple format and work from there.
It would be great to support the Simple to start out with and if there is
time to look at the GML and W3C versions (but only as it makes sense
and if there is time).
>
> I'd like to set up a similar development environment to the OODT
> developers. Is Eclipse the IDE of choice?
Yep most of the OODT devs use Eclipse and there are a wealth of
folks that could help you here on list if you have any trouble.
> I noticed you using it on
> the youtube tutorials and also there's an 'OODT Eclipse Developer
> Help' guide on the wiki. I have version 3.7.2 (Indigo) installed on
> my machine but please let me know if there are any incompatibility
> problems.
That sounds fine, should work great.
>
> Regarding OODT-402, do you have a feel for how long you'd expect me to
> take in completing the project?
I'm hoping that in a month you could have the whole thing running end, to
end, but even if it took 2 months or 3 months that would be great too. There's
a lot of room to grow in both projects, OODT and SIS, and you can really
take it where you want to go from there.
> I'd like to put together a plan of
> action for my GSoC proposal. I have the three step outline from the
> OODT-402 JIRA page as the basis for the plan. I feel that I have a
> good knowledge of XML and core Java, for example I have passed the
> Oracle Certified Java Programmer exam. Hopefully I also have a good
> grounding in some of the design principles used in OODT, for example
> factory design patterns and coding to interfaces for extensibility, as
> I have taken several OO classes so far in my studies.
Yeah I think you are perfect for the project and you will do great. The next
step is probably to start learning about SIS as you get closer to getting
the FM to spit out GeoRSS. Feel free to engage the SIS community
(sis-dev@incubator.apache.org) as you move forward there too and if
you have any questions let us know and we'll all try and help out.
>
> I'm hoping to have some more specific questions about the steps for
> OODT-402 as I start using the webapp and examining the source code in
> more detail.
Awesome happy to help!
>
>
> Many thanks again for your time,
>
And to yours! I'm super excited, great work so far Ross...
Cheers,
Chris
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
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
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++