Birding Database FAQ
(birding.mdb) Created 10 Jan 2001
Last Edited 21 Jun 2001
by Dr Chan Kai Soon


Clickable Index of topics

Why this database was created?
Reason 1: This database was created because I wanted to learn Microsoft Access and I am a birder. As my professional work involves a lot of data management, it is obvious that I need to learn MS Access. So I chose to practise on something I love to learn the software. Naturally birding becomes the obvious choice. Reason 2: Some people are recording and sending out bird lists and sightings in MS Excel or MS Word format which I feel are not the best softwares to manage data collected from birding trips. I hope to create this database for them so that they may try a better alternative. Reason 3: It takes a lot of MANUAL work to publish sightings in Suara Enggang because reports are not submitted in the preferred format i.e. in Word format with certain fonts size and type for common name, scientific name etc. It is hoped that this database can generate reports in the format required by our Suara Enggang editors. However, please note that this database is an individual, spontaneous effort and I do not represent BCC (Bird Conservation Council of Malaysian Nature Society, the publisher of Suara Enggang) in anyway. Hence any deficiency or errors in the database should not be ascribed to the BCC. Use it at your own risk or pleasure. Reason 4: To computerise bird lists of various birding areas available and to update these lists as and when new data are gathered. Although the data is in Access format, these bird lists can easily be printed or exported to other formats such as MS Word, Excel or html files. Thus keeping data in Access is a wise choice.

Back to FAQ index.



How this database was designed?
The database was designed after understanding the needs of a birder to computerise bird sightings, to effectively retrieve and analyse data collected, and to generate reports suitable for the BCC  publication named Suara Enggang.  Firstly, I browsed through three of my bird books (see reference) and find out how data were presented in them. Then I entered all bird names (common and scientific) available in the pocket checklist. Subsequent species and fields were added based on the other two books, but mainly on Allen J's book. Feedback and comments by some birding gurus, in particular Glenda Noramly and Lim Kim Chye played a great part in the final design of the tables. Based on these, modifications and additions were introduced.

Back to FAQ index.



What would you need to use the database?
As the database is designed in MS Access 97, you need to have compatible softwares. Of course you would also need to have some working knowledge of the software. That's about all you need. This database is public domain property and you are not required to pay for its use. However, I remain the copyright holder and you are not allowed to sell the database design for commercial purposes. In using this database, you agree not to hold me or any other body responsible for any data loss or inaccuracy.

Back to FAQ index.



What are the sources of reference for the bird species?
The data about the species are taken from the following three books:
  1. A Pocket Checklist of The Birds of Peninsular Malaysia and Singapore. Richard Gregory-Smith. Malaysian Nature Society 1996. This book was used mainly to enter the common and scientific names only.
  2. A Field Guide to the Birds of West Malaysia and Singapore. Allen Jeyarajasingam and Alan Pearson. Oxford University Press 1999. This book was used to counter check errors, to add local names and other data such as size, migratory status etc
  3. A Field Guide to the Birds of South-East Asia. Craig Robson. New Holland Publishers 2000. This book was used when data is not available in Allen J's book or as a comparison of naming conventions. Data for some species not found in Allen J's book are taken from this guide.
Please be reminded that this database only helps you to computerize your bird sightings and locate appropriate information in the field guides. It is not meant to replace your field guides.

Back to FAQ index.



Who entered the initial data?
The list of common and scientific names, and migratory status were initially entered into the tables by me. Subsequently local names were added by Lim Swee Yian (Thanks). The database was then passed back to me for additions of other data such as size, family classification and the various ID and plate numbers in the field guides. Believe me, it was a testing time trying to enter all those magic numbers precisely at the correct record and in the correct field. If there is any error, please inform me. To test the database, I had also entered some of my personal sightings and several bird lists which I have.

Back to FAQ index.


What data or bird lists had already been added?

In addition to a few records of my own sightings to test this database, I had also added the following bird lists:

  1. Kinta Valley Former Mining Areas Bird List compiled by Lim Kim Chye/Lim Swee Yian
  2. Kuala Gula Perhilitan Bird List from records of Dept of Wildlife and National Parks Malaysia
  3. Bukit Larut Bird List compiled from records of Choy Wai Mun and T. Guna
  4. Burmese Pool Bird List compiled by Lim Kim Chye/Lim Swee Yian
  5. Kledang Hill Bird List compiled by AL Tan
  6. Fraser Hill Bird List from souvenir book 13th Fraser Hill Bird Race 2000
  7. Sg Relau/Kuala Juram Bird List compiled by MNS (1997-2000)
  8. Sungkai Wildlife Sanctuary Bird Lists (Nov and Dec 2000) compiled by Lim Kim Chye
