1

Re: Data exchange with another Recorder user

We are working towards exchanging data with another user of Recorder 6. The data exchange will mostly be one-way (we will be receiving their data, but they don't need ours.)

We are expecting there to be a large amount of overlap in the lists of recorders and I am rather concerned that this will lead to a lot of work, merging individuals when the data reaches our system (in many cases it will be clear that the individual on our system is the same as on theirs, but not always). Obviously it is not enough to do it just on our system as subsequent data exchanges will simply reintroduce the duplication. So I am looking for a way that we can harmonise our INDIVIDUAL (and ORGANISATION and NAME tables with theirs.

I was just wondering if anyone else had tackled this problem before and come up with a protocol?

Would it be possible, after import of the original dataset to resolve duplicated recorders (in so far as this is possible) and then re-export all the records to their system, so that the names on their system are replaced by ours?

Rob Large
Wildlife Sites Officer
Wiltshire & Swindon Biological Records Centre

2

Re: Data exchange with another Recorder user

Would the other Recorder 6 user be prepared to do at least some of the merging for you? If you used a rucksack to export recorders to them without observations they could import that and do the merging, although it would probably be worth trying to restrict the export to just the recorders they need. This would mean that when they export data to you, you would only get their recorders when they haven’t been able to merge them with one of yours. The same applies with locations. A single rucksack can be used to export multiple locations, people and documents. In an ideal world, record centres would use this mechanism to give their contributors the locations, people and documents they need before they started entering their data.

I think what you are proposing would work but it would be worth testing for unforeseen problems. The trouble is it would leave the other Recorder 6 user with the job of deleting their version of the recorders. If they didn’t do this there is always a chance that their version would be used when entering new observations which would mean them reappearing in your system when the new observations were exported to you. In the case of merging locations, it is worth removing as many attributes as possible from the one you are going to get rid of before doing the merge otherwise they get added to the one you are keeping.

Sally Rankin, JNCC Recorder Approved Expert
E-mail: s.rankin@btinternet.com
Telephone: 01491 578633
Mobile: 07941 207687