Search by property

Jump to: navigation, search

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.

Search by property

A list of all pages that have property "skos:note" with value "fr:Voir la page http://code.google.com/p/darwincore/wiki/Location". Since there have been only a few results, also nearby values are displayed.

Showing below up to 27 results starting with #1.

View (previous 50 | next 50) (20 | 50 | 100 | 250 | 500)


    

List of results

  • ggbn:templateType  + (en:under review HTS library terms)
  • ggbn:digestionEnzymeType  + (en:under review HTS library terms)
  • ggbn:pcrReplicateNumber  + (en:under review HTS library terms)
  • ggbn:libraryName  + (en:under review HTS library terms)
  • ggbn:nCutterDigestionEnzyme  + (en:under review HTS library terms)
  • ggbn:pcrCycleNumber  + (en:under review HTS library terms)
  • ggbn:percentageTargetOme  + (en:under review HTS library terms)
  • ggbn:digestionEnzyme  + (en:under review HTS library terms)
  • mixs:extreme event  +
  • mixs:gaseous environment  +
  • mixs:cur vegetation  +
  • mixs:ventilation rate  +
  • mixs:ventilation type  +
  • dwc:verbatimLongitude  + (en:verbatimLatitude and verbatimLongitude
    en:verbatimLatitude and verbatimLongitude are meant to capture the original coordinates for the Location in their original format. If possible, these coordinates should also be translated into the combination of decimalLatitude, decimalLongitude, geodeticDatum, and coordinateUncertaintyInMeters, but only if you really know what you are doing - coordinate transformations can be challenging. Use these two verbatim fields to capture coordinates in systems such as UTM, providing the spatial reference system for them in the verbatimSRS. If the original spatial information is an area (for example, a grid cell or a protected area polygon), use the footprintWKT and the footprintSRS to capture the complete area information. See [[dcterms:Location]] for further discussion of verbatim coordinate terms.
    r discussion of verbatim coordinate terms.)
  • dwc:verbatimLatitude  + (en:verbatimLatitude and verbatimLongitude
    en:verbatimLatitude and verbatimLongitude are meant to capture the original coordinates for the Location in their original format. If possible, these coordinates should also be translated into the combination of decimalLatitude, decimalLongitude, geodeticDatum, and coordinateUncertaintyInMeters, but only if you really know what you are doing - coordinate transformations can be challenging. Use these two verbatim fields to capture coordinates in systems such as UTM, providing the spatial reference system for them in the verbatimSRS. If the original spatial information is an area (for example, a grid cell or a protected area polygon), use the footprintWKT and the footprintSRS to capture the complete area information. See [[dcterms:Location]] for further discussion of verbatim coordinate terms.
    r discussion of verbatim coordinate terms.)
  • mixs:down par  +
  • mixs:samp vol we dna ext  +
  • mixs:water content  +
  • mixs:surf moisture  +
  • mixs:pool dna extracts  +
  • ggbn:preparationDate  + (en:when used for tissues, quite often preparationDate is the same as [[dwc:eventDate]])
  • mixs:medic hist perform  +
  • mixs:crop rotation  +
  • mixs:gravidity  +
  • mixs:hrt  +
  • mixs:wind direction  +
  • eb:firewood  +
  • dwc:occurrenceRemarks  + (en:For discussion see http://code.google.com/p/darwincore/wiki/Occurrence)
  • dwc:individualCount  + (en:For discussion see http://code.google.com/p/darwincore/wiki/Occurrence)
  • dwc:recordNumber  + (en:For specimens this is the equivalent of
    en: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.)
  • dwc:previousIdentifications  + (fr:Voir la page http://code.google.com/p/darwincore/wiki/Occurrence)
  • dwc:occurrenceStatus  + (en:The recommended controlled vocabulary i
    en:The recommended controlled vocabulary includes: ;present :There is at least one well documented record of the taxon's presence in the area. ;absent :There is evidence to document the absence of a taxon in the area. ;common :The taxon has been observed frequently in the area. ;irregular :The presence of the taxon varies episodically in the area. ;rare :The taxon has been observed infrequently in the area. ;doubtful :The taxon is presumed present in the area, but there is doubt over the evidence, including taxonomic or geographic imprecision in the records. Use only "present" or "absent" as the possible values for occurrenceStatus of particular Events. Other values of the vocabulary are permissible for taxon distribution records.
    ermissible for taxon distribution records.)
  • dwc:reproductiveCondition  + (en:For discussion see http://code.google.com/p/darwincore/wiki/Occurrence)
  • dwc:lifeStage  + (en:The recommended controlled vocabulary includes: zygote embryo larva juvenile adult sporophyte spore gametophyte gamete pupa)
  • dwc:associatedReferences  + (en:Remark by GGBN: Material Transfer Agreements (MTAs))
  • dwc:associatedOccurrences  + (en:The recommended best practice is to separate the values with a vertical bar (' | ').)
  • dwc:behavior  + (en:For discussion see http://code.google.com/p/darwincore/wiki/Occurrence)
  • dwc:individualID  + (en:individualID is meant for any records t
    en:individualID is meant for any records that need to identify individuals for whom there may be more than one record. Banded birds, marine mammal photos allowing individual identification, individual trees resampled overtime, periodic biopsies on the same individuals, etc. could all use this term to group the records corresponding to individuals.
    the records corresponding to individuals.)
  • dwc:disposition  + (en:For discussion see http://code.google.com/p/darwincore/wiki/Occurrence Remark by GGBN: "consumed" as another example)
  • dwc:bed  + (en:For discussion see http://code.google.com/p/darwincore/wiki/GeologicalContext)
  • dwc:scientificNameAuthorship  + (en:For discussion see http://code.google.com/p/darwincore/wiki/Taxon)
  • germplasm:BreedingEvent  +
  • germplasm:CollectingEvent  +
  • germplasm:GermplasmAccession  +
  • germplasm:germplasmID  + (Local identifiers such as the catalog number (accessions number) is best reported using the dwc:catalogNumber term.)
  • dwc:geologicalContextID  + (en:For discussion see http://code.google.com/p/darwincore/wiki/GeologicalContext)
  • dwc:measurementDeterminedDate  + (en:Further explanation of the International Standards Organization standard ISO 8601 can be found at http://en.wikipedia.org/wiki/ISO_8601.)
  • dwc:measurementDeterminedBy  +
  • dwc:measurementID  + (en:For discussion see http://code.google.com/p/darwincore/wiki/MeasurementOrFact)
  • dcterms:language  + (en:<b>Audubon Core:</b> Langua
    en:<b>Audubon Core:</b> Language(s) of resource itself represented in ISO639-1 or -3 An image may contain language such as superimposed labels. If an image is of a natural scene or organism, without any language included, the resource is language-neutral (ISO code “zxx”). Resources with present but unknown language are to be coded as undetermined (ISO code “und”). Resources only containing scientific organism names should be coded as "zxx-taxon" (do not use the incorrect “la” for Latin). For regional dialects or other special cases, conform to the [http://tools.ietf.org/html/rfc5646 IETF Best Practices for Tags Identifying Languages]. As of 2012-04-11, the Dublin Core metadata Initiative recommends the use of a controlled vocabulary such as RFC 4646. For '''Darwin Core''', the latest RFC for ISO 639-1 is the recommended version (RFC 5646 as of 2012-04-11). Further documentation on the Internet Engineering Task Force (IETF) language codes can be found at http://en.wikipedia.org/wiki/IETF_language_tag. A list of language codes can be found at http://en.wikipedia.org/wiki/List_of_ISO_639-1_codes.
    ikipedia.org/wiki/List_of_ISO_639-1_codes.)