...
Time | Item | Presenter | Notes |
|---|---|---|---|
URI for plant specimens |
| ||
Lifespan vairable |
| ||
Association dominance | Needs review and potentially vocabulary needs to be created | ||
Fungi on tables | it is more like an occurrence. It is not in a method. This records may have been identified just because it was possible to do so, however they are no part of the methods | ||
overstorey tables | At the moment we will only ingest summary table (suoverstorey). Plant species cannot be identified from raw transect data units problem was an artifact of incorrect join | ||
plant community | > PROJFOLCOVERNR projective foliar cover CV > look at code for plant community reviewed with felicity > DOMINSPCODE legacy data not to be ingested | ||
Other questions |
|
✅ Action items
- Felicity looking into the URI
- Felicity looking into suupstorey what is it, should it be included? and if so what other variables to include?
- Felicity to check with Matt about ingesting raw suovermeasures table
- Felicity to check the join for lustrformation
- Habacuc FM (Unlicensed) finish ingestion of all data following decisions.
- Association dominance definitions are relative to the community; Habacuc FM (Unlicensed) to create vocab
- Habacuc FM (Unlicensed) to look into suitability of stratum for suopkant suplant assembly ingestion, otherwise, define new FOI
⤴ Decisions
...
- Do not add flsp."LIFESPAN"
- suvisageclass won’t be included
- DOMINSPCODE legacy data not to be ingested with plant community
- Dropping OSTOREYSPECHTNR, SHRUBSPECHTNR,GROUNDSPECHTNR frmo suvisit as >99% of rows empty
- suplantassemb to be ingested
- exclude suupstorey and suovermeasures tables