asp.net Import Data Techniques - Best Practice
Posted on 2009-07-01
I'm on the precipice of a pretty important design consideration and thought I'd ask some advice. I am designing a web application that will contain a table that holds "people". The users of my site will want their site to be filled with their people. The hard way to do this is to give them an interface on my site that allows them to view, add, edit, delete - all things I will likely do.
But, the "easy" way (at least from a customer's perspective) is to give them an importing tool. I have seen many ways of doing this over the years, and could likely figure each one out. But here are my assumptions about my design:
1. Not all people have Excel, making a software-dependent upload tool a bad idea
2. Comma-separation is pretty good, but not if the data has commas in it and the user doesn't properly plan for this
3. XML is nice and structured, but is there an easy way for non-tech types to get data into my schema?
What I would like is this approach: A user wants a list of 10,000 people in their company to be available on my web site. They go to their HR and get that list in *SOME FORMAT*. They bring that file to my website and upload it. My program inspects the file and reports back anything bad that might happen before committing the changes. The user accepts/rejects, and the data is synchronized.
Where I'm really getting hung up is the SOME FORMAT part. I realize that a web interface may not be the only way to get this done (i.e. the user could stick it on an FTP site and I could consume from there), but let's assume I want that method. Can someone point me in the right direction. I'd really like some simple examples of schema or approaches that have worked well for others.