Data validation: Difference between revisions

From Biolovision Help
Jump to navigation Jump to search
No edit summary
No edit summary
 
(22 intermediate revisions by 2 users not shown)
Line 1: Line 1:
In such system, data quality is important!
<languages/>
<translate>
<!--T:1-->
<br/>


Errors occurs!
<!--T:2-->
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:<br/>
<br/>


Entering a wrong specie, choosing the wrong line in the list, confusing some species that are very similar, having an exceptionnal observation that need more information...
<!--T:3-->
:*'''Automatic validation'''<br/>
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. <br/>
<br/>


To ensure quality of the data, we have two systems to validate it on areas where a local portal exist only.
<!--T:4-->
::: '''Blue dot:''' 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). <br/>
::: '''Yellow dot:''' 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).<br/>
::: '''Red dot:''' 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.<br/>
<br/>


NB: For NaturaList, the flter occurs only when the data is synchronised, not before:  
<!--T:5-->
:*'''Manual validation:'''<br/>


-Automatic filter
<!--T:6-->
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. <br/>
<br/>


Locally settled by administrator of the Local portal. If an observation is done outside the limits sets, a yellow or blue mark is automatically set.
<!--T:7-->
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. <br/>
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.<br/>
<br/>


-Manual filter:
<!--T:8-->
<center>
<table border="5" width="700px">
<tr>
<td style="padding: 25px; text-align: left; font-family: sans-serif; color: black; background-color: hsl(201, 100%, 89%)">
<!-- GREEN BOX (Tips): hsl(157, 74%, 80%)
YELLOW BOX (Summaries): #ffffdb"
BLUE BOX (Information): hsl(201, 100%, 89%)
RED BOX (Warnings):  hsl(0, 77%, 78%) -->


Many validators work to enhance the data quality. If one of them see something that need to be verified, he will put manually a yellow or blue mark.
<!--T:9-->
<p>
<ul>
<b>NOTE: </b><br />
*When data is submitted through NaturaList, filters apply at synchronisation.<br/>
*Data submitted from areas with no local partner is not validated.
</ul></p>


Please consider the work of each of them and stay polite and human when answering!
<!--T:10-->
</td></tr></table>
</center>
<br />
<br />


After verification, or the specie is approved and the mark is removed, or the observation is rejected and a red mark is set You can delete the data or keep it only for you and the mark will stay and indicate that others don't see it.<center>
<!--T:11-->
<table border="1" width="90%" ;>
<center>
<table border="1" width="75%" ;>


<!--T:12-->
<tr style="padding: 25px; text-align: center; font-family: sans serif; color: black; background-color: LightGray">
<tr style="padding: 25px; text-align: center; font-family: sans serif; color: black; background-color: LightGray">
<th>Automatic</th>
<th></th>
<th>Manual</th>
<th>Automatic filter</th>
<th>Need a formula</th>
<th>Manual filter</th>
<th>Answer by email</th>
<th>Visible to other users</th>
<th>Add comment</th>
<th>Action needed</th>
 
<!--T:13-->
</tr>
</tr>


<tr style="padding: 25px; text-align: center; font-family: sans-serif; color: black; background-color: white; border="></tr>
<!--T:14-->
 
<tr style="padding: 25px; text-align: center; font-family: sans-serif; color: black; background-color: white;"></tr>
 
<tr style="padding: 25px; text-align: center; font-family: sans-serif; color: black; background-color: white;"></tr>
 
<tr style="padding: 25px; text-align: center; font-family: sans-serif; color: black; background-color: white;"></tr>
 
<tr style="padding: 25px; text-align: center; font-family: sans-serif; color: black; background-color: white;"></tr>
 
<tr style="padding: 25px; text-align: center; font-family: sans-serif; color: black; background-color: white;"></tr>
 
<tr style="padding: 25px; text-align: center; font-family: sans-serif; color: black; background-color: white;"></tr>
 
<tr style="padding: 25px; text-align: center; font-family: sans-serif; color: black; background-color: white;"></tr>
 
<tr style="padding: 25px; text-align: center; font-family: sans-serif; color: black; background-color: white;"></tr>
 
<tr style="padding: 25px; text-align: center; font-family: sans-serif; color: black; background-color: white;"></tr>
 
<tr style="padding: 25px; text-align: center; font-family: sans-serif; color: black; background-color: white;"></tr>
 
<tr style="padding: 25px; text-align: center; font-family: sans-serif; color: black; background-color: white;"></tr>
 
<tr style="padding: 25px; text-align: center; font-family: sans-serif; color: black; background-color: white;"></tr>
 
