1

Topic: Not Verified to Passed Veriification

Hi,

All of our records are verified, either by  the original recorder or by county experts before they are put into Recorder 6. However (possibly due to how they have been entered?) the majority are labelled as 'Not verified'. Is there an easy way to change them all from Not verified to Passed Verification? And without making me the Determiner? I don't really fancy having to go through them all one by one to change them manually!

Thanks,
Lizzy

2

Re: Not Verified to Passed Veriification

The Determination Type needs to be changed to something which  results in the verified indicator being set  to passed verification.  If you look in Tools/Term Lists and select determination type you can see what the options are. Look at each determination types and you will see the verification which applies to each one. As far as system supplied determination are concerned only 'Correct' and 'Considered Correct'  result in 'Passed verification', but you might have other user defined ones ?     Changing the determination types on records on records where you are  the Custodian would be simple to do, with a Batch update which I would be happy to do for you, but I would need to know exactly how to identify the records you want changed.  If you want it applied to records where you are not the Custodian, then this is a bit more difficult as it is necessary to create a new determination.

Mike Weideli

3

Re: Not Verified to Passed Veriification

Hi Mike, thanks for your reply. Looking at the Term Lists, we also have an option called Validation which results in 'Passed Verification'. Could the records to be changed be identified using a csv file of the record obs key? I know we've done that in the past. Also, would the batch updates only change the determination type or could it affect other fields? When I try and change it manually it tries to make me the determiner (which is not the case!)

4

Re: Not Verified to Passed Veriification

If you own the record you should  be able to change the  determination type manually without changing the determiner. In edit mode on the record you need to select the determination you want to change then click on the pencil/notebook icon to the right which will allow you to change the Type using the drop down box.  You then need to use the small green tick to save this change, and then click on save to save the record.  If you don't own the record then you do have to add a new determination, which will default to you, but can be changed.

The change can be made using a csv file with the Tocc keys and only the determination type needs to be changed.  This is a bit more complicated than a simple query, so I am not sure when I would have time to do it. I will need the csv file and if possible the  key for the Determination type.

Mike Weideli

5

Re: Not Verified to Passed Veriification

Thanks Mike. What sort of timescale might we be talking? I suppose another way of dealing with this could be to export each survey in turn and then re-import with a determination type column set to 'correct'. That should work shouldn't it?

6

Re: Not Verified to Passed Veriification

I am working on something which will do this amongst other things as part of release 6.24. Should be available i na day or two. You will  need a list of the Taxon_Occurrence_Keys which need changing in a csv file. An excel file from the report Wizard can be used.

Mike Weideli

7

Re: Not Verified to Passed Veriification

While the Batch Update I am working on would do what you require, it is over complicated for your task. I have extracted the relevant  part of it into the attached batch update, This just changes the Determinatio_Type to 'Validation' on the Taxon Occurrences listed in the csv file.  It then brings the verified indiactor in line with this change. The csv file needs just one column named 'TOK' which contains the Taxon_Occurrence_Key.  Other fields can be included and will not affect the process. You could for example generate  a report from the Wizard with the Taxon Occurrence key (rename this to TOK in Excel) and other columns you need for checking. This could the be saved  into Excel and then checked, with the unwanted rows being removed. The final file then needs saving as a csv file. Running the Batch Update  will apply the change to al l Taxon Occurrences listed in the file. Close R6 and install the Batch update by copying the file into the Batch Update folder of R6.  The Batch Update is called 'Update determination based on spreadsheet' and it  is to be found in Batch Updates/LC/Change Determination.  It takes just one parameter which is name of the csv file. Please take a backup before running this and check that the results have been correctly applied.

This could easily be made to work on a whole Survey if this helps or could just work on Determination which are currently  set to 'Observation' or 'Original'.

Post's attachments

LCChangeDeterminer.xml 1.9 kb, 9 downloads since 2015-08-12 

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

8

Re: Not Verified to Passed Veriification

That's brilliant, thanks Mike! I'll give this a go tomorrow.
Thanks again,
Lizzy

9

Re: Not Verified to Passed Veriification

Hi Mike, I've just tried running this on a single record in two different surveys and although it says it has been applied it doesn't seem to have changed anything?

10

Re: Not Verified to Passed Veriification

I have tested it and it does seem to be working. When I have had problems with csv based batch updates it has often turned out to be the format of the csv file. It must be a csv file and not an xls file and its needs the Taxon_Occurrence_Key under a heading TOK. Other columns are Ok and will be ignored.  I attach a sample of a file.  If R6 is displaying  the record when the update is run, it doesn't change on the screen until you close and open the record again.

Post's attachments

DeterminationChange.csv 29 b, 2 downloads since 2015-08-21 

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

11

Re: Not Verified to Passed Veriification

It seems it only works for me if I do remove all of the other columns from the csv file, but it is actually working. Many thanks!

12

Re: Not Verified to Passed Veriification

Probably one or more of the columns isn't acceptable in some way, but as it works probably not worth investigating.

Mike Weideli