The BMS Fungal Records Database (BMSFRD)
The following pages introduce the BMSFRD table structure and provide guidance to those wishing to submit records for inclusion. For those ambitious enough to want to build their own recording database, advice on the required structure, syntax and content is given.
One of the prime reasons for collecting records in the BMSFRD is to allow subsequent interrogation on a range of themes that include species distribution, frequency, and time of appearance, host association and site lists. Unless records are entered into the database in a consistent format and style it is difficult to extract all the useful information.
The current BMSFRD table structure together with rules and recommendations for use is given below. This structure has been enhanced since the database first appeared, and may well be subject to further enhancements, but these are unlikely to radically alter it or the data it contains. Some of the field formats that are specified below have been the subject of discussion and may not suit all recorders. If you wish to vary these, then you must be aware of the need to convert records when submitting them to the BMSFRD.
It is strongly recommended that new records should include as an absolute minimum the fungus name, date, identifier, locality and grid reference. Anything less than this considerably diminishes the value of the record. For historic records it is recognised that this detail may not always be available but for modern records there is really no reason why it should not be supplied. From time to time, records are submitted to the BMSFRD with the fungus name limited to just the genus, e.g. Mycena sp. Unless the record is supported by references to voucher ‘herbarium’ material and/or a good description and/or illustrations (photographs or paintings) so that a subsequent identification may be possible, then its value will be limited and in some circumstances it may not be added to the database.
Note that Field Numbers entered in the explanatory table below are for convenience of reference in the event of queries. They have no other significance and are not used in database entries. A few fields are for use by the Database Managers only. Where this applies the field numbers are entered in bold in the table.
Field Field name number
Accepted Associated Organism
Ecosystem NCC Ecosystem code
Altitude (m) Day
Current Name will be inserted/corrected by the Database Manager Enter A for anamorph, T for teleomorph, H for holomorph or for spore stages of rusts: 0,I,II,III or IV as recorded – preferably a Latin name. Do not use ‘sp.’ as in ‘Quercus sp.’ – just enter ‘Quercus’. Separate two or more associations with ‘ / ’; primary association first edited version – primary association used on web site for speed of access the substrate on which the fungus was recorded - use lower case throughout see Appendix 3 - use lower case throughout see Appendix 3
if unknown leave blank – do not use ‘0’ as this indicates sea level! in form 01, 02, etc. or - for not recorded