Identifying changed records

[davidnicholls125]

What is the best way of identifying records that have been changed after the initial verification? I've looked at the elasticsearch record download and can't immediately see how we would find these changes. In particular we want to know if there has been a redet and/or a change to the verification status.

[johnvanbreda]

The details pages for a record show a log that includes redetermination and status change history, but unfortunately we don't currently store this information in Elasticsearch. We could perhaps write a special report to extract the raw data for you though - e.g. a log of record ID, status changed to, taxon changed to, date, by whom. Would that help?

[davidnicholls125]

Thanks John, yes that sounds a good idea. Kirsty at the Records Centre mentioned she could get details of such changes from her iRecord download so maybe that isn't an elasticsearch report?

[johnvanbreda]

Here's a download tool. Note that this includes a log of all prior identifications for each record that has been changed - it does not contain the current determination of a record- that has to be obtained from the record itself.

[davidnicholls125]

Thanks. Should there be a link to the tool?

[johnvanbreda]

Sorry - https://www.naturespot.org.uk/determinations/download

[davidnicholls125]

Thanks John but I don't think this is going to help at all as it is. We need more details of what has changed and when. We are trying to identify which records have changed after we sent to dataset to the Records Office at the year end. Any changes within a calendar year can be ignored as the year end dataset would have used the amended record anyway. I think the fields we need are listed below.
Record ID
Current determination
Date of current determination
Previous determination
Date of previous determination
Current verification status
Date of current verification
Previous verification status
Date of previous verification
Looking at a few examples, some appear to have been redetermined at exactly the same time as the original determination! How can this be?

[johnvanbreda]

For redeterminations before a code change in 2018, we don't have enough information in the database to correctly determine the date the current determination was made. I have changed the report to make it clear the date is unknown, but you can assume it will be aligned with a comment like "The record's verification status needs to be rechecked as it has been edited" so if there is only one, that will be the correct date. This isn't a problem for newer data.

I've updated the determinations download to your required field list. It's quite a complex report now so a bit slow, but should work OK. Note that it has the same problem with current determination dates for old data, but I've put in a list of the possible dates based on the comment data.

Please close if you are happy with the new report output.