Integrated Population 
Monitoring Reporter 
(IPMR)

General Overview

Please, please take the time to read this introduction. You may waste a considerable amount of effort if you do not read the details in the General Introduction carefully.  I am always trying to make the program more intuitive so that instructions aren’t so important, but until I succeed then please take the time to read them.

Mark Cubitt

Application version 2.1
 
January 2002

IPMR concepts	4
IPMR concepts for Ringing Data	4
IPMR concepts for Colour Mark Observations	5
IPMR concepts for Nest Recording	5
B-Ring and IPMR compatibility	6
IPMR use within partnerships or groups	6
Ringing	6
Nest Recording	6
Nest Recording and Ringing together	7
Automatic creation of Emails	7
Little things that you should know	7
Mapping Tool Integration	8
Standard Reports	8
Report Manager	8
Creating backups of the database	9
IPMR functions	10
General	10
Owner	10
IPMR Setup and Options	10
Observers	11
Place codes - 1km squares	11
For Ringers:	12
Ringing subsites	12
Ring Series	12
Submission sequence number	12
Field setup	12
Constant Effort Sites	13
Retrapping Adults for Survival	14
Swallow Roost Project	14
Entering Captures	14
Importing Captures	15
Creating Submission files	16
Entering information received from BTO HQ	16
Others’ Ring Series	16
Confidential Sites	17
Working with Capture records held in IPMR	17
Ringing Secretary Advice	18
For Nest Recorders:	19
Nest Subsites	19
Nestbox Types	19
Nest Boxes	19
Creating Nests	20
Entering visits	20
Nest statistics	21
Ringing details for nestlings	21
Nest Record Submissions	21
Importing Nest Records	22
Working with Nest records held in IPMR	22
On-line help	23
System Requirements and Installation	24
Diskette or CD install	24
Web Site Download install	24
Setup	24
After Installation	25
Upgrading from IPMR v1 to IPMR v2	25
Upgrading from one IPMR v2 release to another	25
Re-installing IPMR on a new PC	26
Before you change the PC	26
Re-installing IPMR	26

IPMR concepts	
		IPMR is an application that has been developed to assist BTO ringers and nest recorders to enter, manage and submit ringing and nest record data to BTO HQ.  IPMR holds its users’ data in a database. This database holds both ringing and nest recording data. Submissions to BTO HQ for ringing, CES, RAS and nest recording are made independently of each other.	

Multiple databases are supported		IPMR can support multiple databases. The use of more than one database is usually only required for ringers who use both their own rings and also those of a partnership or group; these records must be kept in separate databases. For nest recording in a ringing partnership or group normally the Nest records would be entered or imported into the IPMR database from which the Ringing records were to be submitted. So, for example, if they are to be ringed on partnership rings then use the database for the partnership, but this need not be the case.	
		IPMR concepts for Ringing Data	

Information on Ring Series and captures can be exchanged within ringing groups		The concept behind IPMR is that the prime copy ringing data for an individual or group is maintained within one IPMR system.  The prime copy of ringing data is the authoritative copy - the one from which data are sent to BTO HQ. There are a number of facilities within IPMR to support this including: the checking and automatic setting of record types based on records already within IPMR; the maintenance of the usage of rings within series and the automatic generation of submission sequence numbers.
In a group situation multiple people can enter capture data; it is recommended that this be on the basis of responsibility for discrete series of rings. The series need not be the full series as received from BTO HQ, but could be perhaps a set of, say, 50 or 100 rings out of a series of 1,000. The allocation of rings is managed through the Ring Series facility. The Ring Allocation Splits function aids the entry of ring series which need to be split for allocation for example to ringing group members (they are also used for an auto ring series add facility when importing capture records).	
Use more than one database if appropriate.		Someone who enters ringing captures for their own rings, for another ringer and for a ringing group should do so in three different database files. See the File, Select Database function about creating a new database file. 
You should NOT have a separate database for each year.
IPMR is not really designed to hold personal records of birds ringed on someone else’s rings, e.g. on a ringing course. It can be done, but in this case these captures should certainly be held in a separate database from one used to submit captures to the BTO.	
IPMR automatically manages which records have been submitted to BTO HQ		The submission of records to BTO HQ is done on a different basis to B-Ring. IPMR holds a flag against each record indicating its submission status so there should be no need for the user to control which rings to submit and which not to; this is handled by IPMR automatically. When a submission file is created any records ready for submission are selected (this can be controlled by year if required).	

		IPMR concepts for Colour Mark Observations
Birds observed with colour marks but where the BTO metal ring number is not known can be held and submitted to BTO HQ using the Captures> Observations function.
Observations can be added (or edited) prior to submission. A subset of capture fields is available to record the information required.  These records are submitted as part of the standard Captures Submission function and are held in the same submission file as normal capture records.
If the observation can be identified to a specific ring number then an Observation record can be converted to a normal capture record using the “Create Capture” button from the Observation details form.
IPMR concepts for Nest Recording
All nest records for an individual or group for multiple years are held in a single IPMR database. IPMR v2.1 allows nest record data to be imported thus permitting multiple people to enter nest record data and for these to be consolidated into one IPMR database.	

Places and subsites hold default habitat and nest information to aid nest data entry

Manage your portfolio of Nest Boxes

Submitting Nest Records and Year end totals to the BTO		Each nest has a unique sequentially numbered Nest Record Number in the database; this number cannot be changed and is allocated by IPMR.
Places hold geographic information such as grid reference and county and should be defined before creating any nest records; these represent a piece of woodland, an area of moorland, or a park for instance.  These Place details are shared with Captures data (if you are a ringer).You will often find that there is nest information that is common across nests. This can be because the habitat at a site is the same for large areas or it can be common across years for regularly used nest sites or where Nest Boxes are used. You can set default habitat information for Places or Subsites in IPMR.
Once set up Subsites can be selected directly from the Nest form or can be linked to a Nest Box.
Nest Boxes are a key feature of IPMR. When a Nest Box is set up it can be linked to a Nest Box Type and a Subsite as well as holding information about the box. When a Nest is created a Nest Box code can be selected. If the information above has all been entered when the Nest Box was defined then the Nest Box Type, Subsite, Habitat and other information such as nest height and orientation are copied into the Nest record. 
Both Subsites and Nest Box details can hold a grid reference. This can be your own local reference, but if it is an OS 6 figure grid reference such as NZ372567 then it will be copied into a nest record when selected.
Multiple submissions can be made in a given year, but it is expected that generally only one or two nest record submissions will be made per year.  
There is a Nest Record Year-end Totals report that must be submitted at the end of the nesting season.	

		B-Ring and IPMR compatibility	