You can use the appropriate key words in the BirdListQueryArea or BirdListQueryTripName reports to retrieve these lists.

If you have any other bird list or additional species to existing lists which you would like me to add, please email me.

Back to FAQ index.



Do's and Don'ts
Please do not change the design, delete or rename any of the tables and queries. These have to remain as they are for the reports to work. The initial bird sighting reports are based on only *SOME* my own birding trips and so you may want to delete them (in the 'sighting' table only) to save disk space. If you find it essential, you may add tables or reports to customize your own needs. For example, I am thinking of adding a table to store my video recordings.You may distribute this database as public domain stuff.

Back to FAQ index.



How to add bird sightings?
Data are added by using forms. Every new bird sighting would include data for the following fields: Date, *Species name (common), *Trip Name, *Location, *Birder Name and Sighting Notes among others. Fields preceeded by an asterisk (*) are entered from popup lists which ensure uniformity and consistent spelling for table relationships to work. I had elected not to include fields to store time, plumage, vocalization, abundance/rarity and numbers etc to keep the size of the tables down and to make the database simpler but if these data are important, they can be entered in the Sighting Notes field which is a memo field.

There are two forms (SightingsDetailForm and SightingsSimpleForm) available to add your data but you need to use only one of them. The former allows you to view species related data such as size and scientific names during data entry but has a smaller area for SightingNotes. The latter has a larger area for SightingNotes.

Since some of the data are entered from popup lists, you must ensure that the values you are going to enter are already in the appropriate tables before attempting to add sighting records. For example, for Trip Name you must first go to the Trips form to define that particular Trip (for once only). The same principle applies to the Location and Birder Name.

Back to FAQ index.



What type of reports can I retrive?
The database already comes with many reports. You can generate a report suitable for sending your sightings to Suara Enggang (BCCReportByDate). You can create a list of birds seen during a certain birding trip, bird lists for a certain location or state, list of species (with family and scientific names) and lists of birding locations. However, the accuracy of these reports depend on whether you have entered all the sightings (yours and others) into the database. Most of these reports will prompt you for keywords or dates so that you can customize what records or data need to be included. In addition, you can print out single page labels of plates index to Allen J or Robson's bird guides which would allow you to rapidly find the appropriate plates in these books. Of course, you can create other reports for your special needs.

Back to FAQ index.


Notes on the Tables
Table: Species. Stores information about each species.
Table: Family. Store information about family of birds.
Table: Migration. Store popup values about migratory status.
Table: Location: Store information about birding location/destinations. Please note that 'Location' field refers to a more specific place such as 'Fraser Hill, rubbish dump area' whereas 'BirdingArea' field refers to a more general area such as 'Fraser Hill'. Currently, reports mostly makes use of the latter field only.
Table: Birders. Store information about birders.
Table: Trips. Store information about birding trips.
Table: Sightings. This is the table storing the most important data - information about each bird sighting. Each species sighted in a particular trip is stored as one record.
Table: SightingsArchive. This is a mirror table to Sightings. If you have too many sightings records and want to keep the Sightings table small, you can transfer records by cutting records from the 'Sightings' table and pasting it into the 'SightingsArchive'. Records in the archives will not be available for inclusion in any of the reports unless you create new reports specifically to retrieve them.

Back to FAQ index.



Notes on the Queries
The reports make use of queries to filter records to be included. Do not delete any fields in the query. However, you may want to modify the query criteria to suite your taste.

Some of the queries will prompt you for values to be used for filtering the tables. If the value requested is a keyword (character field), you may type in a complete word, part of a word or a phrase depending on how specific you want your filtering to be. If you type nothing and press enter, it is assumed you want to ignore filtering for the particular field. However, if you are prompted to enter a date, you must enter a valid date for the queries to work.

Back to FAQ index.



Notes on the Forms
Forms are used for data entry. You will be working mostly with the sightings forms to record your obervations. After every birding trips, you will need to add definition for that trip into the Trips form (only one entry per trip). The same principle apply for other data such as birder names and location if there are new values for these tables.

Back to FAQ index.



