up vote 11 down vote favorite
4
share [g+] share [fb]

With this question assume the users understand CSV/Excel.

I am looking for the most usable approach for importing data (5-15 rows) into an application.

  1. Is it better to let the users download an Excel/CSV template, populate then upload?

    or

  2. Is it better to let the users upload whatever Excel/CSV they have and allow mapping functionality?

    or

  3. Tell me a better way.

My thoughts are they you usually give the users some-kind of confirmation on what to import, so why not just go ahead with the mapping functionality and kill two birds with one stone?

link|improve this question
100% accept rate
1  
I've never seen #1 before. Great idea. – Patrick McElhaney Aug 18 '10 at 1:22
1  
We use #1 at our company almost exclusively. We combine our imports with exports that follow the same layout. the idea being a user can download their data into an xls, edit it, then re-import it. Works at treat. We also have error checking for mis-matched columns – invalid_arg Aug 19 '10 at 16:42
1  
A related question about interface for mapping the fields, if option #2 is chosen. – James Crook Jun 9 '11 at 16:28
feedback

2 Answers

up vote 8 down vote accepted

You could tell them what columns are expected and have a button to download a blank file for convenience (#1) or let them create / use their own file.

Once the file is uploaded, if the column names don't already match, you could provide the mapping functionality (#2).

An experienced user might already have the file with the right column names and could skip both steps.

link|improve this answer
1  
I like the idea of checking to see if the columns match and then presenting them with an error and a mapping ui when they don't already match. – LoganGoesPlaces Aug 17 '10 at 14:35
1  
Great Answer Patrick – jessegavin Aug 17 '10 at 14:37
1  
Thanks. It's a great question. – Patrick McElhaney Aug 17 '10 at 15:36
It is a really good question. Is there yet a better way to solve this, I wonder? – mg1075 May 21 '11 at 22:56
feedback
up vote 2 down vote

I actually have this exact problem on the app I design. Header mapping never made it into the roadmap so users are forced to fix the headers in Excel. We give them a template, but users still get really annoyed. They often get lists from 3rd party sources and having to do the fixup is a pain.

I wish I had escalated the header-mapping UI a long time ago. I am still trying to get it on the roadmap.

Currently, we give good feedback on the columns that DO match properly and the ones that don't, but it's not ideal.

link|improve this answer
feedback

Your Answer

 
or
required, but never shown
discard

Not the answer you're looking for? Browse other questions tagged or ask your own question.