Import your old 
B-Ring Data		If the database will hold rings issued to an individual, and no-one else uses them, then the only concern may be that of migrating data from B-Ring to IPMR. B-Ring RDF files or standard Submission (Data on disk format) files can be imported into IPMR. See Importing Captures below.
The B-Ring BTOPL.TAB file can be imported into IPMR from the Import/Export Control Information. See the Place codes section under Starting IPMR for the first time below.
IPMR use within partnerships or groups	

Exchange ringing data within your group or partnership

Group members should use their own name and permit number		IPMR is designed to operate within a group environment for both ringing or nest recording or a combination of both.  
Ringing
Operation as part of a group, partnership or when other people are using an A-permit holder’s rings requires the exchange capture records. The Ringing Secretary should have the Group’s Database (unless he/she does not use IPMR in which case they can delegate this to an IPMR user within the group). Other group members can use IPMR (or B-Ring) to send in Submission (or RDF or Data on disk) files.  The exchange of Place details, Subsites, Observers and Ring Series is also recommended. These can be transferred from the Group’s Database to members’ databases, which is suggested for Ring Series, or vice versa, which is more likely in order to add new Place records. This is accomplished using the Control Import and Export functions available under the Control menu item. See the Ring Series section later in the guide for more information on allocating Ring Series out to group members.
Group members should use their own name and permit number not that of the group in order that the group’s Ringing secretary can distinguish between files sent in my different members.
As a result of all this it is recommended that the person who collates capture records for submission to BTO HQ uses IPMR, but those who collect and enter the data can use either B-Ring or IPMR. There are benefits in having IPMR used by all members of a group such as the exchange of Ring Series information, but this is not critical.
Nest Recording
A group of nest recorders can also collate and submit nest records to the BTO through a single, group IPMR database.  It is suggested that group members of a group with a nest recorder code of, say, “ABC” use nest recorder codes of “ABCA”, “ABCB” et seq. In order to allow the group secretary to distinguish between group members’ submissions.
The use of Control Information Export/Import function is essential for nest records and it is likely that all Nest Submissions to the group secretary will have to be accompanied by a Control Information Export file particularly if subsites and nest boxes are used.
Nest Recording and Ringing together
Nest Record submissions contain a subset of information on Captures associated with the nest.  In order to submit nest record and captures information from a group database to the BTO then both Captures Submissions and Nest Record Submissions should be imported into the group database.  It doesn’t really matter in which order the submissions are added, but the preference would be Nest Records first. Onward submission to the BTO of captures at nests should, preferably not be done before the associated nests have been imported.	

		Automatic creation of Emails
When creating files or reports to be submitted to BTO HQ IPMR can create an email for you if you have Microsoft Outlook, Pegasus or email application such as Outlook Express, Eudora or Netscape Messenger which have a MAPI interface.  IPMR will not set up the Email Application for you so make sure that you can send emails from it, and if MAPI interfacing that MAPI is set up within it, before asking IPMR to create emails for you.  Use Control> Options to select the Email Application type that you use on your PC.
Little things that you should know	
Windows Date and Time formats		•	The Regional settings (in Control Panel) for short dates must be set to English (British) or English (United Kingdom) and the year component must be present. This ensures that date format are day, month and year e.g. dd/MM/yy. Four digit dates e.g. dd/MM/yyyy and period separators e.g. dd.mm.yy are also acceptable. Also the Time display settings (also in Regional Settings) can cause problems, but IPMR v2 will temporarily set them appropriately while running if not set correctly.	

		•	There is an Options form under the Control menu item. This sets up a number of useful things including the Current Year that data is being entered for. Take a look at the form and its accompanying help	
Just type in the day and month for dates after setting the Current Year

Don’t forget the F1 and Esc keys		•	When entering data into some fields, particularly numeric ones, something like __._  is often displayed. This shows the format of the entry required; in this case a number with one decimal place. To enter the data type the number, e.g. 21.1, into the field. Also just 1.1 can be typed into the field; this will initially look like 1_.1, but when the next field is moved to then the number entered will look like 1.1 as might have been expected.
•	Help for a form can always be viewed by just pressing the F1 key
•	Pressing the Esc key will Undo the last edit. Pressing it twice will undo all changes made to the record	
		•	If IPMR goes into an error loop (just in case) then using the Ctrl-Shift-Q key combination will try and shut down IPMR to save turning the PC off!	

		Mapping Tool Integration
From the Capture Selection and Processing facility DMAP or VersaMap files can be generated and managed. DMAP or VersaMap can then use these output files to show point positions or movements. Only more recent releases of DMAP will support movements. 
Standard Reports
IPMR has many standard reports available. If you can’t find a report use Help Search and enter “Report”. The reports include:	
		•	Place summary details
•	Ring series usage
•	Ring stocks
•	Available rings report
•	Costs of rings report
•	Ring costs by observer
•	Capture history
•	Recovery history
•	Recoveries
•	Captures consistency checking
•	No original ringing record
•	Capture details summary
•	Cross-tabulation for captures
•	Captures submissions
•	Outstanding Controls	•	Monthly captures totals
•	Place captures totals
•	Observer captures totals
•	Observer captures report
•	Colour ringed birds
•	Year-end captures Totals
•	Age specific captures Totals
•	Nest Checking with Pulli Ring Dates
•	Nest Checking with Captures
•	Owl Hatching
•	Nest record Species Summary
•	Nest record Species Survival
•	Nest Summary	
•	Cross-tabulation for nest records	
		Report Manager
There is also an ad-hoc reporting facility available using the report manager. Using this facility records can be selected from IPMR tables or existing queries and reports created. The fields for the reports, groupings and sort orders for the data can be selected and row and column headings can be entered	

		Creating backups of the database	

Ensure that your data is safe		As with all valuable information, the data held in the IPMR database needs to be looked after. Periodic backup copies of the database(s) should be made as insurance against software or hardware failure. Having a recent backup will help to reduce the impact of such a failure. Having multiple backups is highly recommended because if the database is unknowingly corrupted and a backup is made when you leave IPMR then the backup will be corrupted too. Backups are set up from the Control> Options menu item. The use of the Compress backup option to a diskette is recommended as the Zip format backups can hold in excess of 20,000 records per diskette and Compress will automatically span multiple diskettes if required.
If a backup option is set up then when IPMR as closed down a backup opportunity is offered to the user.  A backup of the current database can also be  directly created using the button on the main menu form.	
		Creating multiple backup sets can be achieved quite simply. A Backup Set is composed of one or more diskettes. Say that it is decided to have three backup sets. Each set can be used in turn: backup set number 1 after your first session, set 2 after the next, set 3 next time, and then overwrite set 1 again after the fourth session.  Consider taking one copy to be held “off-site” well away from the computer that holds the prime data so that major damage to a building will not destroy the backup.	

