JETSTREAM / News: Recent posts

As you could probably guess by now from emails we have received, the current team members have been very busy with additional workload from our clients. We do have plans to restart some of the work within the next few weeks and hope to have our current codebase released by the end of this week (6/23) as a 1.0 beta.

We have received NUMEROUS emails regarding interest in our project, but only one other individual showed interest in helping us get 1.0 out the door. Please consider doing some development work as you contact us - first, because this is not intended to be a full COTS application replacement - it is intended to be a flexible ETL framework, so some development would be required, - and - secondly, we want this to be a more broadly adopted framework, which means good developer support. Rather than post for a job here, I would rather draw from those people that have interest in the project - i.e. those that come by to see what is happening. We could use a good Java/XML developer to come by and volunteer a few hours of service so we can get 1.0 completed and look to the challenges of the next release.... read more

While everyone patiently awaits the JETSTREAM 1.0 release, the team has released two excerpts to give everyone a flavor of what the 1.0 release will be like. The first is the Table of Contents (we're still working on this, the page numbers aren't right, but it does make for a nice outline. The second is "What Does JETSTREAM Do?" which provides an overview of the features and functionality with this release. Please provide comments/questions back via the open discussion forum.... read more

As we finish up our 1.0 release (which has been for a specific customer), we believe in order to be truly useful to the community we shoudl ask everyone's opinion on how they woudl use JETSTREAM. Please take a few moments and complete our survey on how you would use JETSTREAM and desired features and functionality.

Thanks in advance!
Paul

The development team is close to releasing version 1.0 of JETSTREAM. This release will feature substantial improvements:

- the ability to have an XML document as a data source and a data target as well as a database and to be extensible to new formats
- the ability to pull in multiple data sources to go to one target
- the core use of XSL, while still maintaining an easier to develop XML file for determining the extraction and transformation rules
- still maintains portability through JDBC... read more

The JETSTREAM Team is happy to announce that we have posted the JavaDocs and a User's Guide for the 0.7 release. Additionally, we have posted the specifications to which we are designing for the 1.0 release. We will be posting a few other tidbits for the 0.7 release including our code for the stored procedure and example XML and properties files. This will complete the postings for 0.7; our full focus is currently on 1.0.... read more

We need a logo! The JETSTREAM team would like to ask for submissions for a logo. The logo should be suitable as a GIF image, but we won't constrain you on size - just realize it must look good at a smaller size. You can enter as many times as you wish.

The logo will be judged on the following criteria:

- how close it represents what the JETSTREAM project and product is about (40%)
- how close it ties in what the JETSTREAM weather phenomena is (10%)
- how easy it is to resize and still look good so that it works for banners and "powered by" icons (30%)
- the overall appeal you have to the JETSTREAM team :-) (20%)... read more

The JETSTREAM team is pleased to announce the availability of JETSTREAM 0.7. This release allows some basic transformations for direct population of a database from another database. For extremely complex transformations, you will need to do these in a staging database (we recommend the excellent hsqldb database also available on SourceForge). User documentation is in works, but will be rudimentary in nature.... read more

The current JETSTREAM team is busily preparing files and documentation for what will be termed release 0.7. This is a fairly stable release (consider it at a transition point between beta and a real release) designed primarily for moving data from one database to another. During this transfer you can do the following:

- convert data from one type to another
- merge string data (when you want to populate one target field with two or more source fields)
- split data (when you want to populate two or more target fields with one source field)
- replace data (when a particular string or substring should really become a different value)
- perform any of these based on a simple condition
- populate a staging database
- support more complex transformations within the staging database
- have an update fallback rule when an insert fails due to a record already being present... read more

This is a note for anyone interested in this project.

We do have code that has already been developed. The current team of us are repackaging everything to be uploaded here. We should have that all done within the next few weeks.

If you have an interest in this project, you can send email to me directly at paul.m.boos@saic.com

Thanks!
Paul