Search by property

This page provides a simple browsing interface for finding entities described by a property and a named value. Other available search interfaces include the page property search, and the ask query builder.

List of results

• abcd2:NamedCollectionOrSurvey  + (Note that this element refers to the name accepted by the specimen or data holding institution and this may or may not be different from the project name given under {{{Gathering}}}.)
• abcd2:TaxonIdentified-HigherTaxonRank  + (Note that this is not the abbreviation for a rank that is used in a botanical infraspecific name, as it appears in the name.)
• abcd2:IdentificationSource  + (Note that this is not the literature (e.g. key) used to obtain the identification result (see IdentificationReferences).)
• abcd2:Identification-ISODateTimeBegin  + (Note that this is the most commonly used element here. If it is impossible to map (because the db values are not in an ISO string format or the internal db date datatype), one has to use the {{{DateText}}} element (AbcdConcept0383).)
• abcd2:Sequence  + (Note that this is used in the context of a collection unit and thus automatically refers to that unit.)
• abcd2:Synecology  + (Note that this relationship can be recorde …
  Note that this relationship can be recorded as a feature of the location (e.g. a syntaxon, or certain species known to grow together at the site). It can also be used to record an observed relationship (e.g. caterpillar and observed food plant, parasite and host etc.), but this would be better expressed as a unit association.
  be better expressed as a unit association.)
