Field metadata - atlanticcanadacdc/template GitHub Wiki

Jump to sections: Identifier, When, What, Who, Where, Observation details, Collection data, Notes, Reference attributes

Jump to fields: REFNUM, IDNUM, YYYY, MM, DD, yyyy2, mm2, dd2, OBDATE, obDATEverbatim, OBTIME, OBTIMEend, SCNAME, COMMON NAME, ELCODE, NAMETEMP, NOTETAX, MCODE, GNAME, NNAME {SCINAME}, COMNAME, NOMCOMMUN, OBSERVER, IDENTBY, CDCOBSERVER, LATDEC, LONDEC, LATDEC2, LONDEC2, NOTELOCcoordinates, LOCUNCM, NOTELOClocuncm, SURVEYSITE, NOTELOCsurveysite, DIRECTIONS, NOTELOCdirections, SITECODE, ELEVmin, SUBNAT, OBEVID, OBABUN, OBABUNSITE, OBCOUNT, OBASSP, OBDESC, OBACTIV, OBPHEN, OBSEX, OBDATA, HABITAT, OBTHREAT, GENDESC, ENVIRONMENTAL, URL, PROJECT, PROTOCOL, CONFEATYPE, LOCUNCTYPE, REPRACCU, CONFCOMP, COLLECTION, COLLNUM, COLLDUP, ACCNUM, NOTE1, NOTE2, NOTE3, GENCOM, RUID, BESTSOURCE, importFile, EDITION, MAINHIST

Identifier

`REFNUM`

	`REFNUM`
Definition	Record ID (e.g., field or collection number) assigned by the observer.
Comments	If the field is used consistently by observers, it can be used to join, merge or relate records to existing records in our database. It can also be used by the observer to match data to personal datasets.
Examples	`TP1234`, `NS-RP025-2_617`, `Tupper-Barrens_525`
Data type	TEXT
Length limit	255
Data validation restrictions	Each `REFNUM` value must be unique.
Internal or external use	Both internal and external use
Required field	Yes. Data Manager can add if not present

`IDNUM`

	`IDNUM`
Definition
Comments
Examples
Data type
Length limit
Internal or external use	Internal use only. Database generated field
Required field

When

`YYYY`

	`YYYY`
Definition	Year of observation
Comments	Can include ‘X’ characters for any digits that are uncertain. When the observation was made for multiple, known, years between these dates submit a record for each known year.
Examples	`2021`, `199X`, `19XX`
Data type	TEXT
Length limit	4
Data validation restrictions	Allow: Text length Data: equal to Length: 4
Internal or external use	Both internal and external use
Required field	Yes. This gets loaded into our database.

`MM`

	`MM`
Definition	Month of observation. Allowable values from `1` to `12`
Comments	If missing use `XX`. If 2, `DD` < 30. If 4,6,9,11, `DD` <31
Examples	`12`, `XX`, `5`
Data type	TEXT
Length limit	2
Data validation restrictions	Allow: Text length Data: between Minimum: 1 Maximum: 2
Internal or external use	Both internal and external use
Required field	Yes. This gets loaded into our database.

`DD`

	`DD`
Definition	Day of observation
Comments	If missing use `XX`
Examples	`31`, `2`, `XX`
Data type	TEXT
Length limit	2
Data validation restrictions	Allow: Text length Data: between Minimum: 1 Maximum: 2
Internal or external use	Both internal and external use
Required field	Yes. This gets loaded into our database.

`yyyy2`

	`yyyy2`
Definition	End year of a date range for observation
Comments	If your observation took place over a range of years, use this field for the end year. Use `YYYY` to record the start year of the range.
Examples	`2021`, `199X`, `19XX`
Data type	TEXT
Length limit	4
Data validation restrictions	Allow: Text length Data: equal to Length: 4
Internal or external use	Both internal and external use
Required field	No

`mm2`

	`mm2`
Definition	End month of a date range for observation
Comments	If your observation took place over a range of months, use this field for the end month. Use `MM` to record the start month of the range.
Examples	`12`, `5`
Data type	TEXT
Length limit	2
Data validation restrictions	Allow: Text length Data: between Minimum: 1 Maximum: 2
Internal or external use	Both internal and external use
Required field	No

