+1 to /failure/ingest and /failure/jobs, etc.

That makes sense to me...though unfortunately will cause grumpy people like me 
to have to change to take advantage of the power of RADIX. I'll learn though 
(slowly) over time :)

Cheers,
Chris

On May 19, 2011, at 7:40 AM, Ramirez, Paul M (388J) wrote:

> Hey Chris,
> 
> The failure was just meant to be more generic as there could be other items, 
> from say workflow, that would also go in there. How about having 
> "/failure/ingest"? That still does remove the files word though so 
> "/failure/ingest_files" is a possibility. The reasoning behind not having 
> files in the directory name is that at the highest level we talk about 
> ingestion of products and not files. 
> 
> Thanks,
> Paul
> 
> 
> 
> 
> On May 18, 2011, at 6:21 PM, Mattmann, Chris A (388J) wrote:
> 
>> Hi Paul,
>> 
>> met could be for either the crawler or for the curator.
>> 
>> As for failed_ingest_files, why the rename? Just to be shorter? I think 
>> failed_ingest_files, though more verbose, conveys more meaning than 
>> failure...
>> 
>> Cheers,
>> Chris
>> 
>> On May 18, 2011, at 7:50 AM, Ramirez, Paul M (388J) 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]
>>>> 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: [email protected]
>> 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: [email protected]
WWW:   http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Reply via email to