IPMR functions	

Follow the help screens to set up IPMR right first time		General
When IPMR is started for the first time some Help screens will be popped up automatically. At the bottom of the help screens for the key features of IPMR that are required to set up IPMR are sections headed ‘What next if you are setting up IPMR:’.  These will lead the user through the other things that you need to do to start using IPMR. If a help screen is accidentally closed then go back to the main ‘blue/coloured’ IPMR screen and press F1 and the last help topic will be re-displayed. Some of the information contained in this help flow is given in the following sections:	
		Owner 
IPMR requires the Owner information to be added when an IPMR database is first used. This is information such as individual, partnership or group name, permit number and/or nest recorder name and observer code. The permit number or observer code must be added before ringing capture or nest record data can be added to IPMR. You will be prompted for this automatically.
Ringing capture submission files can contain your e-mail address which will in the future allow the Ringing Unit to return details of recovered birds.  The e-mail address is set from the Owner form.
If you are a nest recorder and not a ringer, but pulli in any of your nests are ringed then PLEASE do enter the details of the ringer or group involved in the Ringer fields (they can give your their permit number). If there is more than one ringer or group ringing your birds then either enter one of the details of dummy values such as ‘Ringer’ and ‘999’. This will enable you to enter pulli (and/or adult) capture information including ring numbers for your nests; this is most valuable to the BTO.	

Make sure that you set the IPMR Options correctly		IPMR Setup and Options
There are a number of options that need to be setup in order to make best use of IPMR’s facilities.
Folders/Directories can be set up as required. During the installation the application folder (c:\ipmr by default) where IPMR and its associated files reside will have been chosen. The Data folder is where the IPMR database(s) are held. Other folders to help manage importing and exporting information can be set too. These folders can be on another drive (e.g. a drive that holds only data to ease the making of backup copies of files).
Backup options (referred to above) are set from the Options form.
Current Year is the way the IPMR avoids having to key in a four digit year with every date entered. Normally it will be the calendar year for which recording is being made, but it can be set to any previous year for entering historical records.
Default Country should be set to GB for Great Britain and Northern Ireland or ER for Eire. This value is the default used when setting up Place codes (see below).
Export Format is the format (comma delimited, WK1 or Excel) used to export information from IPMR in particular from Captures and Nest Selection and Processing functions. 
Own Species List is an optional feature to allow you to select either the default of 201 commoner British Species or (one of) your own list(s) of species in order to speed the data entry of species names. 
Captures data entry options to set the default submission code, control update confirmation, override IPMR measurement method defaults etc.
Email Application can be set to Microsoft Outlook or MAPI and this will enable IPMR to create emails of submission files or reports that you create. The MAPI option supports MAPI interface compliant email applications such as Outlook Express and Netscape Messenger.
Mapping setup allows the location of any mapping product (DMAP or VersaMap)  programs and data files to be setup
Customise some of the colours used on IPMR forms to override or reset to the colours selected through the Windows system colour settings.

The next thing that you will want to do is to try entering some data, but there are a few things that need to be set up first:

Import your B-Ring BTOPL.TAB file		Observers 
Observers, are optional, but are required for allocating ring series to, assigning processors’ or wing measurers’ initials to captures and to assign Nest Records to. They are also used for reporting purposes e.g. for someone’s ringing or training totals for the year.
Place codes - 1km squares
Places codes are references to the 1km squares (in GB, NI and Eire) at which ringing or nest recording takes place. These must be entered. They can be up to 6 characters in length, but if you need to stay compatible with B-Ring they should be kept to three characters in length.  Registered site codes are also entered here; they can be the same as or different to the IPMR place codes (and there can be multiple Place codes sharing a registered site code if required).  There is a check box that you will be prompted to enter to say whether the Site code has been accepted by the Ringing unit.  If it has not then leave the checkbox unchecked, enter the OS Map number and use the report available from the List of Places form to create a Site Registration form to email to the Ringing Unit.
To set up Places use the Own Places option under the Control menu item. If there is an existing B-Ring BTOPL.TAB file then it can be imported from the Control> Import/Export> Import Control Information. The BTOPL.TAB file must be first copied into the Import Folder folder. (Place details can also be shared among IPMR users using the import and export functions).
The ‘Ringing’ check box must be set in order to use the Place code for ringing captures and the ‘Nest Recording’ check box for use with Nest Records. These are automatically set when entering Places manually or on import based on whether there are permit number or nest recorder codes entered on the Owner details form.	

		For Ringers:	
		Ringing subsites	
		Ringing subsite details hold default habitat and capture methods for regularly used sites or nets for general and in particular for CES ringing	

Manage your ring series and keep track of their costs too		Ring Series 
IPMR automatically keeps a record of the usage of Ring Series, allows the management of the allocation out of rings within a group and provides some ring cost reporting. 
If IPMR is to be used for ringing data then Ring Series will need to be entered. They can be entered in advance or added while manually entering captures or during the import process. Adding in these latter cases can be done using the Ring Series form from the menu or, if series splits have been entered in to the Ring Size Information function, a prompt will offer to add a series automatically.
Ring Series can be “allocated” to group members or others who use rings. This allocation allows their use and submission status to be monitored. If the Ring Series are allocated then the Control Export file can be created for an individual in the Observers table. This allows a Ringing Secretary to send out new series of rings and a diskette/email with a file allowing the ringer to load the series information into their IPMR database.
Some old ring series are not in the Ringing Unit’s validation file. Rings in these series cannot be used except if they are imported with the option that they are not to be submitted; in this latter case the ring series are set up by the import function.	
		Submission sequence number
If data on disk submissions have already been made (using B-Ring or your own program) in the calendar year that IPMR is first used then the Reset Submission Sequence Number facility will need to be used to tell IPMR the last sequence number used.	

Ease the burden of new bird and retrap captures data entry		Field setup
When entering capture records it needs to be as efficient as possible. Because IPMR holds all fields in its database (rather than just selected fields as in B-Ring) there is a Field Setup facility. This allows, within certain restrictions, the fields that are displayed when entering data to be selected and tabbed through in a preferred order. Multiple setups for different types of ringing operation can be created.
The field setup is based on putting IPMR fields into one of three categories: Tab order, View list and Hide list.	
		Tab Order list	Fields in the Tab Order list will appear on the Enter Capture Details form and are the only fields that will be tabbed through when entering information. The order of fields in the list determines the order that they will be tabbed through. In the List style Enter Capture Details form it also determines the order in which the fields are displayed. 
View List	Fields in the View list will appear on the Enter Capture Details form, but will not be tabbed to when entering information
Hide list	These fields will not be displayed on the Enter Capture Details form.	
		The best strategy for using the Field setups will be developed by each user over time. Initially it may be easier to have all of the required fields in the tab order list. However, when data entry becomes more familiar then fields for which the auto repeat function is used (see Entering Captures below) can be put in the View list. Once values are set up for the first capture of a data input session (using a mouse to move between fields) this will save the extra tab key depressions required to enter the data for the rest of a session’s captures. 
	
		Constant Effort Sites	
		Constant Effort Site (CES) ringing is supported by IPMR. Captures are entered in the normal way. However, some additional information needs to be set up specifically to support CES. 
•	Place information includes an indication that a Place is used for CES using the CES Checkbox and the CES Site Code. The First and Last years of a CES study can also be set (this is optional - if you don’t set them then all years are assumed).
•	Capture Subsites can be set up for that Place for each net (whether a standard CES net or not). If you need to exclude a net from CES reporting, e.g. when doing a RAS study nearby in non-CES nets, this can be achieved using a subsite code with the CES Exclude check box selected.

When importing data from B-Ring that uses OWN, OWN2 or USER1 field to hold net or additional net information the User defined import code conversions can be used to convert these codes to IPMR Subsites.
•	Ringing Session information is recorded in order set up visit numbers/codes for CES reporting. All mist netting visits during the CES season (from April to August) must have a Ringing Session. These can be either an CES visit (in which case the visit code is numeric - from 01 to 12) or a non-CES visit (with alphabetic codes). Captures cannot be entered for Places where CES ringing occurs during the CES season without a Ringing Session recorded as either a CES or non-CES visit. The CES summary sheet report contains a column for Captures in CES season without a session which should always have zero values as a check that all Ringing Sessions have been set up correctly.

The View Captures button can be used to display all (non-pullus) captures for the session. The subsite and its additional net or excluded net status are also displayed. Also in order to exclude individual birds from CES submission a check box beside each capture can be clicked.
Annual CES submission files and report can be created using the Constant Effort Site Submission Function.	

		Retrapping Adults for Survival	
		Retrapping Adults for Survival (RAS) reports and submissions can be created from IPMR.  Captures are entered in the normal way, but if you ring individuals of that species that are not part of the RAS study at the same Place during the summer RAS period then you will need to use subsite codes to distinguish them.
The Retrapping Adults for Survival function is available from the Captures menu.  Multiple RAS studies can be set up.
The RAS project number is entered together with the species code and the calendar period of the study e.g. 01/04 to 31/08.  The location(s) at which the RAS study operates need to be defined. These can be defined at Place code level and one or many places can be included.  They can also be defined at Subsite level within a Place.
Swallow Roost Project
The Swallow Roost Project (SRP) is the first project that has not required a separate submission to BTO HQ.  Instead each capture record that is part of the project must be linked to the project. This link will automatically be picked up by the BTO Oracle database as part of the standard Captures submission file.
A project must be registered to IPMR using the Captures> Register Project function where the project code, SRP, and your project’s registration number must be added.
When entering capture records for the project a field setup containing all of the fields required by the project must be used.  A field setup called “SRP” contains the fields required for this project. This includes a field Project1 which requires to be set to the project registration ste up previously.	
		Entering Captures	

Current Year is set in Options 

Auto repeat copies information from one record to the next

Let IPMR enter ring numbers automatically

Use IPMR’s Record Type Assist

Use the Toggle list entry to change between a ring size based species list and the full list		There are a number of other things that can be set up to aid the use of IPMR, but this is the minimum. If you want to try it out now you can go to the Captures/New (form or list styles) to enter some captures. You can use either style of form depending on your personal preference; the Form style displays one page per capture record, the List style displays records in a spreadsheet-like manner. The List style shows records for only one day and avoids having to enter the date. (These records can be deleted if you are just testing out IPMR using the Capture Selection and Processing function by selecting all dates, selecting the record and pressing the ‘Delete’ key.)  
Captures will normally be birds you trap yourself during normal ringing activities and will as such usually be New birds or Retraps. However, they can also include birds that have been recovered by non-ringers, found dead or has been observed as field sightings. In these cases the appropriate record type will need to be selected. There are 18 different Record types (not just N, C and R) so if you don’t know how to use them (including recent changes to sightings record types) please use help and search on “record types”. You can also create a recovery record on behalf of another finder. Search for “Finder” in help.
There are a number of facilities to aid the adding of records. These include:
•	To avoid the need to type in the year of Capture into records, the Current Year is set in the Options facility. This can be set to a previous year if you wish to enter historical records. 
•	Double clicking on the input fields for record type, ring number, species, date and some other fields sets the auto repeat function. This copies information from one record to the next (or increments the ring number); the fields’ background turns pale yellow in colour to show that auto repeat is on for that field. A number of fields are set this way by default to get you started.
•	Ring numbers can be incremented using the auto repeat function mentioned above (assuming that it is a new bird). This is useful if a string of new rings is being entered. If, however, a mixed series of rings is being added then IPMR keeps a note of the last ring used of each ring size this is available from the ring number drop down list. When a species is entered then the next ring number for the appropriate size is entered automatically. This facility needs a new-bird record type to be present and depending upon the species the ring number may not be added until the age and/or sex are added.
•	If you enter the ring number first IPMR automatically looks through your database for previous records to set the record type for you. This will only work effectively if you have historical records in the database of course
•	The list of species codes to select from is based on ring size. This means that the number of letters in the species code that you mean to type is minimised. If you use a non-standard ring size for a bird or it is an uncommon species then you will need select the Full List entry in the Species list. This will extend the list to all of the species available. (If it is not one of these then you will need to use the special ****1 species code for rarities, but this is very unlikely.)	

Auto Creation of Ring Series

Continue until error or Bypass error
options on Import

Old codes can be converted to current values		Importing Captures
B-Ring RDF files, Submission files and comma delimited (CSV) files can be imported into IPMR. See Help within IPMR for more details about the CSV format required. The Control > Options function allows the default Import folder to be set. This could be the folder used to hold B-Ring information e.g. c:\bring\btodata\. Place (1km square) codes must be set up beforehand. These can either be created individually from the Control > Places function or imported from a B-Ring BTOPL.TAB file or from Place Export files created by other IPMR systems for example those of other group members.
It is probably best if Ring Series have been set up before importing capture records, but this isn’t required.  If a value is entered in the Split Into Series Of  field for a ring size, in the Control > Ring Series > Ring Size Information facility, then Ring Series of this length will be set up automatically when a capture with an unknown ring number of this ring size is encountered during an Import.
Records can be Skipped or Imported. If IPMR finds an error in the file it will only allow the record to be skipped or for the Import to be cancelled. Skipped records are put into a reject file. If any errors in the reject file are corrected then it can be re-imported.
Warnings will be issued if the capture already exists or if the ringing (as opposed to a recapture) record exists. If the imported record is for a dead pullus then IPMR checks that the date is that if the original ringing record (if any). These records can then be imported or skipped.
There are check boxes to allow the Import to continue until an error is found or to continue to Bypass errors (by automatically skipping them). These options allow you to let IPMR continue to import records which is not a particularly rapid process.
IPMR will try to convert old pre-Data-on-disk codes for some fields e.g. Plumage code or Sexing Method to the current ones. User defined code conversions can also be set up for some fields where you have used your own conventions. Note that using the user defined facility can slow down import processing. 
If the records to be imported are associated with nest records and these nest records have already been imported the special considerations apply.  A message will appear for each existing nest record import capture record (which would have a submission code of NRI).  The Overwrite checkbox does not need to be checked as IPMR will automatically take a note of the nest record number, will replace the record and then update the nest record number of the capture record.
Any errors generated during an import into IPMR are saved in a text file and can be viewed from within IPMR from the Captures > Import menu item.
Creating Submission files	
		Submission files can be created using the Captures > Submissions > Create function. All capture records and observation records appropriate to be submitted to BTO HQ will be selected when this function is used (optionally a particular year can be selected). There is no selection by ring series involved. Submission files only include new captures, retraps and controls of other’s birds. There are facilities for sharing recoveries made by others or the original (first) ring details of controls, but the Ringing Office do not create files of this format yet.	
		Entering information received from BTO HQ	
		When the Ringing Unit sends details of a recovery of one of your ringed birds or ringing details for a control that you have sent in you can enter these details into IPMR. This enables a full capture history to be maintained. There are Capture menu options for ‘Enter recoveries’ and ‘Control First Ringing details’. These ask for the ring number, which is checked before a capture details entry form is presented. Before entering the capture details the Place details will need to be added. These can be added using the standard Places facility, but in order to keep details of your places separate from those of others and to allow the use of a simpler form the “Others’ Places” menu option should be used.
When using the Recoveries function the Record Type will have been set to Control by default in the Captures form. However, if the bird has been recovered by a non-ringer, is a local control i.e. a retrap, is dead or has been observed as a field sighting then the record type will need to be changed. Fields such as the species and ring number will have been completed. The other fields should be completed as normal.	
		Others’ Ring Series	
		Reference details can be held of ring series used by other ringers. It is particularly useful for storing ring series of local ringers with whom you might swap controls. There is a facility to import Others’ ring series information from a file that can be generated from the Ring Series form of another IPMR user’s database.	
		Confidential Sites	
		The places function has a check box to indicate that a place is confidential. When the check box is selected the place name and grid reference fields are displayed and the open details can be entered with a greater coordinate (in)accuracy figure of up to 99 km. The fields to contain the secure details are displayed and must be entered. 	
		The submissions are created using the open place details. Printed Ringing schedules can be created using the confidential information. These are made on the basis of the sets of records in the data on disk submissions and are managed from the Captures/ Submission menu items.
Location details for secure places can be kept in the database in encoded form with the use of a password.	

Analyse your data		Working with Capture records held in IPMR
Select your records: The Capture Selection and Processing function allows records to be selected by record type, species, ring series or number, date and/or submission status. Once the selection criteria have been entered the ‘Run Query’ button should be clicked. The set of records that meet the criteria are then displayed. 
View capture details: These can be viewed or edited by selecting a record and clicking the ‘Edit Record’ button. If the record has already been submitted a warning message will be displayed; if the record is then updated it will be flagged for resubmission 
Standard reports: Capture history and capture details reports can be produced for selected records. 
Export data: An export function allows the selected records to be written to a comma-delimited file. The fields exported can be selected from a menu option. 
Tabulation queries: Using the Report > Cross-tabulation menu item cross-tabulations can be generated into a report. This is a powerful reporting facility allowing you to report on say counts or averages of one field tabulated by up to two others. For example you could compare average weights by site by month of the year. In this case you could have already selected by species using the selection query. The cross-tabulation is saved as a query that can be used by the Report Manager or to be exported into a file that you can put into a spreadsheet, for instance.
Recoveries Reporting: If you select a set of birds, based on either original ring details, recovery details or just place involved then any recoveries that those birds are involved in can be shown in a report or the information can be exported

		Ringing Secretary Advice
Knowing which capture record came from which group member is best done by allocating the ring series they hold to them in the Ring Series function.  If there is a particular ring in question then the ring series list can be sorted by ring series and the owner determined.  The SQL Helper in Captures Selection and Processing also allows the ALLOCATEDTO field to be used to select captures of the ring series owner.
Knowing which capture record came from which import is determined in Captures Selection and Processing by selecting the capture(s) in question and using the Report> Imported Captures report.  This lists the import date/time and the permit number/name of the submitting group member.
Seeing which group members have made a submission this year and when can be seen by using the Imports Summary by Year report from the Captures> Imports menu.
Filing Submission files so that it is clear which files have been imported and which are still to be processed can be achieved simply in IPMR v2.1.  At the end of importing a file IPMR offers the option to move the import file to a sub-directory of the Import folder.  The sub-directory is named either rdf of csv for files of those types or the filename, which should be the permit number of the submitter.
Control Data can be exported by group members and imported by the group secretary in order to add new place codes, for example. Note that this function will only add or update records (places, subsites etc) and not propagate deletions or renaming between databases; these operations need to be done manually, but should be rare.  The Control Import function has a Check Place button which will highlight new places, new registered site codes and mismatches in grid references and county/region codes.	

Nest Subsites can be
     Specific
         or
     General		For Nest Recorders:
Nest Subsites
Subsites can be used in two ways. It is important to understand these:
1)	It can hold information for Specific nests sites. These might include Peregrine eyries or Dipper nests in the same spot under a bridge. They are somewhat analogous to Nest Boxes, but obviously have quite different characteristics.
2)	It can hold General habitat and other nest information that can be used to set default values when you set up a Nest Record. This can be useful at colonies or for regularly used sites with common habitat. The alternative is to enter the habitat information individually for each Nest Record.
You will be presented with a list style form in which you can enter subsites for any of your Places. Clicking on the Subsite Details button will display the detailed information for that subsite.	
 		Nestbox Types	
This is the information that the BTO want to know about your Nest Boxes		If a nest is recorded as being a Nest Box then a Nest Box type must be associated with it. This includes information on the style of box and its size. Generally you will have a set of Nest Box types. You will typically have a number of Nest Boxes that have the same Nest Box Type. A number of Nestbox Types are shipped as a starter set with IPMR; these are based on those in the BTO Nestbox Guide. You will be presented with a list style form in which you can enter new Nest Box types. Clicking on the Box Type Details button will display the detailed information.	
		Nest Boxes	

This is the information that you may want to hold about your Nest Boxes		Nest Boxes are associated with a Place. Each will have a code and must have an associated Nestbox Type. If you use numeric Nest Box codes then it is suggested that you use leading zeroes, e.g. 011 rather than 11 (see below). Usually you will also associate a Subsite to store habitat information. There are a number of other attributes that you can hold for a Nest Box. It is recommended that you complete the Walk Order which, when you select the Nest Box for a Nest record, the box’s walk order is used to set the Nest Finding field in a nest record. The Nest Finding field is used to sort active nests for some IPMR reports. As for Nest Box codes if you want to use numbers for the walk order then you should use leading zeroes in order for the sort to operate as you want (as it sorts by characters, not by number value). Other information such as Nest Box height, etc, may be recorded.	

Rapidly enter your Nest Box details		It is suggested that you add a set of Nest Box codes for a Place in the Nest Box list form. Once these have been entered go to the top of the list and click on the Box Details button. This will show the details about the box. You can navigate back and forward through the list of boxes for that Place using the Next Box and Previous buttons. If you double click on any of the fields the background colour will turn yellow and any values held in that field will be transferred to the next box you go to assuming that the field(s) involved are empty in the next box details (it will not overwrite any information!).	
You can change Nest Box details between seasons		If you move a Nest Box between seasons then you can retain the Nest Box code if you wish. The Nest Box details required by BTO HQ for a nest are copied to and held in the Nest record. This means that changing the Nest Box details will not affect previously entered nests.	
		Creating Nests	
		Nest records can be entered initially from the Nest Recording > New Nests menu item. There are two menu items one where Place codes are used and the second where Place codes are not necessary. If you are a ringer then Place codes must be used; even if you are not a ringer then the use of Place codes are recommended to facilitate reporting and to allow the use of subsites and nest boxes. 
When entering a new nest having entered the Place code then the drop down lists of Subsites and/or Nest Boxes available will be populated with to ones you have set up for that Place.	
Make use of the default values held for your place, subsite or box.		Upon entering a subsite or a box with an attached subsite many of the fields in the Nest Record will be automatically filled if default values have been set up for them (they can then be overridden, if required, for this individual nest). The values, of course, can be entered for any of these fields manually without using subsite or Nest Box codes. Generally the fields should be self explanatory with the aid of the BTO’s Nest Recording handbook.	
		These nest details shouldn’t need to be changed, as it will be Nest Visits that will be updated from now on, but the Edit Nest menu option allows this.
If details are being entered for a number of new nests then the use of the auto repeat function can save much time. Most of the fields for the form can use this facility. To turn it on or off the mouse should be “double clicked” on each field. The background colour will change to a pale yellow colour when auto repeat is on.	
		Entering visits
Once you have entered the Nest Record details you can then use the nest visits form.
Visit information such as date, time, nest contents and status codes can be entered directly for each nest visit. Status codes can be typed in directly, selected from a drop down list (based on the state of the nest) or via a selection panel. The selection panel is displayed by clicking the Status Codes Selection button.	

Update nest visit information for the set of nests that is convenient for you		The Nest Visits entry form can be invoked from a number of places in IPMR depending on what you want to do and how you want to use IPMR. 
•	If you come from the Nest Record Card form using the Visits button then you can look at only the one nest.
•	If you use the Edit Visits menu item then you will have the full set of nests that IPMR holds.
•	If you use the Edit Outstanding Visits menu item then you will have all nests for which an outcome code has not been added. The order of nests in this case is determined primarily by sorting on the content of the Nest Finding/Comments field.	
		•	If you come from the Nest Selection and Processing form then you will have the set of Nests that you have selected available to you. This can be by Place code, Nest Box, Year, etc.	
		You can either select all nests or outstanding nests to edit and you can scroll through the nests using the Next and Previous buttons or use the Goto... button to move directly to a specific nest.	
		Nests are termed “Outstanding” until the Final outcome code has been entered. This can be done from either the Nest Record form or the Nest visits form. In the latter case if you enter a Status Code for visit that IPMR thinks might be for the last visit then IPMR will ask whether this is to be used for the Final Outcome code. Nest Records cannot be submitted unless a Final Outcome code has been added.	
		Other information can be entered for a visit. This includes egg measurements, chick measurements and ringing details (see below) and adult capture details. These are accessed via buttons on the bottom of the form. The buttons are only displayed when the nest has appropriate contents e.g. some eggs for the Egg Details button. To enter adult captures the Adult trapped status code must be entered first. See the Help system for a description of how to enter these details.	
		Nest statistics	

IPMR estimates the nest statistics when you enter a final outcome code for the nest		There are other fields held in the nest record that can be updated from the visits form. These are the first egg and pulli dates, fledging dates and pulli-fledged fields. These are not submitted to BTO HQ, but will be useful for any of your own analyses. IPMR will try to estimate these figures for you when you enter a final outcome for the nest, but you can enter or substitute your own values at any time. The figure for the first pullus date is used for the Pulli Checking report, which lists nests at which there may be ringable young on a given (your next planned visit) date.	
		Ringing details for nestlings	
		When the Young Ringed status code and a status code equal to one of the ringing scheme’s pullus codes e.g. IP or FM, has been entered and the Chick Handling button is pressed then you will have a message prompt asking whether you want to enter the batch of ringing details together (by specifying first ring and the number of pulli ringed). The alternative is to enter the birds separately in order to add measurement details etc. 

This information is held in the Captures part of the database and handled for reporting and submission purposes as normal there, but the details are also included with the Nest Record submission so even if you are not a ringer yourself the if your birds are ringed then please set up some ringer details in the Owner information and add the capture information.

One thing to note is the use of the ‘P’ record type. This is used for pulli that die before fledging. A pullus must only have one capture record submitted to BTO HQ, which if the bird dies in the nest should be a record type P. If you enter a young dead status code for a visit and there have been young ringed then you will be offered options to convert the record types of these birds from N to P. 
Nest Record Submissions
Submission files can be created using the Nest Records > Submissions > Create Submisison File function. All nest records not yet submitted that have an Outcome code assigned will be selected when this function is used (optionally a particular year can be selected). The submission files contain records for nest details, habitat details, visit details, egg details and capture details. 
Importing Nest Records
Submission files can be imported into IPMR using the Nest Records > Import > Import Nest Submission File function. The records for nest details, habitat details, visit details, egg details and capture details are all imported. 
Once a submission file has been selected it is validated to ensure that it as not been changed since created.  It is also checked for nest subsites, nest boxes, nest box types and nest pair codes.  If any of the codes present in the file do not exist in the database then a warning message is issued and the import cancelled.  In this case the Control Information from the source database should be exported from there and imported into the current database. Note that this function will only add or update records (places, nest boxes etc) and not propagate deletions or renaming between databases; these operations need to be done manually, but should be rare.
If there are capture records in the Nest Record Submission file and these captures are already present in the database then they will be updated with the Nest Record number of the appropriate nest.
If there are capture records in the Nest Record Submission file, but the Capture records are not already present in the database, these will be imported into the database.  These records can them be re-submitted from the current database, for instance, to BTO HQ.  However, the capture records only contain a subset of the information required by the Ringing Unit and cannot be submitted as a capture submission.  The capture records created from the nest record submission file have a submission code set to NRI (nest record import) and a record type set to `M`.  They can be viewed in Captures Selection, Reporting and Processing, but the records themselves cannot be edited.
If a Captures Import is performed then the captures records will be updated.  A message will appear for each existing nest record import capture record. IPMR will automatically take a note of the nest record number, will replace the record and then update the nest record number of the capture record.	
		Working with Nest records held in IPMR	
		The Nest Selection and Processing function allows nest records to be selected by place, species, year, subsite, box code or submission number. Once the selection criteria have been entered the ‘Run Query’ button should be clicked. The set of records that meet the criteria are then displayed. 	
View or edit Nests, Visits or the Captures from a selected set of nests

Analyse your data		Nest details: The selected nests can be viewed or updated by double-clicking a record, pressing the View button or Choosing the Edit/Edit Record menu item; the first nest displayed will be the nest that is selected in the list. If the record has already been submitted a warning button displayed. If the button is clicked it will be flagged for resubmission.
Visit Details: The Visits of all selected records (starting with those for the selected nest) can be edited by clicking on the View Visits button
Capture selection: The Captures associated with the selected nest can be viewed by clicking on the View Captures button. This function uses a modified version of the Capture Selection and Processing form
Export data: An export function allows the selected records to be written to a comma-delimited file. The fields exported can be selected from a menu option. 
Tabulation queries: Using the Report menu item cross-tabulations can be generated into a report. This is a powerful reporting facility allowing you to report on say counts or averages of one field tabulated by up to two others. The cross-tabulation is saved as a query that can be used by the Report Manager or to be exported into a file that you can put into a spreadsheet, for instance.	
On-line help	
         		Pressing F1 from within IPMR will take you into the on-line help relevant to the screen that you are using. The Help menu options to start from the Contents page or the help Search facility can be used.	

System Requirements and Installation	
	IPMR v2 requires a 32-bit Windows operating system (95/98/me/NT/2000) based PC. IPMR has been designed for a screen resolution of 800x600, which is normal for SVGA; lower (or higher) resolutions can be used. The minimum configuration is a 300MHz Pentium processor with 64MB RAM, but the more the better. Higher specification PCs are recommended particularly if the database is to hold large numbers of records i.e. greater than 100,000. The maximum size of database will depend on processor speed, the amount of memory installed and the patience of the operator. The initial installation requires about 25MB of disk space.	
	Diskette or CD install
There is a single CD (bot no diskette option). To install IPMR insert the CD. 
•	Windows 95/98NT/2000 users should Click on Start and then Run. In the Open: box type d:\setup and click OK or press the enter key (assuming the your CD is assigned to the d: drive).	
	Web Site Download install
To download the Complete IPMR System use the Complete IPMR System link available from the IPMR Internet Web site that can currently be found at http://www.bto.org. This should then give you an option to save the file. You should set the saving location to be “Desktop”.
You should then Open (execute) the downloaded file. This can be done from the Windows Desktop using the mouse you can either double-click the file name or click the right-hand button the file name and select Open from the shortcut menu. You should take the option to overwrite any existing files. 	
	Setup	
	The installation program provides guidance on the install process and allows for the selection of a target folder for the IPMR application. It is recommended that you take the default values as it is then easier to support you if problems arise.
If you use IPMR at work then there may be restrictions imposed on whether you can install new programs onto your PC.  In this case you may need to use a Windows logon with Administrator privileges to run the installation.	
	After IPMR is installed the IPMR Installation and Maintenance program must be started. At this time the folders or directories that IPMR uses for its databases and input and output files can be changed. By default your database will be put into you’re My Documents\IPMR folder, but this may vary depending upon how you have Windows set up. (If you have upgraded from IPMR v1 then the data folder will still be C:\IPMR\DATA). The Data folder must be a different folder from the application folder selected earlier in the install process; it can only be moved (e.g. putting it in another drive, such as D:\IPMR\DATA) using the IPMR Installation and Maintenance program.	
	IPMR’s other options can be entered at this point using the IPMR Installation and Maintenance or they can be set later using the Options function within IPMR. Use File/Exit from the menu to exit IPMR Installation and Maintenance.	
	After Installation	
	There are two program icons generated by the install process:	
	•	IPM Reporter is used to start IPMR.	
	•	The install program uses Installation and Maintenance initially, if the databases need to be moved to a new data folder, to upgrade databases to a new version or if they become corrupted.	
	Upgrading from IPMR v1 to IPMR v2	
	DO NOT ATTEMPT TO UPGRADE TO IPMR V2 AND CHANGE PC AT THE SAME TIME.
Upgrades to IPMR v2 are distributed using a setup program called ipmr97.exe. These are available from the BTO Web site that can currently be found at http://www.bto.org. To download the new IPMR release click on the Latest release link. This will give an option to save the file. Set the saving location to be “Desktop”	
	You should then Open (execute) the downloaded file. This can be done from the Windows Desktop by double-clicking the file name or clicking the right-hand button the file name and select Open from the shortcut menu. 