Notes on the Reports
A host of different reports are available. These include bird lists for areas and trips, and reports suitable for sending your sightings to Suara Enggang. The plates number in Allen J and Robson's book can be printed out as single A4-page report which can help you quickly find the relevent bird illustrations while in the field. Please note that you can 'export' your report by sending the output to a file instead of to the printer. Right click on the report and select 'Export' from the menu. See also What type of reports can I retrive?

Back to FAQ index.



Tips and tricks
  1. This may sound naive but it is a practical problem: if you have trouble reading the computer screen at 800x600 resolution, change the resolution to 640x480 while entering data in the forms. This can prevent a lot of errors and time wasted in finding and correcting them later on. I am speaking from experience - I typed many double spaces in between words and ended up in a mess at one time because some of these errors occurred in critical fields (involved in relationships). Correcting these errors is a time consuming effort.
  2. You can add sightings records _almost_ exclusively with keyboard alone and circumvent the need to use your mouse to navigate between the fields. Pressing the TAB key on the keyboard (usually just above the CAPS LOCK key) will move the cursor to the next field. Unlike the ENTER key, the TAB key always move the cursor to the next field. In memo fields, the ENTER key will add a hard return/new line instead of moving to the next field. Pressing the Shift-TAB key will move back to the previous field for you to correct mistakes.
  3. Most of the sightings data are added by selecting values from popup lists. While the cursor is in a particular field with popup list, type the first character (do not worry about capitation in the sightings form but use correct capitation in other forms) of the value you are going to enter and the popup list will show you the first matching value available. If that is the value you want to enter, pressing the TAB key again will complete the data entry AND move the cursor to the next field. If that is not the exact value, typing the second, third or more characters etc will quickly move you to more specific values. If this still fails, you can still use the mouse to scroll down or up the list to find your desired value to be entered.
  4. Use short-cut keys such as Ctrl-' whenever possible. When you add new records to the sightings table, the fields need to be typed in include date (of sighting), species name, tripname, location, birder name and date computerised. You will notice that among all these fields, only the species name differs from one record to another. For other fields, you need to enter the correct value only once. After that, use the value of the previous (just added) record to put into subsequent records with the short-cut key: Ctrl-apostrophe (Ctrl-'). Pressing these two keys simultaneously will put the value of the previous record into the existing record. There are probably many other short-cut methods to enter data. Take the trouble to check the HELP menu of Access and you may be able to find other fast ways of doing things in Access.
  5. Work with subsets of the records. It is easier to work with subsets of the records by applying a filter while in a form or table. For example, if you are typing in sightings for a certain trip called 'Fraser Hill Feb 2001 Birding Trip' you can click Records > Filter by form > click tripname in the form and select the filter value. Then click 'Filter' > Apply Filter/Sort. You will then be working only on all records in this trip. You can switch between form view and datasheet view to find your records easily while a filter is in effect. Also, sorting the sightings by SightingsID and then viewing in datasheet view will provide you with a list of records in the order that was entered into the computer. This can then be compared or matched with the hard copy of birding notes to check for errors, omissions or duplications.
  6. If you had modified any forms, reports etc or deleted any records, it is advisable to optimize file size by compacting the database. This is done from the Tools menu > Database Utilities > Repair Database. Then go through the same menu and do Compact Database. This can make your database smaller and save a fair amount of disk space..
  7. This database allows you to generate 'Lifers' list. You must enter your 'lifers' in the sightings form but I am sure many veteran birders had long forgotten the date, trip or location about their 'first time'. This situation can be solved by using a general trip name such as 'Trips before millenium' etc. The location can be something like "Unspecified/Forgotten". The date field can be left empty to indicate a date from the 'dinasour' period. It is suggested that other tha the above situations, trip name used should be easy to remember or find. I usually use a combination of the destination and date to form trip names, e.g. 'Kuala Gula Birding Apr 2000' is a meaningful name which is self explanatory.
  8. Some sightings may be made by more than one birders. In this case, it may be better to define a group of birders such as "Selangor Branch Bird Group" instead of a specific person. This can avoid duplication of sightings records by more than one birders from this group.
  9. The following characters have special meaning in Access so that you should avoid using them in any field if possible: # [ ] ( ) ' "
  10. If you find that in your reports, there are some bird sightings with invalid or empty family name or other fields, it is likely that the bird species name in the sightings table had been entered wrongly. Find that record by noting the sightingsID or details of other fields. Correct the spelling carefully by selecting the name from the pop-up list. See also section on How to correct data which are involved in integrity checks.