`dd2`

	`dd2`
Definition	End day of a date range for observation
Comments	If your observation took place over a range of days, use this field for the end day. Use `DD` to record the start day of the range.
Examples	`31`, `2`
Data type	TEXT
Length limit	2
Data validation restrictions	Allow: Text length Data: between Minimum: 1 Maximum: 2
Internal or external use	Both internal and external use
Required field	No

`OBDATE`

	`OBDATE`
Definition	Complete date of observation in database form
Comments	Two digits for month and day e.g., precise to day: `YYYY MM DD` precise to century: `YYXX XX XX` precise to range of years: `YYYY-YYYY MM DD` precise to range of months: `YYYY MM-MM DD`. Ensure you load the observation date, not the date the observation was reported to AC CDC.
Examples
Data type
Length limit
Data validation restrictions
Internal or external use	Internal use only
Required field	Internal use required

`obDATEverbatim`

	`obDATEverbatim`
Definition	This field can hold any text description of the date or details about uncertainty
Comments
Examples	`spring 2010`, `collected sometime between 4 June and 23 July`
Data type	TEXT
Length limit
Data validation restrictions
Internal or external use	Both internal and external use
Required field	No

`OBTIME`

	`OBTIME`
Definition	Time of observation of or start time of observation period. From GPS waypoint, if available; generally not important.
Comments	`hh:mm` or `hh:mm:ss` format. If time is a range of hours enter as: `OBTIME` = `19:00`, `OBTIMEend` = `21:00`. If time is in a UTC format, convert based on the timezone in which the data were collected. Note to Data Managers: make sure that in Excel this field is coded as custom, `hh:mm` or `hh:mm:ss` for it to be properly loaded into the database, e.g., `01:43`, `21:23`, `21:23:04`
Examples
Data type	hh:mm or hh:mm:ss
Length limit
Data validation restrictions
Internal or external use	Both internal and external use
Required field	No

`OBTIMEend`

	`OBTIME`
Definition	End of observation period
Comments	hh:mm or hh:mm:ss format. if time is a range of hours enter as: [OBTIME] = 19:00, [OBTIMEend] = 21:00. It time is in a UTC format, convert based on timezone in which the data were collected. Note to Data Managers: FileMaker ‘time’ field
Examples
Data type	hh:mm or hh:mm:ss
Length limit
Data validation restrictions
Internal or external use	Both internal and external use
Required field	No

What

`SCNAME`

	`SCNAME`
Definition	Scientific name as given by reference
Comments
Examples	`Clemmys insculpta`
Data type	TEXT
Data validation restrictions
Internal or external use	External use

`COMMON NAME`

	`COMMON NAME`
Definition	English name
Comments
Examples	`Wood Turtle`
Data type	TEXT
Data validation restrictions
Internal or external use	External use

`ELCODE`

	`ELCODE`
Definition	Unique Element identification code
Comments	Also used for indirect types of evidence including tracks, scat, browse, perennial nests – if the identification is certain. Added by data manager later.
Examples
Data type	TEXT
Length limit	10-12
Data validation restrictions
Internal or external use	Internal use only
Internal use required	Yes otherwise, record will not be exported from FileMaker

`NAMETEMP`

	`NAMETEMP`
Definition	Temporary taxonomic name or description of taxon. Use this field to store names/related information about names you are uncertain about and names not yet identified to the species or subspecies/variety level. This information can be used to attach a species identification (with an `ELCODE`) in the future.
Comments	Note to AC CDC: Use this field to store information about ecological communities that lack ELCODES. See our standards for complex observation types for more information about `COMMUNITY` data for communities that lack ELCODES.
Examples	`Poa`, `indet.`, `Amelanchier sp.`
Data type	TEXT
Length limit	255
Data validation restrictions

`NOTETAX`

	`NOTETAX`
