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 <[email protected]>
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 <[email protected]>
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" <[email protected]>
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 <
[email protected]>
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
[email protected]
-----Original Message-----
From: Michael Starch <[email protected]>
Reply-To: <[email protected]>
Date: Wednesday, May 20, 2015 at 10:10 AM
To: <[email protected]>
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) <
[email protected]> 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
<[email protected]<mailto:[email protected]>>
Reply-To: "[email protected]<mailto:[email protected]>" <
[email protected]<mailto:[email protected]>>
Date: Wednesday, May 20, 2015 2:02 AM
To: "[email protected]<mailto:[email protected]>"
<[email protected]
<mailto:[email protected]>>
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
[email protected]
--
Eva Schlauch
MPI f. Radioastronomie
Auf dem Huegel 69
D-53121 Bonn
Phone - 0228 525 254
[email protected]
