Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Correct BBS data with wrong vice-county (database location ID lookup) #1758

Open
sacrevert opened this issue Nov 5, 2024 · 4 comments
Open
Assignees

Comments

@sacrevert
Copy link
Collaborator

Due to a configuration error with the 'Bryophytes (BBS)' survey type, some records were imported matching a supplied vice-number to the "vice-county database location ID" field. This has created some nonsense vice-county values held against some bryophyte records (I'm not sure of the exact field name, as a download puts them in a column named "Vice county2", presumably because of multiple columns having the same name.)

For the attached records, can we do two things please:

  1. Delete values in the "Vice county2" (== vice-county from database location ID) for these records
  2. Copy correct values from VC number to the (currently empty) Vice county (supplied) field
    Bryophyte records with vice county information given.csv
@johnvanbreda
Copy link
Collaborator

@sacrevert I've had a look at a few example records (e.g. https://irecord.org.uk/record-details?occurrence_id=38912241) but they seem to be stored correctly. Also in the download on iRecord the data looked OK. Where are you getting the download from that shows these problems?

@sacrevert
Copy link
Collaborator Author

@robin-hutchinson supplied it. Can you shed light Robin please?

@robin-hutchinson
Copy link
Collaborator

I'm getting the download from iRecord but I'm using the single survey download option?

@sacrevert
Copy link
Collaborator Author

@johnvanbreda I suppose there must be some incorrect values stored somewhere in the "vice-county from database location ID" field if they were loaded to it and available by a least one download route. Rather than replace them (that seems unnecessary given that the correct information is apparently in the correct fields elsewhere), perhaps we can just clear that field for the records attached here?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants