ENSCOBASE: the ENSCONET Virtual Seed Bank

How to use the ENSCONET database

The ENSCONET database offers 5 kind of searches:

1. by taxon
2. by geographical area
3. by germination
4. by conservation status
5. by any kind of fields
(complex search)

Help for importing data

Synonyms (if any) are listed in all searches.


1. Search by Taxon


This menu allows the user to look for ENSCONET accessions by taxon name, genus, family or division.

When searching a taxon name, authorities should not be entered and cases are insensitive.

After clicking the "Search" button, the number of accessions stored for this taxon is displayed as well as the full name of the taxon.

Clicking the taxon link redirects the user to another window displaying taxonomic and threat status information :

Taxonomic information:
- Synonyms
- Vernacular names
- Flora Europaea taxonomy
- IPNI taxonomy
- BGCI Plant Search
- Distribution (EUNIS)
- Literature and Storage (SID)
- Images (Google Image)

Threat Status information:
- overall Europe (BGCI European Threatened Taxa List)
- in Bio-geographical regions (IUCN categories)

Clicking the accessions number redirects the user to the accessions list and clicking on an accession redirects the user to seed information gathered within 8 tabs:

- Seed Lot : complete data of the seed accession
- Verification & Vouchers : seed lot verification details
- Geocode : information about the geographic coordinates related to the collecting event
- Collecting information : information about the collectors who got involved into the collecting event
- Habitat : information about the habitat from which the seed lot have been collected
- Moisture content tests : information about seed moisture content tests (if any) carried out on the seed lot
- Germination tests : information about germination tests (if any) carried out on the seed lot
- Recovery Programs : information about any recovery program (if any) undertaken from the germinated accession



2. Search by Geographical area


2.1. Search by Bio-geographical group

Following the EEA 2001 map of bio-geographical regions, 11 regions (Mediterranean has been divided into 2 sub-regions) are recorded in ENSCONET:

- Atlantic
- Anatolian
- Alpine
- Black Sea
- Boreal
- Continental
- Macaronesian
- Mediterranean East
- Mediterranean West
- Pannonian
- Steppic

Click here to get the full list of holdings collected per bio-geographical region.
Please note that only 'W' accessions and 'Z' accessions whose wild accessions of origin are known are included in the country distribution count.

Selecting a bio-geographical group within the drop-down list returns the whole list of taxa and seed accessions which have been collected in this bio-geographical group.

2.2. Search by Country

Click here to get the full list of holdings collected per country.
Please note that only 'W' accessions and 'Z' accessions whose wild accessions of origin are known are included in the country distribution count.

Selecting a country within the drop-down list returns the whole list of seed accessions collected in this country.

2.3. Search by Institution

On Nov. 19 2017, ENSCOBASE holds ex situ seed data of 35 institutions :

Definition of the acronyms:

Acronym Address email Current
ENSCONET
Consortium
member?
1. ATHD Julia & Alexander N. Diomides Botanic Garden. Athens. Greece No
2. BBGK The Balkan Botanic Garden at Kroussia Mountains. Thessaloniki. Greece No
3. BGBM Botanischer Garten und Botanisches Museum Berlin-Dahlem. Berlin. Germany Yes
4. BGM Botanic Garden Meise. Belgium Yes
5. BOKU University of Natural Resources and Life Sciences. Gregor-Mendel-Straße 33. 1180 Vienna, Austria Yes
6. BG-CBDC-PAS Botanical Garden-Center for Biological Diversity Conservation of Polish Academy of Sciences. Warsaw. Poland Yes
7. Canario Jardín Botánico Canario Viera y Clavijo. Las Palmas. Spain Yes
8. CCB Centro Conservazione Biodiversita. University Cagliari. Sardinia. Italy Yes
9. Cordoba Cordoba Botanic Garden. Spain No
10. CYARI Cyprus Agricultural Research Institute. Cyprus. Yes
11. FUL Jardim Botânico - Fundação da Universidade de Lisboa. Portugal Yes
12. Geneva Conservatoire Botanique de Genève. Switzerland Yes
13. GIJON Jardín Botánico Atlántico. Universidad de Oviedo. Gijon. Spain Yes
14. Kostrzyca Kostrzyca Forest Gene Bank. Miłków nr 300. 58-535 Miłków. Poland Yes
15. LUOMUS Finnish Museum of Natural History. University of Helsinki. Finland Yes
16. Luxembourg Luxembourg Botanic Gardens. Luxembourg Yes
17. MAICh Mediterranean Agronomic Institute of Chania. Crete. Greece Yes
18. MNHN Museum National d'Histoire Naturelle. Paris. France Yes
19. NCU Frederick Institute of Technology, Nature Conservation Unit, P.O.Box 24729, 1303 Nicosia. Cyprus Yes
20. NKUA National and Kapodistrian University of Athens. Athens. Greece Yes
21. OEC Conservatoire Botanique National de la Corse. Corsica. France No
22. OSN Botanischer Garten der Universitat Osnabruck Osnabruck. Germany No
23. PAVIA Istituto e Orto Botanico dell'Universita di Pavia. Pavia. Italy Yes
24. Perugia Orto Botanico di Perugia. Perugia. Italy No
25. PISA Istituto de Orto Botanico della Universita. Pisa. Italy Yes
26. RBGK Royal Botanic Gardens. Kew. UK Yes
27. SARC-RIPP Pieštany. Slovak Republic No
28. Soller Jardí Botànic de Sóller. Spain Yes
29. SVGB Suceava Genebank. Romania No
30. TCD Trinity College Dublin Botanic Gardens. Dublin. Ireland No
31. UNICT Department of Biological, Geological and Environmental Sciences. University Catania. Sicily. Italy No
32. UOBG University of Oslo Botanical Garden. Norway Yes
33. UPM Universidad Politécnica de Madrid. Spain Yes
34. UPOL Palacky University, Faculty of Science, Department of Botany in Olomouc. Czech Republic No
35. UVEG Jardí Botànic de la Universitat de València. Spain Yes

