05-26-2018, 04:18 AM
@Mike
I suppose it really all depends on whether there is a legitimate reason for someone to have unrecognized column headers in the file; If there is no reason then, to my mind, the user should be warned as they probably need to edit the file (easier for them to cancel the load instead of trying to unpick it).
What do you do currently if you detect unrecognized keywords? (I suspect you ignore them - I would if I was programming it!)
Perhaps it would be easiest if you accepted multiple spellings for the field headers e.g. match the first 4 letters (say, assuming unique in 4) rather than the whole header. This would cater for simple misspellings like whether or not there should be a trailing 's'. Obviously, this wouldn't cater for errors in the first 4 chars so a prompt might still be necessary.
I think the main problem is that the load is going to add a lot of entries to the database so one would rather it not happen if it isn't going to have the desired effect. Additionally, this is likely to be something that users do only occasionally (unlike loading individual songs) so they are more likely to make mistakes, especially on their first attempts.
Another possibility, and perhaps it is there already, would be a method to remove a physical file and all the database entries that relate to it; this would make it relatively easy to unpick a faulty load of a CSV file (as opposed to trying to remove all the individual data records which then results in the physical file being deleted)
Not a show stopper for me, just trying to help you improve an already great program
Cheers
Geoff
I suppose it really all depends on whether there is a legitimate reason for someone to have unrecognized column headers in the file; If there is no reason then, to my mind, the user should be warned as they probably need to edit the file (easier for them to cancel the load instead of trying to unpick it).
What do you do currently if you detect unrecognized keywords? (I suspect you ignore them - I would if I was programming it!)
Perhaps it would be easiest if you accepted multiple spellings for the field headers e.g. match the first 4 letters (say, assuming unique in 4) rather than the whole header. This would cater for simple misspellings like whether or not there should be a trailing 's'. Obviously, this wouldn't cater for errors in the first 4 chars so a prompt might still be necessary.
I think the main problem is that the load is going to add a lot of entries to the database so one would rather it not happen if it isn't going to have the desired effect. Additionally, this is likely to be something that users do only occasionally (unlike loading individual songs) so they are more likely to make mistakes, especially on their first attempts.
Another possibility, and perhaps it is there already, would be a method to remove a physical file and all the database entries that relate to it; this would make it relatively easy to unpick a faulty load of a CSV file (as opposed to trying to remove all the individual data records which then results in the physical file being deleted)
Not a show stopper for me, just trying to help you improve an already great program
Cheers
Geoff
Samsung Galaxy Tab A6