You are not logged in.
Announcement
#1 2010-08-05 13:45:38
- Paul Leonard
- Member
- Registered: 2010-01-22
- Posts: 9
Recorder import wizard - another problem!?
When importing bird records using BTO two-letter species codes, Recorder somehow 'loses' the single letter codes for Blackbird ('B') and Dunnock ('D'), highlighting these records in red as containing errors that must be be fixed. When checked, the species field in these records is blank and the codes have to be typed in manually to progress the import. This is an intermittent problem - sometimes its Blackbird records, sometimes Dunnock - but never both. Neither does it seem to happen with Robin records (BTO code 'R').
Any ideas why this happens and how to avoid it?
Cheers,
Paul
Rotherham MBC
Biological Records Centre
Offline
#2 2010-08-09 06:18:37
- MikeWeideli
- Administrator
- From: Littlefield Consultancy
- Registered: 2006-07-05
- Posts: 529
- Website
Re: Recorder import wizard - another problem!?
I have tried to duplicate this problem in 6.14, 1.202 but can't. Which version or Recorder are you using ? Also what format is the import file in (ie Excel, Access) ?.
Mike
Mike Weideli
JNCC Recorder Approved Expert
Offline
#3 2010-08-09 11:18:21
- Paul Leonard
- Member
- Registered: 2010-01-22
- Posts: 9
Re: Recorder import wizard - another problem!?
Hi Mike,
Thanks for your response. I am importing via Excel spreadsheets into R6 v 6.14.4.212. When the import gets to the column matching stage, these records are highlighted as containing errors and their species name fields are blank! To get around it I either have to cancel the import and change the relevant records to either the full English or taxonomic name in the spreadsheet and re-import, or manually re-enter the name or species code for each record at the column matching stage. As I said, its not consistent, nor is it predictable - sometimes its Dunnock, sometimes Blackbird, but never both!?
Cheers,
Paul
Rotherham MBC
Biological Records Centre
Offline
#4 2010-08-15 15:18:35
- MikeWeideli
- Administrator
- From: Littlefield Consultancy
- Registered: 2006-07-05
- Posts: 529
- Website
Re: Recorder import wizard - another problem!?
Paul
The import Wizard doesn't like the code in an EXCEL column being the same as the column. So having B in Excel column B or D in Excel column D causes the problem you are experiencing. This could also possibly account for other single letter problems with other columns such as Measurement . I have no idea why this should be.
A temporary fix is either to save the excel file as a csv file and import that, which seem to fix the problem. Or you can open Excel and create a new column A, copy the species column into this and then delete the original species column. From the internet it doesn't look like the letter A is a BTO two letter code so this will fix the problem.
The issue will be added to the Recorder bug list.
Mike
Mike Weideli
JNCC Recorder Approved Expert
Offline
#5 2010-09-02 13:32:07
- Paul Leonard
- Member
- Registered: 2010-01-22
- Posts: 9
Re: Recorder import wizard - another problem!?
Thanks Mike, however, the reason that you give does not appear to be correct in this case! I have issued all of my regularly contributing naturalists with an identical Excel spreadsheet and the species name column is column A, which shouldn't cause any conflict with the BTO codes for Dunnock (D) or Blackbird (B). I'll try your suggestion of importing as csv files and see how I go with that for the time being.
On a similar subject, I have also found that when importing datasets including records of Lesser Redpoll (BTO code LR) they are sometimes - not always - 'read' and imported as Little Ringed Plover (LP)! Another bit of strange R6 behaviour that I can't fathom. Has anyone else reported this problem??
Many thanks,
Paul
Rotherham MBC
Biological Records Centre
Offline