• abcd2:Gathering-DateTime-TimeOfDayBegin  + (Note that time can also be expressed in the {{{ISODateTimeElement}}}.)
• abcd2:MultiMediaObjects  + (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).)
• abcd2:MultiMediaObject  + (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).)
• abcd2:Gathering-Altitude  + (Note the difference from the {{{Height}}} and {{{Depth}}} elements, which are measured relative to a local surface.)
• abcd2:Identification-References  + (Note: this is not the citation from which an identification was taken, see under Identifier/Identification-Source.)
• abcd2:Identification-Reference  + (Note: this is not the citation from which an identification was taken, see under {{{Identifier/IdentificationSource}}}.)
• ggbn:permitURI  + (One will eventually need a direct link to [[ggbnvoc:IRCC | IRCC]] in the future.)
• biorel:derives from  + (Original definition from OBO_REL: "instanc …
  Original definition from OBO_REL: "instance level derives_from holds between distinct material continuants when one succeeds the other across a temporal divide in such a way that at least a biologically significant portion of the matter of the earlier continuant is inherited by the later"
  lier continuant is inherited by the later")
• biorel:develops from  + (Original note in RO: "This is the transiti …
  Original note in RO: "This is the transitive form of the develops from relation. "x" develops from "y" if and only if either (a) "x" directly develops from "y" or (b) there exists some "z" such that "x" directly develops from "z" and "z" develops from "y""
  velops from "z" and "z" develops from "y"")
• biorel:adjacent to  + (Original note in RO: "x adjacent to y if and only if x and y share a boundary" - it is not entirely clear how this is differentiated from [[biorel:connected to]])
• biorel:develops from part of  + (Original note in RO: "x develops from part of y if and only if there exists some z such that x develops from z and z is part of y")
• biorel:surrounded by  + (Original note in RO: "x surrounded_by y if and only if x is adjacent to y and for every region r that is adjacent to x, r overlaps y")
• biorel:has habitat  + (Original note in RO: Note: x 'has habitat' …
  Original note in RO: Note: x 'has habitat' y if and only if: x is an organism, y is a habitat, and x is specially adapted (either naturally or via artifical selection) to living in y. Here 'living in' encompasses the majority of the animal's lifespan. (Note: adapted for 'living in').
  lifespan. (Note: adapted for 'living in').)
• biorel:connected to  + (Original note in RO: X connected_to Y if and only if X and Y share a flat boundary)
• biorel:overlaps  + (Original note in RO: x overlaps y if and only if there exists some z such that x has part z and z part of y)
• ggbn:materialSampleType  + (Please use preparationType for further specification such as 'leg','blood','gDNA','axenic culture','whole genome library','environmental barcoding library', 'Reduced representation sequencing library'. Equal to KindOfUnit in ABCD!)
• ggbn:permitType  + (Predefined vocabulary! See [[ggbnvoc:permitType_vocabulary | permitType vocabulary]])
• ggbn:quality  + (Predefined vocabulary! See: [[ggbnvoc:quality_vocabulary | quality vocabulary]])
• ggbn:permitStatus  + (Predefined vocabulary, See [[ggbnvoc:permitStatus_vocabulary | permitStatus vocabulary]]; entry of data is mandatory)

• abcd2:TaxonIdentified-CombinationAuthorTeamAndYear  + (Purely optional under the zoological code.)

• germplasm:biologicalStatus  + (Recommended best practice is to follow a controlled vocabulary, such as the code list defined by the MCPD term, SAMPSTAT.)
• dcterms:relation  + (Recommended best practice is to identify t …
  Recommended best practice is to identify the related resource by means of a string conforming to a formal identification system. This term is intended to be used with non-literal values as defined in the DCMI Abstract Model (http://dublincore.org/documents/abstract-model/). As of December 2007, the DCMI Usage Board is seeking a way to express this intention with a formal range declaration.
  intention with a formal range declaration.)
• dc:relation  + (Recommended best practice is to identify t …
  Recommended best practice is to identify the related resource by means of a string conforming to a formal identification system. A second property with the same name as this property has been declared in the dcterms: namespace (http://purl.org/dc/terms/). See the Introduction to the document "DCMI Metadata Terms" (http://dublincore.org/documents/dcmi-terms/) for an explanation.
  documents/dcmi-terms/) for an explanation.)
• dc:identifier  + (Recommended best practice is to identify t …
  Recommended best practice is to identify the resource by means of a string conforming to a formal identification system. A second property with the same name as this property has been declared in the dcterms: namespace (http://purl.org/dc/terms/). See the Introduction to the document "DCMI Metadata Terms" (http://dublincore.org/documents/dcmi-terms/) for an explanation.
  documents/dcmi-terms/) for an explanation.)
• dc:language  + (Recommended best practice is to use a cont …
  Recommended best practice is to use a controlled vocabulary such as RFC 4646 [RFC4646]. A second property with the same name as this property has been declared in the dcterms: namespace (http://purl.org/dc/terms/). See the Introduction to the document "DCMI Metadata Terms" (http://dublincore.org/documents/dcmi-terms/) for an explanation.
  documents/dcmi-terms/) for an explanation.)
• dc:type  + (Recommended best practice is to use a cont …
  Recommended best practice is to use a controlled vocabulary such as the DCMI Type Vocabulary [DCMITYPE]. To describe the file format, physical medium, or dimensions of the resource, use the Format element. A second property with the same name as this property has been declared in the dcterms: namespace (http://purl.org/dc/terms/). See the Introduction to the document "DCMI Metadata Terms" (http://dublincore.org/documents/dcmi-terms/) for an explanation.
  documents/dcmi-terms/) for an explanation.)
• dcterms:bibliographicCitation  + (Recommended practice is to include sufficient bibliographic detail to identify the resource as unambiguously as possible.)
• ggbn:blocked  + (Records/samples/specimens not to be published should be blocked on database level. If they are available via Darwin Core or ABCD, they are visible for everyone. This element is to be used for samples/specimens that cannot be loaned.)
• dwc:associatedReferences  + (Remark by GGBN: Material Transfer Agreements (MTAs))
• dwc:ResourceRelationship  + (Resources can be thought of as identifiabl …
  Resources can be thought of as identifiable records or instances of classes and may include, but need not be limited to Occurrences, Organisms, MaterialSamples, Events, Locations, GeologicalContexts, Identifications, or Taxa. Example: An instance of an Organism is the mother of another instance of an Organism.
  mother of another instance of an Organism.)
• abcd2:SourceInstitutionID  + (Reviewed OK)
• tp:taxon-name-part  + (Scientific names are latinized Bi- or Trin …
  Scientific names are latinized Bi- or Trinomen including a species epithet and genus name or infraspecific epithet, species epithet and genus name respectively. Higher level categories have names that are latinized and in some cases with a given ending, eg -idae for family level names in zoology. There is no defined number of hierarchical levels.
  no defined number of hierarchical levels.)
• abcd2:Unit-Owner-Organisation-Text  + (So far, for these pages I have been using …
  So far, for these pages I have been using the term "unit". Should it be "unit record" or something else? <br/><br/>$$Yael$$ Here, we should speak of Unit record; the same is true for the IPR Statements (next item in the schema diagram). I thought I got these things more or less right in the explanations on the unit-level, but found some exeptions (will change in the schema, too): <br/><br/>The following should be "unit record" instead of Unit: <br/>Unit Content Contacts, .. subtypes of the unit (2 cases), Associations, Assemblages <br/><br/>The following should be "unit" instead of Sampling Unit (a term not to be used):<br/>Gathering<br/><br/>The following are correctly termed Unit: <br/>Source Reference, Unit References, Identifications, Kind Of Unit, Multi Media Object, Named Collection Or Surveys, Measurements Or Facts, Sex, Age, Sequences.
  easurements Or Facts, Sex, Age, Sequences.)
• dc:coverage  + (Spatial topic and spatial applicability ma …
  Spatial topic and spatial applicability may be a named place or a location specified by its geographic coordinates. Temporal topic may be a named period, date, or date range. A jurisdiction may be a named administrative entity or a geographic place to which the resource applies. Recommended best practice is to use a controlled vocabulary such as the Thesaurus of Geographic Names [TGN]. Where appropriate, named places or time periods can be used in preference to numeric identifiers such as sets of coordinates or date ranges. A second property with the same name as this property has been declared in the dcterms: namespace (http://purl.org/dc/terms/). See the Introduction to the document "DCMI Metadata Terms" (http://dublincore.org/documents/dcmi-terms/) for an explanation.
  documents/dcmi-terms/) for an explanation.)
• dcterms:coverage  + (Spatial topic and spatial applicability ma …
  Spatial topic and spatial applicability may be a named place or a location specified by its geographic coordinates. Temporal topic may be a named period, date, or date range. A jurisdiction may be a named administrative entity or a geographic place to which the resource applies. Recommended best practice is to use a controlled vocabulary such as the Thesaurus of Geographic Names [TGN]. Where appropriate, named places or time periods can be used in preference to numeric identifiers such as sets of coordinates or date ranges.
  uch as sets of coordinates or date ranges.)
• dwc:continent  + (Standard continents and their codes can be found at http://en.wikipedia.org/wiki/List_of_countries_by_continent_(data_file). See [[dcterms:Location]] for further discussion of geographic terms.)
• dwc:taxonomicStatus  + (The GBIF recommended controlled value voca …
  The GBIF recommended controlled value vocabulary can be found at http://rs.gbif.org/vocabulary/gbif/taxonomic_status.xml and includes the following: <table border="1"> <tr> <td>'''Value'''</td> <td>'''Comment'''</td> </tr> <tr> <td>accepted</td> <td>botanical</td> </tr> <tr> <td>valid</td> <td>zoological</td> </tr> <tr> <td>synonym</td> <td>unknown if homo- or heterotypic</td> </tr> <tr> <td>homotypic synonym</td> <td>objective</td> </tr> <tr> <td>heterotypic synonym</td> <td>subjective</td> </tr> <tr> <td>proParteSynonym</td> <td>some series members assigned to new type</td> </tr> <tr> <td>misapplied</td> <td></td> </tr> </table> See also the discussion at http://vocabularies.gbif.org/vocabularies/taxonomic_status.
  es.gbif.org/vocabularies/taxonomic_status.)
• dwc:taxonRank  + (The GBIF recommended controlled value voca …
  The GBIF recommended controlled value vocabulary can be found at http://rs.gbif.org/vocabulary/gbif/rank.xml and includes the following (English, followed by Latin in parentheses): kingdom (regnum) <br /> subkingdom (subregnum) division or phylum (divisio or phylum) <br /> subdivision or subphylum (subdivisio or subphylum) <br /> class (classis) <br /> subclass (subclassis) <br /> order (ordo) <br /> suborder (subordo) <br /> family (familia) <br /> subfamily (subfamilia) <br /> tribe (tribus) <br /> subtribe (subtribus) <br /> genus (genus) <br /> subgenus (subgenus) <br /> section (sectio) <br /> subsection (subsectio) <br /> series (series) <br /> subseries (subseries) <br /> species (species) <br /> subspecies (subspecies) <br /> variety (varietas) <br /> subvariety (subvarietas) <br /> form (forma) <br /> subform (subforma) <br /> See also the discussion at http://vocabularies.gbif.org/vocabularies/taxonomic_status.
  es.gbif.org/vocabularies/taxonomic_status.)
• dwc:nomenclaturalCode  + (The GBIF recommended controlled value voca …
  The GBIF recommended controlled value vocabulary can be found at http://rs.gbif.org/vocabulary/gbif/nomenclatural_code.xml and includes the following: BioCode <br /> ICBN (International Code of Botanical Nomenclature) <br /> ICNB (International Code of Nomenclature of Bacteria) <br /> ICNCP (International Code of Nomenclature for Cultivated Plants) <br /> ICZN (International Code of Zoological Nomenclature) <br /> ICVCN (International Code of Virus Classifications and Nomenclature) <br /> Combinations of codes for ambiregnal names should be made by concatenating the codes, separated by a semi-colon (';'). Example: "ICZN; ICBN" See also the discussion at http://vocabularies.gbif.org/vocabularies/nomeclaturalCode.
  es.gbif.org/vocabularies/nomeclaturalCode.)
• abcd2:SpecimenUnit-NomenclaturalTypeDesignation-TypeStatus  + (The application of an enumeration (control …
  The application of an enumeration (controlled vocabulary) for this element has to be evaluated. However, a free text field is clearly necessary to accommodate existing datasets, as shown by the following list of terms (supplied by Charles Hussey as the contents found in databases at the NHM in London): [(Syn)type (?); Allotype; Allotypes; Cotype; Cotype (?); Cotype (see note); Cotype Genotype; Cotype(s); Cotype(s) (see note); Cotypes; Cotypes (see note); former syntypic material (?); Holotype; Holotype (?); Holotype (?), desig. Lectotype; Holotype (allotype attached); Holotype (dubious); Holotype + Paratype; Holotype + Paratypes; Holotype Allotype; Holotype Allotype Paratypes; Holotype and 2 Paratypes; Holotype and 6 Paratypes; Holotype and Paratype; Holotype and Paratypes; Holotype and young phase; Holotype Paratype; Holotype Paratypes; Holotype Paratypes (2); Idiotypes; includes Holotype(?)(1881.10.26.117); Lectotype; Lectotype (?) syntypic material; Lectotype + 2 Paralectotypes; Lectotype + Paralectotype; Lectotype and Paralectotypes; Neotype; Neotype and Paraneotype; Paralectotype; Paralectotype(s); Paralectotypes; Paratype; Paratype (?); Paratype (see note); Paratype Topotype (?); Paratype(s); Paratypes; Paratypes (?); Paratypes (of S. pseudobrowniana); Paratypes (see note); Para[lecto]type; Para[lecto]type(s); Para[lecto]types; Parelectotype; part of type series; parts of Syntype; parts of Syntypes; Possible syntypic material; Referred material; Referred specimen in type desc; Syntype; Syntype (?); Syntype (dubious); Syntype (may be holotype); Syntype (see notes); Syntype fragment; Syntype(s); Syntypes; Syntypes (?); Syntypes (see note); syntypic material (dubious); Topotype; Topotype(s); Topotypes; Topotypes (see note)];
  type(s); Topotypes; Topotypes (see note)];)
• rdfs:Class  + (The class of classes.)
• rdfs:isDefinedBy  + (The definition of the subject resource. It points to the authoritative information about the resource (which are not necessarily RDF, often html, and in some cases PDF).)
• biorel:produces  + (The delimitation between and production process (from very basic substances) and a transformation process (from more complex precursor substances) is weak and difficult to delineate, when in doubt this relation may cover both.)
• biorel:produced by  + (The delimitation between and production process (from very basic substances) and a transformation process (from more complex precursor substances) is weak and difficult to delineate, when in doubt this relation may cover both.)
• dc:source  + (The described resource may be derived from …
  The described resource may be derived from the related resource in whole or in part. Recommended best practice is to identify the related resource by means of a string conforming to a formal identification system. A second property with the same name as this property has been declared in the dcterms: namespace (http://purl.org/dc/terms/). See the Introduction to the document "DCMI Metadata Terms" (http://dublincore.org/documents/dcmi-terms/) for an explanation.
  documents/dcmi-terms/) for an explanation.)