Re: Comment on module name Data::ETL

On 05/04/2016 09:27 AM, Smylers wrote: Robert Wohlfarth writes: I'm weighing 3 ideas... 2. Create a top-level namespace for ETL. Idea 2 looks like so... * ETL * ETL::Extract * ETL::Extract::Excel * ETL::Extract::DelimitedText * ETL::Extract::XML * ETL::Load * ETL::Load::MSAccess Not

Re: Comment on module name Data::ETL

ETL::$Brand - That's an excellent idea! -- Robert W. On Wed, May 4, 2016 at 12:15 PM Jed Lund wrote: > I would second the ETL::$Brand suggestion. There isn't necessarily a > consensus on how ETL should be done even outside the perl community. I > also think

Re: Comment on module name Data::ETL

I would second the ETL::$Brand suggestion. There isn't necessarily a consensus on how ETL should be done even outside the perl community. I also think ETL::$Brand honors the perl TIMTOWDI culture and that allows for multiple ETL styles with overlapping function. Jed On Wed, May 4, 2016 at 6:27

Re: Comment on module name Data::ETL

Robert Wohlfarth writes: > I'm weighing 3 ideas... > 2. Create a top-level namespace for ETL. > > Idea 2 looks like so... > * ETL > * ETL::Extract > * ETL::Extract::Excel > * ETL::Extract::DelimitedText > * ETL::Extract::XML > * ETL::Load > * ETL::Load::MSAccess Not necessarily. That would be

Re: Comment on module name Data::ETL

Hi, I noticed that your ETL modules are not designed to use a dimensional model (facts and dimensions), so it may be better to have your own namespace instead of using DataWarehouse namespace. Since it is more generic than a DataWarehouse, I would say Data::ETL is a reasonable option. In fact,

Re: Comment on module name Data::ETL

This is all very helpful. I'm weighing 3 ideas... 1. Take Nelson up on his offer and name it something like Datawarehouse::ETL::Script. 2. Create a top-level namespace for ETL. 3. Make a new namespace like StructuredDataConverter. Idea 1 ends up with a tree like this... *

Re: Comment on module name Data::ETL

I don't know what the general feeling is but I've always felt that there should be an ETL Top level module namespace. ( if you don't count practical extraction and reporting language :) The issue is, there doesn't appear to be very good community consensus on best practices for ETL behavior or

Re: Comment on module name Data::ETL

I'm the maintainer of the DataWarehouse::* modules. Let me know if you would like to use the DataWarehouse::ETL namespace. On Tue, May 3, 2016 at 10:36 AM, Smylers wrote: > Robert Wohlfarth writes: > > > I am looking to release a collection of modules for converting

Re: Comment on module name Data::ETL

Robert Wohlfarth writes: > I am looking to release a collection of modules for converting data. > The modules read data from a source, convert the data, then add it > into an SQL database. > > The modules are named like this... > * Data::ETL > * Data::ETL::Extract > * Data::ETL::Extract::Excel >

Comment on module name Data::ETL

I am looking to release a collection of modules for converting data. The modules read data from a source, convert the data, then add it into an SQL database. The modules are named like this... * Data::ETL * Data::ETL::Extract * Data::ETL::Extract::Excel * Data::ETL::Extract::DelimitedText *