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:PlantGeneticResourcesUnit-DecodedDonorInstitute  +
• abcd2:Gathering-UTMText  +
• abcd2:PreviousUnit-TimeOfDayBegin  + (en:Note that Time can also be expressed in the ISO {{{DateTimeElement}}}.)
• abcd2:ZoologicalUnit-PhasesOrStages  + (en:Note that counts can be provided in the Unit's {{{MeasurementsOrFacts}}} section.)
• abcd2:Age  + (en:Note that counts for different age classes can be provided in the Unit's {{{MeasurementsOrFacts}}} section.)
• abcd2:Annotation  + (en:Note that for annotation labels captured from the specimen there is the SpecimenUnit/Marks structure (AbcdConcept0561).)
• abcd2:TaxonIdentified-HigherTaxon  + (en:Note that if a higher taxon such as a family name is the result of the identification itself, it should (also) be noted under Full-Scientific-Name-String (mandatory) and Genus-Or-Monomial (optional).)
• abcd2:TaxonIdentified-HigherTaxonName  + (en:Note that if a higher taxon such as a family name is the result of the identification itself, it should (also) be noted under Full-Scientific-Name-String (mandatory) and Genus-Or-Monomial (optional).)
• abcd2:CultureCollectionUnit-Strain  + (en:Note that if the strain name is also the unique identifier of the unit in the collection database, this name should also be entered under Unit/UnitID (AbcdConcept0140).)
• abcd2:DataSet-DateModified  + (en:Note that it may well be that the result of the query, i.e. the document containing this datum, does not contain the parts of the souce that have actually been changed.)
• abcd2:SpecimenUnit-DuplicatesDistributedTo  + (en:Note that most observation data items are site related and thus covered under Gathering.)
• abcd2:Unit-Owner  + (en:Note that ownership of physical specimens is handled under SpecimenUnit. If present, overrides the equivalent Owners element on the level of dataset.)
• abcd2:SpecimenUnit-TypifiedName-InfraspecificEpithet  + (en:Note that quadrinomials etc. are not supported here as names; if deemed necessary, they can be entered in the FullScientificNameString, this element should than contain the last infraspecific epithet.)
• abcd2:TaxonIdentified-InfraspecificEpithet  + (en:Note that quadrinomials etc. are not supported here as names; if deemed necessary, they can be entered in the FullScientificNameString, this element should than contain the last infraspecific epithet.)
• abcd2:KindOfUnit  + (en:Note that sex, stages etc. should normally be recorded using the respective elements, but may also end up here if the source database mixes them with other data.)
• abcd2:BotanicalGardenUnit-DonorCategory  + (en:Note that the ITF-Donor field is found under {{{AccessionSource}}} and the Donor's Accession Number is found in the {{{PreviousUnitID}}} (the first record in the {{{UnitHistory}}}).)
• abcd2:TaxonIdentified-Viral-GenusOrMonomial  + (en:Note that the classification of the ide …
  en:Note that the classification of the identification result (e.g. the family of a species identified) should be listed under HigherTaxon. <br/><br/>Generic names are essentially the same under the different codes; however, to avoid having to place the essential parts of a name on different levels of the hierarchy, all name elements recognized under a specific code are listed in the respective section.
  code are listed in the respective section.)
• abcd2:Synecology-Viral-GenusOrMonomial  + (en:Note that the classification of the ide …
  en:Note that the classification of the identification result (e.g. the family of a species identified) should be listed under HigherTaxon. <br/><br/>Generic names are essentially the same under the different codes; however, to avoid having to place the essential parts of a name on different levels of the hierarchy, all name elements recognized under a specific code are listed in the respective section.
  code are listed in the respective section.)
• abcd2:Synecology-AssociatedTaxa  + (en:Note that the determination of the associated taxa relies on the collector's information in this case.)
• abcd2:RecordBasis  + (en:Note that the element {{{SourceReference}}} provides for the case that the record is based on a publication.)
• abcd2:Identification-TimeZone  + (en:Note that this element is not normally used for identifications.<br/><br/>The time zone to which the time-of-day data for the unit identification event refer.)
• abcd2:Identification-TimeOfDayEnd  + (en:Note that this element is not normally used in the context of an identification event.)
• abcd2:Identification-TimeOfDayBegin  + (en:Note that this element is not normally used in the context of an identification event.)
• abcd2:Identification-PeriodExplicit  + (en:Note that this element is not normally used in the context of an identification event.)
• abcd2:Identification-DayNumberBegin  + (en:Note that this element is not normally used for identifications.)

• abcd2:Identification-DateText  + (en:Note that this element is not normally used for searches.)

• abcd2:NamedCollectionOrSurvey  + (en: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  + (en: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  + (en:Note that this is not the literature (e.g. key) used to obtain the identification result (see IdentificationReferences).)
• abcd2:Identification-ISODateTimeBegin  + (en: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  + (en:Note that this is used in the context of a collection unit and thus automatically refers to that unit.)
• abcd2:Synecology  + (en:Note that this relationship can be reco …
  en: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  + (en:Note that time can also be expressed in the {{{ISODateTimeElement}}}.)
• abcd2:MultiMediaObject  + (en: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:MultiMediaObjects  + (en: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  + (en:Note the difference from the {{{Height}}} and {{{Depth}}} elements, which are measured relative to a local surface.)
• abcd2:Identification-References  + (en:Note: this is not the citation from which an identification was taken, see under Identifier/Identification-Source.)
• abcd2:Identification-Reference  + (en:Note: this is not the citation from which an identification was taken, see under {{{Identifier/IdentificationSource}}}.)
• dwc:georeferenceRemarks  + (en:For discussion see http://code.google.com/p/darwincore/wiki/Location)
• mixs:investigation type  +
• abcd-efg:DistanceFromBaseline  +
• abcd2:ObservationUnitIdentifier  +
• mst:pelagic  +
• dwc:fieldNotes  + (en:For discussion see http://code.google.com/p/darwincore/wiki/Event)
• abcd2:TaxonIdentified-Botanical-GenusOrMonomial  + (en:Generic names are essentially the same …
  en:Generic names are essentially the same under the different codes; however, to avoid having to place the essential parts of a name on different levels of the hierarchy, all name elements recognized under a specific code are listed in the respective section.
  code are listed in the respective section.)
• abcd2:Synecology-Botanical-GenusOrMonomial  + (en:Generic names are essentially the same …
  en:Generic names are essentially the same under the different codes; however, to avoid having to place the essential parts of a name on different levels of the hierarchy, all name elements recognized under a specific code are listed in the respective section.
  code are listed in the respective section.)
• abcd2:SpecimenUnit-TypifiedName-Botanical-GenusOrMonomial  + (en:Generic names are essentially the same …
  en:Generic names are essentially the same under the different codes; however, to avoid having to place the essential parts of a name on different levels of the hierarchy, all name elements recognized under a specific code are listed in the respective section.
  code are listed in the respective section.)
• ac:scientificNameSynonym  + (en:'''Audubon Core:''' The primary purpose …
  en:'''Audubon Core:''' The primary purpose of this is in support of resource discovery, not developing a taxonomic synonymy. Misidentification or misspellings may thus be of interest.<br/>Where multiple taxa are present in a resource and multiple Scientific Taxon Names are given, the association between synonyms and names may not be deducible from the AC record alone.
  not be deducible from the AC record alone.)
• ggbn:permitURI  + (en:One will eventually need a direct link to [[ggbnvoc:IRCC | IRCC]] in the future.)
• abcd-efg:StratigraphicSectionImage-Disclaimer-Details  +
• abcd-efg:SectionUnitImage-License-Details  +