3. Search by Germination


Selecting a taxon within the drop-down list returns the whole list of germination tests which have been carried out on this taxon.

Definition of the germination rate:
Depends on the equation of the Mean Time to Germinate (MTG)
MTG: Σ (N x d) / n
Where N is the number of seed germinating between each time interval (d in days) when the germination is recorded and n is the total number of seed germinated in the test.

4. Search by Conservation status



For this search, ENSCONET has used the EEA 2001 map of bio-geographical regions and selected 8 regions :

- Atlantic
- Alpine
- Black Sea
- Boreal
- Continental
- Mediterranean East
- Mediterranean West
- Pannonian

Please note that the West-Mediterranean list has been divided into 2 sub-parts: France-Italy and Portugal-Spain.

4.1. Searching by Taxon threat categories

4.1.1. Searching by IUCN code
Selecting a bio-geographical region and an IUCN code within drop-down lists returns the whole list of taxa and seed accessions which were collected within the selected bio-geographical region and which are classified under the selected IUCN code.
The threat status scores based on the IUCN categories have been calculated as follow:

Threat status (according to IUCN 1978 or 1994 or 2001 or other comparable system) data collated from red lists, either world, national, local or original studies. Scores
CR (incl. EW)-critically endangered (incl. extinct in the wild)4
EN-endangered3
VU-vulnerable2
Other (DD, NT, LC, etc...)-data deficient, near threatened, least concerned1
Not threatened0

The structure of the IUCN categories is explained below:

Categories will be displayed such as:

4.1.2. Searching by ENSCONET-biogroup priority score


ENSCONET has assessed whether the reserves of seed at the moment conserved in European seed banks cover or not, and to what extent, the species currently threatened of extinction in the wild. This analysis was essential to identify if there were gaps in the present holdings and to establish the need of future collections, producing a list of additional target species to collect, with reference to specific regions. ENSCONET agreed that this action would be best carried out on a bioregional basis, establishing specific groups that would deal with this difficult issue regionally.

It is important to note, as stated by IUCN itself, that "the category of threat is not necessarily sufficient to determine priorities for conservation action. The category of threat simply provides an assessment of the extinction risk under current circumstances, whereas a system for assessing priorities for action will include numerous other factors concerning conservation action. (...) However, assessment of taxa using Red List Criteria represents a critical first step in setting priorities for conservation action." (quoted from: Standards & Petitions Working Group. 20061, §2.4 Conservation priorities and actions p.11).

Therefore the two criteria "Threat status"(see part 5.A.) and "Endemicity" have been assessed on a biogeographical level.

Selecting a bio-geographical region and Priority score within the drop-down list returns the whole list of taxa and seed accessions which were collected within the selected bio-geographical region and which are classified under the selected Priority code.
Endemicity rough estimate based on best distribution data available. Scores
Narrow endemic - species with an extremely localised distribution typically occurring in one or few locations not too far apart e.g. a mountain top in the dolomites, a small mediterranean island4
Endemic - species distributed over a wider area with respect to the previous one, typically occurring on part of an homogeneous and continuous geographical unit e.g. the western Alps, Crete3
Subendemic - species distributed over an even wider area with respect to the previous one, typically covering a whole - or nearly so - homogeneous and continuous geographical unit e.g. Alps, Pyrenees2
Not endemic0