Definition	Relevant information on identification, especially key features or uncertainty
Comments	A description of how the identification was made. This can include physical attributes of the individual used to support the identification. This would include chemical tests used in lichen identification. If AC CDC staff make changes to ID, details are included here. If changed by others (e.g., herbarium) could go in `IDENTBY`.
Examples	`orig. ID C. subdentata (=C. spinigera)`, `Hypericum boreale/mutilum`, `ID not confirmed`
Data type	TEXT
Length limit	255
Data validation restrictions
Internal or external use	Both internal and external use
Required field	No

`MCODE`

	`MCODE`
Definition	8 character ‘Museum Code’ (1 to 4 = genus, 5 to 8 = sp+ssp)
Comments
Examples
Data type	TEXT
Length limit	8
Internal or external use	Internal use only. Database generated field.
Required field	No. Automatically generated in FM

`GNAME`

	`GNAME`
Definition	Nature Serve name
Comments
Examples
Data type
Length limit
Internal or external use	Database generated field.
Required field

`NNAME {SCINAME}`

	`NNAME {SCINAME}`
Definition	ACCDC use. Scientific name of taxon given by reference
Comments	Nature Serve Specifications: Genus + species (+ ssp. or var.), without authors; italics not necessary.
Examples
Data type	TEXT
Length limit
Internal or external use	Internal use only. Database generated field.
Required field	No. This gets Inherited in FM from the observation’s ELCODE

`COMNAME`

	`COMNAME`
Definition	English common name
Comments	Nature Serve Specifications
Examples
Data type	TEXT
Length limit
Internal or external use	Internal use only. Database generated field.
Required field	No. This gets Inherited in FM from the observation’s ELCODE

`NOMCOMMUN`

	`NOMCOMMUN`
Definition	French common name
Comments	Nature Serve Specifications. Accents...
Examples
Data type	TEXT
Length limit
Internal or external use	Internal use only. Database generated field.
Required field	No. This gets Inherited in FM from the observation’s ELCODE

Who

`OBSERVER`

	`OBSERVER`
Definition	Person who collected datum in field
Comments	Use this format: `lastname1, firstname1; lastname2, firstname2`. Use `unknown` only if the observer is confidently known to be unknown. Otherwise, use `blank`. If the first name or last name is missing, use a `?` to indicate a missing name. See our people names standard for more information.
Examples	`Blaney, Sean; Robinson, Sarah; Mazerolle, David`, `Blaney, Sean; et al.`, `unknown`, `<blank>`, `Cochran, ?` `Atlasser ID: <number>`, `Blaney, Sean; Robinson, Sarah; Mazerolle, David, plus 8 observers`, `iNaturalist user: dominique150`
Data type	TEXT
Length limit	255
Data validation restrictions
Internal or external use	Both internal and external use
Required field	No, but the credibility of observation should be suspect if no observer name is provided

`IDENTBY`

	`IDENTBY`
Definition	Person identifying the record (especially where it is different from the observer)
Comments	If a history of identification exists (e.g., changes over time), include this information here. Can contain dates and institution info. Format names as in OBSERVER. Only fill in if identified to species
Examples	`Blaney, Sean`
Data type	TEXT
Length limit	255
Data validation restrictions
Internal or external use	Both internal and external use
Required field	No, but the credibility of the identification should be suspect if no name is provided

`CDCOBSERVER`

	`CDCOBSERVER`
Definition	A field identifying AC CDC observers. It is used to identify records that were collected through AC CDC work. It is 1 only when the observer is current CDC staff or someone was hired by CDC for a field project.
Comments
Examples	`1`,`0`
Data type	INTEGER
Length limit	1
Data validation restrictions
Internal or external use	Internal use only
Required field

Where

`LATDEC`

	`LATDEC`
Definition	Latitude of observation in Decimal Degrees
Comments	5 decimal places are required for observation to be plotted with ~1m accuracy. If converting from other formats and 5 decimal places are not used, the record will be shifted from true location
Examples	`42.12345`
Data type	DECIMAL NUMBER
Length limit
Data validation restrictions	Allow: Decimal Data: between Minimum: -90 Maximum: 90
Internal or external use	Both internal and external use
Required field	Yes. Imprecision in location can be expressed in the `LOCUNCM` field

`LONDEC`

	LONDEC