You MUST then reboot Windows otherwise IPMR may not function correctly and any database upgrade may fail.
The IPMR application is installed into c:\Program Files\Ipmr97 and the runtime Access programs into c:\Program Files\Access 97 Runtime.  Your databases will still be in the same Folder as for IPMR v1 (c:\ipmr\data by default).	
	If you have been using a previous version of IPMR then any databases may need to be upgraded. First ensure that you have a backup of the database file in case problems occur. Then start the Installation and Maintenance program. Under the File menu item there is an Upgrade option. This entry should be selected. This will present a list of your database(s) from which you should select one and click on the Upgrade button. This will then open your database and display a button entitled “Upgrade to Current Database Version” which should be clicked. A confirmatory message will be displayed after the upgrade process. You should then restart your computer before using IPMR.	
	Upgrading from one IPMR v2 release to another	
	Upgrades to IPMR v2 are distributed using a setup program called ipmr97upgrade.exe. These are available from the BTO Web site that can currently be found at http://www.bto.org. To download the new IPMR release click on the Latest release link. This will give an option to save the file. Set the saving location to “Desktop”.	
	You should then Open (execute) the downloaded file. This can be done from the Windows Desktop by double-clicking the file name or clicking the right-hand button the file name and select Open from the shortcut menu.
The IPMR upgrade must be installed into the IPMR Application folder. This was selected when IPMR was first installed and is c:\Program Files\Ipmr97 by default.
You MUST then reboot Windows otherwise IPMR may not function correctly and any database upgrade may fail.	
	Your databases may need to be upgraded. First ensure that you have a backup of the database file in case problems occur. Then start the Installation and Maintenance program. Under the File menu item there is an Upgrade option. This entry should be selected. This will present a list of your database(s) from which you should select one and click on the Upgrade button. This will then open your database and display a button entitled “Upgrade to Current Database Version” which should be clicked. A confirmatory message will be displayed after the upgrade process. You should then restart your computer before using IPMR.	
	Re-installing IPMR on a new PC	
	Before you change the PC
If you are planning to change PC then you should backup copies of your database(s) and also IpmrRefDB.ipm. The databases can be found in the Data Folder set in the Options form (by default this is c:\ipmr\data\).  IpmrRefDB.ipm is held in the Application Folder (c:\Program Files\Ipmr97 by default).
DO NOT ATTEMPT TO UPGRADE TO IPMR V2 AND CHANGE PC AT THE SAME TIME.
Re-installing IPMR
IPMR should be installed from CD or ipmr97.EXE download. 
You will create a dummy database which you will delete again later.  Start IPMR Installation and Maintenance. When asked for the database name you should choose say DUMMY. Go into Control>Options and make a note of Application and Data Folders.
Exit Installation and Maintenance, but do not start IPMR yet.
Copy your databases back to the Data Folder and IpmrRefDB.ipm to the Application Folder. 
Start IPMR. This will Attach your DUMMY database.  Select File> Select Database from the menu bar.  Click on the Attach button and enter the name of your database. Your database name should appear on the List box on the form. Repeat this for any other databases you have. If you are installing the same version of IPMR then click on your database name and then click on the Select button. Once successfully selected you can click on the DUMMY database name and click the Delete button.
If you are installing a later release of IPMR then use Installation and Maintenance to upgrade your databases between the Attach and Select steps mentioned in the previous paragraph.
Appendix - IPMR use for non-BTO UK ringing
If you are licenced to use IPMR for non-BTO UK recording then a copy of the IPMR Reference database will be made and associated with your IPMR database. It will be named the same as your database name with REF97.MDB appended e.g. if your database was FOREIGN then the reference database would be FOREIGNREF97.mdb.
The Own Ringing Scheme value on the Owner form should be set to the ringing scheme under which the database will operate.
Most of the tables within this database will be the same for BTO and non-BTO use.  However, there are a number that will need to change to operate effectively. These are summarised below.  The maintenance of these tables can be performed using Access 97 directly or using the File> IPMR Tables and Queries function which has update, import and export facilities available for these tables. 
If the ringing scheme is retained as GBT for BTO ringing abroad then only the Country Codes and species tables can be changed.  
Country codes	The column headed GBT should have an S for the countries in which you operate. Having set this the Default Country code should be set in Control> Options.

RingPrefix	This table must contain the prefix for all valid ring sequnces that you will use. So for a ring sequence KK00001-KK99999 the PREFIX characters are KK the Other Digits is 5 as there are five numerics and the Ring Size is A. This information is different to your Ring Series that you have it is just used to validate the ring series entered are valid and to set the ring size. Use of the table is mandatory.

RingSize	All rows in this table could be deleted in which case no ring size checking will be performed.  If ring size checking is required then for each SPECies code at least one row is required. For a species using just one ringsize irrespective of age or sex SEX should be set to MFU and AGE to AP and the SIZE code surrounded by / characters e.g. /A/. Multiple ring sizes are denoted e.g. /A/A2/. If Adults take A and Pulli B then two rews are required with AGE for one being A with /A/ for SIZE and the seconf row with P for AGE and /B/ for SIZE. Both rows would have SPEC value and SEX of MFU. The SEX column is used similarly with U being for Unknown sex.

Species	The Species table contains all of the species codes and names and their schedule 1 & 2 status. (This and the following two have changed in IPMRv2.1). New species that you add should be copied from the Extra Species table.  The Extra Species table is not used in IPMR, but contains over 9000 species with their scientific names and Sibley Monroe species codes. Ensuring that the SM codes are maintained will allow data to be transferred between ringers operating within different schemes. These records can be exported from Captures Selection and processing with SM Species codes. 

SpeciesDetails 	The Species Details table contains more detailed information such as biometrics for 202 commoner species.  The SpeciesDetails table isn`t mandatory, but certain functions such as biometrics checking, age specific and year end totals will not work without it. RingPrefix	This table must contain the prefix for all valid ring sequences that you will use. This table should not be changed for BTO scheme rings. So for a ring sequence KK00001-KK99999 the PREFIX characters are KK the Other Digits is 5 as there are five numerics and the Ring Size is A. This information is different to your Ring Series that you have it is just used to validate the ring series entered are valid and to set the ring size. Use of the table is mandatory.

SpeciesAgeChecking	This, optional, table contains the age codes applicable to species for each month in the year.  The Age codes must be separated by the / character.