4.1.3. Searching ENSCONET taxa in BGCI European Threatened Taxa List

Clicking the link redirects the user to taxa listed in the 2009 BGCI European Threatened Taxa List and stored in ENSCONET seed banks.

4.1.4. Searching ENSCONET taxa in European Habitat Directive List

Clicking the link redirects the user to taxa listed in the 1992 European Habitat Directive List and stored in ENSCONET seed banks.

4.2. Searching by Recovery Programs

4.2.1. Searching taxa recovered by bio-geographical region

The user can browse the taxa recovered by bio-geographical region by selecting a bio-geographical region from the drop-down menu.

4.2.2. Searching all taxa recovered from ENSCONET accessions

Clicking the link redirects the user to the full list of taxa recovered from ENSCONET seed accessions.

5. Complex search


This menu allows searching almost any kind of information through the ENSCONET database. Please be aware that the options offered in this menu are more detailed and technical than the previous 5. This means that the user should know a little bit about the ENSCONET tables/fields and how a query works. This menu will return a list of taxa and accessions which match the query built by up to 3 parameters:

Please note:

- if the query is very general (ie: taxa-genus is not equal to "Acacia"), it will return ALL THE GENERA STORED (minus Acacia), therefore this may take a while!

- whenever possible, values of fields are automatically populated in a value list.

- searches are case insensitive.

Parameter 1:
- First the user has to select a table from a drop-down list storing the tables of the database (e.g. "Geocodes")
- A second drop-down list, fields stored in the selected table, will then appear below. The user has to select a field from this list (e.g. "Country of Origin")
- A third drop-down list of conditions will then appear below. The user has to choose the condition to apply to the query.

If the field selected is an integer or a numeric, the user will choose between:
- "is equal to"
- "is greater than"
- "is less than"
- "is greater than or equal"
- "is less than or equal"
- "is not equal to"

If the field selected is a variable string, the user will choose between:
- "is equal to"
- "is not equal to"
- "contains"
- "does not contain"

For example: (e.g. "is equal to")

- Then, depending on the field selected by the user, an input text box has to be filled in or a drop- down list populated by the values of the database has to be selected. Those inputs fields correspond to the value to be loaded into the query (e.g. "France").

The above query will then become "Geocodes-Country of origin is equal to France"
The user will then either "submit" this query by clicking the "submit" button or add a second Searchable parameter by choosing either "AND" or "OR".

If "AND" is selected, a second drop-down list of tables pops up and the user can repeat the same procedure to add a second parameter to his query (see Parameter 2).

If "OR" is selected, the user has to choose another field from the same table than the first one, a condition and value for the query.

e.g. "Geocodes-Country of Origin is equal to France OR is equal to Belgium"
The user will then submit his query by clicking the "submit" button.

Parameter 2:
The user will follow the same procedure than for Parameter 1 and he will then either submit his query by clicking the "submit" button or add a third Searchable parameter by choosing either "AND" or "OR".

If "AND" is selected, a third drop-down list of tables pops up and the user can repeat the same procedure to add a third parameter to his query (see Parameter 3).

If "OR" is selected, the user has to choose another field from the same table than the second one, a condition and value for the query.

e.g. "Geocodes-Country of Origin is equal to France AND Geocodes-Bioregion is equal to Atlantic OR Geocodes-Bioregion is equal to Alpine"

The user will then submit his query by clicking the "submit" button.

Parameter 3:
The user will follow the same procedure than for Parameter 2 and he will then submit this query by clicking the "submit" button.
e.g. "Geocodes-Country of Origin is equal to France AND Geocodes-Bioregion is equal to Atlantic AND Germinations-Germination Percentage is greater than 80%"



Importing data into ENSCOBASE



A. Introduction

On 30th September 2013 was released the bulk-import service which Partners can use to "bulk upload" their data.
To import data, Partners need two elements:
- institutional URL that only the institute that the URL was created for must access: it is highly recommended to bookmark the URL and the URL must not be shared with other Partners as this would result in data conflicts.
The personal URL is composed of an institute acronym, an underscore and a 16 digits code.
- institutional import templates which are available from the URL. Please note that there are 2 types of templates, i.e. "data-import" (4) and "history" (1):

