Great Work Keyton

[RichardH]

I usually end up doing imports of spreadsheets on most of my Django
projects. This looks like a very useful generic extraction of that
functionality.
Many thanks.
Richard

[Keyton Weissinger]

Hi Richard!

Thanks for the kind words. As the second member of the google group,
you deserve some kind of prize or something. ;-)

Since I can't think of anything I will ask you this:
- What other features would you like to see?

Here are some I've considered:
- Having the field-to-column matching screen try to auto match looking
for the field_name in each column name.
- Having some wizardless-process where all you do is upload a
spreadsheet and the system knows the model from the name of the
spreadsheet and the field-to-column mapping from the title row. This
way you could have a simple upload-import.

Others?

Keyton

[RichardH]

Having this app is prize enough. Up to now I have had some boiler
plate code for doing spreadsheet imports which has been pasted into
apps that I develop for report creation at work. I had a play with
your app today and its great.
My first suggestion is the same as yours. If a spreadsheet column name
(stripped of spaces and matched case-insensitively) matches a field
name, then have that set in the initial mappings, allowing the user to
change any if required.
The automatic upload also sounds useful. In my tools, I had a
validation function (without database load) which allowed checking of
new data and reported out rows where problems were found.
In one case, I used to "round-trip" data from the database through
spreadsheets and back again, so that users could make data updates
remotely via spreadsheets, but that would involve a "django-
batchexport".
Regards,
Richard

On Jan 9, 12:48 pm, "Keyton Weissinger" <key...@gmail.com> wrote:
> Hi Richard!
>
> Thanks for the kind words. As the second member of the google group,
> you deserve some kind of prize or something. ;-)
>
> Since I can't think of anything I will ask you this:
> - What other features would you like to see?
>
> Here are some I've considered:
> - Having the field-to-column matching screen try to auto match looking
> for the field_name in each column name.
> - Having some wizardless-process where all you do is upload a
> spreadsheet and the system knows the model from the name of the
> spreadsheet and the field-to-column mapping from the title row. This
> way you could have a simple upload-import.
>
> Others?
>
> Keyton
>

[Keyton Weissinger]

(Richard: I've copied you on this note just in case you don't get the
google groups postings as they happen.)

I committed two changes to batchimport you'll want to get:
1. Added the auto column-selection feature we'd discussed.
2. I corrected a potentially fatal flaw where if one model imported
another it looked like the imported model was part of the same app and
would bomb. It's fixed now.

Keyton

[RichardH]

Thanks for the enhancement and the fix. I will do more with the app
over the next week and let you have further feedback.
Richard

On Jan 10, 3:43 pm, "Keyton Weissinger" <key...@gmail.com> wrote:
> (Richard: I've copied you on this note just in case you don't get the
> google groups postings as they happen.)
>
> I committed two changes to batchimport you'll want to get:
> 1. Added the auto column-selection feature we'd discussed.
> 2. I corrected a potentially fatal flaw where if one model imported
> another it looked like the imported model was part of the same app and
> would bomb. It's fixed now.
>
> Keyton
>