<tr style="padding: 25px; text-align: center; font-family: sans-serif; color: black; background-color: white;"></tr>
 
<tr style="padding: 25px; text-align: center; font-family: sans-serif; color: black; background-color: white;"></tr>
 
<tr style="padding: 25px; text-align: center; font-family: sans-serif; color: black; background-color: white;"></tr>
 
</table>
</center>
 
 
<center>
<table border="1" width="70%" ;>
 
<tr style="padding: 25px; text-align: center; font-family: sans-serif; color: black; background-color: white; border=">
<tr style="padding: 25px; text-align: center; font-family: sans-serif; color: black; background-color: white; border=">
<td>[[File:Capture 2022-12-12 at 20.20.19.png|650px|frameless|center]]</td>
<td>[[File:Capture 2022-12-12 at 20.20.19.png|650px|frameless|center]]</td>
<td>Atomatic filter, differs from one area to another.<br />
<td style="color:green">YES</td>
Manual filter when there is an incongruency of data (ex. name and picture do not match).<br />
<td style="color:green">YES</td>
Visible to all users.</td>
<td style="color:green">YES</td>
 
<td style="color:green">YES</td>
</tr>
</tr>


<tr style="padding: 25px; text-align: center; font-family: sans-serif; color: black; background-color: white; border=">
<!--T:15-->
<tr style="padding: 25px; text-align: center; font-family: sans-serif; color: black; background-color: white;">
<td>[[File:Capture 2022-12-12 at 20.20.27.png|700px|frameless|center]]</td>
<td>[[File:Capture 2022-12-12 at 20.20.27.png|700px|frameless|center]]</td>
<td>Requires additional information. <br />
<td style="color:green">YES</td>
Visible to observer and administrators only. </td>
<td style="color:green">YES</td>
 
<td style="color:red">NO<sup>1</sup></td>
<td style="color:green">YES</td>
</tr>
</tr>


<!--T:16-->
<tr style="padding: 25px; text-align: center; font-family: sans-serif; color: black; background-color: white;">
<tr style="padding: 25px; text-align: center; font-family: sans-serif; color: black; background-color: white;">
<td>[[File:Capture 2022-12-12 at 20.20.38.png|700px|frameless|center]]</td>
<td>[[File:Capture 2022-12-12 at 20.20.38.png|700px|frameless|center]]</td>
<td>Invalid data. It will not be used. <br />
<td style="color:red">NO</td>
Visible only to observer.</td>
<td style="color:green">YES</td>
<td style="color:red">NO<sup>1</sup></td>
<td style="color:red">NO</td>
</tr>


<!--T:17-->
<tr style="padding: 25px; text-align: center; font-family: sans-serif; color: black; background-color: white;">
<td>[[File:Capture 2023-03-02 at 14.51.33.png|700px|frameless|center]]</td>
<td style="color:green">YES</td>
<td style="color:green">YES</td>
<td style="color:green">YES</td>
<td style="color:green">YES<sup>2</sup></td>
</tr>
</tr>


<!--T:18-->
</table>
</table>
</center>
</center>
<!--T:19-->
<p style="margin-left: 130px; font-size:10pt">
<sup>1</sup> Visible to observer and administrators.<br/>
<sup>2</sup> Opens Rarity Committee Module.<br/></p>
<br/>
<!--T:20-->
After verification, an observation may be:<br/>
:-Accepted: a green tick appears next to the dot indicating the record has been accepted.<br/>
:-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.<br/>
<br/>
<!--T:21-->
===Homologation by the Rarity Committee===
<br/>
<!--T:22-->
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 > [[Modules#Rarity_Comitee_(RC)_Module|Rarity Committee Module]].<br/>
<br/>
<!--T:23-->
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. <br/>
<!--T:24-->
See all rarity committees in Europe at [http://www.aerc.eu www.aerc.eu].<br/>
<br/>
</translate>

Latest revision as of 12:25, 17 June 2023

Other languages:


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:

  • 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.

Blue dot: 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).
Yellow dot: 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).
Red dot: 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.

    NOTE:
    • When data is submitted through NaturaList, filters apply at synchronisation.
    • Data submitted from areas with no local partner is not validated.



Automatic filter Manual filter Visible to other users Action needed
Capture 2022-12-12 at 20.20.19.png
YES YES YES YES
Capture 2022-12-12 at 20.20.27.png
YES YES NO1 YES
Capture 2022-12-12 at 20.20.38.png
NO YES NO1 NO
Capture 2023-03-02 at 14.51.33.png
YES YES YES YES2

1 Visible to observer and administrators.
2 Opens Rarity Committee Module.


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.