Re: Request for advice on workflows

[Ross Laidlaw]

Hi Chris,

Apologies for my delay in replying.  I'm still seeing this issue.  I have a
sequential workflow that's working fine, but when I add a parallel section
I'm seeing the error that I pasted into my previous email.  I might be
missing some config steps.  Is my understanding correct - that OODT is
trying to generate a special task (branch redirection task) that sets up a
new workflow on a batch node?  What should happen after that?  Should this
workflow task then try to run one of the parallel tasks?  I've configured a
batch stub running on the same machine as the master workflow to handle
these requests...  I'm not sure if it can access the same workflow manager
configs though...  I checked the workflow manager URL and it seems fine for
the branch redirection task.

Ross



On 15 May 2015 at 18:11, Mattmann, Chris A (3980) <
chris.a.mattm...@jpl.nasa.gov> wrote:

> Ross you still having this issue?
>
> ++
> Chris Mattmann, Ph.D.
> Chief Architect
> Instrument Software and Science Data Systems Section (398)
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 168-519, Mailstop: 168-527
> Email: chris.a.mattm...@nasa.gov
> WWW:  http://sunset.usc.edu/~mattmann/
> ++
> Adjunct Associate Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++
>
>
>
>
>
>
> -Original Message-
> From: Ross Laidlaw 
> Reply-To: "dev@oodt.apache.org" 
> Date: Wednesday, May 13, 2015 at 2:37 AM
> To: "dev@oodt.apache.org" 
> Subject: Re: Request for advice on workflows
>
> >Hi Chris,
> >
> >As a first step I got an XMLWorkflowRepository workflow running.  I then
> >tried using the PackagedWorkflowRepository to create a workflow with the
> >same tasks.  I got a sequential workflow up and running, similar to the
> >following:
> >
> >
> >  
> >
> >
> >
> >
> >
> >
> >
> >  
> >
> >  
> >  ...
> >
> >
> >
> >
> >I found that I could run the workflow using ./wmgr-client --url
> >[WorkflowManagerUrl] --sendEvent --eventName [WorkflowId]
> >e.g.  ./wmgr-client --url http://localhost:9001 --sendEvent --eventName
> >urn:test:MainWorkflow
> >
> >
> >After getting the sequential workflow running, I wanted to run tasks C and
> >D in parallel so I then tried adding a  section as follows:
> >
> >
> >  
> >
> >
> >
> >  
> >  
> >
> >
> >
> >
> >  
> >  ...
> >
> >
> >
> >The parallel section generates an additional task to be submitted called
> >'Redirector Task' that wants to be executed in the 'high' queue using the
> >BranchRedirector class:
> >
> >INFO: Task: [Redirector Task] has no required metadata fields
> >May 13, 2015 1:27:29 AM
> >org.apache.oodt.cas.resource.system.XmlRpcResourceManagerClient submitJob
> >FINEST:
> >[
> >  {
> >job.queueName=high,
> >job.instanceClassName=org.apache.oodt.cas.workflow.structs.TaskJob,
> >job.name=redirector-322db9d2-4663-4b89-9af0-f8f97ad74c80,
> >job.id=, job.status=, job.load=2,
> >job.inputClassName=org.apache.oodt.cas.workflow.structs.TaskJobInput
> >  },
> >  {
> >
> >task.instance.class=org.apache.oodt.cas.workflow.examples.BranchRedirector
> >,
> >task.config={},
> >task.metadata={...}
> >  }
> >]
> >
> >
> >I wasn't sure how to configure my setup to deal with this task.  From
> >reading OODT-70 I gather that it might be trying to start up other
> >wmgr-clients on batch stubs to run these tasks in separate workflows.  I
> >tried setting up a local batch stub that accepts jobs from the 'high'
> >queue.  When running the full workflow I get the following exception from
> >the batch stub when it tries to execute the redirector task:
> >
> >INFO: Assigning job: [redirector-8561de94-2681-477b-8bcb-331d83224d5b] to
> >node: [local-redirector]
> >May 13, 2015 1:36:51 AM
> >org.apache.oodt.cas.resource.system.extern.XmlRpcBatchStub
> >genericExecuteJob
> >INFO: stub attempting to execute class:
> >[org.apache.oodt.cas.workflow.structs.TaskJob]
> >org.apache.xmlrpc.XmlRpcClientException: Failure writing request
> >  at
> >org.apache.xmlrpc.XmlRpcClientRequestProcessor.encodeRequest(XmlRpcClientR
> >equestProcessor.java:76)
> >  at
> >org.apache.xmlrpc.XmlRpcClientRequestProcessor.encodeRequestBytes(XmlRpcCl
> >ientRequestProcessor.java:102)
> >  at
> >org.apache.xmlrpc.XmlRpcClientWorker.execute(XmlRpcClientWorker.java:70)
> >  at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:194)
> >  at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:185)
> >  at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:178)
> >  at
> >org.apache.oodt.cas.workflow.system.XmlRpcWorkflowManagerClient.sendEvent(
> >XmlRpcWorkflowManagerClient.java:477)
> >  at
> >org.apache.oodt.cas.workflow.examples.BranchRedirector.run(BranchRedirecto
> >r.java:

RE: OODT book proposal

[Tom Barber]

Thanks Val

I'm not sure how many people will contribute content-wise so I may ask for
help from people I may not.

My main concern currently is making sure I get the content right for the
pitch tomorrow and to make sure it's broad enough to make sense to non
scientists as part of what I'm trying to achieve is drag oodt from purely
science into more mainstream applications. So if anyone can think of
anything else that is missing now is the time to speak up! ;)

Tom
On 26 May 2015 17:06, "Mallder, Valerie"  wrote:

> Hi Tom,
>
> I may be able to contribute some content to section 1.4.1 depending on how
> many examples you want to provide. I am using OODT Radix to build the two
> pipeline projects that I currently working on.
>
> Val
>
>
>
> Valerie A. Mallder
> New Horizons Deputy Mission System Engineer
> Johns Hopkins University/Applied Physics Laboratory
>
>
> > -Original Message-
> > From: Tom Barber [mailto:tom.bar...@meteorite.bi]
> > Sent: Tuesday, May 26, 2015 5:53 AM
> > To: dev@oodt.apache.org
> > Subject: Re: OODT book proposal
> >
> > Alright chaps this is pretty last minute as I have to chat to the guy
> from Manning
> > tomorrow so if anyone has 5 minutes, can you scan:
> > https://docs.google.com/document/d/1dGVf0j25WzXZCyTyuX9aMmmQ06yAPLOF
> > tuTFZe-0aXk/edit?usp=sharing
> > and add anything you think is missing. The link is open to all so you
> should be
> > able to add/change entries, just italicise them or something so I can
> spot them.
> >
> > Thanks
> >
> > Tom
> >
> > On Wed, May 20, 2015 at 7:14 PM, Tom Barber 
> wrote:
> >
> > > Thanks for the feedback guys.
> > >
> > > The chat I had with the chap was certainly around a full book as I
> > > have to pitch 9 - 14 chapters. He did say they are trying to move away
> > > from generic platform books so I think pitching it in the style of a
> > > look at all the main components and heavy on the real world how-to and
> > > use cases would be the way I'm tending to go along with a load of
> > > stuff on the value of metadata etc.
> > >
> > > We discussed use case ideas and I went over some of the crazy NASA
> > > stuff which he said I should include and also a bunch of real world
> > > use cases(smart meters/regulatory compliance application and stuff
> > > from my day job), but of course, you lot don't live in the real world
> > > so you'll have to leave that to me ;)
> > >
> > > On 1.0 I'm sure it will come out during the time we would spend
> > > writing a book.
> > >
> > > I'll come back with a draft toc tonight or tomorrow and those
> > > interested can add their 10 cents.
> > >
> > > Tom
> > > On 20 May 2015 18:26, "Lewis John Mcgibbney"
> > > 
> > > wrote:
> > >
> > >> Spoke to Tom White a while ago @ApacheCon about this very topic folks
> > >> with one interesting outcome.
> > >> Many publishers (I don't know about Manning, however Chris will
> > >> likely
> > >> know) are interested in Microbooks or picket guides as well.
> > >> An example is the following
> > >> http://shop.oreilly.com/product/9780596007430.do
> > >> I don't know if this fits for something like OODT but you guys can
> > >> consider.
> > >> Lewis
> > >>
> > >> On Wed, May 20, 2015 at 10:11 AM, Chris Mattmann <
> > >> chris.mattm...@gmail.com>
> > >> wrote:
> > >>
> > >> > Thanks Mike. I don’t think 1.0 is required
> > >> > *before* writing the book, but can happen while the book is going
> > >> > on (and be pushed in many cases by the book!) :)
> > >> >
> > >> > We had the same scenario with Tika in Action.
> > >> >
> > >> > Cheers,
> > >> > Chris
> > >> >
> > >> > 
> > >> > Chris Mattmann
> > >> > chris.mattm...@gmail.com
> > >> >
> > >> >
> > >> >
> > >> >
> > >> > -Original Message-
> > >> > From: Michael Starch 
> > >> > Reply-To: 
> > >> > Date: Wednesday, May 20, 2015 at 10:10 AM
> > >> > To: 
> > >> > Subject: Re: OODT book proposal
> > >> >
> > >> > >I am definitely up for this.  Are we going to push for an OODT-1.0
> > >> > >"polished" released before we write a book?  There seem to be a
> > >> > >lot of very nice features in the pipe, which will affect the
> > >> > >content of a book.
> > >> > >
> > >> > >Regardless, I believe the following may be helpful for the book.
> > >> > >
> > >> > >- Setting Up OODT
> > >> > >- Major OODT Components
> > >> > >- Extending OODT
> > >> > >- OODT in Operations
> > >> > >
> > >> > >-Michael
> > >> > >
> > >> > >On Wed, May 20, 2015 at 9:24 AM, Freeborn, Dana J (398G) <
> > >> > >dana.j.freeb...@jpl.nasa.gov> wrote:
> > >> > >
> > >> > >> Hi Tom,
> > >> > >>
> > >> > >> This is great.  I would be happy to contribute to the book if my
> > >> level
> > >> > >>of
> > >> > >> experience with OODT (which is high) is helpful.  It's not clear
> > >> > >>to
> > >> me
> > >> > >>your
> > >> > >> focus for the book, so you'll just have to tap me if I can
> > >> contribute.
> > >> > >> Paul and Chris will know if I do.  Otherwise, I will cheer on
> > >> > >> your efforts.  :

RE: OODT book proposal

[Mallder, Valerie]

Hi Tom,

I may be able to contribute some content to section 1.4.1 depending on how many 
examples you want to provide. I am using OODT Radix to build the two pipeline 
projects that I currently working on.

Val



Valerie A. Mallder
New Horizons Deputy Mission System Engineer
Johns Hopkins University/Applied Physics Laboratory


> -Original Message-
> From: Tom Barber [mailto:tom.bar...@meteorite.bi]
> Sent: Tuesday, May 26, 2015 5:53 AM
> To: dev@oodt.apache.org
> Subject: Re: OODT book proposal
> 
> Alright chaps this is pretty last minute as I have to chat to the guy from 
> Manning
> tomorrow so if anyone has 5 minutes, can you scan:
> https://docs.google.com/document/d/1dGVf0j25WzXZCyTyuX9aMmmQ06yAPLOF
> tuTFZe-0aXk/edit?usp=sharing
> and add anything you think is missing. The link is open to all so you should 
> be
> able to add/change entries, just italicise them or something so I can spot 
> them.
> 
> Thanks
> 
> Tom
> 
> On Wed, May 20, 2015 at 7:14 PM, Tom Barber  wrote:
> 
> > Thanks for the feedback guys.
> >
> > The chat I had with the chap was certainly around a full book as I
> > have to pitch 9 - 14 chapters. He did say they are trying to move away
> > from generic platform books so I think pitching it in the style of a
> > look at all the main components and heavy on the real world how-to and
> > use cases would be the way I'm tending to go along with a load of
> > stuff on the value of metadata etc.
> >
> > We discussed use case ideas and I went over some of the crazy NASA
> > stuff which he said I should include and also a bunch of real world
> > use cases(smart meters/regulatory compliance application and stuff
> > from my day job), but of course, you lot don't live in the real world
> > so you'll have to leave that to me ;)
> >
> > On 1.0 I'm sure it will come out during the time we would spend
> > writing a book.
> >
> > I'll come back with a draft toc tonight or tomorrow and those
> > interested can add their 10 cents.
> >
> > Tom
> > On 20 May 2015 18:26, "Lewis John Mcgibbney"
> > 
> > wrote:
> >
> >> Spoke to Tom White a while ago @ApacheCon about this very topic folks
> >> with one interesting outcome.
> >> Many publishers (I don't know about Manning, however Chris will
> >> likely
> >> know) are interested in Microbooks or picket guides as well.
> >> An example is the following
> >> http://shop.oreilly.com/product/9780596007430.do
> >> I don't know if this fits for something like OODT but you guys can
> >> consider.
> >> Lewis
> >>
> >> On Wed, May 20, 2015 at 10:11 AM, Chris Mattmann <
> >> chris.mattm...@gmail.com>
> >> wrote:
> >>
> >> > Thanks Mike. I don’t think 1.0 is required
> >> > *before* writing the book, but can happen while the book is going
> >> > on (and be pushed in many cases by the book!) :)
> >> >
> >> > We had the same scenario with Tika in Action.
> >> >
> >> > Cheers,
> >> > Chris
> >> >
> >> > 
> >> > Chris Mattmann
> >> > chris.mattm...@gmail.com
> >> >
> >> >
> >> >
> >> >
> >> > -Original Message-
> >> > From: Michael Starch 
> >> > Reply-To: 
> >> > Date: Wednesday, May 20, 2015 at 10:10 AM
> >> > To: 
> >> > Subject: Re: OODT book proposal
> >> >
> >> > >I am definitely up for this.  Are we going to push for an OODT-1.0
> >> > >"polished" released before we write a book?  There seem to be a
> >> > >lot of very nice features in the pipe, which will affect the
> >> > >content of a book.
> >> > >
> >> > >Regardless, I believe the following may be helpful for the book.
> >> > >
> >> > >- Setting Up OODT
> >> > >- Major OODT Components
> >> > >- Extending OODT
> >> > >- OODT in Operations
> >> > >
> >> > >-Michael
> >> > >
> >> > >On Wed, May 20, 2015 at 9:24 AM, Freeborn, Dana J (398G) <
> >> > >dana.j.freeb...@jpl.nasa.gov> wrote:
> >> > >
> >> > >> Hi Tom,
> >> > >>
> >> > >> This is great.  I would be happy to contribute to the book if my
> >> level
> >> > >>of
> >> > >> experience with OODT (which is high) is helpful.  It's not clear
> >> > >>to
> >> me
> >> > >>your
> >> > >> focus for the book, so you'll just have to tap me if I can
> >> contribute.
> >> > >> Paul and Chris will know if I do.  Otherwise, I will cheer on
> >> > >> your efforts.  :-)
> >> > >>
> >> > >> Thanks,
> >> > >> Dana
> >> > >>
> >> > >>
> >> > >> From: Tom Barber
> >> > >>mailto:tom.bar...@meteorite.bi>>
> >> > >> Reply-To: "dev@oodt.apache.org" <
> >> > >>dev@oodt.apache.org>
> >> > >> Date: Wednesday, May 20, 2015 2:02 AM
> >> > >> To: "dev@oodt.apache.org"
> >> > >> >> > >> >
> >> > >> Subject: OODT book proposal
> >> > >>
> >> > >> Hi guys,
> >> > >>
> >> > >> I was on the phone to Manning today about an OODT book that me,
> >> > >>Chris and  Mike Starch mulled over in Texas.
> >> > >>
> >> > >> I've been tasked with coming up with a TOC as the proposal so
> >> > >> I'll
> >> knock
> >> > >> something tog

