Re: You can save your matches to a temporary database using the Commit....
Well after 3 days of importing on one small file and jumping through many hoops it looked like I had to restart Recorder to continue. I cancelled the the import believing that the matches I made would be remembered. THEY WERE NOT.
When I get to the match species page of the import process all entries are EMPTY. I checked the appropriate table in the database and indeed it is populated. I guess that the 'remembered' in this instance means forgotten.
Ahh not so I hear you say, well actually pretty well YES. If I do a search using my primary source dictionary from the first time around it then Identifies those which I found manually [yes including the ones it should have found automatically but could not be bothered too] it does indeed mark those I manually had to find BUT only from that dictionary.
The implication is that I should have made a precise note of all the dictionaries [I still think an Otter is an Otter which ever dictionary is in R6] I used the first time around and go through them one at a time.
So this to me is NOT remembering. Why does it tell me it will remember then?
I wonder can I create the tony_price dictionary and put all the names in it? Then all this silliness will go away. I say silliness as when I get a record it does not tell me what source/checklist/R6 dictionary was used to identify the species, so why do I need to falsely say which was probably not the one used. It seems to take up a lot of time to place it against some checklist that might have been used thereby falsely attributing information about taxa.
Somerset Environmental Records Centre