Hi All,
As a portion of the development for a Ubercart book covering creating dynamic digital products (on the fly created custom products realized as file downloads) I am almost finished with a D6 UC2 bulk importer. This far, I have working bulk imports of:
- bulk import a directory hierarchy into the "files" table; this updates existing files that have moved as well as adds new files
- both export and import, where an export can be loaded into Excel, modified, written back out and imported to realize any changes
- new or existing product nodes of a specific type; each product type uses a separate import routine for support of custom fields
- implemented through Services.module, functionality can be accessed remotely
- import/export supports any taxonomy terms associated with products
- import/export supports custom sku strings for each option of a product with attributes & options
- a single image-cache image for each product, with title and alt strings supported
I've been developing this with a working set of about 400 different products, of two (soon 5) different product types. One product type has 4 options, and the other product type has 3 options, giving me something like 1280 different downloadable product files.
I have two features left to complete this Import/Export module: bulk import/export of the downloadable product files themselves, and bulk import/export of the sell_price modifications associated with each product option.
Considering that product features are not stored in the node itself, I'm thinking that supporting them will be an additional routine after the initial import. As far as I can tell, I see no usable API routine that supports working with product features, so I'll need to hit the database directly. Does this sound correct for how they are structured in the database?
- uc_files is a DB table auto-populated with all the files located inside the "files_path" field of File Download Settings on the admin/store/products/files page
- uc_product_features is a "higher level" DB table that tracks all product features (both file downloads and role assignments),
- uc_file_products is a DB table that tracks all downloadable product files, providing the linkage between uc_product_features and uc_files
My question, after this long prelude, is: are there any other tables I need to modify to support bulk import of file download product features?
Anyone know of previous work in this area I could reference? Seems like supporting attributes is a challenge that stopped most work in this area, before getting to product features...

)