We have made this website as easy for you to use as possible and included help bubbles () to most functions.
There are lots of features on this website and we hope you’ll enjoy exploring it!
Hereafter we provide some guidance on how you may use it.
To search or browse the list of species included in the website, click «Taxa information» on the navigation banner.
A search interface as well as the full list of species then appears.
You may then either:
Once you have found your favourite species, just click on its name to move to its dedicated web page, which contains info about its taxonomy, biology, distribution etc. as well as some pictures.
To search on specimens included in the website, simply click «Search on database» on the navigation banner.
A search interface then appears.
You can search on specimens using (part of) their collection number, the taxon they belong to or their sampling locality.
Once your search is completed simply click on the code of the specimen or in the information button to move to its dedicated webpage, which contains info about its taxonomy, sampling locality (link to Google Earth) etc. as well as some pictures and link to available DNA sequences.
First you need to check the box next to the specimens you are interested in (to select all specimens check the box next to the column headers). Then click «Lis » (just above the column headers), «Add selection to list» and press «OK» in the popup window.
It is possible to include more specimens to the current list by searching on other criteria, select resulting specimens and again « Add [your new] selection to list »
Once your list is created click on «List» > «List Management».
A window appears on which you can select the information you are interested in, just move the items from the left to the right table by clicking the arrows. Once you are happy with your selection, press «Next». You can export the data in word or excel format.
This tool allows to compare your query sequence to all sequences present in our database (including those that are not yet published). You can perform a BLAST of a query sequence against the pool of reference sequences included in our database. It is also possible to view the query sequence embedded within a phylogenetic tree (distance methods, e.g. Neighbor joining) and check to which sequences of the database it is the most closely related.
The barcode gene used for PhylAphid@base is a 648 base-pair region in the mitochondrial cytochrome c oxidase 1 gene (“COI”, standard barcode fragment http://www.barcodeoflife.org). To use the identification tool you therefore need to get sequences for the same gene region.
PCR primers and protocols are available in these two publications:
Of course the longer and cleaner is the sequence, the more accurate the identification will be!
Perform identification (BLAST / tree)
Click « BLAST» on the navigation banner
Paste your query sequence in the dedicated box
Change BLAST parameters if needed (though default parameters must be adequate)
Read the disclaimer… and check the box if you agree
Then, Start the alignment
Results are sorted by BLAST hits (best BLAST scores), i.e sequences included in the database that are the most similar (Similarity%) over a certain length of coverage (Overlap%) to your query sequences are on top.
You can click on any specimen of the hit table to reach its specific webpage and then get further information on the species it belongs to.
You can export the BLAST hits table is you whish to either excel of word files.
Some details regarding BLAST algorithm: Using specific scoring matrices (derived from the pairwise sequence alignment parameters), the BLAST algorithm calculates similarity scores for local alignments (i.e. the most similar regions of the sequences) between your query sequence and sequences that are included in the database. The algorithm then returns a table which shows the best hits (matches) from the database sorted by BLAST Score. This table includes other information including e.g. the query coverage (percentage of the query sequence that overlaps the reference sequence), and the percentage of similarity between the query and reference sequences over the length of the coverage area.
For further information you may have a look to the NCBI Handbook
It is also possible to view the query sequence embedded within a phylogenetic tree (distance methods, e.g. Neighbor joining) and check to which sequences of the database the query is the most closely related.
To do so, click Draw Tree (above the BLAST hits table) and choose the method you want to use. On the resulting tree, your query sequence is labelled as « My Data ». Here again, you can click on any specimen of the tree to be redirected to its specific webpage.
Be careful when interpreting the results. A high percentage of similarity over a long alignment length does not necessarily means your query sequence belongs to the same species as the specimen from which the reference sequence has been obtained. Some cases of mitochondrial introgression have been reported in certain groups; some species are in fact species complexes, which are difficult to distinguish genetically.
This is why, in many cases, we provided sequences of other gene fragments to allow a more accurate identification.
In the case of aphids, intra-specific divergence is generally very low (close to 0) and inter-specific divergences are much higher.
We recommend considering identification as valid only if the percentage of similarity (Similarity%) is equal or higher than 99% and the percentage of overlap (Overlap%) reaches at least 90%.
Numerous species groups are known in aphids. These groups are morphologically and genetically very close, though they are biologically well characterized. BLAST may be non-informative in those cases. Indeed, BLAST of your query sequence may result in high and similar scores with specimens belonging to different species (all belonging to the same species group). If you have some data about host plants it could be possible to refine the results of the identification. Anyway, if you obtain such a result, we highly recommend to read the webpage dedicated to the species to get more information on them and have a look to the companion paper of this website:
Coeur d’acier A., Cruaud A., Robert V., Artige E., Genson G., Pierre E., SimonJ-C., Jousselin E., Rasplus J-Y.(2014) DNA barcoding and associate PhylAphidB@se website for the identification of European Aphids (Insecta: Hemiptera: Aphididae), PLOS ONE.
If you use the database in a publication, please cite: Coeur d'acier et al. (2014). DNA barcoding and the Associated PhylAphidB@se Website for the identification of European Aphids (Insecta: Hemiptera: Aphididae). Plos One, 9 (6). doi: 10.1371/journal.pone.0097620
The French Ministry of Agriculture, Nature and Food Quality has carefully compiled the information on this website. The Ministry however is not responsible for the correctness and completeness of the information supplied. The Ministry cannot be held liable for any damage that occur as a result of the use of this information. In addition, you cannot claim any rights in relation to this information. The Ministry is not responsible for the content of externally-linked web pages.
FEEDBACK: Send a mail to help us improve the database by letting us know if you come across an error (misidentification of specimens, mislabelling of photos ..).
COPYRIGHT: Coeur d'acier et al. (2014). DNA barcoding and the Associated PhylAphidB@se Website for the identification of European Aphids (Insecta: Hemiptera: Aphididae). Plos One, 9 (6) to use the database in a publication. DOI:10.1371/journal.pone.0097620
Website built using BioloMICS Software.
If you would like to know more about cookies and how they work, please visit www.allaboutcookies.org.
1. Table-columns-strains_2: contains the list of columns that must be displayed (when changed by the end-user) when searching Strains_2 table views (this is there to keep the preferences of the end-users; It will not be present if the end-user has not changed this option).
2. Queries-layout-strains_2: contains the list of queries that have been done by the end-user when searching Strains_2 table views (this is there to keep the preferences of the end-users; It will not be present if the end-user has not changed this option).
3. Table-columns- strains_3: contains the list of columns that must be displayed (when changed by the end-user) when searching strains_3 table views (this is there to keep the preferences of the end-users; It will not be present if the end-user has not changed this option).
4. Queries-layout- strains_3: contains the list of queries that have been done by the end-user when searching strains_3 table views (this is there to keep the preferences of the end-users; It will not be present if the end-user has not changed this option).
5. Table-columns-Open%20collection: contains the list of columns that must be displayed (when changed by the end-user) when searching 20collection table views (this is there to keep the preferences of the end-users; It will not be present if the end-user has not changed this option).
6. Queries-layout- 20collection: contains the list of queries that have been done by the end-user when searching 20collection table views (this is there to keep the preferences of the end-users; It will not be present if the end-user has not changed this option).
7. List-display: keeps the end-user preference in terms of display format (either results in grid or results looking like a Google format) (this is there to keep the preferences of the end-users; It will not be present if the end-user has not changed this option).
8. SearchState: this keeps the information about the last query and the page number where the end-user was the last time he/she did a query.
9. ASP.NET_SessionId: this is an automatic cookie that keeps the unique session ID number to be used on the server side. This is deleted when session is finished/expired.
10. last-query-layout-Open%20collection and similar, contain the last query done by the end-user on the Open%20collection table view. This is used when first reloading the page. It is replaced each time there is a query done.
11. _utma, _utmb, _utmc, _utmd, etc are Google analytics cookies to analyze web traffic (see https://helpful.knobs-dials.com/index.php/Utma,_utmb,_utmz_cookies).
Cookies mentioned in the last point are Google analytics cookies that are IP anonymized which means that we cannot trace single users. See below for more information.
No other cookies than the ones mentioned above are used on our websites.
Google cookies and technologies
Google Analytics: These cookies allow us to see information on user website activities including, but not limited to page views, source and time spent on a website. The information is depersonalized and is displayed as numbers, meaning it cannot be traced back to individuals. This will help to protect your privacy. Using Google Analytics, we can see what content is popular on our websites.
You can prevent the information generated by the Google cookie about your use of our Sites from being collected and processed by Google in the future by downloading and installing Google Analytics Opt-out Browser Add-on for your current web browser. This Add-on is available at http://tools.google.com/dlpage/gaoptout.