A.1. Data-import templates
Important: the "Accession template" must be uploaded first so that accessions are stored in the database and further information related to these accessions - contained in templates "Recovery", "Germination" or "Moisture" - can be uploaded in a second step.


- Accession template: to import accessions. This represents the "main" template for uploading accessions. Without it, it will not be possible to upload extra information such recovery, germination or moisture.
- Recovery template: to import recovery programs data. Important note: accessions listed in this import file must have first been imported using the import accession template.
- Germination template: to import germination data. Important note: accessions listed in this import file must have first been imported using the import accession template.
- Moisture template: to import moisture data. Important note: accessions listed in this import file must have first been imported using the import accession template.
Procedures will check accession_id contained in your accession.txt file, row by row. If an accession is already stored in ENSCOBASE, the procedure will keep the accession and update all the fields from the values contained in your file. If the accession does not exist, it will insert it in ENSCOBASE.


A.2. History template
This template is used for any accession which does no longer exist "physically" in a seed bank (for example, the entire material has been used for propagation). ENSCOBASE will not delete these accessions but will mark them as "History" ("H" value will be stored the availability field). The reason for not deleting the accessions is because extra information may be linked to it, such as germination tests or recovery programs and deleting the accession would also delete these linked data. A "History" accession is clearly marked as such when browsing it. Please note that "History" accessions are not counted in the overall analysis of your current holdings in http://enscobase.maich.gr/data_information.tml



B. Details of templates

B.1. Accession template
B.1.1. Mandatory fields for template "Accession"
A total of 14 fields are mandatory and must be filled in for each accession.


1. Accession ID
2. Availability for order
3. Collecting date
4. Banking date
5. Bio-geographical group of collection
6. Country of collection
7. Division
8. Family
9. Genus
10. Species Epithet
11. Species Author
12. Verification Date
13. Verification Level
14. Provenance type flag


B.1.2 Structure
The accession template:
- must be a tab-delimited file
- must be called Instiution acronym + underscore+ accession .txt. For example: TCD_accession.txt. The list of the accessions and acronyms can be found here: http://enscobase.maich.gr/help.tml#geo
- must contain a header with (first row) with the names of the fields which are listed below. Please refer to find out more information about the fields in the ENSCONET Conceptual schema available from http://ensconet.maich.gr/Database.htm :

Fields also must follow this exact order:
1. Accession ID

Syntax: Accession ID must be in the format: Institution Acronym Underscore Number, e.g. TCD_0123456789


2. Availability for order

We interpret availability as availability for all sorts of non-commercial research and conservation purposes, including recovery and restoration programmes thereby contributing to the second part of GSPC target 8.
To be declared "available", accessions should be available in sufficient quantity - or ready to be bulked up, with maximum genetic diversity and of known provenance.
Syntax:
- 'Y': i.e. yes: available for order
- 'N': i.e. no: not available for order
- 'H': historical accessions, i.e. accessions which no longer exist in a seed bank (availability = 'N' de facto)


3. Collecting date

Syntax:
Must be in format YYYYMMDD (e.g. 20130824) or YYYYMM00 (e.g. 20130800) or YYYY0000 (e.g. 20130000).


4. Donation date

Syntax:
Must be in format YYYYMMDD (e.g. 20130824) or YYYYMM00 (e.g. 20130800) or YYYY0000 (e.g. 20130000).


5. Banking date

Syntax:
Must be in format YYYYMMDD (e.g. 20130824) or YYYYMM00 (e.g. 20130800) or YYYY0000 (e.g. 20130000).


6. Biogeographical group of collection

The European bio-geographical region where the accession was collected.
If the value of Provenance Type Flag is "Z", the value of this field becomes the same as the original wild accession ID.
Syntax: Alpine, Anatolian, Arctic, Atlantic, Black Sea, Boreal, Continental, Macaronesian, East-Mediterranean, West-Mediterranean or Pannonian.
http://www.eea.europa.eu/data-and-maps/figures/biogeographical-regions-in-europe
The limit between West- and East-Mediterranean is France (West) and Italy (East).


7. Country of collection

The European country where the accession was collected.
Syntax: must be one of the countries listed in : http://enscobase.maich.gr/total_country.tml


8. Division

Syntax: "Angiosperm", "Gymnosperm" or "Fern or Fern Ally"


9. Family

Very Important note about Taxonomy:
In the absence of a European Native Plant checklist, it was not possible to check any new taxon being imported. Therefore there will be no control on the quality and the accuracy of the taxa imported. Therefore this can lead to "wrong" taxa being imported into the database. Therefore please make sure that all taxa that you insert are native of Europe (no Washingtonia, Datura etc...).


