ABCDEFGHIJKLMNOPQRSTUVWXYZAAAB
1
revisedCategoryoriginal_HC_labeloriginal_HC_definitioncurrent_termNamereview_decisionnotesterm_localNamelabelrdfs_comment [DEFINITION]dcterms_description [COMMENTS]examplesrdf_typetdwgutility_abcdEquivalencetdwgutility_organizedInClasstdwgutility_decisiontdwgutility_usageScope
2
General Dataset & Identificationdataset nameSpecified by data entry person. Title of paper in most cases.datasetNamedirect mapping to DwCdatasetNameDataset NameThe name identifying the data set from which the record was derived.Grinnell Resurvey Mammals, Lacey Ctenomys Recaptureshttp://www.w3.org/1999/02/22-rdf-syntax-ns#PropertyRecord-levelsimple
3
General Dataset & Identificationdataset identifierA unique identifer automatically filled out for the record when ingested to MOLdatasetIDdirect mapping to DwCdatasetIDDataset IDAn identifier for the set of data. May be a global unique identifier or an identifier specific to a collection or institution.b15d4952-7d20-46f1-8a3e-556a512b04c5http://www.w3.org/1999/02/22-rdf-syntax-ns#PropertyRecord-levelsimple
4
General Dataset & Identificationdataset publisherThe entity making the dataset availabledeprecatehttps://github.com/tdwg/hc/issues/5
5
General Dataset & Identificationdataset licenseThe legal description giving official permission to do something with the datasetlicensedirect mapping to DwClicenseLicenseA legal document giving official permission to do something with the resource.http://creativecommons.org/publicdomain/zero/1.0/legalcode, http://creativecommons.org/licenses/by/4.0/legalcodehttp://www.w3.org/1999/02/22-rdf-syntax-ns#PropertyRecord-levelsimple
6
General Dataset & Identificationdataset rights holderThe entity that holds the rights to the datasetrightsHolderdirect mapping to DwCrightsHolderRights HoldersA person or organization owning or managing rights over the resource.The Regents of the University of Californiahttp://www.w3.org/1999/02/22-rdf-syntax-ns#PropertyRecord-levelsimple
7
General Dataset & Identificationdataset modifiedThe date when the dataset was changedmodifieddirect mapping to DwCmodifiedModifiedThe most recent date-time on which the resource was changed.Recommended best practice is to use a date that conforms to ISO 8601-1:2019.1963-03-08T14:07-0600 (8 Mar 1963 at 2:07pm in the time zone six hours earlier than UTC). 2009-02-20T08:40Z (20 February 2009 8:40am UTC). 2018-08-29T15:19 (3:19pm local time on 29 August 2018). 1809-02-12 (some time during 12 February 1809). 1906-06 (some time in June 1906). 1971 (some time in the year 1971). 2007-03-01T13:00:00Z/2008-05-11T15:30:00Z (some time during the interval between 1 March 2007 1pm UTC and 11 May 2008 3:30pm UTC). 1900/1909 (some time during the interval between the beginning of the year 1900 and the end of the year 1909). 2007-11-13/15 (some time in the interval between 13 November 2007 and 15 November 2007).http://www.w3.org/1999/02/22-rdf-syntax-ns#PropertyRecord-levelsimple
8
yesGeneral Dataset & Identificationinventory performed byThe person or people who performed the inventorysamplingPerformedByHC termsamplingPerformedBySampling Performed ByA person, group, or organization responsible for recording the Event.The sampling Event could be at any level of hierarchy. In the case of a higher level Event (parent), include all the organizations or people involved in the child Events that contributed to the parent Event. Recommended best practice is to separate multiple values in a list with space vertical bar space ( | ).`North American Butterlfy Association`, `KK Wall`, `JJ Green`, `LL Pink and FF Grey | Aspen Center for Environmental Studies`http://www.w3.org/1999/02/22-rdf-syntax-ns#Propertyhttp://rs.tdwg.org/dwc/terms/Eventextension
9
General Dataset & Identificationcitation referenceThe APA formatted reference to the published description of the checklistbibliographicCitationdirect mapping to DwCRequest to add event example in DwC: https://github.com/tdwg/dwc/issues/311bibliographicCitationBibliographic CitationA bibliographic reference for the resource as a statement indicating how this record should be cited (attributed) when used.Recommended practice is to include sufficient bibliographic detail to identify the resource as unambiguously as possible.Specimen example: Museum of Vertebrate Zoology, UC Berkeley. MVZ Mammal Collection (Arctos). Record ID: http://arctos.database.museum/guid/MVZ:Mamm:165861?seid=101356. Source: http://ipt.vertnet.org:8080/ipt/resource.do?r=mvz_mammal. Taxon example: Oliver P. Pearson. 1985. Los tuco-tucos (genera Ctenomys) de los Parques Nacionales Lanin y Nahuel Huapi, Argentina Historia Natural, 5(37):337-343..http://www.w3.org/1999/02/22-rdf-syntax-ns#PropertyRecord-levelsimple
10
General Dataset & Identificationcitation identifierA reference identifer. DOI is preferred but a URI or ISBN number is adequatedeprecate/indirect mappingIncluded in citation reference / bibliographicCitation
11
General Dataset & Identificationcitation URLA full URL to the cited document, if availabledeprecate/indirect mappingIncluded in citation reference / bibliographicCitation
12
General Dataset & Identificationmetadata recorderNames of the data entry recorders and validators for this datasetEMLEML route would be: eml:dataset/associatedParty and eml:dataset/associatedParty/role. See https://eml.ecoinformatics.org/schema/eml-resource_xsd.html#ResourceGroup_associatedParty. See https://github.com/tdwg/hc/issues/14
13
General Dataset & Identificationmetadata reviewerNames of those reviewing entries during a QA/QC processEMLEML route would be: eml:dataset/associatedParty and eml:dataset/associatedParty/role. See https://eml.ecoinformatics.org/schema/eml-resource_xsd.html#ResourceGroup_associatedParty. See https://github.com/tdwg/hc/issues/14
14
yesGeneral Dataset & Identificationtaxa identified byThe agent(s) who performed taxonomic identifications in the fieldidentifiedByHC term (borrowed DwC)https://github.com/tdwg/hc/issues/7identifiedByIdentified ByA list (concatenated and separated) of names of people, groups, or organizations who assigned the Taxon to the subject.Recommended best practice is to separate multiple values in a list with space vertical bar space ( | ).`James L. Patton`, `Theodore Pappenfuss | Robert Macey`http://www.w3.org/1999/02/22-rdf-syntax-ns#Propertyhttp://rs.tdwg.org/dwc/terms/Identificationextension
15
General Dataset & Identificationassessed quality of taxonomic identificationsHow confident is the assessor in the quality of identifications on a scale from 1 (not confident) to 5 (fully confident)identificationQuality OR identificationQualifierdeprecatehttps://github.com/tdwg/hc/issues/6
16
yesGeneral Dataset & Identificationcitation reference of taxonomic authority for identificationThe published reference to the taxonomic authority used in the checklistidentificationReferencesHC term (borrowed DwC)similar to issue https://github.com/tdwg/hc/issues/7identificationReferencesIdentification ReferencesA list (concatenated and separated) of references (publication, global unique identifier, URI) used in the Identification.Recommended best practice is to separate the values in a list with space vertical bar space (` | `).`Aves del Noroeste Patagonico. Christie et al. 2004.`, `Stebbins, R. Field Guide to Western Reptiles and Amphibians. 3rd Edition. 2003. | Irschick, D.J. and Shaffer, H.B. (1997). The polytypic species revisited: Morphological differentiation among tiger salamanders (Ambystoma tigrinum) (Amphibia: Caudata). Herpetologica, 53(1), 30-49.`http://www.w3.org/1999/02/22-rdf-syntax-ns#Propertyhttp://rs.tdwg.org/dwc/terms/Identificationextension
17
yesGeospatial Scope & Habitatnumber of separate sitesAuthor-reported number of separate sites inventoriedsiteCountHC termComplete dcterms_description (comments) when issue is solved. https://github.com/tdwg/hc/issues/8
Check some ontologies to refer to
siteCountSite CountTotal number of individual sites surveyed during the Event.Site refers to the location at which observations are made or samples/measurements are taken. The site could be at any level of hierarchy.`1`, `15`http://www.w3.org/1999/02/22-rdf-syntax-ns#Propertyhttp://rs.tdwg.org/dwc/terms/Eventextension
18
yesGeospatial Scope & Habitatsite nestingAuthor-reported hierarchical sample design e.g. sampled subunits nested with larger unitssiteNestingDescriptionHC termComplete dcterms_description (comments) when issue is solved. https://github.com/tdwg/hc/issues/8siteNestingDescriptionSite Nesting DescriptionTextual description of the hierarchical sampling design.Site refers to the location at which observations are made or samples/measurements are taken. The site could be at any level of hierarchy.`5 sampling sites of 3-5 plots each`http://www.w3.org/1999/02/22-rdf-syntax-ns#Propertyhttp://rs.tdwg.org/dwc/terms/Eventextension
19
yesGeospatial Scope & Habitatsite namesAuthor-reported site namessiteNamesHC termProposed term name change. Complete dcterms_description (comments) when issue is solved. https://github.com/tdwg/hc/issues/8verbatimSiteNamesVerbatim Site NamesA list (concatenated and separated) of original site names.Site refers to the location at which observations are made or samples/measurements are taken. The site could be at any level of hierarchy. Recommended best practice is to separate multiple values in a list with space vertical bar space ( | ).`East Coastal Fringe | St. Marks Wildlife Management Area`, `S1 | S2 | C1 | C2 | R14 | R22 | W1`http://www.w3.org/1999/02/22-rdf-syntax-ns#Propertyhttp://rs.tdwg.org/dwc/terms/Eventextension
20
yesGeospatial Scope & Habitatsite detailsAuthor-reported site information (utilizes terms below per site if more than one)siteDetailsHC termProposed term name change. Complete dcterms_description (comments) when issue is solved. https://github.com/tdwg/hc/issues/8verbatimSiteDescriptionsVerbatim Site DescriptionsOriginal textual description of the site(s).Site refers to the location at which observations are made or samples/measurements are taken. The site could be at any level of hierarchy. Recommended best practice is to separate multiple values in a list with space vertical bar space ( | ).`Wet flatwoods | Wet depression surrounded by mesic longleaf pine flatwoods | Ground cover of thick Andropogon spp., Sporobolus floridanus, Vaccinium spp, Rhynchospora spp., Centella erecta, Panicum rigidulum.`http://www.w3.org/1999/02/22-rdf-syntax-ns#Propertyhttp://rs.tdwg.org/dwc/terms/Eventextension
21
Geospatial Scope & Habitatgeospatial scopeThe region of the inventory as described in text form (e.g. "Kruger National Park" or "Alberta")deprecate/indirect mappingMapping to several DwC terms in Location class, all in the Event Core. Request to DwC to add protected area example in dwc:locality
https://github.com/tdwg/dwc/issues/315. See https://github.com/tdwg/hc/issues/15
25
22
yesGeospatial Scope & Habitattotal area covered by geospatial scopeAuthor's reported total area of the geospatial scope in km2geospatialScopeAreaInSquareKilometersHC termhttps://github.com/tdwg/hc/issues/15geospatialScopeAreaInSquareKilometersGeospatial Scope Area In Square KilometersTotal area in km2 of the geospatial scope of the Event.Geospatial scope refers to the Event location reported using the dwc:Location class terms. This area is always greater than or equal to totalAreaSampledInSquareKilometers.`25`
23
yesGeospatial Scope & Habitattotal area covered by species inventoryAuthor's reported total area covered by effort to inventory species in km2 (always less than or equal to "geospatial scope" term abovetotalAreaSampledInSquareKilometersHC termhttps://github.com/tdwg/hc/issues/15totalAreaSampledInSquareKilometersTotal Area Sampled In Square KilometersTotal area in km2 surveyed during the Event.This area is always less than or equal to geospatialScopeAreaInSquareKilometers.`0.8`
24
Geospatial Scope & Habitatlatitude rangeAuthor's reported latitude or latitude range reported for the geospatial scopedeprecate/indirect mappingCould actually be mapped to more than one DwC term (verbatimLatitude, decimalLatitude, verbatimCoordinates)
25
Geospatial Scope & Habitatlongitude rangeAuthor's reported latitude or longitude range reported for the geospatial scopedeprecate/indirect mappingCould actually be mapped to more than one DwC term (verbatimLongitude, decimalLongitude, verbatimCoordinates)
26
Geospatial Scope & Habitatelevation (lower bound)Author's reported elevational lower bounddeprecate/indirect mappingCould actually be mapped to more than one DwC term (minimumElevationInMeters, verbatimElevation)
27
Geospatial Scope & Habitatelevation (upper bound)Author's reported elevation upper bounddeprecate/indirect mappingCould actually be mapped to more than one DwC term (maximumElevationInMeters, verbatimElevation)
28
Geospatial Scope & Habitatelevation unitAuthor's reported unit of elevation (e.g. meters, feet)deprecate
29
Geospatial Scope & Habitatdepth (lower bound)Author's reported depth lower bounddeprecate/indirect mappingCould actually be mapped to more than one DwC term (verbatimDepth, minimumDepthInMeters)
30
Geospatial Scope & Habitatdepth (upper bound)Author's reported depth upper bounddeprecate/indirect mappingCould actually be mapped to more than one DwC term (verbatimDepth, maximumDepthInMeters)
31
Geospatial Scope & Habitatdepth unitAuthor's reported unit of depth (e.g. meters, feet)deprecate
32
Geospatial Scope & Habitatsurvey time blocksThe time blocks in which surveys were performed, either in sum or by site.deprecatehttps://github.com/tdwg/hc/issues/9
33
Geospatial Scope & Habitatnumber of time units spent surveying in each blockThe number of (months, days, hours) spent in each time block.deprecatehttps://github.com/tdwg/hc/issues/9
34
yesTemporal ScopeHC termNew termeventDurationEvent DurationThe length of the Event in the unit reported in hc:eventDurationUnit.Recommended best practice is to use a controlled vocabulary. An hc:eventDuration should have a corresponding hc:eventDurationUnit.`1`, `30`
35
yesTemporal Scopetemporal unitThe temporal units described for the time block (months, days, years)HC termhttps://github.com/tdwg/hc/issues/9eventDurationUnitEvent Duration UnitThe temporal unit used to report hc:eventDuration.An hc:eventDurationUnit should have a corresponding hc:eventDuration.`minutes`, `hours`, `days`, `months`, `years`
36
Temporal Scopestart yearThe year surveying begandeprecate/indirect mappingCould actually be mapped to more than one DwC term (eventDate, verbatimEventDate, year)
37
Temporal Scopestart monthThe month surveying begandeprecate/indirect mappingCould actually be mapped to more than one DwC term (eventDate, verbatimEventDate, month)
38
Temporal Scopestart dayThe day surveying begandeprecate/indirect mappingCould actually be mapped to more than one DwC term (eventDate, verbatimEventDate, day)
39
Temporal Scopeend yearThe year surveying endeddeprecate/indirect mappingCould actually be mapped to more than one DwC term (eventDate, verbatimEventDate, year)
40
Temporal Scopeend monthThe month surveying endeddeprecate/indirect mappingCould actually be mapped to more than one DwC term (eventDate, verbatimEventDate, month)
41
Temporal Scopeend dayThe day surveying endeddeprecate/indirect mappingCould actually be mapped to more than one DwC term (eventDate, verbatimEventDate, day)
42
Temporal Scopestart timeThe hour of day starteddeprecate/indirect mappingCould actually be mapped to more than one DwC term (eventDate, eventTime)
43
Temporal Scopeend timeThe hour of day endeddeprecate/indirect mappingCould actually be mapped to more than one DwC term (eventDate, eventTime)
44
Temporal Scopestudy diurnalityAuthor reported sampling during day, night, or both?diurnalitydeprecate
45
Temporal Scopestudy seasonDid the author report seasons surveyed? Which ones (from a pick list).seasondeprecate
46
yesTaxonomic Scopeprospective taxonomic scopeSet of searched species during inventorytaxonomicScopeHC termtargetTaxonomicScopeTarget Taxonomic ScopeTaxonomic group(s) targeted for sampling during the Event.The Event could be at any level of hierarchy. In the case of a higher level Event (parent), include all taxonomic groups surveyed in the child Events that contributed to the parent Event. Recommended best practice is to separate multiple values in a list with space vertical bar space ( | ).`Aves`, `Aves | Mammalia`, `Procellariformes`http://www.w3.org/1999/02/22-rdf-syntax-ns#Propertyhttp://rs.tdwg.org/dwc/terms/Eventextension
47
yesTaxonomic Scopetaxonomic group(s) excluded from studySet of species explicitly excluded from the inventoryexcludedTaxonomicScopeHC termexcludedTaxonomicScopeExcluded Taxonomic ScopeTaxonomic group(s) explicitly excluded from sampling during the Event.The Event could be at any level of hierarchy. In the case of a higher level Event (parent) include all the taxonomic groups explicitly excluded from the child Events that contributed to the parent Event. Recommended best practice is to separate multiple values in a list with space vertical bar space ( | ).`nocturnal Aves`, `Quercus`http://www.w3.org/1999/02/22-rdf-syntax-ns#Propertyhttp://rs.tdwg.org/dwc/terms/Eventextension
48
yesTaxonomic Scopedevelopmental stageType(s) of individuals included when sampling due to developmental stage. Pick list: "Adult/Reproductive/Juvenile/Larval/Seedling/Vegetative/Reproductive"lifeStageScopeHC termrelated question posted to DwC repo: https://github.com/tdwg/dwc/issues/321targetLifestageScopeTarget Life Stage ScopeThe targeted age class(es) or life stage(s) of the Organism(s) sampled during the Event.This term i s defined based on the definition of the Darwin Core term lifeStage (http://rs.tdwg.org/dwc/terms/lifeStage). Recommended best practice is to use a controlled vocabulary and separate multiple values in a list with space vertical bar space ( | ).`larva`, `adult | juvenile`http://www.w3.org/1999/02/22-rdf-syntax-ns#Propertyhttp://rs.tdwg.org/dwc/terms/Eventextension
49
yesTaxonomic Scopedevelopmental stage excludedType(s) of individuals excluded when sampling due to developmental stage. Pick list: "Adult/Reproductive/Juvenile/Larval/Seedling/Vegetative/Reproductive"excludedLifeStageScopeHC termrelated question posted to DwC repo: https://github.com/tdwg/dwc/issues/321excludedLifeStageScopeExcluded Life Stage ScopeThe explicitly excluded age class(es) or life stage(s) of the organism(s) sampled during the Event.This term is defined based on the definition of the Darwin Core term lifeStage (http://rs.tdwg.org/dwc/terms/lifeStage). Recommended best practice is to use a controlled vocabulary and to separate multiple values in a list with space vertical bar space ( | ).`seedling`, `nestling | fledgling`http://www.w3.org/1999/02/22-rdf-syntax-ns#Propertyhttp://rs.tdwg.org/dwc/terms/Eventextension
50
yesTaxonomic Scopedistributional statusDistributional status explicitly included in inventory. Pick list: "Native/Non-Native/Invasive/Naturalized"degreeOfEstablishmentScopeHC termtargetDegreeOfEstablishmentScopeTarget Degree Of Establishment ScopeDegree(s) of establishment targeted for sampling during the Event.Recommended best practice is to use controlled value strings from the controlled vocabulary (http://rs.tdwg.org/dwcdoe/) for the Darwin Core term degreeOfEstablishment. For details, refer to https://doi.org/10.3897/biss.3.38084. Recommended best practice is to separate multiple values in a list with space vertical bar space ( | ).`native`, `invasive | widespreadInvasive`http://www.w3.org/1999/02/22-rdf-syntax-ns#Propertyhttp://rs.tdwg.org/dwc/terms/Eventextension
51
yesTaxonomic Scopedistributional status excludedDistributional status explicitly exluded in inventory. Pick list: "Native/Non-Native/Invasive/Naturalized"excludedDegreeOfEstablishmentScopeHC termexcludedDegreeOfEstablishmentScopeExcluded Degree Of Establishment ScopeDegree(s) of establishment explicitly excluded from sampling during the Event.Recommended best practice is to use controlled value strings from the controlled vocabulary (http://rs.tdwg.org/dwcdoe/) for the Darwin Core term degreeOfEstablishment. For details, refer to https://doi.org/10.3897/biss.3.38084. Recommended best practice is to separate multiple values in a list with space vertical bar space ( | ).`native`, `invasive | widespreadInvasive`http://www.w3.org/1999/02/22-rdf-syntax-ns#Propertyhttp://rs.tdwg.org/dwc/terms/Eventextension
52
yesTaxonomic Scopegrowth formGrowth form explicitly included in inventory. Current controlled vocab. list: tree/shrub.growthFormScopeHC termrelated question posted to DwC repo: https://github.com/tdwg/dwc/issues/321targetGrowthFormScopeTarget Growth Form ScopeTargeted growth form(s) or habit(s) of the Organism(s) sampled during the Event.Recommended best practice is to use a controlled vocabulary and separate multiple values in a list with space vertical bar space ( | ).`tree`, `shrub | sub-shrub`http://www.w3.org/1999/02/22-rdf-syntax-ns#Propertyhttp://rs.tdwg.org/dwc/terms/Eventextension
53
yesTaxonomic Scopegrowth form excludedGrowth form explicitly excluded in inventory. Current controlled vocab. list: tree/shrub.excludedGrowthFormScopeHC termrelated question posted to DwC repo: https://github.com/tdwg/dwc/issues/321excludedGrowthFormScopeExcluded Growth Form ScopeExplicitly excluded growth form(s) or habit(s) of the Organism(s) sampled during the Event.Recommended best practice is to use a controlled vocabulary and separate multiple values in a list with space vertical bar space ( | ).`tree`, `shrub | sub-shrub`http://www.w3.org/1999/02/22-rdf-syntax-ns#Propertyhttp://rs.tdwg.org/dwc/terms/Eventextension
54
Taxonomic Scopesize classSize classes included in the study for the prospective taxa (e.g., only small mammals)sizeClassScopedeprecatehttps://github.com/tdwg/hc/issues/10 [agreement to deprecate...close issue]
55
Taxonomic Scopesize class excludedSize classes excluded in the study for the prospective taxa (e.g., only small mammals)excludedSizeClassScopedeprecatehttps://github.com/tdwg/hc/issues/10 [agreement to deprecate...close issue]
56
Organismal informationenvironmental information providedControlled vocabulary includes "Environment reported by site", "reported but not by site", and "not reported"environmentReporteddeprecate
57
yesGeospatial Scope & Habitathabitat inclusionA verbatim text description of the habitats reported as included in the surveyshabitatScopeHC termis this part of geospatial scope?habitatScopeHabitat ScopeTargeted habitat(s) sampled during the Event.Recommended best practice is to use a controlled vocabulary and separate the values in a list with space vertical bar space ( | ).`dunes`, `pine forest`, `riparian`, `scrub | grassland`http://www.w3.org/1999/02/22-rdf-syntax-ns#Propertyhttp://rs.tdwg.org/dwc/terms/Eventextension
58
yesGeospatial Scope & Habitathabitat exclusionA verbatim text description of the habitats explicitly reported as not included in the surveysexcludedHabitatScopeHC termis this part of geospatial scope?excludedHabitatScopeExcluded Habitat ScopeExplicitly excluded habitat(s) sampled during the Event.Recommended best practice is to use a controlled vocabulary and separate multiple values in a list with space vertical bar space ( | ).`wet flatwoods`, `swamp | estuary`http://www.w3.org/1999/02/22-rdf-syntax-ns#Propertyhttp://rs.tdwg.org/dwc/terms/Eventextension
59
yesGeospatial Scope & Habitatreported on the ground weather conditionsWeather or climate conditions experienced during the survey (e.g., drought, frost)reportedWeatherHC termis this part of geospatial scope?reportedWeatherReported WeatherA list of weather or climatic conditions present at the time of the Event.Recommended best practice is to use a key:value encoding schema for a data interchange format such as JSON.`{'minimumTemperatureInDegreesFarenheit':18, 'maximumTemperatureInDegreesFarenheit':32, 'stillWaterCondition':'Partly Frozen'}`http://www.w3.org/1999/02/22-rdf-syntax-ns#Propertyhttp://rs.tdwg.org/dwc/terms/Eventextension
60
yesGeospatial Scope & Habitatreported local conditional impactsAdverse conditions that affected the survey or survey sites (e.g., fire, floods)reportedImpactsHC termis this part of geospatial scope?reportedExtremeConditionsReported Extreme ConditionsA description of any extreme weather or environmental condition(s) that may have affected the Event.`flooding during week 3 of surveys`, `rockslide at site 2`http://www.w3.org/1999/02/22-rdf-syntax-ns#Propertyhttp://rs.tdwg.org/dwc/terms/Eventextension
61
yesMethodologyinventory typeInventory type can be restricted search, open search, opportunistic search, trap, incidental or adventitous or material sample. Recommend using a subclasee of bco:taxonomic inventory process.inventoryTypeHC terminventoryTypesInventory TypesThe type(s) of search process(es) used to conduct the inventory.This term is only relevant if the Event represents an inventory. Recommended best practice is to use a controlled vocabulary such as the terms included under the Biological Collections Ontology superclass 'taxonomic inventory process' (http://purl.obolibrary.org/obo/BCO_0000047). Recommended best practice is to separate multiple values in a list with space vertical bar space ( | ).`restricted search`, `open search`, `opportunistic search`, `adventitious`, `compilation`, `open search | opportunistic search`http://www.w3.org/1999/02/22-rdf-syntax-ns#Propertyhttp://rs.tdwg.org/dwc/terms/Eventextension
62
yesMethodologyinventory compilation typeCompiled data is ancillary data that was not directly collected by authors but assembled from other sources. Inventories can be compiled only, survey only, or both.compilationTypeHC termcompilationTypeCompilation TypeA statement specifying whether data reported are derived from sampling event(s), ancillary data compiled from other sources, or a combination of both.This term is only relevant if the Event is an inventory. Recommended best practice is to use a controlled vocabulary.`surveyOnly`, `compilationIncludingSurveys`, `compilationNotIncludingSurveys`http://www.w3.org/1999/02/22-rdf-syntax-ns#Propertyhttp://rs.tdwg.org/dwc/terms/Eventextension
63
yesMethodologytype of compilationCompilation types include expert and local knowledge, museum specimens, literature, or other sourcescomplicationSourcesHC termProposed term name change.compilationSourceTypesCompilation Source TypesThe type(s) of data sources contributing to the compilation reported.This term is only relevant if the Event is a compilation in which one or more types of data sources were used. Recommended best practice is to use a controlled vocabulary and separate multiple values in a list with space vertical bar space ( | ).`museum specimens`, `literature`, `expert knowledge | local knowledge`http://www.w3.org/1999/02/22-rdf-syntax-ns#Propertyhttp://rs.tdwg.org/dwc/terms/Eventextension
64
Methodologyshape of search area (if restricted or open search)The shape of the search area can be rectangle, circle, line, or polygoninventoryGeometryTypedeprecate [group decision]Ultimately the term is not necessary provided that the info would already be captured with the combination of footprintWKT and protocol, protocol details.
65
yesMethodologyprotocol nameThe published name of the protocol used to carry out survey (e.g., Pollard walk)samplingProtocolHC termSuggestion made to DwC to tweak definition slightly (to include plurals) and to add comment. See: https://github.com/tdwg/dwc/issues/322
Screen reader support enabled.
first round review suggested to use dwc:samplingProtocol
Difficult to map to dwc::samplingProtocol because the mapping would be 3 to 1
Group discussion decided to keep it as a separate term
protocolNamesProtocol NamesCategorical descriptive name(s) for the method(s) used during the Event.Recommended best practice is to use a controlled vocabulary and separate multiple values in a list with space vertical bar space ( | ).`boxTrapping`, `floraInventory`, `boxTrapping | funnelTrapping`http://www.w3.org/1999/02/22-rdf-syntax-ns#Propertyhttp://rs.tdwg.org/dwc/terms/Eventextension
66
yesMethodologyprotocol detailAny variations in the published protocol. For compilations that don't have a standard protocol or have an unpublished protocol, details are presented here.samplingProtocolHC termIncluded in samplingProtocol
First round review suggested to use dwc:samplingProtocol
Group discussion decided to keep it as a separate term
protocolDescriptionProtocol DescriptionA detailed description of the method(s) used during the Event.This description should be associated with reporting of protocolNames. This may include deviations from the published protocol referred to in protocolReferences. Good practices may include instruments used, calibration, etc.`Three conventional harp traps (3.2m ht x 2.2m w) were established in flight path zones for a period of 4 hrs at dawn and dusk for a total of 10 trap nights. Traps were visited on an hourly basis during each deployment period and the trap catch recorded for species, size, weight, sex, age and maternal status.http://www.w3.org/1999/02/22-rdf-syntax-ns#Propertyhttp://rs.tdwg.org/dwc/terms/Eventextension
67
Methodologyprotocol citationAPA (American Psychological Association) formatted reference to protocol usedsamplingProtocoldeprecate [group decision]Included in samplingProtocol
68
yesMethodologyprotocol referenceDOI, URL or ISBN to the published protocol reference if availablesamplingProtocolHC termIncluded in samplingProtocol
First round review suggested to use dwc:samplingProtocol
Group discussion decided to keep it as a separate term
protocolReferencesProtocol ReferencesThe reference(s) to the method(s) used during the Event.Recommended best practice is to separate multiple values in a list with space vertical bar space ( | ).`Penguins from space: faecal stains reveal the location of emperor penguin colonies, https://doi.org/10.1111/j.1466-8238.2009.00467.x`http://www.w3.org/1999/02/22-rdf-syntax-ns#Propertyhttp://rs.tdwg.org/dwc/terms/Eventextension
69
yesMethodologywere abundances reported?Did the survey results include number of individuals captured per species? (yes/no)isAbundanceReportedHC termisAbundanceReportedIs Abundance ReportedA statement about whether the number of Organisms collected or observed is reported.If the Event is a compilation that contains at least one reported abundance, the value should be 'true'. Typically abundance values reported would be associated with related occurrences, either under the term dwc:individualCount or the combination of terms dwc:organismQuantity and dwc:organismQuantityType.`true`, `false`http://www.w3.org/1999/02/22-rdf-syntax-ns#Propertyhttp://rs.tdwg.org/dwc/terms/Eventextension
70
yesMethodologyreported abundance capWhat value, if any, was used a maximum cap on reported abundances? (yes/no)isAbundanceCapReportedHC termisAbundanceCapReportedIs Abundance Cap ReportedA statement about whether a maximum number of Organisms is reported, as specified or restricted by the protocol used.If the Event is a compilation that contains at least one reported abundance capped, the value should be 'true'. Values of abundance cap should be captured under the term hc:abundanceCap.`true`, `false`http://www.w3.org/1999/02/22-rdf-syntax-ns#Propertyhttp://rs.tdwg.org/dwc/terms/Eventextension
71
yesMethodologyHC termNew term. Implementation advice: if there is a non-Null value provided here, code isAbundanceCapReported boolean field to automatic=YESabundanceCapAbundance CapMaximum number of Organisms reported.If the Event is a compilation that contains at least one reported abundance capped, the value should be the maximum abundance cap among the ones reported.`300`,`700`http://www.w3.org/1999/02/22-rdf-syntax-ns#Propertyhttp://rs.tdwg.org/dwc/terms/Eventextension
72
yesMethodologywas vegetation cover reported?In vegetation surveys, was cover metric reported as output (yes/no)isVegetationCoverReportedHC termisVegetationCoverReportedIs Vegetation Cover ReportedA statement about whether a vegetation cover metric is reported.If the Event is a compilation that contains at least one reported vegetation cover metric, the value should be 'true'. Typically values or descriptions of vegetation cover would be captured under the term hc:verbatimSiteDescriptions.`true`, `false`http://www.w3.org/1999/02/22-rdf-syntax-ns#Propertyhttp://rs.tdwg.org/dwc/terms/Eventextension
73
yesMethodologywere absences reported?Did the authors report species expected in the survey that were not found? (yes/no)isAbsenceReportedHC termisAbsenceReportedIs Absence ReportedA statement about whether taxonomic absences are reported.If the Event is a compilation that contains at least one reported taxonomic absence, the value should be 'true'. Absences could be reported at any taxonomic level.`true`, `false`http://www.w3.org/1999/02/22-rdf-syntax-ns#Propertyhttp://rs.tdwg.org/dwc/terms/Eventextension
74
yesMethodologytaxonomic list of reported absencesList of taxa reported absence(s) at whatever taxonomic level reportedabsentTaxaHC termSuggested new name: notRecordedTaxaabsentTaxaAbsent TaxaA list (concatenated and separated) of taxa reported absent during the Event.Absences could be reported at any taxonomic level. Recommended best practice is to separate multiple values in a list with space vertical bar space ( | ).`Parabuteo unicinctus | Geranoaetus melanoleucus`, `Cetoniinae | Aclopinae | Cyclocephala modesta`http://www.w3.org/1999/02/22-rdf-syntax-ns#Propertyhttp://rs.tdwg.org/dwc/terms/Eventextension
75
yesMethodologywere specimen vouchers taken during survey?Did the authors collect specimen vouchers? (yes/no)hasVouchersHC termCheck GGBN and materialSample task group.hasVouchersHas VouchersA statement about whether specimen voucher(s) were collected during Event.If the Event is a compilation that contains at least one specimen voucher collected, the value should be 'true'.`true`, `false`http://www.w3.org/1999/02/22-rdf-syntax-ns#Propertyhttp://rs.tdwg.org/dwc/terms/Eventextension
76
yesMethodologywhere were vouchers deposited?If collected, the name of the repository where vouchers were depositedvoucherLocationsHC termCheck GGBN and materialSample task group.voucherInstitutionsVoucher InstitutionsA list (concatenated and separated) of the name(s) or acronym(s) of the institution(s) where voucher(s) collected during the Event were deposited.Recommended best practice is to separate multiple values in a list with space vertical bar space ( | ).`FMNH`, `AMNH | MVZ`, `Nairobi National Museum`http://www.w3.org/1999/02/22-rdf-syntax-ns#Propertyhttp://rs.tdwg.org/dwc/terms/Eventextension
77
yesMethodologywere samples taken from organisms during survey?Did the author collect samples from organisms during the survey?hasSamplesHC termProposed term name change. Check GGBN and materialSample task group.hasMaterialSamplesHas Material SamplesA statement about whether MaterialSample(s) were collected during the Event.If the Event is a compilation that contains at least one MaterialSample, the value should be 'true'.`true`, `false`http://www.w3.org/1999/02/22-rdf-syntax-ns#Propertyhttp://rs.tdwg.org/dwc/terms/Eventextension
78
yesMethodologywhat kind of samples were taken from organisms?Sample types include blood, tissue, fecal, etc.sampleTypesHC termProposed term name change. Check GGBN and materialSample task group.materialSampleTypesMaterial Sample TypesA list (concatenated and separated) of MaterialSample type(s) collected during the Event.Recommended best practice is to use a controlled vocabulary and separate multiple values in a list with space vertical bar space ( | ).`whole organism`, `skeleton`, `tissue | blood | fecal | stomach content`http://www.w3.org/1999/02/22-rdf-syntax-ns#Propertyhttp://rs.tdwg.org/dwc/terms/Eventextension
79
Methodologywere measurements of organisms taken during survey?This explicitly refers to physical measurements e.g. length, mass, etc. (yes/no)hasTraitsdeprecatetrue', 'false'http://www.w3.org/1999/02/22-rdf-syntax-ns#Propertyhttp://rs.tdwg.org/dwc/terms/Eventextension
80
Methodologyrecording or measurement agent typeThe agent taking the recording. This can be "human" or "machine" (e.g., camera traps)deprecatehttps://github.com/tdwg/hc/issues/13
Final decision to deprecate since multiple other grups are working on this definition
81
Completeness & Effort
inferred compilation effortMeasured as "low, medium and high" and discussed in more detail in paper text.compilationEffortLeveldeprecateSee sections in HC paper:
- Reporting on methodology and effort
- Determining overall compilation and survey effort.
82
yesCompleteness & Effort
was information about effort provided?Measured as "no/partial/complete".isEffortReportedHC termisSamplingEffortReportedIs Sampling Effort ReportedA statement about whether sampling effort associated with the Event is reported.If the Event is a compilation that contains at least one sampling effort reported, the value should be 'true'. Typically values of effort would be captured under the terms hc:samplingEffortValue and hc:samplingEffortUnit.`true`, `false`http://www.w3.org/1999/02/22-rdf-syntax-ns#Propertyhttp://rs.tdwg.org/dwc/terms/Eventextension
83
Completeness & Effort
if partial, for which part did authors provide info?For cases where effort was made clear for only some parts of the surveying effortdeprecateSee 3 new terms
84
Completeness & Effort
effort amount upper boundMaximum amount of effort based on author reporting or data-entry personsamplingEffortdeprecatehttps://github.com/tdwg/hc/issues/11
See 3 new terms
Sampling EffortThe amount of effort expended during an Event."40 trap-nights", "10 observer-hours; 10 km by foot; 30 km by car"http://www.w3.org/1999/02/22-rdf-syntax-ns#Propertyhttp://rs.tdwg.org/dwc/terms/Eventsimple
85
Completeness & Effort
effort upper bound unitThe units of efforts (bucket-night, net-hours, person-hours, sample-days, trap-nights, or other)deprecateSee 3 new terms
86
Completeness & Effort
effort amount lower boundMinimum anount of effort based on author reporting or data-entry persondeprecateSee 3 new terms
87
Completeness & Effort
effort lower bound unitThe units of efforts (bucket-night, net-hours, person-hours, sample-days, trap-nights, or other)deprecateSee 3 new terms
88
Completeness & Effort
more granular breakdown of effort reported?Choose "yes" if effort was broken down by day/night, individual site, or other criteria, otherwise "no"deprecateSee 3 new terms
89
Completeness & Effort
granular effort breakdown descriptionA verbal description of how effort was reported in more detail, e.g. by individual sites or sampling time blocksdeprecateSee 3 new terms
90
Completeness & Effort
effort calculated by author or by data entry person?Was the final assessment of effort reported directly by author or an assessment by data entry person?effortCalculatedBydeprecatehttps://github.com/tdwg/hc/issues/12
See 3 new terms
91
Completeness & Effort
description of effort calculationIf calculated, what data and what method were used to determine assessment of effort?effortCalculationProtocoldeprecateSee 3 new termsEffort Calculation ProtocolA description of or reference to (publication, URI) the method or rationale used to determine the sampling effort.The sampling effort may be originally reported or inferred.summed from reporting of hours', 'summed time trawled'http://www.w3.org/1999/02/22-rdf-syntax-ns#Propertyhttp://rs.tdwg.org/dwc/terms/Eventextension
92
yesCompleteness & Effort
HC termNew termsamplingEffortProtocolSampling Effort ProtocolA description of or reference to (publication or URL) the method(s) used to determine the sampling effort.This description should be associated with reporting of hc:samplingEffortValue and hc:samplingEffortUnit. This is a specialisation of hc:protocolDescritption focused on the effort as distinct from the survey method itself. The effort relates to the intensity of sampling and therefore can assist in interpreting measures of completeness.`40 box traps deployed at even spacings along 4 parallel 100m transects placed 50m apart and visited at 6 hourly intervals over a 48 hour period`, `2 people occupying a bird hide for a period of 8 hours and undertaking a 30 minute count of species within the 150 degree field of view every 2 hours`, `A single baited camera trap station with motion sensor trigger, deployed for a period of 10 days and configured for detecting large fauna moving through a known traffic way`
93
yesCompleteness & Effort
HC termNew termsamplingEffortValueSampling Effort ValueThe numeric value of sampling effort expended during the Event in the unit reported in hc:samplingEffortUnit.This term is meant to capture the total sampling effort value, to express details use hc:samplingEffortProtocol. For compilations it is recommend not to infer effort.`1900`, `40`, `5.5`
94
yesCompleteness & Effort
HC termNew termsamplingEffortUnitSampling Effort UnitThe unit used to report hc:samplingEffortValue.Recommended best practice is to use a controlled vocabulary. hc:samplingEffortUnit should always be used in conjunction with hc:samplingEffortValue.`trap hours`, `person hours`, `trap days`
95
Completeness & Effort
quality assurance procedureA list of any data quality procedures that were reported by the inventory authors.EMLEML route would be: eml:dataset/methods/qualityControl. See https://eml.ecoinformatics.org/schema/eml-dataset_xsd.html. See https://github.com/tdwg/hc/issues/14
96
yesCompleteness & Effort
was taxonomic completeness reported?Choices for this field: "No, not reported", "Yes, reported as complete", "Yes, reported as incomplete".isTaxonCompletenessReportedHC termProposed term name change.taxonCompletenessReportedTaxon Completeness ReportedStatement about whether, given the hc:targetTaxonomicScope, the Event yielded a complete list of the expected taxa.Recommended best practice is to use a controlled vocabulary. For compilations it is recommended not to infer completeness.`notReported`, `reportedComplete`, `reportedIncomplete`http://www.w3.org/1999/02/22-rdf-syntax-ns#Propertyhttp://rs.tdwg.org/dwc/terms/Eventextension
97
yesCompleteness & Effort
if reported incomplete, was how incompleteness assessed?If author reported their assessment of incompleteness, capture author reported measurement or inferred assessment of incompleteness.taxonCompletenessMethodHC termProposed term name change.taxonCompletenessProtocolsTaxon Completeness ProtocolsA description of or reference to (publication, URL) the method(s) used to determined hc:taxonCompletenessReported.This term allows users to determine how comprehensively an area has been sampled. Recommended best practice is to separate multiple values in a list with space vertical bar space ( | ).`Census | Based on sampling effort`, `Based on species accumulation curves`http://www.w3.org/1999/02/22-rdf-syntax-ns#Propertyhttp://rs.tdwg.org/dwc/terms/Eventextension
98
Completeness & Effort
how was completeness inferred?A description of the rationale for the inferred completeness assessment often based on how well sampling was done across the geospatial scope, and the survey and compilation effort.inferredTaxonCompletenessMethoddeprecate
99
Completeness & Effort
inferred or reported taxonomic completeness , lower boundInferred lower bound completeness is captured in quartiles (0, 25, 50, 75, 100).minimumTaxonCompletenessdeprecate
100
Completeness & Effort
inferred or reported taxonomic completeness, upper boundInferred upper bound completeness is captured in quartlies (0, 25, 50, 75, 100).maximumTaxonCompletenessdeprecate