Definition	Longitude of observation in Decimal Degrees
Comments	5 decimal places are required for observation to be plotted with ~1m accuracy. If converting from other formats and 5 decimal places are not used, the record will be shifted from true location
Examples	`-64.12345`
Data type	DECIMAL NUMBER
Length limit
Data validation restrictions	Allow: Decimal Data: between Minimum: -180 Maximum: 180
Internal or external use	Both internal and external use
Required field	Yes. Imprecision in location can be expressed in the `LOCUNCM` field

`LATDEC2`

	`LATDEC2`
Definition	If observation is a linear transect, add end point here
Comments	If this field contains a value, `LATDEC` must also have a value
Examples	`42.12345`
Data type	DECIMAL NUMBER
Length limit
Data validation restrictions	Allow: Decimal Data: between Minimum: -90 Maximum: 90
Internal or external use	Both internal and external use
Required field	No

`LONDEC2`

	`LONDEC2`
Definition	If observation is a linear transect, add end point here
Comments	If this field contains a value, `LONDEC` must also have a value
Examples	`-64.12345`
Data type	DECIMAL NUMBER
Length limit
Data validation restrictions	Allow: Decimal Data: between Minimum: -180 Maximum: 180
Internal or external use	Both internal and external use
Required field	No

`NOTELOCcoordinates`

	`NOTELOCcoordinates`
Definition	Basis of coordinates and/or remark upon extent
Comments	Be as concise as possible. Waypoint numbers are permissible in this field, if relevant.
Examples	`phone GPS`, `Google Maps`, `True coordinates obtained from iNaturalist`, See the NOTELOCcoordinates controlled vocabulary for permissible values, `wpt 345`, `wpt 345-356`
Data type	TEXT
Length limit	255
Data validation restrictions
Internal or external use	Both internal and external use
Required field	No

`LOCUNCM`

	`LOCUNCM`
Definition	Estimated horizontal uncertainty distance of location (metres)
Comments	Use '10' for GPS locations. Use at least 100 m if measurements are made using Google Maps/Google Earth, and the location has no recognizable landmarks nearby. If recognizable landmarks exist, it may be possible to assign a smaller `LOCUNCM` value (i.e., it is easier to derive accurate coordinates). Use `200` if coordinates are from iNaturalist and no `LOCUNCM` is provided by the iNat record.
Examples	`10`, `50`, `500`, `1000`
Data type	POSITIVE INTEGER
Length limit
Data validation restrictions	Allow: Whole number Data: greater than or equal to Minimum: 10
Internal or external use	Both internal and external use
Required field	Yes. Data cannot be loaded without this field completed

`NOTELOClocuncm`

	`NOTELOClocuncm`
Definition	Further information on location uncertainty
Comments	Be as concise as possible.
Examples	`LOCUNCM estimated by AC CDC; phone GPS`; `LOCUNCM set at 200m minimum` (for iNaturalist records)
Data type	TEXT
Length limit	255
Data validation restrictions
Internal or external use	Both internal and external use
Required field	No

`SURVEYSITE`

	`SURVEYSITE`
Definition	Single placename of general locality, especially designated or proposed Protected Areas. Good survey sites are major landmarks: permanent town or land features nearby.
Comments	No abbreviations. `SURVEYSITE` must be a placename. If blank: The nearest locality in the Canadian Geographic names database could be used; there is an ArcGIS routine for this If assigned by CDC add a note in `NOTEloc`: `SURVEYSITE set by AC CDC as nearest CGNDB locality` If `LOCUNCM` is high (how high?) a `SURVEYSITE` should not be assigned by the script
Examples	`Saint John River`
Data type	TEXT
Length limit	255
Data validation restrictions
Internal or external use	Both internal and external use
Required field	No

`NOTELOCsurveysite`

	`NOTELOCsurveysite`
Definition	Further information about survey site.
Comments	Be as concise as possible.
Examples	`SURVEYSITE set by AC CDC as nearest CGNDB locality`
Data type	TEXT
Length limit	255
Data validation restrictions
Internal or external use	Both internal and external use
Required field	No

`DIRECTIONS`

	`DIRECTIONS`