10. Genus

Very Important note about Taxonomy:
In the absence of a European Native Plant checklist, it was not possible to check any new taxon being imported. Therefore there will be no control on the quality and the accuracy of the taxa imported. Therefore this can lead to "wrong" taxa being imported into the database. Therefore please make sure that all taxa that you insert are native of Europe (no Washingtonia, Datura etc...).


11. Interspecific Hybrid Flag

A field to indicate if the Species Epithet field refers to a hybrid.
Syntax:
H - i.e. A hybrid formula for an Interspecific hybrid
x - i.e. A Nothotaxon name for an Interspecific hybrid
+ - i.e. An Interspecific graft hybrid or graft chimaera


12. Species Epithet

Very Important note about Taxonomy:
In the absence of a European Native Plant checklist, it was not possible to check any new taxon being imported. Therefore there will be no control on the quality and the accuracy of the taxa imported. Therefore this can lead to "wrong" taxa being imported into the database. Therefore please make sure that all taxa that you insert are native of Europe (no Washingtonia, Datura etc...).


13. Species Author
14. Infraspecific Rank1

Syntax:
Should be f. or subsp. or var.


15. Infraspecific Epithet1

Very Important note about Taxonomy:
In the absence of a European Native Plant checklist, it was not possible to check any new taxon being imported. Therefore there will be no control on the quality and the accuracy of the taxa imported. Therefore this can lead to "wrong" taxa being imported into the database. Therefore please make sure that all taxa that you insert are native of Europe (no Washingtonia, Datura etc...).


16. Infraspecific Author1
17. Infraspecific Rank2

Syntax:
Should be f. or var.


18. Infraspecific Epithet2

Very Important note about Taxonomy:
In the absence of a European Native Plant checklist, it was not possible to check any new taxon being imported. Therefore there will be no control on the quality and the accuracy of the taxa imported. Therefore this can lead to "wrong" taxa being imported into the database. Therefore please make sure that all taxa that you insert are native of Europe (no Washingtonia, Datura etc...).


19. Infraspecific Author2
20. Verification Date

Syntax:
Must be in format YYYYMMDD (e.g. 20130824) or YYYYMM00 (e.g. 20130800) or YYYY0000 (e.g. 20130000).


21. Verification Level

Syntax: "0" or "1" or "2" or "3" or "4", where:
- 0: Collector Identification, to be verified
- 1: Determined by comparison with other named plants
- 2: Determined by a taxonomist or other competent person using the facilities of a library and/or herbarium, or other documented living material
- 3: Determined by a taxonomist who is currently or has been recently involved in a revision of the family or genus
- 4: The plant represents all or part of the type material on which the name was based, or the plant has been derived therefore by asexual propagation


22. Rank Qualified Flag

The lowest name/epithet of the taxon qualified by the entry in field Identification Qualifier field (see below).
Syntax:
- "Below Family"
- "Family"
- "Genus"
- "Species"
- "first Infraspecific Epithet"
- "second Infraspecific Epithet"


23. Identification Qualifier

A standard term to qualify the identification of the taxon when doubts have arisen while comparing the plant and the plant description.
Syntax:
aff. - i.e. "akin to or bordering"
cf. - i.e. "compare with"
forsan - i.e. "perhaps"
near - i.e. "close to"


24. Provenance type flag

Syntax: "W", "Z", "G" or "U", where:
W: Accession of wild source
Z: Propagule from a wild source plant in cultivation
Z: Propagule from a garden origin
U: Insufficient data to determine wild source or propagule in cultivation


25. Propagation history flag

A code to indicate the nature of the production of the plant material being accessioned, for use in association with the previous field, Provenance Type Flag. If the value of Provenance Type Flag is "Z", this field becomes mandatory.
Syntax:
S - i.e. Plant material arising from sexual reproduction (excluding apomixis)
SA - i.e. From open breeding
SB - i.e. From controlled breeding
SC - i.e. From plants that are isolated and definitely self-pollinated
VB - i.e. From apomictic cloning (agamospermy)
U - i.e. Propagation history uncertain, or no information.


26. Wild accession ID lineage (for Z accessions)

Syntax: If the value of Provenance Type Flag is "Z" and the seed accession comes from plants derived from an accession that has been banked, then this field becomes mandatory and should have the original wild accession ID from which the Z accession has been propagated.


27. Original seed quantity

Syntax:
Integer field: number without a decimal component, e.g. 21.


28. Date original seed quantity counted