Re: OODT book proposal

[Tom Barber]

Thanks Dan, very useful!

Tom

On Tue, May 26, 2015 at 4:08 PM, Crichton, Daniel J (3902) <
daniel.j.crich...@jpl.nasa.gov> wrote:

> Tom,
>
> Looking at the outline, a few things jump out at me.
>
> 1. Architectural concepts behind OODT
>
> OODT was defined by an initial set of architectural principles that I
> believe still hold today.  A key one being the separation of the software
> components from the information model.  It's my belief that this is why
> OODT could be applied to so many different domains.
>
> In addition, there are some key architectural patterns behind OODT but two
> very prominent ones:
> (1) Information capture, processing, etc - In the early days this was
> first implemented by the Palomar Testbed Interferometer and SeaWinds)
> which defined the CAS
> (2) Data discovery, access, distribution, integration, of highly
> distributed, heterogeneous systems - This was defined by projects like
> NASA/PDS, NCI/EDRN, etc
>
> Many of the architectural decisions made the foundation of OODT as a data
> science ecosystem and have allowed for it to be applied not only to
> different domains, but also to allow it to scale and integrate with
> different technologies and standards including messaging systems, cloud
> infrastructures, different database backends, etc.  In fact, this allowed
> NASA to move away from being tightly coupled to a vendor ground data
> systems to use OODT an open source processing infrastructure for Earth
> Science back in 2003.
>
> It would be good to include this in Part I.  Much of it right now is in
> academic papers.
>
> 2. Section 5.x - OODT's web grid components are much less about
> computation/processing and more about data intensive capabilities of
> discovery (e.g., Profile Services) , access, transformation, and
> distribution (e.g., Product Services).  I would stress the distributed
> deployment of OODT to integrate highly distributed, heterogeneous systems.
>  This is how PDS, EDRN, and some other biomedical data networks are using
> it.
>
> We've kept Profile/Product and CAS components as separate so I would think
> that 5.1, 5.2, 5.3, and 5.6 should move up to section 4 or a new section
> should be create to address the information integration aspects with the
> web grid pieces moving into it.
>
>
> 3.  Section 10 - EDRN is certainly example of integrating heterogeneous,
> distributed systems together but PDS and others can be discussed.  For
> EDRN and PDS, it's much less about distributed data entry and much more
> focused on how to integrate, transform, and distribute data across highly
> distributed systems.
>
> Hope this helps.
>
> Dan
>
> On 5/26/15 7:38 AM, "Tom Barber"  wrote:
>
> >Thanks Chris.
> >
> >Eva, I think we can probably include that stuff within one of the existing
> >tutorial sections as your ideas aren't too crazy ;)
> >
> >Tom
> >
> >On Tue, May 26, 2015 at 3:07 PM, Mattmann, Chris A (3980) <
> >chris.a.mattm...@jpl.nasa.gov> wrote:
> >
> >> you have to have a chapter on NASA earth science missions :)
> >> I added it..good luck!
> >>
> >> 
> >> From: Tom Barber [tom.bar...@meteorite.bi]
> >> Sent: Tuesday, May 26, 2015 2:52 AM
> >> To: dev@oodt.apache.org
> >> Subject: Re: OODT book proposal
> >>
> >> Alright chaps this is pretty last minute as I have to chat to the guy
> >>from
> >> Manning tomorrow so if anyone has 5 minutes, can you scan:
> >>
> >>
> >>
> https://docs.google.com/document/d/1dGVf0j25WzXZCyTyuX9aMmmQ06yAPLOFtuTFZ
> >>e-0aXk/edit?usp=sharing
> >> and add anything you think is missing. The link is open to all so you
> >> should be able to add/change entries, just italicise them or something
> >>so I
> >> can spot them.
> >>
> >> Thanks
> >>
> >> Tom
> >>
> >> On Wed, May 20, 2015 at 7:14 PM, Tom Barber 
> >> wrote:
> >>
> >> > Thanks for the feedback guys.
> >> >
> >> > The chat I had with the chap was certainly around a full book as I
> >>have
> >> to
> >> > pitch 9 - 14 chapters. He did say they are trying to move away from
> >> generic
> >> > platform books so I think pitching it in the style of a look at all
> >>the
> >> > main components and heavy on the real world how-to and use cases
> >>would be
> >> > the way I'm tending to go along with a load of stuff on the value of
> >> > metadata etc.
> >> >
> >> > We discussed use case ideas and I went over some of the crazy NASA
> >>stuff
> >> > which he said I should include and also a bunch of real world use
> >> > cases(smart meters/regulatory compliance application and stuff from my
> >> day
> >> > job), but of course, you lot don't live in the real world so you'll
> >>have
> >> to
> >> > leave that to me ;)
> >> >
> >> > On 1.0 I'm sure it will come out during the time we would spend
> >>writing a
> >> > book.
> >> >
> >> > I'll come back with a draft toc tonight or tomorrow and those
> >>interested
> >> > can add their 10 cents.
> >> >
> >> > Tom
> >> > On 20 May 2015 18:26, "Lewis John Mcgibbney"
> >>
> >> > wrote:

Re: OODT book proposal

[Crichton, Daniel J (3902)]

Tom,

Looking at the outline, a few things jump out at me.

1. Architectural concepts behind OODT

OODT was defined by an initial set of architectural principles that I
believe still hold today.  A key one being the separation of the software
components from the information model.  It's my belief that this is why
OODT could be applied to so many different domains.

In addition, there are some key architectural patterns behind OODT but two
very prominent ones:
(1) Information capture, processing, etc - In the early days this was
first implemented by the Palomar Testbed Interferometer and SeaWinds)
which defined the CAS
(2) Data discovery, access, distribution, integration, of highly
distributed, heterogeneous systems - This was defined by projects like
NASA/PDS, NCI/EDRN, etc

Many of the architectural decisions made the foundation of OODT as a data
science ecosystem and have allowed for it to be applied not only to
different domains, but also to allow it to scale and integrate with
different technologies and standards including messaging systems, cloud
infrastructures, different database backends, etc.  In fact, this allowed
NASA to move away from being tightly coupled to a vendor ground data
systems to use OODT an open source processing infrastructure for Earth
Science back in 2003.

It would be good to include this in Part I.  Much of it right now is in
academic papers.

2. Section 5.x - OODT's web grid components are much less about
computation/processing and more about data intensive capabilities of
discovery (e.g., Profile Services) , access, transformation, and
distribution (e.g., Product Services).  I would stress the distributed
deployment of OODT to integrate highly distributed, heterogeneous systems.
 This is how PDS, EDRN, and some other biomedical data networks are using
it.

We've kept Profile/Product and CAS components as separate so I would think
that 5.1, 5.2, 5.3, and 5.6 should move up to section 4 or a new section
should be create to address the information integration aspects with the
web grid pieces moving into it.


3.  Section 10 - EDRN is certainly example of integrating heterogeneous,
distributed systems together but PDS and others can be discussed.  For
EDRN and PDS, it's much less about distributed data entry and much more
focused on how to integrate, transform, and distribute data across highly
distributed systems.

Hope this helps.

Dan

On 5/26/15 7:38 AM, "Tom Barber"  wrote:

>Thanks Chris.
>
>Eva, I think we can probably include that stuff within one of the existing
>tutorial sections as your ideas aren't too crazy ;)
>
>Tom
>
>On Tue, May 26, 2015 at 3:07 PM, Mattmann, Chris A (3980) <
>chris.a.mattm...@jpl.nasa.gov> wrote:
>
>> you have to have a chapter on NASA earth science missions :)
>> I added it..good luck!
>>
>> 
>> From: Tom Barber [tom.bar...@meteorite.bi]
>> Sent: Tuesday, May 26, 2015 2:52 AM
>> To: dev@oodt.apache.org
>> Subject: Re: OODT book proposal
>>
>> Alright chaps this is pretty last minute as I have to chat to the guy
>>from
>> Manning tomorrow so if anyone has 5 minutes, can you scan:
>>
>> 
>>https://docs.google.com/document/d/1dGVf0j25WzXZCyTyuX9aMmmQ06yAPLOFtuTFZ
>>e-0aXk/edit?usp=sharing
>> and add anything you think is missing. The link is open to all so you
>> should be able to add/change entries, just italicise them or something
>>so I
>> can spot them.
>>
>> Thanks
>>
>> Tom
>>
>> On Wed, May 20, 2015 at 7:14 PM, Tom Barber 
>> wrote:
>>
>> > Thanks for the feedback guys.
>> >
>> > The chat I had with the chap was certainly around a full book as I
>>have
>> to
>> > pitch 9 - 14 chapters. He did say they are trying to move away from
>> generic
>> > platform books so I think pitching it in the style of a look at all
>>the
>> > main components and heavy on the real world how-to and use cases
>>would be
>> > the way I'm tending to go along with a load of stuff on the value of
>> > metadata etc.
>> >
>> > We discussed use case ideas and I went over some of the crazy NASA
>>stuff
>> > which he said I should include and also a bunch of real world use
>> > cases(smart meters/regulatory compliance application and stuff from my
>> day
>> > job), but of course, you lot don't live in the real world so you'll
>>have
>> to
>> > leave that to me ;)
>> >
>> > On 1.0 I'm sure it will come out during the time we would spend
>>writing a
>> > book.
>> >
>> > I'll come back with a draft toc tonight or tomorrow and those
>>interested
>> > can add their 10 cents.
>> >
>> > Tom
>> > On 20 May 2015 18:26, "Lewis John Mcgibbney"
>>
>> > wrote:
>> >
>> >> Spoke to Tom White a while ago @ApacheCon about this very topic folks
>> with
>> >> one interesting outcome.
>> >> Many publishers (I don't know about Manning, however Chris will
>>likely
>> >> know) are interested in Microbooks or picket guides as well.
>> >> An example is the following
>> >> http://shop.oreilly.com/product/9780596007430.do
>> >> I don't know if this fi

Re: OODT book proposal

[Tom Barber]

Thanks Chris.

Eva, I think we can probably include that stuff within one of the existing
tutorial sections as your ideas aren't too crazy ;)

Tom

On Tue, May 26, 2015 at 3:07 PM, Mattmann, Chris A (3980) <
chris.a.mattm...@jpl.nasa.gov> wrote:

