TDWG root element: container for one or more DataSets. A dataset containing unit data and their shared metadata elements. A globally unique identifier for the entire data collection the present dataset was derived from. The exact format and/or semantics are still under discussion. Metadata item normally not used for end-user display. UDDI registry element for GBIF registry. Questions and feedback about availability of a provider or resource should be directed to the technical contact. This contact normally represents the Agent acting as the publisher of the datasets in the network. The element is unbounded to provide for alternative contacts (vacation etc.). UDDI registry element ("AdministrativeContact") for GBIF registry. Questions and feedback about data, or restrictions on use of the data should be directed to the adminstrative contact. This contact normally represents the agent acting as the original supplier or custodian of the dataset. If a content contact is given on the unit-level, that one should be used for end-user purposes. The element is unbounded to provide for alternative contacts (vacation etc.). Other known on-line providers of this dataset. The UUID (identifier in the UDDI registry) of another data provider known to serve this dataset. Metadata referring to the principal source of the entire data collection (the metadata scope may be wider than the objects actually contained in the data set). In its current form, this collection represents a mixture of elements useful for resource discovery (e.g. scope) with metadata actually pertaining to the received (partial) dataset. A container for one or more unit data records from the gathering A container for all data referring to a unit (specimen or observation record) Elements describing the event and site of collecting or observing a unit. A string that identifies all material or records that resulted from a collecting or observation event. Date(s) and time(s) of the collecting or observation event A container element for the agent(s) responsible for collecting or recording. The person, or one of the persons or team(s) or organization(s) responsible for collecting or recording. Attributes: a flag indicating the primary collector, and a sequence number. Free text alternative for individual Agent. Free text details for Agent. Agent organization name and code(s). Agent Person details. Free text representation or concatenated version of those responsible for collecting or recording. A container element for references to (or texts of) permits related to the gathering. Project information concerning the gathering event. Title of collection project Contact details for Project Officer or other person with knowledge of the project. The 'platform' from which observations or collections were made, e.g. the name of a research vessel or a remote operated vehicle. The method (including technical means) used to make the collection or observation. Original locality data as appearing on a label or in an original entry. Details of the country. Separate from NamedArea for compatibility reasons. Atomised place names as applied to the collection or observation site; with possibility for hierarchical structuring and categorization. Atomised place name with possibility for hierarchical structuring. Attribute for sequence. Specified relationship to a named place that does not directly apply to the site of collection or observation, e. g. 10 Km South of Mytown. The nearest named place to the collection or observation location Distance and directional point. Free text description of further details pertaining to the observation, sampling, or collection locality which which did not fit into the previous elements. Spaceholder for GML-conformant schema extension to express the spatial representation of the gathering locality including coordinates, footprint, and uncertainties in GML (Geographical Markup Language). The GML application schema developed by the BioGeomancer Project (see http:\\www.biogeomancer.org) can be used here. Retrieval of a boundary polygon or centroid spatial reference relating to the gathering site. URL (GET) or POST text, for Web Feature Service (OpenGIS Consortium Specification 01-023) reference. URI (e.g. web address) for the location of a boundary polygon or centroid spatial reference relating to a gathering site, according to the Web Map Services (WMS) specification of the Open GIS Consortium Container for multiple sets of coordinates indicating the site of collection or observation. Attributes for Original data and for begin and end of sequence . Composite element to allow recording multiple coordinates or same coordinate in different systems Coordinates measuring system e.g. GPS, field map reference, inferred map reference The numerical Zone corresponding to the central meridian and origin upon which the UTMEasting is based. The Subzone letter corresponding to one of the 20 North-South divisions of the UTM grid system. The hemisphere to which the UTMNorthing refers. An alternative composite text to capture a zone expressed as a combination of UTMZone and UTMSubzone. The distance in meters east of the origin of the UTMZone. The distance in meters north of the origin for the UTMSubzone. Mathematical surface on which the mapping and coordinate system used for the geocodes of the record are based. A alternative composite text to capture unatomized UTM coordinate data. Geospatial coordinates recorded using a grid system Grid system name e.g. "GB OS" Grid reference precision qualifier Element that allows the recording of the latitude and longitude of a recording or collecting position. Could be simplified by converting many of the sub-elements into attributes. Maps to Darwin Core 2: Longitude. Express in decimal degrees Maps to Darwin Core 2: Latitude. Express in decimal degrees Mathematical surface on which the mapping and coordinate system used for the geocodes of the record are based Free text statement of degree of accuracy Maps to Darwin Core 2: Coordinate Precision. An estimate of how tightly the collecting locality was specified; expressed as a distance in meters corresponding to a radius around the Lat/Long coordinates. Use NULL where precision is unknown, cannot be estimated or is not applicable. The altitude of the gathering site land or floor level given as distance above (positive) or below mean sea level. Vertical distance point or range measurement in relation to a ground datum such as water level, or level of the sea floor for benthic samples. Vertical distance measure or range in relation to a ground datum, e.g. ground level. Further measurements or facts taken at the collection locality at the time of collection, e.g. (water-) temperature, slope, weather conditions, etc. Images taken at the Gathering site A container for geological dating and rock unit names related to the site or sample locations An container element for citing biotope type terms (e.g. classification terms) and measurements (e.g. vegetation height, salinity, slope) related to the unit's gathering site Attribute for classification system used. Attribute for type designating ShortName, Long name, Code, or BiotopeText Free text field for informal recording of Biotope A container allowing to linking any biotope-related measurement to the site description Relationship of the unit gathered with other taxa at the gathering site A syntaxon name and category assigned to the gathering site. Free text comment on synecological features of the gathering site. Other taxa observed at the gathering site Other taxon found at the gathering site Facing direction (aspect) of whole site or sample point. Further text referring to the gathering event that does not fit one of the elements specified. The application of a name (or concept), i.e. the data pertaining to an identification event and the result of the identification itself. The result of the identification, currently either a material (substrate) or a taxon name, but in the future to be extended to include other types of identifications used in natural history collections and surveys. The Taxon (concept) or Taxonomic name assigned to the unit (or excluded, "non") in the Identification. A material identified as the result of the identification event (e.g. a non-organismic substrate of a microorganism) A placeholder for a temporary extension to include identification results not yet covered by the schema. This serves to accommodate urgent inter-version additions to the unit-object schema. True to designate current identification. True to designate negative identifications. True to designate the idenfication under which the entire unit is stored (in a physical collection) or otherwise preferrably referenced. Used to designate the role of the identification result (e.g. substrate, isolate, host, parasite, etc.) Atomized record of individual, team member, or organization that made the identification. Atomised data for the parts of the Identifier's name. The Organisation the Identifier is affiliated with, or the Organisation (institution) acting as the identifier. Alternatve text indicating the person, person team, or Organization that made the identification. A reference which has provided the identification (and - if present - the identifier's name and/or organisation). The entire identification event was taken from the literature or comparable source given here. Note that this is not the literature (e.g. key) used to obtain the result (see IdentificationReferences). Indication of the nature of the taxonomic verification; e.g. "conf." or "det." References that were used by the identifier to provide the identification (e.g. by means of providing a key or a description of the taxon). It circumscribes the taxon identified (and thus can act as a potential taxon's sec. reference). Note: this is not the citation from which and identification was taken, see under Identifier/IdentificationSource. A reference (e.g. an article or monograph) that was used as the base for the identifier's taxon identification (e.g. by means of providing a key or a description of the taxon). It circumscribes the taxon identified (and thus can act as a potential taxon's sec. reference). Note: this is not the citation from which and identification was taken, see under Identifier/IdentificationSource. Date of the identification event. The method by which the identification was obtained, e.g. details of molecular analysis or acoustical procedures. Supplementary remarks about the identification. The level to which the identification has been verified. Different standards may use different values here. See ITF-2 for an example. The name and category of an administrative or geoecological area. Allows recording of categories for local or national subdivision levels, geomorphological units, protected areas, etc. Name of a geographic, geomorphological, geoecological, or administrative area. Standard coding scheme the AreaCode adheres to. Abbreviation or code for area names Elements for all unit-level data A globally unique identifier for the unit record. Following DwC, in the absence of a persistent global unique identifier, this should be constructed in the form "URN:catalog:[InstitutionCode]:[CollectionCode]:[CatalogNumber]". Unique identifier (code or name) of the institution holding the original data source (first part of record identifier). In specimen collections, this is normally the institution or private holder of the collection itself. For herbaria and botanical gardens, the standard abbreviations should be used. Name or code of the data source (unique within the institution, second part of the record identifier) A unique identifier for the unit record within the data source. Preferrably, the ID should be stable in the database, so that it also can be used to find the same record again (e.g. for data exchange purposes). Third part of the record identifier. Numeric catalogue number. Facilitates soriting of numbers. Name or other indication of the person or team that created or last edited this record. Date of creation or last change of this unit record. The legal owner of the unit record. Note that ownership of physical specimens is handled under SpecimenUnit. If present, overrides the equivalent Ownders element on the level of dataset. Specific rights, terms and other conditions pertaining to the individual record. If present, override the equivalent statements on the level of dataset. Container element for one to many content contacts for the unit record. If present, overrides the equivalent ContentContact on the level of dataset. Questions and feedback about data, or restrictions on use of the data should be directed to the contact given here. If present, overrides the equivalent ContentContact on the level of dataset. Reference that is the source of the information about the unit given in the record. Container element for references citing the unit See SourceReference for the case that the record is based on a publication. Published reference citing this unit. Container element for identification events, i.e. the circumstances and result of assigning a name to the unit. In cases where more than one name applies to a single unit, several identifications should be formed and flagged as preferred. Relationships between differently identified sub-units of the unit can be specified by means of the IdentificationRole. This is a free text field for use when extracting data from datasources where the identification or verification history (or part of it) is a free text field. In normal circumstances the history can be constructed by sorting identification events by date and reference to the preferred identification flag An indication of what the unit record describes. Note that the element SourceReference provides for the case that the record is based on a publication. Part(s) of organism or class of materials represented by this unit. Physical state-specific subtypes of the unit record A Unit subtype containing data elements specific to specimens (living, fossil, or preserved). The legal owner or holder of the physical specimen Acquisition date, source and type. Textual statement of the date of acquisition of the specimen by the institution Free text field for informal recording of acquisition source details. Type of acquisition. Name of person and/or organisation the unit was acquired from (e.g. depositor of a strain). Accession details. Repeatable triple to accommodate accession number in multiple catalogues. Textual statement of the date on which the accession was recorded. Identifier of an accessions catalogue or numbering scheme which contains the SpecimenUnit The institutional number applied to an accession and recorded in the accessions register. Specimen preparation details, possibly a sequence of preparation steps Specimen preparation details. Description of preparation type. Process used in preparing the specimen. Materials and chemicals used in the preparation of the specimen. Person and/or institution responsible for or effecting the preparation. Label text(s), writing or inscription(s). Label or inscription Text transcription of an inscription Position of inscription, writing or mark. Name of person who created the label, writing or inscription. Summary, interpretation or opinion of the text. References to an image or images of the label or inscription The ID of a multimedia object representing the image of the mark A wrapper for previous units. A container for past ID and location of this specimen. Name or code of collection previously holding this specimen. Identifier of specimen in previous collection. Dates that the specimen was held in previous collection. Any further information about this specimen in its previous collection. An alternative text identifying the previous unit when no ABCD standard ID s can be assigned. Information on the type status of the specimen. The name based on the specimen. Published reference. Full term designating the status. Indication whether the type is conserved or rejected/suppressed by the Code or is proposed for conservation or suppression/rejection Indicator for unverified type status (kind and fact). The person assigning or verifying the type status of the specimen. Date of verification. Further information about the verification process. A free text field to note the known other recipients of a duplicate of the unit, preferrably in the form of a delimited list of SourceInstitionIDs. Data elements specific to observation (recording) units. Note that most observation data items are site related and thus covered under Gathering. Numbers or other registration mark associated with an observation record. Attribute for PreferredFlag. Separated from the equivalent AccessionNumber of specimen collections because of the more standardised approaches taken in physical collections. Collection type and/or taxonomic domain-specific schema extensions (subtypes of the unit record). Data specific to microbial and similar culture methods. Data specific to mycological and lichenological units. Data specific to herbarium specimens (incl. mycological specimens). Data specific to units in botanical live (horticultural) collections. Data specific to units in plant genetic resource collections, e.g. gene banks. Data specific to zoological units. Data specific to palaeontological units. Multimedia objects such as images, movies, etc. relating to (or forming) the unit. Note that RecordBasis should be set accordingly if the multimedia object actually is the unit in the collection (e.g. collections of images taken in the field, sound recordings, etc.). Relationships of this unit record with other unit records in ABCD conformant datasets. A binary relationship or association of units. First part of a fully qualified identifier of a related item's dataset. Second part of a fully qualified identifier of a related item's dataset. Fully qualified identifier of the related item within the specified dataset. Description of the association. Further information about an association. A container for groupings of this unit record with other unit records in this dataset by means of an additional ID. A unit assemblage handles symmetric relationships between several units. Identifier for assemblage. Name of assemblage. Unit may belong to one or several collections or survey projects which have distinctive names and do not correspond to the SourceName. Note that this element refers to the name accepted by the specimen or data holding institution, this may or may not be different from the project name given under Gathering. Elements describing the field events that created the unit and their location. A number assigned to the unit by the collector or observer. Note that the respective collector's name is found under gathering (GatheringAgents). A container for quantitative and categorical measurements (including observations) refering to the unit, e.g. counts, size measurements, colours, etc. Quantitative or categorical measurement refering to the unit. Maps to Darwin Core 2: Sex. Refers to the entire unit, which may be mixed. Note that counts can be provided in the Unit's MeasurementsOrFacts section. Age of the organism at the time of collection or observation. Note that counts for different age classes can be provied in the Unit's MeasurementsOrFacts section. Container for medata on sequences derived from this unit. Miscellaneous notes referring to the unit that do not fit elsewhere. Gives the web address of the page where more information on this particular record (not on the whole dataset) can be found. [OBIS] Annotations in electronic form not (yet) added to the physical specimen. The extension is temporary and serves only to accommodate urgent inter-version additions to the unit-object schema [in future to the the various schemas/objects used in ABCD]. For example, if a specific community (e.g. culture collections) discover that there are elements missing in the current version of ABCD (as they did for 1.2), they communicate that to the group responsible for schema development, where it will be discussed if these elements are already accommodated in the schema, if not, if they can and should be generalized and where they should end up in the schema. IF the culture collection community needs to move rapidly (e.g. due to project pressures), they can add these elements to the current version as an extension schema under a structure that follows SDD's CustomExtensions element (CustomExtensions-CustomExtension-Any ##other). In future modular versions of ABCD, such a structure should exist in the root of every object/schema. A first proposal for this type of data. Note that this is used in the context of a collection unit and thus automatically refers to that unit. E.g. GenBank, SwissProt, etc. Use "Internal" for unpublished sequence. E.g. GenBank accession number. A description of the method used to achive the sequence. Description of the actually sequenced material (DNA/RNA/Protein, Gene or part of gene, completeness, etc.), Reference where the sequence was published. The person and/or organisation responisible and/or effecting the sequencing. Length of the sequence in basepairs Types that may be used for different domains (descriptions, taxonomy, specimen collections, etc.): Many of the types or elements within the types are resulting from attemtps to standardize usage between ABCD and SDD and many originate from Gregor Hagedorn's work on the UBIF schema. However, note that this is work in progress, so there may be considerable differences between types with the same names in UBIF/SDD and ABCD. ============================================================================== Basic generic types normalized string required to contain at least 1 character (this removes the xml string anomaly, i. e. either element/attribute may be optional, but if they are required the content may not be an empty string) normalized string restricted to 1..50 character length to be used for abbreviations (the recommended length of abbreviations is usually much shorter, but 50 characters should be a normalized string restricted to 1..255 character length (i. e. required, may not be empty string) hack annotation system Complex types that add attributes language or preferred to the simple types String, String255, anyURI: String (i. e. xs:string with minimum length=1) extended with language attribute String (i. e. xs:string with minimum length=1) extended with language attribute String255 (i.e. xs:string with length 1-255), extended with language attribute String (i. e. xs:string with minimum length=1) extended with preferred attribute String255 (i.e. xs:string with length 1-255), extended with preferred attribute StringEmpty annotation hack String (i. e. xs:string with minimum length=1) extended with language and preferred attribute String255 (i.e. xs:string with length 1-255), extended with language and preferred attribute xs:anyURI extended with Preferred attribute Date and Time The date and time expressed in a way conforming to a subset of ISO 8601 Temporal aspects of an event or activity. The date in text format The time zone to which the time-of-day data refer The exact date (and time) or beginning of a period, expressed in a modified ISO/ANSI 8601 standard structured format Julian day number in the year for the exact date or for the beginning day of a period Time of day in hours from midnight for an exact point in time or for the beginning of a time period The end of a period expressed in a modified ISO/ANSI 8601 standard structured format The Julian day number of the last day in a period. Time of day in hours from midnight for the end of a time period Set to True if the event takes place for the period indicated, set to false if it occurs at some point of time during the period, not filled if unknown or no period specified. Intellectual Property Rights (IPR) Text, optional Details (both free-form text) and optional URI. A concise representation of a statement, recommended to be as short as possible, but actual length is unconstrained. Optional text of unconstrained length, elaborating details of the ShortText An optional resource on the net providing details on the statement (may be used as an alternative to the long text). A sequence of statements related to Intellectual Property Rights, credit and acknoledgement. Container element for one to several statements, normally representing different language representations of the same content. Used where the IPR declaration cannot be parsed into the specific items or for forms of IPR declaration not yet covered (e.g. database rights), Container element for one to several statements, normally representing different language representations of the same content. Copyright may include the information that the data has been released to the public domain. Container element for one to several statements, normally representing different language representations of the same content. To be used if data are placed under a public license (GPL, GFDL, OpenDocument). Placing data under a public license while maintaining copyright is recommended! Container element for one to several statements, normally representing different language representations of the same content. Defines conditions under which the data may be analised, distributed or changed. "Terms of use" includes concepts like "Usage conditions" and "Specific Restrictions". Container element for one to several statements, normally representing different language representations of the same content. Disclaimer statement, e. g. concerning responsibility for data quality or legal implications. Container element for one to several statements, normally representing different language representations of the same content. A free form text acknowledging support (e. g. grant money, help, permission to reuse published material, etc.) Container element for one to several statements, normally representing different language representations of the same content. Indicates how this dataset or record should be attributed if used [OBIF 1.0] Multimedia Elements to describe digital images, sound recordings, etc. Identifier for the multimedia object. May be a filename. Universal Resource Identifier of the underlying multimedia file, i.e. "naked" path to electronic source of multimedia object (e.g. web address). Universal Resource Identifier of an electronic source of multimedia object including HTML, Javascript or similar means deliver rendered output. The context of the object in relation to the specimen or observation. E.g. image of entire specimen, sound recording the observation is based on, image of original valid publication, etc. Code or descriptive term for file or object format e.g. jpg, pcx, tiff for digital images; 16mm, beta video, AVI, mpg for moving images; transparency, print for photographs etc. Image size in pixels x pixels. Resolution expressed in dots per inch. Size in Kb of the file referred to by URI or filename. Intellectual Property Rights relating specifically to the image. Free text of formatted text (rtf) description of the feature - not controlled length e.g. often a memo field Date the object was created. Identifier, e.g. name or other id, of (technical) personnel who has taken the image. Does not imply copyrights or other rights. Equipment used to create this multimedia object. ## Element under discussion ## See Bob Morris' comments under http://efgblade.cs.umb.edu/twiki/bin/view/BDEI/ColorManagement Picture width in pixel Picture height in pixel Various An abbreviated designation of an institution. A standard designator for the nature of the object of the record. Sex of the organism (Male, Female, Unknown, Not applicable (e.g. for a fungus in a herbarium), MiXed. Published reference. Formal citation for a paper or electronic publication. Specific page, figure or illustration number(s) within the reference. Universal Resource Identifier - Path to electronic source of document. Provides a minimalized local Agent definition. Person, person team, or role name (e. g., 'head of departement') (voice phone) Minimalised local Agent definition with preferred flag Contact Type and types used therein: Contact details. Organisation to contact Person to contact Analogue to vCard:Role: Functional contact name, e.g. "Database administrator", "The Director", etc. Contact addresses (one preferred, different languages possible) Contact address as string. Telephone and fax numbers Telephone or fax number E-mail addresses E-mail address for contact URIs for person or organisation URI for person or organisation URL of a logo image. Full organization or corporate name in multiple languages (en: 'Botanical Garden of ...', de: 'Botanischer Garten von ...'). vCard:Org.OrgName). The Label mechanism also supports acronyms / abbreviations (no vCard equivalent!). If the contact contains no person definition: the unit within the organization the agent represents; else a list of the various organisational units to which a person may belong. (vCard:OrgUnit) (vCard:OrgUnit) Collection of language-specific label representations Language-specific label representation [ATTR: language] Language-specific simple label, using simple formatted text Label text in a specific language. Restricted to 50 characters maximum length, including blanks (recommended to be shorter!). Label abbreviations are especially important when displaying information in a tabular format. Name of an individual person Preferred form of personal name for display as a string. The full name with the elements in preferred sorting sequence (vCard: Sort-String). Family names, generational names, clan name, parents/grandparents personal names, etc. This (= last name in western cultures) may be compound ('Fischer von Waldheim', 'da Selva', 'Silvano Morales'). Depending on culture it is not necessarily the name of the parents nor common to the married couple and children, thus 'family name' should be avoided even though used in vCard. (vCard:N.Family) Prefix to inherited name that should be output before name, but is usually not included in sorting. Examples: 'von', 'Lord'. Compare Title for 'Prof', 'Dr.' (vCard:N.Prefix) Suffix to name that should be output after name, regardless whether it is in sorting sequence (Inherited, Given) or not. Examples: 'Jun.', 'III.'. (vCard:N.Suffix) The name given to a person as a personal name (= first or christian name in western cultures, including 'middle initials') may contain several words ('Ana Maria', 'Jerry B.'). Applicable only to persons. (vCard:N.Given + vCard:N.Middle) May differ from the first given name: second given name, nickname ('Bob' for 'Robert'), etc. (vCard:Nickname) Type of device reached by telephone number, e.g. voice, fax, voice/fax Telephone or Fax number Full number in standard international format Free text for constraints on use e.g. "weekdays only" or "home number" The role of an agent or contact. Elements specific to units from botanical gardens Minimum numbers of individuals the garden is holding under the UnitID. Current status (current or not current) of the accession in the garden. Current location of the living plant in the botanical garden. Type of material the current living accession is composed of. A flag indicating that the accession is grown outdoors in the botanical garden. A code to indicate the provenance of the accession [ITF-2]. A code to indicate the nature of the production of the plant material being accessioned, for use in association with the element ProvenanceCategory [ITF-2] The purpose of this element is to trace the lineage of an accession to either one or two immediate parent unit ID's. A code to indicate the type of the immediate donor from which the accession was obtained. This may not be necessarily the original collector of wild material. [ITF-2] Allows for cultivation information to be passed as free text in order to help the receiving garden care for the transferred accession [ITF-2] or to record the garden's experience made with this accession. The date the plant was planted at its current location in the botanical garden. Allows for information about any propagation requirements to be passed as free text in order to help the receiving garden propagate the transferred accession [ITF-2] or to record the garden's experience made with this accession. A code to indicate the means of perennation, providing a means of noting living plant accessions that require regular curatorial monitoring [ITF-2]. A code to indicate the breeding system of the accession [ITF-2]. Unique number given to plant materials accessioned in conformance with the rules of the International Plant Exchange Network (see http://www.bgci.org/abs/ipen_numbers.html). Elements only used for units in culture collections E.g. "Bacteria" or "Archaea" Variety designation, epithet, authors and reference. This field excludes the pathovar name and the serovar name, which are both infrasubspecific names but are to be entered under Identification/... ../FullScientificName Container element for names under which the culture is known Reference or trade name for a microbial culture Name of a microbial or viral strain. Note that this name may also denote the unique identifier of the record in the collection, in which case it should also be used for UnitID. Name and author of serovar or serotype Name and author of the pathovar. Type and parent of mutant if strain is a mutant strain Names of chromosomal markers of the strain. Especially recommended for strains of species for which many genetically modified strains exist An alternative full text field for culture medium, atmospheric and light conditions, temperature conditions and additional remarks on the cultivation. The growth medium for a microbial or similar culture e.g. agar Preferably a number - attribute gives temperature scale used References for the culture conditions and method or for a description of the strain Attribute for RefType Form in which the strain will be sent to the customer Elements only used for herbarium units Information relating this specimen to an Exsiccatum A list of collection abbreviations of the herbaria duplicates were distributed to The unique institutional loan number applied with the loan sequence number to uniquely identify a specimen on loan [HISPID3]. The sequence of a specimen within a given loan, assigned with the Loan Identification to uniquely identify a specimen on loan [HISPID3] Institution to which the loan is being sent [HISPID3] Name of botanist for whom the loan is destined [HISPID3] The means by which the loan is being despatched from the home institution [HISPID3] The date the loan is prepared and/or sent [HISPID3] Elements only used for mycological units Name of algal or cyanobacterial component of lichen Spore states present in the sample. Spore states present in the sample. Extension for elements only used in plant genetic resource collections. Currently, all elements represent EURISCO descriptors. A designation specific to EURISCO. FAO Institute Code of the institute that has bred the material. ISO 3-letter code for the country where the breeding institute is located. FAO Institute Code of the institute that has collected the material. A name given to the accession that cannot be covered by the name structure given for botanical names under identification (i.e. not a formal cultivar or trade designation name). An alternative concatenated text representation of the Accession Names. FAO Institute Code; the codes consist of the 3-letter ISO 3166 country code of the country where the institute is located plus a three-digit number. Code for the (propagation-)provenance of the unit. Code for the (location-) provenance of the unit. Code for the type of storage of the unit in the collection. Elements only used for palaeontological units Description of the fossil preservation of the specimen. Original, mould, cast etc The sediment or mineral matrix enclosing the fossil Form of mineralisation Life position, allochthonous death assemblage, post mortem history details etc. Known or assumed time range of a fossil Elements expressing stratigraphy at the gathering site. Chronostratigraphic dating term e.g. Jurassic Period biostratigraphic zonation term e.g. Psiloceras planorbis zone lithostratigraphic term describing geology e.g. Mercia Mudstone Group Free text field for informal recording of field contents Elements only used for zoological units Container element for the phase or stage of the individual organism or the organisms present in the unit. Note that counts can be provided in the Unit's MeasurementsOrFacts section. Combined element for phase (e.g. polyp and meduse of the Cnidaria) or stage (juvenile, nauplius, copepodite) of the organism(s) in the unit. Details of the country Name of country or major region for specimen or observation Derived name of country or major region for specimen or observation 2- or 3-letter (ISO3166-1) or 4-letter (ISO3166-3) code for representation of name of country or origin. Orientation, outlook or aspect of slope The direction, orientation or aspect of slope expressed in compass points Orientation or bearing from North Accuracy of aspect reading or estimation Text expression of slope or aspect General purpose measurement and fact (descriptor) recording. Attribution of the measurement to a Person Date and/or Time the measurement was taken Duration of measurement in time. Method used to make measurement. Describes type of measurement or fact, such as width, abundance, circumference, temperature etc. or color etc. Depending on the use of the type, this can further specify the actual part measured. For example, a measurement of temperature may be a surface, air or sub-surface measurement. Lower or only value or fact text. Upper value where there is a range. Unit of measurement. Statement of accuracy of measurement. Reference (publication) where this measurement was taken from Flag indicating if the value represents the numerical result of a quantitative measurement (TRUE) or a descriptor with textual or categorical result (FALSE). Free text alternative to atomised version. Descriptive term. May be taken from a controlled vocabulary maintained by a third party. Subject area of the term list. Descriptive term. If the term has been drawn from a named term list or thesaurus, its name is recorded here. Version or date of the term list or thesaurus from which the term is drawn. Free text comment. LookupType extended with Language attribute Metadata referring to the principal source of the entire data collection (thus the metadata scope may be wider than the objects actually contained in the data set). If a history of the data collection (revised or expanded in various projects or at different institutions) exist, this must be reflected in the IPR statements and possibly in the list of Owners. Dublin Core conformant elements describing the content of the data source queried, representation in different languages possible The description in a specified language. Only one representation should be delivered for each language. [ATTR: language] The URI of an icon/logo symbolizing the project. Keyword lists of geographical, taxonomic, etc. scopes. In the case of projects in progress, 'scope' may define the planned or intended, rather than the achieved scope (or coverage). If scope is given, the content available should be entirely within scope, because this item is for resource discovery purposes. Compare also Coverage in DC.Description (which is language-specific). (Items from Scope may be added to DC.Coverage) A collection of terms describing the geoecological scope of the source queried by means of area names (e.g. 'Worldl', 'Germany', 'Atlantic Ocean', 'Andes', 'Mountains'. A list of recommended terms should be developed. A collection of taxon names of higher rank describing the taxonomic scope of the source queried. A list of recommended terms should be developed. Number and date of current version (particularly for citing purposes) The major version number ('1' in 1.2) as defined by the content creators. An optional minor version number ('2' in 1.2) Unconstrained text specifying status + optional number, e. g., 'beta', 'alpha', 'rc/release candidate', 'internal'. If missing, release status is assumed. Source for Dublin-Core standard element Date.Issued: Citable 'publication date' of the current version (comp. RevisionData/DateCreated and DateModified for version- independent dates). This date should be missing if the current version is not yet published! Creators, Revision status, and dates of the entire data collection from which the current dataset is derived. Entities having legal possession of the data collection content. Here defined for the entire data collection, not for individual units. If an owner statement is present on the unit level, it should override this dataset-level statement. Entitiy having legal possession of the data collection content. Copyright, terms of use, license and other IPR-related statements like disclaimer or acknowledgement. Giving a copyright statement and a (if possible public) licence is highly recommended! (=DC.Rights) Language-specific content metadata (title, description, etc.) with *required* Language attribute added. Source for Dublin-Core standard element "Title": A short, concise title. General Note on DublinCore translation: In addition to those that can bee transformed from UBIF metadata, an additional DC.Type='dataset' should be added. Source for Dublin-Core standard element "Description": Free-form text containing a longer description of the project. Source for Dublin-Core standard element "Coverage": Free-form text describing geographic, taxonomic, or other coverage aspects of terminology or descriptions available in the current project. URL pointing to an online source related to the current project, which may or may not serve an updated version of the description data. RevisionData (creators, dates, revision) for the entire project/data set or individual objects. Source for Dublin-Core standard element "Creators", i.e. Author or editor. Source for Dublin-Core standard element"Contributors": General contributors, or translators. Source for Dublin-Core standard element "Date.Created": Date/time when the intellectual content (project, term, description, etc.) was created. Applications may initially set this to the system date for new data objects, but authors must be able to change it to an earlier date if necessary. If for legacy data this is imprecisely known, it may be missing here. Earlier versions in other data formats should then be mentioned in the copyright or acknowl. statements. Source for Dublin-Core standard element Date.Modified: Date/time when the last modification of the object was made. If in online data sources the provider can not assess this, the current date/time may be substituted. For legacy data this may be set to the file date of imported data, or estimated. Scientific or informal name as a result of an identification. Wrapper element for multiple designations of higher taxa. These are higher-level classifications of the name identified, NOT a higher taxon as the sole identification. The scientific name of a taxon with a rank higher than Genus which is commonly used to classify the group the unit belongs to. Name of the taxon identified, formed according to the different Codes of Nomenclature which apply to scientific names - with additional elements for suffixes or other expressions commonly used in taxonomic identifications. The outcome of an identification event that does not adhere to the rule of a Code of Nomenclature. Any free text comments related to the name The Code of Nomenclature that applies to the scientific name. An atomised name under the International Code of Nomenclature of Bacteria Genus name. Subgenus name. Author team and year of the subgenus name. Species epithet Maps to Darwin Core 2: Subspecies Author team and Year of the basionym of a species or subspecies combination. The author(s) who published the full name as it stands and its year. Approbation of name according to approved list, validation list,or validly published, paper in IJSB after 1980. An atomised scientific name under the International Code of Botanical Nomenclature or the International Code of Nomenclature for Cultivated Plants Genus or higher taxon name. The first epithet in a botanical name combination (species epithet or the epithet of the subdivision of a genus. The final epithet of a botanical name of infraspecific rank. The rank of the name where needed to form it. Flag indicating that this is a named hybrid ("x") or a graft chimaera ("+"). The attribute insertionpoint defines the name element in front of which the qualifier should be inserted (1 = before entire name, 2= before first epithet, 3 = before rank designation for second epithet.) Author team of the basionym of a combination. The author(s) who published the full name as it stands. Cultivar group name Cultivar name according to the ICNCP. Container for trade names Trade name used for a specific cultivar An atomised scientific name under the International Code of Virus Classification and Nomenclature Genus or higher taxon name formed according to the code and representing the result of the identification. E.g. Comovirus. The formal name of a viral species. Examples: vaccinia virus; human herpes virus 2 (herpes simplex virus 2); poliovirus 1; Saccharomyces cerevisiae virus L-A; enterobacteria phage PRD1 [Source: ICTV]. The accepted acronym for the Virus, e.g. PCV for Peanut Clump Virus. An atomised scientific name under the International Code of Zoological Nomenclature Genus or higher taxon name. Subgenus name. Species epithet Maps to Darwin Core 2: Subspecies The first person(s) who validly published a species-group name and the year of publication. The parenthetical citation of the original author when a species-group was transferred to another genus and the year of the original publication. The citation of the authors responsible for the new combination and the year of its publication. Name of the breed of an animal A name element dependent on a genus or a species name under the bacteriological, botanical, and zoological code. A generic or higher taxon name (monomial) under the bacteriological, botanical, viral, and zoological code. A multiplication or plus sign designating a hybrid or draft chimaera in botany. The abbreviation of a taxonomic rank as used in (botanical) name strings. A taxonomic rank designation above the rank of genus. Name of the taxon identified, formed according to the different Codes of Nomenclature which apply to scientific names. Concatenated scientific name, preferrably formed in accordance with a Code of Nomenclature, i. e. a monomial, bionomial, or trinomial plus author(s) or author team(s) and - where relevant - year, or the name of a cultivar or cultivar group, or a hybrid formula, as fully as possible. Atomised data items of the taxon identified, with subtypes according to the different Codes of Nomenclature which apply to scientific names. Atomised name with elements according to the International Code of Nomenclature of Prokaryotes Atomised name with elements according to the International Code of Botanical Nomenclature Atomised name with elements according to the International Code of Zoological Nomenclature Atomised name with elements according to the International Committee on Taxonomy of Viruses Name of the taxon identified, formed according to the different Codes of Nomenclature which apply to scientific names - with additional elements for suffixes or other expressions commonly used in taxonomic identifications. A term to qualify the identification of the unit when doubts have arisen as to its identity (e.g. "cf." or "aff."). If it applies to an atomised name, the attribute insertionpoint defines the name element in front of which the qualifier should be inserted (1 = before entire name, 2= before first epithet, 3 = before second epithet.) A free-text suffix added to the taxon identified (e.g. "sensu lato"), or an additional name element in common use but without formal nomenclatural standing (e.g. Isolate names for viruses). Taxon name used to further classify the identification result. An enumeration of the Codes of Nomenclature