Syntax:
Must be in format YYYYMMDD (e.g. 20130824) or YYYYMM00 (e.g. 20130800) or YYYY0000 (e.g. 20130000).


29. Current_seed_quantity

Syntax:
Integer field: number without a decimal component, e.g. 21.


30. Date current seed quantity counted

Syntax:
Must be in format YYYYMMDD (e.g. 20130824) or YYYYMM00 (e.g. 20130800) or YYYY0000 (e.g. 20130000).


31. Average 1000 Seed Weight

Syntax:
Numeric value of the weight of 1000 seeds in grams, e.g. 21.05 or 4.6


32. Number seed full

Syntax:
Integer field: number without a decimal component, e.g. 21.


33. Number seed part_full

Syntax:
Integer field: number without a decimal component, e.g. 21.


34. Number seed empty

Syntax:
Integer field: number without a decimal component, e.g. 21.


35. Number seed infested

Syntax:
Integer field: number without a decimal component, e.g. 21.


36. Method used to determine state of seed

Syntax:
Integer field: number without a decimal component, e.g. 21.


37. Collecting notes
38. ISO code

The 2-letter code for the Country from where the seeds have been collected, using the codes assigned by the International Standards Organisation (ISO 3166).
http://en.wikipedia.org/wiki/ISO_3166-1 target="_blank">http://en.wikipedia.org/wiki/ISO_3166-1


39. World geographic scheme

A location code from the World Geographical Scheme for Recording Plant Distributions by S. Hollis and R.K. Brummitt.


40. Country primary subdivision of collection
41. Country secondary subdivision of collection
42. Specific geographic unit of collection
43. Locality of collection
44. Altitude of collection

Syntax:
Numeric field which can be written with a decimal component, e.g., 21.0 .


45. Altitude accuracy

Syntax:
Numeric field which can be written with a decimal component, e.g., 21.0 .


46. Altitude determination method

The method used to determine the Altitude.
Syntax:
- Altimeter
- DEM
- GPS
- Field estimate
- Map
- Unknown


47. Latitude degrees

Syntax:
Integer field: number without a decimal component, e.g. 21.


48. Latitude minutes

Syntax:
Integer field: number without a decimal component, e.g. 21.


49. Latitude seconds

Syntax:
Numeric field which can be written with a decimal component, e.g., 21.0 .


50. Latitude direction

Syntax:
Must consist of one of the letters 'N' or 'S' (for North or South).


51. Longitude degrees

Syntax:
Integer field: number without a decimal component, e.g. 21.


52. Longitude minutes

Syntax:
Integer field: number without a decimal component, e.g. 21.


53. Longitude seconds

Syntax:
Numeric field which can be written with a decimal component, e.g., 21.0 .


54. Longitude direction

Syntax:
Must consist of one of the letters 'E' or 'W' (for East or West).


55. Spatial grid projection
56. Map datum
57. Geocode accuracy
58. Geocode source
59. Geocode determination method

The Method used for measuring the Geocode.
Syntax:
- GPS
- DGPS
- Estimate
- Map
- Unknown


60. Number plants found

Syntax:
Integer field: number without a decimal component, e.g. 21.


61. Number plants sampled

Syntax:
Integer field: number without a decimal component, e.g. 21.


62. Area sampled
63. EUNIS Land Cover Classification
64. Habitat description
65. Land use (Commercial, Leisure, Grazing, Agriculture)
66. Slope

Syntax:
Numeric field which can be written with a decimal component, e.g., 21.0 .


67. Aspect
68. Soil texture
69. Soil ph

Syntax:
Numeric field which can be written with a decimal component, e.g., 21.0 .


70. Soil Sample ID

Syntax:
Text field: '1234' or 'TCD-1234' etc....


71. Habitat depth

Syntax:
Numeric field which can be written with a decimal component, e.g., 21.0 .


72. Habitat conservation status (threats)
73. Site notes
74. Sampling method
75. Seed collected from ground?

Syntax:
"Y" - i.e. yes: collected from ground
"N" - i.e. no: not collected from ground


76. Collection number
77. Mava (Y/N)
"Y" - i.e. yes: collected as part of the MAVA project October 2011-September 2014
"N" - i.e. no: not collected as part of the MAVA project October 2011-September 2014


B.2. Recovery template
B.2.1 Mandatory fields for template "Recovery"
Two fields are mandatory and must be filled in for each recovery test.

1. recovery_testid
2. recovery_accession_id