> you have to have a chapter on NASA earth science missions :)
> I added it..good luck!
>
> 
> From: Tom Barber [tom.bar...@meteorite.bi]
> Sent: Tuesday, May 26, 2015 2:52 AM
> To: dev@oodt.apache.org
> Subject: Re: OODT book proposal
>
> Alright chaps this is pretty last minute as I have to chat to the guy from
> Manning tomorrow so if anyone has 5 minutes, can you scan:
>
> https://docs.google.com/document/d/1dGVf0j25WzXZCyTyuX9aMmmQ06yAPLOFtuTFZe-0aXk/edit?usp=sharing
> and add anything you think is missing. The link is open to all so you
> should be able to add/change entries, just italicise them or something so I
> can spot them.
>
> Thanks
>
> Tom
>
> On Wed, May 20, 2015 at 7:14 PM, Tom Barber 
> wrote:
>
> > Thanks for the feedback guys.
> >
> > The chat I had with the chap was certainly around a full book as I have
> to
> > pitch 9 - 14 chapters. He did say they are trying to move away from
> generic
> > platform books so I think pitching it in the style of a look at all the
> > main components and heavy on the real world how-to and use cases would be
> > the way I'm tending to go along with a load of stuff on the value of
> > metadata etc.
> >
> > We discussed use case ideas and I went over some of the crazy NASA stuff
> > which he said I should include and also a bunch of real world use
> > cases(smart meters/regulatory compliance application and stuff from my
> day
> > job), but of course, you lot don't live in the real world so you'll have
> to
> > leave that to me ;)
> >
> > On 1.0 I'm sure it will come out during the time we would spend writing a
> > book.
> >
> > I'll come back with a draft toc tonight or tomorrow and those interested
> > can add their 10 cents.
> >
> > Tom
> > On 20 May 2015 18:26, "Lewis John Mcgibbney" 
> > wrote:
> >
> >> Spoke to Tom White a while ago @ApacheCon about this very topic folks
> with
> >> one interesting outcome.
> >> Many publishers (I don't know about Manning, however Chris will likely
> >> know) are interested in Microbooks or picket guides as well.
> >> An example is the following
> >> http://shop.oreilly.com/product/9780596007430.do
> >> I don't know if this fits for something like OODT but you guys can
> >> consider.
> >> Lewis
> >>
> >> On Wed, May 20, 2015 at 10:11 AM, Chris Mattmann <
> >> chris.mattm...@gmail.com>
> >> wrote:
> >>
> >> > Thanks Mike. I don’t think 1.0 is required
> >> > *before* writing the book, but can happen
> >> > while the book is going on (and be pushed in
> >> > many cases by the book!) :)
> >> >
> >> > We had the same scenario with Tika in Action.
> >> >
> >> > Cheers,
> >> > Chris
> >> >
> >> > 
> >> > Chris Mattmann
> >> > chris.mattm...@gmail.com
> >> >
> >> >
> >> >
> >> >
> >> > -Original Message-
> >> > From: Michael Starch 
> >> > Reply-To: 
> >> > Date: Wednesday, May 20, 2015 at 10:10 AM
> >> > To: 
> >> > Subject: Re: OODT book proposal
> >> >
> >> > >I am definitely up for this.  Are we going to push for an OODT-1.0
> >> > >"polished" released before we write a book?  There seem to be a lot
> of
> >> > >very
> >> > >nice features in the pipe, which will affect the content of a book.
> >> > >
> >> > >Regardless, I believe the following may be helpful for the book.
> >> > >
> >> > >- Setting Up OODT
> >> > >- Major OODT Components
> >> > >- Extending OODT
> >> > >- OODT in Operations
> >> > >
> >> > >-Michael
> >> > >
> >> > >On Wed, May 20, 2015 at 9:24 AM, Freeborn, Dana J (398G) <
> >> > >dana.j.freeb...@jpl.nasa.gov> wrote:
> >> > >
> >> > >> Hi Tom,
> >> > >>
> >> > >> This is great.  I would be happy to contribute to the book if my
> >> level
> >> > >>of
> >> > >> experience with OODT (which is high) is helpful.  It's not clear to
> >> me
> >> > >>your
> >> > >> focus for the book, so you'll just have to tap me if I can
> >> contribute.
> >> > >> Paul and Chris will know if I do.  Otherwise, I will cheer on your
> >> > >> efforts.  :-)
> >> > >>
> >> > >> Thanks,
> >> > >> Dana
> >> > >>
> >> > >>
> >> > >> From: Tom Barber
> >> > >>mailto:tom.bar...@meteorite.bi>>
> >> > >> Reply-To: "dev@oodt.apache.org" <
> >> > >> dev@oodt.apache.org>
> >> > >> Date: Wednesday, May 20, 2015 2:02 AM
> >> > >> To: "dev@oodt.apache.org"
> >> > >> >> > >> >
> >> > >> Subject: OODT book proposal
> >> > >>
> >> > >> Hi guys,
> >> > >>
> >> > >> I was on the phone to Manning today about an OODT book that me,
> Chris
> >> > >>and
> >> > >> Mike Starch mulled over in Texas.
> >> > >>
> >> > >> I've been tasked with coming up with a TOC as the proposal so I'll
> >> knock
> >> > >> something

RE: OODT book proposal

[Mattmann, Chris A (3980)]

you have to have a chapter on NASA earth science missions :)
I added it..good luck!


From: Tom Barber [tom.bar...@meteorite.bi]
Sent: Tuesday, May 26, 2015 2:52 AM
To: dev@oodt.apache.org
Subject: Re: OODT book proposal

Alright chaps this is pretty last minute as I have to chat to the guy from
Manning tomorrow so if anyone has 5 minutes, can you scan:
https://docs.google.com/document/d/1dGVf0j25WzXZCyTyuX9aMmmQ06yAPLOFtuTFZe-0aXk/edit?usp=sharing
and add anything you think is missing. The link is open to all so you
should be able to add/change entries, just italicise them or something so I
can spot them.

Thanks

Tom

On Wed, May 20, 2015 at 7:14 PM, Tom Barber  wrote:

> Thanks for the feedback guys.
>
> The chat I had with the chap was certainly around a full book as I have to
> pitch 9 - 14 chapters. He did say they are trying to move away from generic
> platform books so I think pitching it in the style of a look at all the
> main components and heavy on the real world how-to and use cases would be
> the way I'm tending to go along with a load of stuff on the value of
> metadata etc.
>
> We discussed use case ideas and I went over some of the crazy NASA stuff
> which he said I should include and also a bunch of real world use
> cases(smart meters/regulatory compliance application and stuff from my day
> job), but of course, you lot don't live in the real world so you'll have to
> leave that to me ;)
>
> On 1.0 I'm sure it will come out during the time we would spend writing a
> book.
>
> I'll come back with a draft toc tonight or tomorrow and those interested
> can add their 10 cents.
>
> Tom
> On 20 May 2015 18:26, "Lewis John Mcgibbney" 
> wrote:
>
>> Spoke to Tom White a while ago @ApacheCon about this very topic folks with
>> one interesting outcome.
>> Many publishers (I don't know about Manning, however Chris will likely
>> know) are interested in Microbooks or picket guides as well.
>> An example is the following
>> http://shop.oreilly.com/product/9780596007430.do
>> I don't know if this fits for something like OODT but you guys can
>> consider.
>> Lewis
>>
>> On Wed, May 20, 2015 at 10:11 AM, Chris Mattmann <
>> chris.mattm...@gmail.com>
>> wrote:
>>
>> > Thanks Mike. I don’t think 1.0 is required
>> > *before* writing the book, but can happen
>> > while the book is going on (and be pushed in
>> > many cases by the book!) :)
>> >
>> > We had the same scenario with Tika in Action.
>> >
>> > Cheers,
>> > Chris
>> >
>> > 
>> > Chris Mattmann
>> > chris.mattm...@gmail.com
>> >
>> >
>> >
>> >
>> > -Original Message-
>> > From: Michael Starch 
>> > Reply-To: 
>> > Date: Wednesday, May 20, 2015 at 10:10 AM
>> > To: 
>> > Subject: Re: OODT book proposal
>> >
>> > >I am definitely up for this.  Are we going to push for an OODT-1.0
>> > >"polished" released before we write a book?  There seem to be a lot of
>> > >very
>> > >nice features in the pipe, which will affect the content of a book.
>> > >
>> > >Regardless, I believe the following may be helpful for the book.
>> > >
>> > >- Setting Up OODT
>> > >- Major OODT Components
>> > >- Extending OODT
>> > >- OODT in Operations
>> > >
>> > >-Michael
>> > >
>> > >On Wed, May 20, 2015 at 9:24 AM, Freeborn, Dana J (398G) <
>> > >dana.j.freeb...@jpl.nasa.gov> wrote:
>> > >
>> > >> Hi Tom,
>> > >>
>> > >> This is great.  I would be happy to contribute to the book if my
>> level
>> > >>of
>> > >> experience with OODT (which is high) is helpful.  It's not clear to
>> me
>> > >>your
>> > >> focus for the book, so you'll just have to tap me if I can
>> contribute.
>> > >> Paul and Chris will know if I do.  Otherwise, I will cheer on your
>> > >> efforts.  :-)
>> > >>
>> > >> Thanks,
>> > >> Dana
>> > >>
>> > >>
>> > >> From: Tom Barber
>> > >>mailto:tom.bar...@meteorite.bi>>
>> > >> Reply-To: "dev@oodt.apache.org" <
>> > >> dev@oodt.apache.org>
>> > >> Date: Wednesday, May 20, 2015 2:02 AM
>> > >> To: "dev@oodt.apache.org"
>> > >>> > >> >
>> > >> Subject: OODT book proposal
>> > >>
>> > >> Hi guys,
>> > >>
>> > >> I was on the phone to Manning today about an OODT book that me, Chris
>> > >>and
>> > >> Mike Starch mulled over in Texas.
>> > >>
>> > >> I've been tasked with coming up with a TOC as the proposal so I'll
>> knock
>> > >> something together and share it later in the week, but on this topic.
>> > >>
>> > >> a) Does anyone have anything they'd especially like to see in an OODT
>> > >>book?
>> > >> b) Does anyone want to help donate some hours writing a bit of the
>> book
>> > >> (won't be any time soon and takes months so don't worry about it,
>> and I
>> > >> wont hold you to it, just looking for interest)
>> > >>
>> > >>
>> > >> Tom
>> > >>
>> > >>
>> >
>> >
>> >
>>
>>
>> --
>> *Lewis*
>>
>

