1

Re: Setting up for entry of abundance data (DAFOR etc)

Hi

Can someone please run through how I should set up term lists etc to allow entry of DAFOR or similar data. I have tried to use a screenshot Charles posted a while back as an example, but it doesnt seem to work as I expected so I may have gone wrong somewhere.

Thanks

Gordon

Gordon Barker
Biological Survey Data Manager
National Trust

2

Re: Setting up for entry of abundance data (DAFOR etc)

Where's the screenshot?

Charles Roper
Digital Development Manager | Field Studies Council
http://www.field-studies-council.org | https://twitter.com/charlesroper | https://twitter.com/fsc_digital

3

Re: Setting up for entry of abundance data (DAFOR etc)

Charles

- linked from this discussion. http://forums.nbn.org.uk/viewtopic.php?id=204 , just an example really. I also used the information in the help file.

Attempting to import a spreadsheet with lots of d's and f's afterwards produced unexpected data (everything with a 1 instead of a DAFOR letter) so it might be the matching in the wizard that went wrong.

G

Gordon Barker
Biological Survey Data Manager
National Trust

4

Re: Setting up for entry of abundance data (DAFOR etc)

Ah, OK. If you've setup the DAFOR measurement as I have in that screenshot - as Coverage of Taxon (DAFOR) in other words - then all you need to is:

* Have a seperate DAFOR column in your import spreadsheet containing just the DAFOR letter.

* When in the import wizard at the column matching stage, click the drop-down above the DAFOR column and select <more options>.

* Scroll nearly to the bottom and expand the Taxon Occurrence Data node

* Find Coverage of Taxon (DAFOR) (see screenshot)

That should import your DAFOR measurements successfully.

Charles Roper
Digital Development Manager | Field Studies Council
http://www.field-studies-council.org | https://twitter.com/charlesroper | https://twitter.com/fsc_digital

5

Re: Setting up for entry of abundance data (DAFOR etc)

Hi Dan,

A simple but effective approach would be to expand the term list content included with the Recorder installation in the UK, and to include the new terms in the upgrade. It would be possible to perform auto-reallocation of matching existing terms using the upgrade kit, so someone who already has DAFOR as a measurement will not end up with duplicate terms. Of course if they have written it differently e.g. D.A.F.O.R. then we might not pick it up unless we could predict the different term beforehand.

The disadvantage of this approach is everyone will get the same terms, so it doesn't cater for having terms which are only applicable to certain recording groups but are widely used within those groups. I suppose a simple approach to this issue would be to publish a number of optional import files containing terms applicable to each import group. These import files would not be able to reallocate existing terms though, but would still help to standardise future data.

A third option would be an online "term server" which manages official list content, and with Recorder including capabilities for using this content and reallocating existing data to it. It would obviously be more costly to set up than the other approaches though.

Best Wishes

John van Breda
Biodiverse IT