B.2.2 Structure
Accessions used to carry out recovery programs must first have been uploaded via the Accession template (see B.1). If not the import process will stop and the recovery programs will be rejected.
The recovery template:
- must be a tab-delimited file
- must be called Institution acronym + underscore+ recovery .txt. For example: TCD_recovery.txt. The list of the accessions and acronyms can be found here: http://enscobase.maich.gr/help.tml#geo
- must contain a header with (first row) with the names of the fields which are listed below. Please refer to find out more information about the fields in the ENSCONET Conceptual schema available from http://ensconet.maich.gr/Database.htm :

Fields must follow this exact order:
1. recovery_testid

Syntax: Recovery test ID must be in the format: Institution Acronym Underscore Number. It is composed of the Accession ID and, a dash and a number. For example: TCD_001-1


2. recovery_accession_id

Syntax: Accession ID must be in the format: Institution Acronym Underscore Number, e.g. TCD_0123456789 and must corresponf to an accession ID already stored in ENSCOBASE (if not please use the accession upload template).


3. recovery_date_started

Syntax:
Must be in format YYYYMMDD (e.g. 20130824) or YYYYMM00 (e.g. 20130800) or YYYY0000 (e.g. 20130000).


4. recovery_biogroup

The European bio-geographical region where the recovery program is taking place.
If the value of Provenance Type Flag is "Z", the value of this field becomes the same as the original wild accession ID.
Syntax: Alpine, Anatolian, Arctic, Atlantic, Black Sea, Boreal, Continental, Macaronesian, East-Mediterranean, West-Mediterranean or Pannonian.
http://www.eea.europa.eu/data-and-maps/figures/biogeographical-regions-in-europe
The limit between West- and East-Mediterranean is France (West) and Italy (East).


5. recovery_country

The European country where the recovery program is taking place.
Syntax: must be one of the countries listed in : http://enscobase.maich.gr/total_country.tml


6. rec_notes

Syntax: text



B.3. Germination template
B.3.1 Mandatory fields
A total of 3 fields are mandatory and must be filled in for each germination test.

1. germ_testid
2. germ_accessionid
3. germ_percent


B.3.2 Structure
Accessions used to carry out germination tests must first have been uploaded via the Accession template (see B.1). If not the import process will stop and the recovery programs will be rejected.
The germination template:
- must be a tab-delimited file
- must be called Institution acronym + underscore+ recovery .txt. For example: TCD_germination.txt. The list of the accessions and acronyms can be found here: http://enscobase.maich.gr/help.tml#geo
- must contain a header with (first row) with the names of the fields which are listed below. Please refer to find out more information about the fields in the ENSCONET Conceptual schema available from http://ensconet.maich.gr/Database.htm :
Please refer to find out more information about the fields in the ENSCONET Conceptual schema available from http://ensconet.maich.gr/Database.htm :
Fields must also follow this exact order:
1. germ_testid
2. germ_accessionid

Syntax:
Accession ID must be in the format: Institution Acronym Underscore Number


For example: TCD_001
3. germ_percent

Syntax:
numbers that can be written with a decimal component, for example 21.4


4. germ_rate

Syntax:
numbers that can be written with a decimal component, for example 21.4


5. germ_avail
6. germ_start_date

Syntax:
Must be in format YYYYMMDD (e.g. 20130824) or YYYYMM00 (e.g. 20130800) or YYYY0000 (e.g. 20130000).


7. germ_duration

Syntax:
numbers that can be written with a decimal component, for example 21.4


8. sterilisation
9. scarification
10. pretreat_date

Syntax:
Must be in format YYYYMMDD (e.g. 20130824) or YYYYMM00 (e.g. 20130800) or YYYY0000 (e.g. 20130000).


11. pre1_conditions
12. pre1_temp1

Syntax:
numbers that can be written with a decimal component, for example 21.4


13. pre1_temp2

Syntax:
numbers that can be written with a decimal component, for example 21.4


14. pre1_duration

Syntax:
numbers that can be written with a decimal component, for example 21.4


15. pre1_chemical
16. pre2_conditions
17. pre2_temp1

Syntax:
numbers that can be written with a decimal component, for example 21.4


18. pre2_temp2

Syntax:
numbers that can be written with a decimal component, for example 21.4


19. pre2_duration

Syntax:
numbers that can be written with a decimal component, for example 21.4


20. pre2_chemical
21. pre3_conditions
22. pre3_temp1

Syntax:
numbers that can be written with a decimal component, for example 21.4


23. pre3_temp2

Syntax:
numbers that can be written with a decimal component, for example 21.4


24. pre3_duration

Syntax:
numbers that can be written with a decimal component, for example 21.4