Re: OODT book proposal

[Eva Schlauch]

Hi Tom,

the example I mean is basically what I am trying to build... :-D so my 
version does not exist yet. But I can come up with some documentation 
while building/configuring my oodt (which is what I will do anyways, 
just the extent of the documentation may vary if more people will read it).


My scenario (as it is in my head now):

One server, different work stations: people/processes at remote work 
stations will add data of different kinds to the catalog via some 
interface. then oodt decides what to do with the data, i.e., do some 
postprocessing and visualization etc. Primary data and secondary 
(processed) data should be available via some web interface as well as 
some interaction with the data. Since there is interaction, versioning 
is important. I assume that this may be a model also interesting for 
other applications?? Or more probable, covered already by one of the 
other examples?


Best regards, Eva



Am 26.05.15 um 12:40 schrieb Tom Barber:

Hi Eva

Thanks for the feedback.

Can you just expand a little upon your scenario? I'm happy to include
whatever people think would be useful in the proposal.

Tom

On Tue, May 26, 2015 at 11:04 AM, Eva Schlauch 
wrote:


Hi Tom and all,

I am looking forward to the book, it will be a great help for people like
me :-)

Since I don't know the examples: will there be one that explains an
implementation that gets used by different people (different products) and
gives back a new product like a summary on a web page and provides
extensions for statistics on the new products? (is that a scenario
interesting for more people than only me?)

Best regards, Eva


Am 26.05.15 um 11:52 schrieb Tom Barber:

  Alright chaps this is pretty last minute as I have to chat to the guy from

Manning tomorrow so if anyone has 5 minutes, can you scan:

https://docs.google.com/document/d/1dGVf0j25WzXZCyTyuX9aMmmQ06yAPLOFtuTFZe-0aXk/edit?usp=sharing
and add anything you think is missing. The link is open to all so you
should be able to add/change entries, just italicise them or something so
I
can spot them.

Thanks

Tom

On Wed, May 20, 2015 at 7:14 PM, Tom Barber 
wrote:

  Thanks for the feedback guys.

The chat I had with the chap was certainly around a full book as I have
to
pitch 9 - 14 chapters. He did say they are trying to move away from
generic
platform books so I think pitching it in the style of a look at all the
main components and heavy on the real world how-to and use cases would be
the way I'm tending to go along with a load of stuff on the value of
metadata etc.

We discussed use case ideas and I went over some of the crazy NASA stuff
which he said I should include and also a bunch of real world use
cases(smart meters/regulatory compliance application and stuff from my
day
job), but of course, you lot don't live in the real world so you'll have
to
leave that to me ;)

On 1.0 I'm sure it will come out during the time we would spend writing a
book.

I'll come back with a draft toc tonight or tomorrow and those interested
can add their 10 cents.

Tom
On 20 May 2015 18:26, "Lewis John Mcgibbney" 
wrote:

  Spoke to Tom White a while ago @ApacheCon about this very topic folks

with
one interesting outcome.
Many publishers (I don't know about Manning, however Chris will likely
know) are interested in Microbooks or picket guides as well.
An example is the following
http://shop.oreilly.com/product/9780596007430.do
I don't know if this fits for something like OODT but you guys can
consider.
Lewis

On Wed, May 20, 2015 at 10:11 AM, Chris Mattmann <
chris.mattm...@gmail.com>
wrote:

  Thanks Mike. I don’t think 1.0 is required

*before* writing the book, but can happen
while the book is going on (and be pushed in
many cases by the book!) :)

We had the same scenario with Tika in Action.

Cheers,
Chris


Chris Mattmann
chris.mattm...@gmail.com




-Original Message-
From: Michael Starch 
Reply-To: 
Date: Wednesday, May 20, 2015 at 10:10 AM
To: 
Subject: Re: OODT book proposal

  I am definitely up for this.  Are we going to push for an OODT-1.0

"polished" released before we write a book?  There seem to be a lot of
very
nice features in the pipe, which will affect the content of a book.

Regardless, I believe the following may be helpful for the book.

 - Setting Up OODT
 - Major OODT Components
 - Extending OODT
 - OODT in Operations

-Michael

On Wed, May 20, 2015 at 9:24 AM, Freeborn, Dana J (398G) <
dana.j.freeb...@jpl.nasa.gov> wrote:

  Hi Tom,

This is great.  I would be happy to contribute to the book if my


level

of

experience with OODT (which is high) is helpful.  It's not clear to


me

your

focus for the book, so you'll just have to tap me if I can


contribute.

Paul and Chris will know if I do.  Otherwise, I will cheer on your

efforts.  :-)

Thanks,
Dana


From: Tom Barber
mailto:tom.bar...@meteorite.bi>>
Reply-To: "dev@oodt.apache.org" <
dev@oodt.apache.org

Re: OODT book proposal

[Tom Barber]

Hi Eva

Thanks for the feedback.

Can you just expand a little upon your scenario? I'm happy to include
whatever people think would be useful in the proposal.

Tom

On Tue, May 26, 2015 at 11:04 AM, Eva Schlauch 
wrote:

> Hi Tom and all,
>
> I am looking forward to the book, it will be a great help for people like
> me :-)
>
> Since I don't know the examples: will there be one that explains an
> implementation that gets used by different people (different products) and
> gives back a new product like a summary on a web page and provides
> extensions for statistics on the new products? (is that a scenario
> interesting for more people than only me?)
>
> Best regards, Eva
>
>
> Am 26.05.15 um 11:52 schrieb Tom Barber:
>
>  Alright chaps this is pretty last minute as I have to chat to the guy from
>> Manning tomorrow so if anyone has 5 minutes, can you scan:
>>
>> https://docs.google.com/document/d/1dGVf0j25WzXZCyTyuX9aMmmQ06yAPLOFtuTFZe-0aXk/edit?usp=sharing
>> and add anything you think is missing. The link is open to all so you
>> should be able to add/change entries, just italicise them or something so
>> I
>> can spot them.
>>
>> Thanks
>>
>> Tom
>>
>> On Wed, May 20, 2015 at 7:14 PM, Tom Barber 
>> wrote:
>>
>>  Thanks for the feedback guys.
>>>
>>> The chat I had with the chap was certainly around a full book as I have
>>> to
>>> pitch 9 - 14 chapters. He did say they are trying to move away from
>>> generic
>>> platform books so I think pitching it in the style of a look at all the
>>> main components and heavy on the real world how-to and use cases would be
>>> the way I'm tending to go along with a load of stuff on the value of
>>> metadata etc.
>>>
>>> We discussed use case ideas and I went over some of the crazy NASA stuff
>>> which he said I should include and also a bunch of real world use
>>> cases(smart meters/regulatory compliance application and stuff from my
>>> day
>>> job), but of course, you lot don't live in the real world so you'll have
>>> to
>>> leave that to me ;)
>>>
>>> On 1.0 I'm sure it will come out during the time we would spend writing a
>>> book.
>>>
>>> I'll come back with a draft toc tonight or tomorrow and those interested
>>> can add their 10 cents.
>>>
>>> Tom
>>> On 20 May 2015 18:26, "Lewis John Mcgibbney" 
>>> wrote:
>>>
>>>  Spoke to Tom White a while ago @ApacheCon about this very topic folks
 with
 one interesting outcome.
 Many publishers (I don't know about Manning, however Chris will likely
 know) are interested in Microbooks or picket guides as well.
 An example is the following
 http://shop.oreilly.com/product/9780596007430.do
 I don't know if this fits for something like OODT but you guys can
 consider.
 Lewis

 On Wed, May 20, 2015 at 10:11 AM, Chris Mattmann <
 chris.mattm...@gmail.com>
 wrote:

  Thanks Mike. I don’t think 1.0 is required
> *before* writing the book, but can happen
> while the book is going on (and be pushed in
> many cases by the book!) :)
>
> We had the same scenario with Tika in Action.
>
> Cheers,
> Chris
>
> 
> Chris Mattmann
> chris.mattm...@gmail.com
>
>
>
>
> -Original Message-
> From: Michael Starch 
> Reply-To: 
> Date: Wednesday, May 20, 2015 at 10:10 AM
> To: 
> Subject: Re: OODT book proposal
>
>  I am definitely up for this.  Are we going to push for an OODT-1.0
>> "polished" released before we write a book?  There seem to be a lot of
>> very
>> nice features in the pipe, which will affect the content of a book.
>>
>> Regardless, I believe the following may be helpful for the book.
>>
>> - Setting Up OODT
>> - Major OODT Components
>> - Extending OODT
>> - OODT in Operations
>>
>> -Michael
>>
>> On Wed, May 20, 2015 at 9:24 AM, Freeborn, Dana J (398G) <
>> dana.j.freeb...@jpl.nasa.gov> wrote:
>>
>>  Hi Tom,
>>>
>>> This is great.  I would be happy to contribute to the book if my
>>>
>> level

> of
>>> experience with OODT (which is high) is helpful.  It's not clear to
>>>
>> me

> your
>>> focus for the book, so you'll just have to tap me if I can
>>>
>> contribute.

> Paul and Chris will know if I do.  Otherwise, I will cheer on your
>>> efforts.  :-)
>>>
>>> Thanks,
>>> Dana
>>>
>>>
>>> From: Tom Barber
>>> mailto:tom.bar...@meteorite.bi>>
>>> Reply-To: "dev@oodt.apache.org" <
>>> dev@oodt.apache.org>
>>> Date: Wednesday, May 20, 2015 2:02 AM
>>> To: "dev@oodt.apache.org"
>>> >> >
>>> Subject: OODT book proposal
>>>
>>> Hi guys,
>>>
>>> I was on the phone to Manning today about an OODT book that me, Chris
>>

Re: OODT book proposal

[Eva Schlauch]

Hi Tom and all,

I am looking forward to the book, it will be a great help for people 
like me :-)


Since I don't know the examples: will there be one that explains an 
implementation that gets used by different people (different products) 
and gives back a new product like a summary on a web page and provides 
extensions for statistics on the new products? (is that a scenario 
interesting for more people than only me?)


Best regards, Eva


Am 26.05.15 um 11:52 schrieb Tom Barber:

Alright chaps this is pretty last minute as I have to chat to the guy from
Manning tomorrow so if anyone has 5 minutes, can you scan:
https://docs.google.com/document/d/1dGVf0j25WzXZCyTyuX9aMmmQ06yAPLOFtuTFZe-0aXk/edit?usp=sharing
and add anything you think is missing. The link is open to all so you
should be able to add/change entries, just italicise them or something so I
can spot them.

Thanks

Tom

On Wed, May 20, 2015 at 7:14 PM, Tom Barber  wrote:


Thanks for the feedback guys.

The chat I had with the chap was certainly around a full book as I have to
pitch 9 - 14 chapters. He did say they are trying to move away from generic
platform books so I think pitching it in the style of a look at all the
main components and heavy on the real world how-to and use cases would be
the way I'm tending to go along with a load of stuff on the value of
metadata etc.

We discussed use case ideas and I went over some of the crazy NASA stuff
which he said I should include and also a bunch of real world use
cases(smart meters/regulatory compliance application and stuff from my day
job), but of course, you lot don't live in the real world so you'll have to
leave that to me ;)

On 1.0 I'm sure it will come out during the time we would spend writing a
book.

I'll come back with a draft toc tonight or tomorrow and those interested
can add their 10 cents.

Tom
On 20 May 2015 18:26, "Lewis John Mcgibbney" 
wrote:


Spoke to Tom White a while ago @ApacheCon about this very topic folks with
one interesting outcome.
Many publishers (I don't know about Manning, however Chris will likely
know) are interested in Microbooks or picket guides as well.
An example is the following
http://shop.oreilly.com/product/9780596007430.do
I don't know if this fits for something like OODT but you guys can
consider.
Lewis

On Wed, May 20, 2015 at 10:11 AM, Chris Mattmann <
chris.mattm...@gmail.com>
wrote:


Thanks Mike. I don’t think 1.0 is required
*before* writing the book, but can happen
while the book is going on (and be pushed in
many cases by the book!) :)

We had the same scenario with Tika in Action.

Cheers,
Chris


Chris Mattmann
chris.mattm...@gmail.com




-Original Message-
From: Michael Starch 
Reply-To: 
Date: Wednesday, May 20, 2015 at 10:10 AM
To: 
Subject: Re: OODT book proposal


I am definitely up for this.  Are we going to push for an OODT-1.0
"polished" released before we write a book?  There seem to be a lot of
very
nice features in the pipe, which will affect the content of a book.

Regardless, I believe the following may be helpful for the book.

- Setting Up OODT
- Major OODT Components
- Extending OODT
- OODT in Operations

-Michael

On Wed, May 20, 2015 at 9:24 AM, Freeborn, Dana J (398G) <
dana.j.freeb...@jpl.nasa.gov> wrote:


Hi Tom,

This is great.  I would be happy to contribute to the book if my

level

of
experience with OODT (which is high) is helpful.  It's not clear to

me

your
focus for the book, so you'll just have to tap me if I can

contribute.

Paul and Chris will know if I do.  Otherwise, I will cheer on your
efforts.  :-)

Thanks,
Dana


From: Tom Barber
mailto:tom.bar...@meteorite.bi>>
Reply-To: "dev@oodt.apache.org" <
dev@oodt.apache.org>
Date: Wednesday, May 20, 2015 2:02 AM
To: "dev@oodt.apache.org"
mailto:dev@oodt.apache.org>>
Subject: OODT book proposal

Hi guys,

I was on the phone to Manning today about an OODT book that me, Chris
and
Mike Starch mulled over in Texas.

I've been tasked with coming up with a TOC as the proposal so I'll

knock

something together and share it later in the week, but on this topic.

a) Does anyone have anything they'd especially like to see in an OODT
book?
b) Does anyone want to help donate some hours writing a bit of the

book

(won't be any time soon and takes months so don't worry about it,

and I

wont hold you to it, just looking for interest)


Tom







--
*Lewis*



--
Eva Schlauch
MPI f. Radioastronomie
Auf dem Huegel 69
D-53121 Bonn
Phone - 0228 525 254
eschla...@mpifr.de

Re: OODT book proposal

[Tom Barber]

Alright chaps this is pretty last minute as I have to chat to the guy from
Manning tomorrow so if anyone has 5 minutes, can you scan:
https://docs.google.com/document/d/1dGVf0j25WzXZCyTyuX9aMmmQ06yAPLOFtuTFZe-0aXk/edit?usp=sharing
and add anything you think is missing. The link is open to all so you
should be able to add/change entries, just italicise them or something so I
can spot them.

Thanks

Tom

On Wed, May 20, 2015 at 7:14 PM, Tom Barber  wrote:

> Thanks for the feedback guys.
>
> The chat I had with the chap was certainly around a full book as I have to
> pitch 9 - 14 chapters. He did say they are trying to move away from generic
> platform books so I think pitching it in the style of a look at all the
> main components and heavy on the real world how-to and use cases would be
> the way I'm tending to go along with a load of stuff on the value of
> metadata etc.
>
> We discussed use case ideas and I went over some of the crazy NASA stuff
> which he said I should include and also a bunch of real world use
> cases(smart meters/regulatory compliance application and stuff from my day
> job), but of course, you lot don't live in the real world so you'll have to
> leave that to me ;)
>
> On 1.0 I'm sure it will come out during the time we would spend writing a
> book.
>
> I'll come back with a draft toc tonight or tomorrow and those interested
> can add their 10 cents.
>
> Tom
> On 20 May 2015 18:26, "Lewis John Mcgibbney" 
> wrote:
>
>> Spoke to Tom White a while ago @ApacheCon about this very topic folks with
>> one interesting outcome.
>> Many publishers (I don't know about Manning, however Chris will likely
>> know) are interested in Microbooks or picket guides as well.
>> An example is the following
>> http://shop.oreilly.com/product/9780596007430.do
>> I don't know if this fits for something like OODT but you guys can
>> consider.
>> Lewis
>>
>> On Wed, May 20, 2015 at 10:11 AM, Chris Mattmann <
>> chris.mattm...@gmail.com>
>> wrote:
>>
>> > Thanks Mike. I don’t think 1.0 is required
>> > *before* writing the book, but can happen
>> > while the book is going on (and be pushed in
>> > many cases by the book!) :)
>> >
>> > We had the same scenario with Tika in Action.
>> >
>> > Cheers,
>> > Chris
>> >
>> > 
>> > Chris Mattmann
>> > chris.mattm...@gmail.com
>> >
>> >
>> >
>> >
>> > -Original Message-
>> > From: Michael Starch 
>> > Reply-To: 
>> > Date: Wednesday, May 20, 2015 at 10:10 AM
>> > To: 
>> > Subject: Re: OODT book proposal
>> >
>> > >I am definitely up for this.  Are we going to push for an OODT-1.0
>> > >"polished" released before we write a book?  There seem to be a lot of
>> > >very
>> > >nice features in the pipe, which will affect the content of a book.
>> > >
>> > >Regardless, I believe the following may be helpful for the book.
>> > >
>> > >- Setting Up OODT
>> > >- Major OODT Components
>> > >- Extending OODT
>> > >- OODT in Operations
>> > >
>> > >-Michael
>> > >
>> > >On Wed, May 20, 2015 at 9:24 AM, Freeborn, Dana J (398G) <
>> > >dana.j.freeb...@jpl.nasa.gov> wrote:
>> > >
>> > >> Hi Tom,
>> > >>
>> > >> This is great.  I would be happy to contribute to the book if my
>> level
>> > >>of
>> > >> experience with OODT (which is high) is helpful.  It's not clear to
>> me
>> > >>your
>> > >> focus for the book, so you'll just have to tap me if I can
>> contribute.
>> > >> Paul and Chris will know if I do.  Otherwise, I will cheer on your
>> > >> efforts.  :-)
>> > >>
>> > >> Thanks,
>> > >> Dana
>> > >>
>> > >>
>> > >> From: Tom Barber
>> > >>mailto:tom.bar...@meteorite.bi>>
>> > >> Reply-To: "dev@oodt.apache.org" <
>> > >> dev@oodt.apache.org>
>> > >> Date: Wednesday, May 20, 2015 2:02 AM
>> > >> To: "dev@oodt.apache.org"
>> > >>> > >> >
>> > >> Subject: OODT book proposal
>> > >>
>> > >> Hi guys,
>> > >>
>> > >> I was on the phone to Manning today about an OODT book that me, Chris
>> > >>and
>> > >> Mike Starch mulled over in Texas.
>> > >>
>> > >> I've been tasked with coming up with a TOC as the proposal so I'll
>> knock
>> > >> something together and share it later in the week, but on this topic.
>> > >>
>> > >> a) Does anyone have anything they'd especially like to see in an OODT
>> > >>book?
>> > >> b) Does anyone want to help donate some hours writing a bit of the
>> book
>> > >> (won't be any time soon and takes months so don't worry about it,
>> and I
>> > >> wont hold you to it, just looking for interest)
>> > >>
>> > >>
>> > >> Tom
>> > >>
>> > >>
>> >
>> >
>> >
>>
>>
>> --
>> *Lewis*
>>
>