Definition	Detailed instructions for re-finding observation. Distance and direction from a landmark
Comments	If not provided, can be added by AC CDC script for observations with `LOCUNCM` <= `100`. If added by script add to `NOTELOCdirections`: `Directions generated by AC CDC script`
Examples	`S of Gagetown, 100m upstream from mouth of Mud Creek`
Data type	TEXT
Length limit	255
Data validation restrictions
Internal or external use	Both internal and external use
Required field	No

`NOTELOCdirections`

	`NOTELOCdirections`
Definition	Further information about directions
Comments	Be as concise as possible. If `DIRECTIONS` added by script add to `NOTELOCdirections`: `Directions generated by AC CDC script`
Examples
Data type	TEXT
Length limit	255
Data validation restrictions
Internal or external use	Both internal and external use
Required field	No

`SITECODE`

	`SITECODE`
Definition	Site reference code specific to the project or data collection event
Comments	Helps link observation back to data provider's study sites
Examples
Data type	TEXT
Length limit
Data validation restrictions
Internal or external use	Both internal and external use
Required field	No

`ELEVmin`

	`ELEVmin`
Definition	Elevation in metres. From GPS waypoint, if available; generally not important.
Comments	Should be integer between 0 and 820 if in Maritimes. Note for AC CDC: This could be added from a Maritimes DEM during `add spatial attributes` script
Examples	`70`, `152`, `30`, `9`
Data type	POSITIVE INTEGER
Length limit
Data validation restrictions	Allow: Whole number Data: greater than or equal to Minimum: 0
Internal or external use	Both internal and external use
Required field	No

`SUBNAT`

	`SUBNAT`
Definition	Province (e.g., NB, NS, PE)
Comments
Examples	`NB`, `NS`, `PE`
Data type	TEXT
Length limit	2
Internal or external use	Internal use only. Database generated field.
Required field	No. This gets added to record by data manager with script (based on coordinates)…but required if checking whether ELCODE-PR exists in EST

Observation details

Ensure there is no redundancy across Observation fields.

`OBEVID`

	`OBEVID`
Definition	Nature of the evidence associated with the observation
Comments	Default is `sight record`. Generally added when data entry is completed.
Examples	See the OBEVID controlled vocabulary for allowable values.
Data type	LOWERCASE TEXT
Length limit	255
Data validation restrictions	Lowercase text only.
Internal or external use	Both internal and external use
Required field	No

`OBABUN`

	`OBABUN`
Definition	Verbal description of frequency with reference to the abundance at a specific point location. Abundance at the precise location
Comments
Examples	See the OBABUN controlled vocabulary for allowable values.
Data type	LOWERCASE TEXT
Length limit	255
Data validation restrictions	Lowercase text only.
Internal or external use	Both internal and external use
Required field	No

`OBABUNSITE`

	`OBABUNSITE`
Definition	Verbal description of frequency with reference to the larger survey area. Abundance over the whole field site.
Comments
Examples	See the OBABUNSITE controlled vocabulary for allowable values.
Data type	LOWERCASE TEXT
Length limit	255
Data validation restrictions	Lowercase text only.
Internal or external use
Required field

`OBCOUNT`

	`OBCOUNT`