Back to FAQ index.

How to correct data which are involved in integrity checks?
If you had accidentally mis-spelled data for the species name, trip name, location or birder name, and then linked one of these to the corresponding sightings table from the popup list, you cannot correct the errors in these fields directly. Access will report violation of relationship integrity and prevent you from saving the corrected records. To correct errors in these fields, you must first delete all records in the sightings table with the same field values. Then correct the error and add back new records in the sightings table with the corrected value.

Back to FAQ index.



Limitations
  1. I am a relatively new user of Access and do not know how to add modules/macros. Thus the database is not as user-friendly as I would like it to be and you would need to have some knowledge of Access to use it.
  2. The use of many popup lists aids in accurate data entry but this means that the database may not be compatible with PalmPilot (using Palm OS) which is a popular handheld device allowing data entry in the field. I do not own a PalmPilot or other handheld computers and has no knowledge of Windows CE (the operating system for the latter gadgets). So the database had been designed without taking into account of compatibility with Palm OS or Windows CE. I can only hope that it is compatible and some days in the future, you can actually enter sightings data in the field and later sync the database with your desktop computer or notebook.
  3. If multiple birders are entering sightings into the same database, this database has no way of preventing multiple entries of the same sighting under different birder names.
  4. The relationships between tables were designed with enforcement of 'referential integrety'. This means that Access will check to ensure correct spelling of data involved in relationships. Mis-spelled values will be rejected and this may seem to slow down or prevent data entry altogether. But it is a small price to pay for error-free data entry. This also means that once data had been entered into some fields (e.g. TripName, BirderName and Location) they should not be changed or deleted. The sightings form is an exception. You can delete a record in sightings without disrupting the integrety of the relationships.
  5. I realise that the three books I referred to sometimes have different convention in bird names. Some birds included in one book may not be included in another as present in Malaysia but these species had been included in the database as long as they are listed in any one of the three books. Species without ID for Allen J or Robson's books indicate that I could not find them in the respective books. I presume Plumed Egret (Alle J)and Intermediate Egret (Robson) are the same species and have different scientific names. Both had been entered into the species tables. Some of the bird lists also contain species not listed in Allen J and I added these to the species table too e.g. Vinous-breasted Starling and Bar-backed Partridge. Oriental Dwarf Kingfisher is listed as two different species (Black-backed and Rufous-back) as they have different scientific names..
Back to FAQ index.


Potential Enhancements
  1. I shall be entering bird lists from other areas as they become available to me.
  2. I may decide to add a table or modify the species table to enable cataloging recordings of bird videos or pictures.
  3. You may notice that there are some extra/unused fields in some tables. These are for potential enhancements in the future such as multiuser data entry. If there is anyone interested in starting a bird sighting registration on the web in future, these field will be used.
Back to FAQ index.


Acknowledgements
I would like to thank all those who had provided help, comments, suggestions and encouragement in one way or another. In particular, Glenda and Yeap Chin Aik had provided advice on what type of data are essential. Lim Kim Chye had provided advice on the type and content of output (reports) to be designed. Lim Swee Yian helped in keying in some of the data and performed some data checking. I had also received encouragement from others including Ooi Beng Yean and others.

I would like to thank the owners/compilers of the bird lists which I had computerized into the database. If you feel your list should not be put in, please contact me so that I can remove the records.

Many thanks.

Back to FAQ index.


Update Notes

9 Apr 2001. One new report (BirdListQueryAreaObserverDetail) had been added. This is similar to an existing report
(BirdListQueryAreaSortedBySpecies) but in addition list the names of all observers (birders) and dates (in descending order)
for each bird species reported. An additional field (Location) which specify the exact location within a birding area is also
added to the report. This field had to be added to the query (BirdListQueryArea) with which the report is associated. The
Location field is more specific e.g Location can refer to "Fraser Hill, Rubbish dump area" whereas the Birding Area field is
more general e.g "Fraser Hill". All other feathers in this version are as detailed in birding_db_faq_20010118.html

21 June 2001. Made a correction in species name "White-crested Babbler" to "White-crested Babbler" Error notified by Mr Lim Kim Chye.

Back to FAQ index.


Send your comments and feedback.
If you have any comments, enquiry or wish to report any problems with this database, please email to me at:
[email protected]

Back to FAQ index.