1 (edited by atheta01 24-11-2012 21:15:52)

Topic: Changing determinations to Preferred Checklist taxa

I have records in Recorder 6 which were entered long ago using the Recorder 3 list: example Atheta pertyi which is now Atheta aenicollis in the Preferred Coleoptera List. When I want to produce species maps in DMAP or an entry in my county Coleoptera list (using a bespoke Access routine) I find I get maps for both taxa and entries for both taxa in the county list, because the species have different Sort Order numbers. There are many other examples of this. I can achieve a correction by going into each A. pertyi record and changing the determination to the taxon A. aenicollis from the Preferred Checklist. This is OK if there are only a few records to deal with, but can get very tedious with many records. Is there a batch update that will deal with this?

In Tools>Run Batch Updates there are 4 items (Det 1, Det2, Det 4 and Det 5). Will one of these perform the task that I need here? The reason I ask this without trying them is that if something goes wrong it takes about 48 hours minimum to get a database restore via our IT system.

Any comments on this would be appreciated....

Since writing this post I have tried to run the Batch Update "Determination Updates > Det 1 Creates new Determination for specified taxa" on a standalone R6 installation. I enter the "old" taxon and the "new" taxon. When trying to run the Batch Update I get an error message which reads "The following error occurred while attempting to run the batch update SQL: Must declare the scalar variable "@New_TLI_Key"" What does this mean and does the batch update work properly?

Bob Marsh
Doncaster LRC
Coleoptera recorder for YNU

2

Re: Changing determinations to Preferred Checklist taxa

Det2 looks like the best bet for you.  The version in R6 isn't working, but a new version is attached. I have tested it and it looks Ok. If you want to test it yourself create a taxon occurrence for a taxon you never use, then run the update to change it to something else. You can delete it afterwards.  Having, said that do make sure you have backup and check that the results look Ok.  Batch Update Det1 may also be OK, but test it first. It may be better for you as it doesn't require so many parameters.

Post's attachments

JNCCDet2Determinations.xml 5.19 kb, 1 downloads since 2012-11-25 

You don't have the permssions to download the attachments of this post.
Mike Weideli

3

Re: Changing determinations to Preferred Checklist taxa

Sorry Mike but where's the attachment?

Bob Marsh
Doncaster LRC
Coleoptera recorder for YNU

4

Re: Changing determinations to Preferred Checklist taxa

Sorry added in above. I have also noticed that Det1 doesn't work. I would anyway be a little concerned about Det1 for use in the situation you describe, because if works on all taxa whcih have the  preferred key. I am fixing Det1 and doing a new update Det3 which may be more suitable for your needs. Det3 is is attached. I have tested it and it seems Ok, but do make sure that you have a backup just in case I have missed something. It will definitey only affect the taxon selected and the date changed will be updated so it should be possible to back track if there any issues.

Post's attachments

JNCCDet3Determinations.xml 3.26 kb, 4 downloads since 2012-11-25 

You don't have the permssions to download the attachments of this post.
Mike Weideli

5

Re: Changing determinations to Preferred Checklist taxa

Many thanks for that Mike - looks like the Det 3 has done what I wanted. With the 2 species Atheta pertyi and A. aeneicollis, looks like all pertyi records are now referred to aeneicollis; updating and running DMAP and the county checklist routines after running Det 3 on the database shows that the A. pertyi map has gone and all the pertyi records appear as aeneicollis on the map and in the county checklist.

Bob Marsh
Doncaster LRC
Coleoptera recorder for YNU