atlanticcanadacdc / template Goto Github PK

• Line features for transects
• Polygon features when mapped

Rationale:

• so that the field is searchable
• to provide examples for how folks should prepare data in this field

Do we include a NOTE in absence records like the following?

Revisit of record IDNUM 155484 from 2000 06 30

This is currently not something that is noted in our absence record standards. JEP has been including NOTE1 strings like this.

• As far as I know we currently don't have any way to recognize or notify users of significant NS communities or significant patches like old/old-growth forests.

We definitely need to work on community data generally and getting it out with data requests in all provinces. This is something that is on Sarah’s workplan and something I would like to see progress on. We could work on standardization of content for community data within fieldnotes, which doesn’t typically have an ELCODE. Using NSDNR forest community codes may be a good short-term solution to taxonomy for NS. I like to restrict the NAMEtemp field to scientific names of the dominant stratum and minimal descriptions (i.e. “Acer saccharum – Fagus grandifolia – Betula allegheniensis upland forest”), then use the obDESC field to describe age and condition, and the obASSP field to list other associated species, preferably in order of abundance within a plant layer (subcanopy, shrub/sapling, understory, moss/lichen on ground)

relates to our people names standard

For reporting; Tiger Beetle; lichens

Task 589_staicerLandbirdsAtRisk has some good examples of what this might look like.

This was provided to me by Jeremy Lundholm:

Discuss with the team and add this to our data dictionary.

Provide more support or documentation about what clues or supporting info need to be provided for LOCUNCM, if the data provider cannot give us any quantitative LOCUNCM data and doesn't feel comfortable estimating these values themselves.

Does this resource capture everything?

https://woodlot.novascotia.ca/book/export/html/284

E.g., Found/not-found attribute

This is not a specific template issue, but this is a good place to track it anyways :)

Alternatively, make it clearer in the wiki or metadata what fields are required.
Required fields:
Species name
Location
Location uncertainty
Make it clear what fields are very desirable (e.g., REFNUM for dataset crosswalking)

add: conventions for specific cases of OBCOUNT vs. OBDESC (ACTION: manager to compile cases for team review)

• no explicit protocol - worth developing
• we've loaded data from these before - but no standard

(James) For records that are neither species nor communities (field = otherFEATURE) we need to be able to see what they are in list view. Currently the details (otherFEATURE, otherFEATUREnote, otherFEATUREtype) are only visible in item view.

For example, include:

• flowering (vs. in flower)
• dead (vs. deceased)
• seeding (vs. in seed)

From the Google Doc Data Dictionary

Should not use SURVEYSITE for records with LOCUNCM > _.

Add metadata to the wiki

README.md can include a column MANDATORY= {TRUE, FALSE}

pertains to YYYY field