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

• dwc:individualCount  + (For discussion see http://code.google.com/p/darwincore/wiki/Occurrence)
• dwc:reproductiveCondition  + (For discussion see http://code.google.com/p/darwincore/wiki/Occurrence)
• dwc:occurrenceRemarks  + (For discussion see http://code.google.com/p/darwincore/wiki/Occurrence)
• dwc:behavior  + (For discussion see http://code.google.com/p/darwincore/wiki/Occurrence)
• dwc:recordNumber  + (For specimens this is the equivalent of a …
  For specimens this is the equivalent of a collector's number - the identifier given by the collector to a specimen or sample in the field and which is likely to have been written in associated field notes. The same idea applies to original numbers applied to any observation or sample in the field, though the terminology in a given discipline might be distinct. The recordNumber isn't the same as the catalogNumber, which is usually only applied once the specimen gets accessioned into a collection.
  ecimen gets accessioned into a collection.)
• tp:taxon-type-location  + (From a nomenclatural point of view the nam …
  From a nomenclatural point of view the name of depository institution of the holotype has to be explicitly mentioned in a treatment of a new species level taxon in order to create an available name. Acronyms of the institutions can be used. The location of the institution has to be provided. Institutions can be private collections to public natural history museums.
  ections to public natural history museums.)
• dwc:dateIdentified  + (Further explanation of the International Standards Organization standard ISO 8601 can be found at http://en.wikipedia.org/wiki/ISO_8601.)
• dwc:eventTime  + (Further explanation of the International Standards Organization standard ISO 8601 can be found at http://en.wikipedia.org/wiki/ISO_8601.)
• dwc:relationshipEstablishedDate  + (Further explanation of the International Standards Organization standard ISO 8601 can be found at http://en.wikipedia.org/wiki/ISO_8601.)
• dwc:measurementDeterminedDate  + (Further explanation of the International Standards Organization standard ISO 8601 can be found at http://en.wikipedia.org/wiki/ISO_8601.)
• abcd2:TaxonIdentified-Botanical-GenusOrMonomial  + (Generic names are essentially the same und …
  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:TaxonIdentified-Bacterial-GenusOrMonomial  + (Generic names are essentially the same und …
  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:TaxonIdentified-Zoological-GenusOrMonomial  + (Generic names are essentially the same und …
  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  + (Generic names are essentially the same und …
  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-Bacterial-GenusOrMonomial  + (Generic names are essentially the same und …
  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-Zoological-GenusOrMonomial  + (Generic names are essentially the same und …
  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-Viral-GenusOrMonomial  + (Generic names are essentially the same und …
  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  + (Generic names are essentially the same und …
  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-Bacterial-GenusOrMonomial  + (Generic names are essentially the same und …
  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-Zoological-GenusOrMonomial  + (Generic names are essentially the same und …
  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.)
• skos:Concept  + (However, what constitutes a unit of though …
  However, what constitutes a unit of thought is subjective, and this definition is meant to be suggestive, rather than restrictive. The notion of a SKOS concept is useful when describing the conceptual or intellectual structure of a knowledge organization system, and when referring to specific ideas or meanings established within a KOS. Note that, because SKOS is designed to be a vehicle for representing semi-formal KOS, such as thesauri and classification schemes, a certain amount of flexibility has been built in to the formal definition of this class. See the [http://www.w3.org/TR/skos-reference/#ref-SKOS-PRIMER SKOS-PRIMER] for more examples of identifying and describing SKOS concepts.
  identifying and describing SKOS concepts.)
• abcd2:SpecimenUnit-Mark-Images  + (I did not see comments for this - should I just put something like "An image of the label or inscription found on or associated to the unit"?<br/><br/>This was an unedited area of the schema. I changed it for v. 2.01; see AbcdConcept01438)
• dwc:geodeticDatum  + (Ideally one should use a standard European …
  Ideally one should use a standard European Petroleum Survey Group (EPSG) code to a Spatial Reference System as a value for this term. The recommended controlled vocabulary is to use a value consisting of the string "EPSG:" followed by a valid EPSG code corresponding to the spatial reference system used for the geographic coordinates in the terms decimalLatitude and decimalLongitude. A good resource for determining the EPSG code from the Datum name can be found at http://spatialreference.org/. Some common EPSG codes and the Datums they use can be found below: EPSG:4326: WGS84 <br /> EPSG:4269: NAD83 <br /> EPSG:4267: NAD27 <br /> If you don't know the details of the SRS, then it is permissible to provide the name or code of the geodetic datum for the decimalLatitude and decimalLongitude coordinates. Sometimes this information is not on the original source (such as a map), while an ellipsoid name is given. In this case, provide the name of the ellipsoid. If the spatial reference system, datum, or ellipsoid are not known, use the value "unknown" for this term. A good reference for datum and ellipsoid names is http://www.colorado.edu/geography/gcraft/notes/datum/edlist.html See [[dcterms:Location]] for further discussion of georeference terms.
  further discussion of georeference terms.)
• dwc:nameAccordingTo  + (If no nameAccordingTo or nameAccordingToID …
  If no nameAccordingTo or nameAccordingToID is given explicitly given for a Taxon record, the "nominal concept" as defined by TCS should be assumed. In most cases, the nameAccordingTo will refer to a publication, but it may also refer to other sources, such as single-copy documents and other documented taxon concept definitions asserted by an individual, institution, or team of individuals.
  dual, institution, or team of individuals.)
• dwc:nameAccordingToID  + (If no nameAccordingTo or nameAccordingToID …
  If no nameAccordingTo or nameAccordingToID is given explicitly given for a Taxon record, the "nominal concept" as defined by TCS should be assumed. In most cases, the nameAccordingTo will refer to a publication, but it may also refer to other sources, such as single-copy documents and other documented taxon concept definitions asserted by an individual, institution, or team of individuals.
  dual, institution, or team of individuals.)

• ggbn:sampleDesignation  + (In case of multiple numbers please separate them with ";")

• tp:taxon-name  + (In general this is a scientific name follo …
  In general this is a scientific name following the convention of the Codes ruling nomenclature (eg International Code for Zoological Nomenclature ([http://iczn.org/code ICZN]), but it can also be a vernacular name as used in field guides. Scientific names are latinized bi- or trinomen at species and infraspecific level, and latinized names at higher taxonomic levels. Names are normalized and the combination of the name can be inferred from the <[[taxpub:taxon-name-part | tp:taxon-name-part]]>, but they can additionally be given as a name string. External linking to reference databases such as Zoobank is made with the <object-id> element.
  s made with the <object-id> element.)
• dwc:Organism  + (Instances of the Organism class are intend …
  Instances of the Organism class are intended to facilitate linking of one or more Identification instances to one or more Occurrence instances. Therefore, things that are typically assigned scientific names (such as viruses, hybrids, and lichens) and aggregates whose occurrences are typically recorded (such as packs, clones, and colonies) are included in the scope of this class.
  ) are included in the scope of this class.)
• biorel:occurs in  + (Inverse of [[biorel:has_site_in|has site in]])
• abcd2:Gathering-Altitude-Parameter  + (Is the generic description for parameter I …
  Is the generic description for parameter I found in the schema ok for this element? Should I take out the examples like width, circumference etc.?<br/><br/>The parameter element makes sense only where the measurmentOrFact type is used to describe "open" measurements, where the users decide what it is what is measured. Altitude etc. are a special case, the parameter is actually always altitude. A solution to this would be to exclude this from the MoF and put it into an extension, only used when general measurements are asked for. I added this to the Schema discussion page. For the time being, the above (English?) can serve as a template for similar cases (depth etc.).
  a template for similar cases (depth etc.).)
• dwc:georeferenceProtocol  + (It is recommended to give a citation (publ …
  It is recommended to give a citation (publication or URL) to the resource describing the methods used to determine the georeference (coordinates AND uncertainty, or footprint). Good resources on methods include: # Chapman, A.D. and J. Wieczorek (eds). 2006. Guide to Best Practices for Georeferencing. Copenhagen: Global Biodiversity Information Facility. Accessible from http://www.gbif.org/prog/digit/Georeferencing # MaNIS/HerpNet/ORNIS Georeferencing Guidelines.(HTML) Accessible from http://manisnet.org/GeorefGuide.html #Georeferencing Quick Reference Guide. (PDF) Accessible from http://manisnet.org/GeoreferencingQuickReferenceGuide.pdf See [[dcterms:Location]] for further discussion of georeference terms.
  further discussion of georeference terms.)
• skos:Collection  + (Labelled collections can be used where you would like a set of concepts to be displayed under a 'node label' in the hierarchy.)
• dcmitype:Event  + (Metadata for an event provides descriptive information that is the basis for discovery of the purpose, location, duration, and responsible agents associated with an event. For discussion see http://code.google.com/p/darwincore/wiki/DwCTypeVocabulary)
• dctype:Event  + (Metadata for an event provides descriptive information that is the basis for discovery of the purpose, location, duration, and responsible agents associated with an event. For discussion see http://code.google.com/p/darwincore/wiki/DwCTypeVocabulary)
• ggbnvoc:quality vocabulary  + (Methods and parameters defining low, medium or high quality of a sample are described with [[ggbn:qualityRemarks]])
• skos:narrower  + (Narrower concepts are typically rendered as children in a concept hierarchy (tree). By convention, skos:broader is only used to assert an immediate (i.e. direct) hierarchical link between two conceptual resources.)
• abcd2:Gathering-Altitude-TitleCitation  + (Need to decide on whether a particular standard for citations should be adopted - such as the Council of Biology Editors 6th edition with the NLM Internet extensions??)
• abcd2:PreviousUnit-TimeOfDayBegin  + (Note that Time can also be expressed in the ISO {{{DateTimeElement}}}.)
• abcd2:ZoologicalUnit-PhasesOrStages  + (Note that counts can be provided in the Unit's {{{MeasurementsOrFacts}}} section.)
• abcd2:Age  + (Note that counts for different age classes can be provided in the Unit's {{{MeasurementsOrFacts}}} section.)
• abcd2:Annotation  + (Note that for annotation labels captured from the specimen there is the SpecimenUnit/Marks structure (AbcdConcept0561).)
• abcd2:TaxonIdentified-HigherTaxon  + (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  + (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  + (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  + (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  + (Note that most observation data items are site related and thus covered under Gathering.)
• abcd2:Unit-Owner  + (Note that ownership of physical specimens is handled under SpecimenUnit. If present, overrides the equivalent Owners element on the level of dataset.)
• abcd2:TaxonIdentified-InfraspecificEpithet  + (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:SpecimenUnit-TypifiedName-InfraspecificEpithet  + (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  + (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  + (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}}}).)