Definition	The number of individuals/units (e.g,. The number of adults, young, eggs). Preferably just number of units that could survive if severed from connected neighbors. Description such as `11 clumps`, `15 flowering stems`, `15 burrows` can go in `OBDESC`. It is preferable to indicate the units of the count, if known, in `OBDESC` (e.g., `OBDESC`: `4 plants`, `OBCOUNT`:`4`.
Comments	Use special characters like ~, +, < only when absolutely necessary. Omit phenological info in this field. E.g., ‘1 adult’ becomes `OBCOUNT`=1;`OBPHEN`=adult OBCOUNT vs OBDESC: 1. clonal species: `obcount` = `200`; `obdesc` = `200 shoots; 9000 flowers` 2. if only have flower count, `obcount` = `<blank>`, `obdesc` = `9000 flowers`
Examples	`10-50`, `1`, `>100`,`50+`
Data type	POSITIVE INTEGER, sometimes TEXT
Length limit	255
Data validation restrictions
Internal or external use	Both internal and external use
Required field	No

`OBASSP`

	`OBASSP`
Definition	Associated Species; species observed with taxon recorded
Comments	Use scientific names; separate species by semicolon. Include host or nectaring plant species here if available; can also add to `HABITAT` if deemed appropriate. Use a semi-colon to separate OBASPP taxa.
Examples	`Abies balsamea; Picea rubens; Acer rubrum; Betula allegheniensis; Betula papyrifera; Onoclea sensibilis; Matteuccia struthiopteris`, `Leucodon brachypus`, `Thuja occidentalis; Betula papyrifera; Picea glauca`, `Nectaring on Malus pumila`
Data type	TEXT
Length limit	255
Data validation restrictions
Internal or external use	Both internal and external use
Required field	No

`OBDESC`

	`OBDESC`
Definition	Description of state, condition or appearance of individual/group.
Comments	E.g., patch dimensions, number of clumps, interesting markings or state of individual, e.g. 'pregnant'. Behavior and activity go in `OBACTIV`
Examples	`corticolous`, `collected incidentally with CJC 4129`, `only 1 or 2 populations observed`, `1 thallus`, `2 thalli`
Data type	TEXT
Length limit	255
Data validation restrictions
Internal or external use	Both internal and external use
Required field	No

`OBACTIV`

	`OBACTIV`
Definition	Activity or behavior observed. Breeding evidence for birds.
Comments	For birds use formal MBBA breeding evidence statements found in file OBACTIV_bird_strings.csv. Include additional relevant activity following a semicolon.
Examples	`just molted`, `Confirmed breeding: Adult carrying food. 5 adults hunting and bringing food back to nest sites`, `terrestrial, stationary, in sun`, `Nesting`, `mating`
Data type	TEXT
Length limit	255
Data validation restrictions
Internal or external use	Both internal and external use
Required field	No

`OBPHEN`

	`OBPHEN`
Definition	Phenology (bud, flower, seed; age or life stage)
Comments	Full names: adult, juvenile, immature
Examples	`adult`, `mature`, `flowering`, `fruiting`, `senescent`, `eggs`
Data type	LOWERCASE TEXT
Length limit	255
Data validation restrictions	Lowercase text only
Internal or external use	Both internal and external use
Required field	No

`OBSEX`

	`OBSEX`
Definition	Sex of individuals observed, if relevant
Comments	Full words: male; female; 1 male, 2 females
Examples	`female`, `male`, `1 male, 1 female`
Data type	LOWERCASE TEXT
Length limit	255
Data validation restrictions	Lowercase text only
Internal or external use	Both internal and external use
Required field	No

`OBDATA`

	`OBDATA`
Definition	Compiled observation data
Comments	Automatically compiled from `OBABUN, OBCOUNT, OBPHEN, OBACTIV, OBASSP, OBDESC, SIZE, OBSIZE, OBSEX`
Examples
Data type
Length limit	255
Data validation restrictions
Internal or external use	Internal use only
Required field	No

`HABITAT`

	`HABITAT`
Definition	Habitat in which the taxon was found
Comments	Microhabitat (e.g., lichen or bryophyte substrate) should also be added here. Please decode any habitat codes.
Examples	`gravel island in river`, `WD2: Red maple / Cinnamon fern / Sphagnum`, `on red maple in red maple/balsam fir swamp`
Data type	TEXT
Length limit	255
Data validation restrictions
Internal or external use	Both internal and external use
Required field	No

`OBTHREAT`

	`OBTHREAT`
Definition	Information about natural or anthropogenic threats to the identified taxon at the place it was observed
Comments
Examples	`numerous ATV tracks through nesting area`, `tree harvesting edge of swamp`, `vegetation control under powerline`
Length limit	255
Data type	TEXT
Data validation restrictions
Internal or external use	Both internal and external use
Required field	No

`GENDESC`

	`GENDESC`
Definition	Compiled General Description data
Comments	compiled from Habitat, ecology (3 entries), LocUseCls (2011), SOILcode (added to all recs)
Examples
Data type	TEXT
Length limit	255
Data validation restrictions
Internal or external use	Internal use only
Required field	No

`ENVIRONMENTAL`

	`ENVIRONMENTAL`
Definition	A general field for any environmental conditions it is deemed valuable to retain
Comments	Cloud cover, temperature, wind.
Examples	`temp: 23C; cloud cover: partial`
Data type	TEXT
Length limit	255
Data validation restrictions
Internal or external use	Both internal and external use
Required field	No

`URL`

	`URL`
Definition	URL of associated record for iNat, eBird checklist if applicable.
Comments	For the record, not for a photo associated with the record
Examples
Data type	TEXT
Length limit
Data validation restrictions
Internal or external use	Both internal and external use
Required field	No

`PROJECT`

	`PROJECT`
Definition	Name for project for which the data were collected. AC CDC: use project numbers from work outline.
Comments	Helpful for sorting collections of data in our database. This information is not always present in the citation field, SURVEYSITE, NOTE1 or NOTE2 fields
Examples
Data type	TEXT
Length limit
Data validation restrictions
Internal or external use	Both internal and external use
Required field	No, but helps find collections of data in our database

`PROTOCOL`

	`PROTOCOL`
Definition	Type of survey used for data collection
Comments	This provides an indication of biases and level of search effort
Examples	See the PROTOCOL controlled vocabulary for suggested values.
Data type	LOWERCASE TEXT
Length limit
Data validation restrictions	Lowercase text only.
Internal or external use	Both internal and external use
Required field	No

Accuracy/Quality Attributes

`CONFEATYPE`

	`CONFEATYPE`
Definition	Conceptual Feature Type. Geometry representing the observation
Comments
Examples
Data type	TEXT
Length limit
Internal or external use	Internal use only. Database generated field.
Required field	No. Added by Data Manager

`LOCUNCTYPE`

	`LOCUNCTYPE`
Definition	Location Uncertainty Type. "Areal - Delimited" = contained within a specified landscape feature.
Comments	{`Negligible`, `Areal - Estimated`, `Areal – Delimited`, `Linear`} When LOCUNCM <=15 = Negligible When LOCUNCM >15 = Areal – Estimated
Examples
Data type	TEXT
Length limit
Internal or external use	Internal use only. Database generated field.
Required field	No. Added by Data Manager

`REPRACCU`

	`REPRACCU`
Definition
Comments	{`very high`, `high`, `medium`, `low`, `very low`} Under 15 m = very high 16-56 m = high 57-399 m = medium 400-2800 m = low 2800+ m = very low
Examples
Data type	TEXT
Length limit
Internal or external use	Internal use only. Database generated field.
Required field	No. Added by Data Manager

`CONFCOMP`

	`CONFCOMP`
Definition
Comments	{`unknown`} is the only value we use.
Examples
Data type	TEXT
Length limit
Internal or external use	Internal use only. Database generated field.
Required field	No. Added by Data Manager

Collection data

`COLLECTION`

	`COLLECTION`
Definition	Museum or institution holding specimen
Comments	Abbreviated as: {`ACAD`, `MICH`, `NBM`…}. AC CDC: added when specimens are sent away.
Examples	`NFM`, `ACAD, NSPM` `UNB`
Data type	TEXT
Length limit	255
Data validation restrictions
Internal or external use	Both internal and external use
Required field	No

`COLLNUM`

	`COLLNUM`
Definition	Field or collection number assigned by the observer
Comments	This can be used as `REFUNUM` if it provides a unique ID for all records in the dataset. Typically assigned after all data is in, sequentially by collection date/time
Examples	`TP1234`, `3907`, `6365322-22-NOWA`
Data type	TEXT
Length limit	255
Data validation restrictions
Internal or external use	Both internal and external use
Required field	No

`COLLDUP`

	`COLLDUP`
Definition	Number of duplicate specimens collected
Comments
Examples	`1`, `2`
Data type	POSITIVE INTEGER
Length limit	255
Data validation restrictions	Allow: Whole number Data: greater than Minimum: 0
Internal or external use	Both internal and external use
Required field	No

`ACCNUM`

	`ACCNUM`
Definition	Museum Accession number (assigned by museum/institution)
Comments	For iNaturalist data, unique iNat record number, preceded by `iNat`
Examples	`NBM-00484`, `B144361`, `OBS504457741`
Data type	TEXT
Length limit
Data validation restrictions
Internal or external use	Both internal and external use
Required field	No

Notes

`NOTE1`

	`NOTE1`
Definition	Miscellaneous information of value that cannot be entered in other fields
Comments	Ensure these do not contain values that fit in other standard fields
Examples
Data type	TEXT
Length limit	255
Data validation restrictions
Internal or external use	Both internal and external use
Required field	No

`NOTE2`

	`NOTE2`
Definition	Miscellaneous information of value that cannot be entered in other fields
Comments	Ensure these do not contain values that fit in other standard fields
Examples
Data type	TEXT
Length limit	255
Data validation restrictions
Internal or external use	Both internal and external use
Required field	No

`NOTE3`

	`NOTE3`
Definition	Miscellaneous information of value that cannot be entered in other fields
Comments	Ensure these do not contain values that fit in other standard fields
Examples
Data type	TEXT
Length limit	255
Data validation restrictions
Internal or external use	Both internal and external use
Required field	No

`GENCOM`

	`GENCOM`
Definition	Compiled General comments data
Comments	Compiled from `NOTETAX, NOTELOC, NOTE1, NOTE2, NOTE3`
Examples
Data type	TEXT
Length limit	255
Data validation restrictions
Internal or external use	Internal use only. Database generated field
Required field	No. automatically generated in FM

Reference attributes

`RUID`

	`RUID`
Definition	a unique ID to help trace back to the source record as follows: `ID_BESTSOURCE_LOAD DATE`
Comments	using the formula: `=B2&"_"&AI2&"_LOADDATE"` where: `ID` is any ID the record originally came with. If the provided IDs are not unique or the data didn't come with any identifier I add another column called [line], then just give each record a sequential identifier then use that in the formula above. Concatenating this info makes the RUID unique across all datasets in the database (mostly) which helps when needing to check records `LOADDATE` is the day it gets loaded (yymmdd)
Examples
Data type	TEXT
Length limit
Internal or external use	Internal use only
Internal use required	Yes. Added by Data Manager

`BESTSOURCE`

	`BESTSOURCE`
Definition	Unique ID identifying the dataset
Comments	This is assigned in the SOURCES database when a new citation is created When creating a SOURCE in the SOURCES database, be as concise as possible. The fine details are captured in the record itself. E.g., TITLE: "Email to Sean Blaney re: nesting Snapping Turtle, NB" ABSTRACT: "Email to Sean Blaney re nesting Snapping Turtle in Lower Burton/Upper Swan Creek area, NB."
Examples
Data type	TEXT
Length limit	12
Internal or external use	Internal use only
Internal use required	Yes. Added by Data Manager

`importFile`

	`importFile`
Definition	name of the spreadsheet file used to load the records
Comments	an excel spreadsheet name. append ‘!’ and worksheet name if relevant
Examples
Data type	TEXT
Length limit	255
Internal or external use	Internal use only
Internal use required	Yes. Added by Data Manager

`EDITION`

	`EDITION`
Definition	Edition of the dataset
Comments	This now gets loaded to offload some work previously performed by FileMaker
Examples	`JLC 2017 04 13`
Data type	TEXT
Length limit	14
Internal or external use	Internal use only
Internal use required	Yes. Added by Data Manager

`MAINHIST`

	`MAINHIST`
Definition	standard maintenance history string added to new records
Comments	`="ACCDC "&AJ2&" QC,GIS"` (note that 4 spaces used to separate items here)
where AJ is EDITION
Examples
Data type	TEXT
Length limit
Internal or external use	Internal use only
Internal use required	Yes. Added by Data Manager

Deprecated fields

`OWNER`

	`OWNER`
Definition	Crown vs. private; specific name of private owner if known and shareable
Comments
Examples
Data type	TEXT
Length limit	255
Data validation restrictions
Internal or external use	Internal use
Required field	No

`_NOTELOCcoordinates`

See NOTELOCcoordinates

`_NOTELOClocuncm`

See NOTELOClocuncm

`_NOTELOCsurveysite`

See NOTELOCsurveysite

`_NOTELOCdirections`

See NOTELOCdirections

⚠️ GitHub.com Fallback ⚠️