Data validation

Errors may occur when typing or identifying species. On occasions, exceptional observations may take place. To ensure the quality of the data in our systems, validation filters are applied when observers submit data. These, search for exceptional data in areas covered by a local portal, and may ask observers to provide more details in order to validate or reject the observation:

Different validation systems exist:
· Public validation
· Automatic validation
· Manual validation

Public validation

Users can flag any observation they consider unusual. It can be done from:
· Search engine,
· The past 5 days, or
· Gallery.

Public validation process is different for registers users and for validators.

Public validation for registered users

When a registered user marks and observation,
· Validators are notified and can then review the observation as usual (see subsection manual validation below).
· A yellow dot appears next to the observation prompting the observer to provide further information. It will only be visible to the observer and validators, but not to the general public or the user flagging it.
· The observer cannot see who flagged the observation.
· The user flagging the observation does not have a follow up. They can only see further changes if accessing the validation history.

1. Select to open the panel.
2. Select the reason for your flagging on the expandable menu.

3. Leave a comment to justify your flagging, if necessary.
4. SEND THE REQUEST.

Public validation for validators

Validators can assign a validation level to an observation and request further details.
Depending on the local portal, it can also include indicating the validity level.

Validation level

avlidators can assign a colour dot to observations. See meaning of dots in subsection Automatic validation below.

1. Select to open the panel.

2. Indicate the reason for flagging the observation.
3. Send a message to the observer.
· The language of the template is determined by the observer's predetermined language on the local portal and is indicated next to the cell.
· The template's name is given in the validator's predetermined language in the local portal.
· Observer name and other information like species, site and date of of the sighting are automatically uploaded when using a template.

4. Select the level of validation. If in doubt, consider opening a discussion by checking the cell.

5. Send the request.

Validity level

When available, besides all the above validators can also assign a validity level to the observation. Levels available differ from country to country.

Available levels are country dependant, but may include:

	Confirmed-very likely: The data is accurate. There is not significant doubt as to the accuracy of the observation or the determination of the taxon. Validation has been carried out notably on the basis of evidence of observation confirming the producer/'s determination, or after verification with the observer and/or determiner.
	Probable: The data has a good level of reliability. It is plausible and credible. There is no reason to doubt the accuracy of the data, but there are not sufficient additional elements available or (notably the presence of proof or the possibility of going back to the source data) to allow a higher level of certainty to be assigned.
	Doubtful: The data is implausible or surprising, but there is insufficient evidence of an obvious error. The data is considered doubtful.
	Invalid: The data has been invalidated (obvious/confirmed error) or is too unreliable. It is considered too improbable (aberrant, particularly with regar to the known range, biotic and abiotic parameters of the taxon/'s ecological niche, evidence reveals a determination error). It is considered invalid.
	Not feasible: The data has undergone the entire validation process, but the operator (human or machine) has been unable to decide on the level of reliability. In particular: insufficient knowledge of the taxon and/or insufficient information on the observation.
	Not rated: Initial or temporary level. The data has not been submitted to the validation operation, or the operation has not yet been completed (validation in progress). It is therefore not evaluated at a precise time defined by the validation date.

Automatic validation

Filter locally set by administrators of the Local portal covering the area the observation takes place at. When an observation falls outside the parameters determined by the local administrators, a yellow or blue mark is automatically displayed next to the observation (see table below for meaning of markings). The observer then receives an automatic e-mail to inform them.

informs caution to other users. There is possibly a mistake in the data (ie. wrong species, or the species is not particularly rare but is often seen at a different altitude or environment).
the observation is probably correct but details need to be confirmed (ie. the species is in the right place, but the number of individuals is uncommon, or the hour the observation took place seems unusual).
the observation has 'been rejected. It means that even if your observation is right, you did not provide enough proof to validate it and it cannot be included in the statistics.

Manual validation

The yellow or blue mark indicating the observation is either incorrect or requires more information, can be displayed manually by an authorised validator. The observer can receive either an automatic or a personalised e-mail informing them.

If you see a marking next to any of your observations, please do check the spam folder if you did not receive an email informing you -your email provider may have filtered the message. Reply to the email and/or correct as requested. Validators will see your corrections and decide if your data is accepted or rejected.
Please, consider the valuable work of validators and stay polite. To become a validator or know more about it, please refer to the local portal the data are linked to.

	Public filter	Automatic filter	Manual filter	Visible to other users	Action needed
	n/a3	YES	YES	YES	YES
	YES	YES	YES	NO1	YES
	n/a3	NO	YES	NO1	NO
	n/a	YES	YES	YES	YES2

¹ Visible to observer and administrators.
² Opens Rarity Committee Module.
³ Only available to validators.

After verification, an observation may be:
· Accepted: a green tick appears next to the dot indicating the record has been accepted.
· Rejected: the yellow or blue marking associated to an observation becomes red. The observation remains at the observer’s list of observations but is invisible to other users.

Homologation by the Rarity Committee

Besides the usual validating process, some exceptional observations may be sent to the local rarities committee for homologation. When this is the case, a module will open asking for additional details. See more about the Rarity Committee Module at Web interface > Modules > Rarity Committee Module.

A Rarity Committee is an independent group of ornithologist evaluating if uncommon observations could be considered for scientific purposes. They are normally concerned about the area and time of the year the observation takes place, and data of first breeding.

See all rarity committees in Europe at www.aerc.eu.