Hey Paul, All volunteers are welcome. Actually your timing is great as one items we were going to tackle next was UIs and services within OODT. We hadn't planned on getting to this until July as our initial delivery of crawler, filemgr, and workflow is end of June. Currently, there are a few UIs and services that are packaged as war files within the OODT code. For RADiX we need to understand how we deliver them out the box (i.e. configured and ready to go), which likely means packaging in a Tomcat or Jetty server. In addition, we need to know if there is any tailoring the end consumer would do for that UI/service and how they would do that tailoring (think skins for a web app). Here are the steps I would take to get started.
1) Join the OODT Apache community (i.e. get on our mailing lists) 2) Read the RADiX Wiki 3) Survey what UI/services are available in the OODT codebase 4) Formulate how these should be packaged into a distribution and put them into our test distribution which is being developed in a branch 5) Update the RADiX archetype to make the tested out packaging happen 6) Further UI/service development in the OODT codebase for any gaps in the current set For items one through five you wouldn't be developing anything new in the UI/services area but it will help give you a view of what we have and the direction we are going. Generally, I would say that there are 2 classes of UIs/services that we are looking to support, a management UI for understanding what is going on behind the scenes, and a portal to deliver to an community products from the data management system. There is support for both in the codebase but help to fill in gaps and evolve would be great (long term). At the end of the day people just want something that just works out of the box so RADiX is aiming to appeal to that group and leverage what has already been done; think wrapping paper, tape, and some bows. I'll be on vacation for a few weeks but Cameron Goodale is around if you have questions. Thanks, Paul On May 18, 2011, at 6:53 PM, Paul Vee wrote: Nice to see you again. SO...Thought Leader gave me a wink today at lunch stating that I would be able to help with RADiX...not sure how I can help (since I am a UI guy), but if you can point me some kind of direction I'll be glad to pick up a shovel. On Wed, May 18, 2011 at 7:50 AM, Ramirez, Paul M (388J) <[email protected]<mailto:[email protected]>> wrote: Hey Chris, The met directory was for generated metadata by the crawler or was it for the curator? I updated the page with a description of the paths and renamed failed_ingest_files to failure. On the next pass I'll start posting a description of the source structure that will be available as output from the RADiX archetype. Thanks, Paul On May 17, 2011, at 7:45 PM, Mattmann, Chris A (388J) wrote: > Hey Guys, > > FYI: https://cwiki.apache.org/confluence/display/OODT/RADiX+Powered+By+OODT > > I updated the page to propose a: > > /data > /archive > /staging > /work > /met > /failed_ingest_files > > Dir structure for RADIX to more closely match our existing OODT deployments. > > Cheers, > Chris > > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > Chris Mattmann, Ph.D. > Senior Computer Scientist > NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA > Office: 171-266B, Mailstop: 171-246 > Email: [email protected]<mailto:[email protected]> > WWW: http://sunset.usc.edu/~mattmann/ > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > Adjunct Assistant Professor, Computer Science Department > University of Southern California, Los Angeles, CA 90089 USA > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > -- Paul Vee [email protected]<mailto:[email protected]>