25. pre3_chemical
26. pre4_conditions
27. pre4_temp1

Syntax:
numbers that can be written with a decimal component, for example 21.4


28. pre4_temp2

Syntax:
numbers that can be written with a decimal component, for example 21.4


29. pre4_duration

Syntax:
numbers that can be written with a decimal component, for example 21.4


30. pre4_chemical
31. pre5_conditions
32. pre5_temp1

Syntax:
numbers that can be written with a decimal component, for example 21.4


33. pre5_temp2

Syntax:
numbers that can be written with a decimal component, for example 21.4


34. pre5_duration

Syntax:
numbers that can be written with a decimal component, for example 21.4


35. pre5_chemical
36. germ_medium
37. germ_chemical
38. germ_ph

Syntax:
numbers that can be written with a decimal component, for example 21.4


39. germ_light_temp1

Syntax:
numbers that can be written with a decimal component, for example 21.4


40. germ_light_temp2

Syntax:
numbers that can be written with a decimal component, for example 21.4


41. germ_dark_temp1

Syntax:
numbers that can be written with a decimal component, for example 21.4


42. germ_dark_temp2

Syntax:
numbers that can be written with a decimal component, for example 21.4


43. germ_light_hours

Syntax:
numbers that can be written with a decimal component, for example 21.4


44. germ_dark_hours

Syntax:
numbers that can be written with a decimal component, for example 21.4


45. nb_sown

Syntax:
numbers that can be written without a fractional or decimal component. For example: 21.


46. nb_germ

Syntax:
numbers that can be written without a fractional or decimal component. For example: 21.


47. nb_empty

Syntax:
numbers that can be written without a fractional or decimal component. For example: 21.


48. nb_infest

Syntax:
numbers that can be written without a fractional or decimal component. For example: 21.


49. nb_abnorm

Syntax:
numbers that can be written without a fractional or decimal component. For example: 21.


50. nb_dead

Syntax:
numbers that can be written without a fractional or decimal component. For example: 21.


51. nb_unimb

Syntax:
numbers that can be written without a fractional or decimal component. For example: 21.


52. germ_notes

B.4. Moisture template
B.4.1 Structure
Accessions used to carry out recovery programs must first have been uploaded via the Accession template (see B.1). If not the import process will stop and the recovery programs will be rejected.
The moisture template:
- must be a tab-delimited file
- must be called Institution acronym + underscore+ recovery .txt. For example: TCD_moisture.txt. The list of the accessions and acronyms can be found here: http://enscobase.maich.gr/help.tml#geo
- must contain a header with (first row) with the names of the fields which are listed below. Please refer to find out more information about the fields in the ENSCONET Conceptual schema available from http://ensconet.maich.gr/Database.htm :
Fields must also follow this exact order:
moist_testid
moist_accid
moist_percent
moist_method
moist_date
moist_temperature
moist_sample

B.4.2 Mandatory fields
A total of 3 fields are mandatory and must be filled in for each recovery test.

1. moist_testid
2. moist_accid
3. moist_percent



B.4.3 Rules of syntax
B.4.3.1. Accession ID
Field Accession ID must be in the format: Institution Acronym Underscore Number
For example: TCD_001
B.4.3.2. Date fields
Date fields must be in format YYYYMMDD (e.g. 20130824) or YYYYMM00 (e.g. 20130800) or YYYY0000 (e.g. 20130000). This applies for the fields listed below:
moist_date
B.4.3.3. Integer fields
Integer fields are numbers that can be written without a fractional or decimal component. For example, 21, 4, and -2048 are integers. This applies for the fields listed below:
moist_sample
B.3.3.4. Numeric fields
Numeric fields are numbers that can be written with a fractional or decimal component. For example, 21.0, 4.6, and -3.32 are numerics. This applies for the fields listed below:
moist_temperature

B.5. History template
B.5.1 Structure
This file is composed by the list of the accessions ID currently stored in the ENSCOBASE which will be marked as "History". It is simply a list of accessions, one accession per row. For example:
TCD_001
TCD_002
TCD_003
B.5.2 Mandatory fields
A total of 1 mandatory field:
Accession_id
B.5.3 Rules of syntax
B.5.3.1. Accession ID
Field Accession ID must be in the format: Institution Acronym Underscore Number
For example: TCD_001


For any help or enquiries please contact:
- Data/Information Management & Coordination: Stéphane Rivière
- Technical Lead: Nicolas Boretos
- Project Coordinator: Elinor Breman

Released in October 2009. Last data import: October 2017