Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Review florabank2 #177

Open
14 of 22 tasks
peterdesmet opened this issue Jun 14, 2022 · 6 comments
Open
14 of 22 tasks

Review florabank2 #177

peterdesmet opened this issue Jun 14, 2022 · 6 comments
Assignees

Comments

@peterdesmet
Copy link
Member

peterdesmet commented Jun 14, 2022

  • modified: remove field
  • language: en (not EN) or remove field
  • bibliographicCitation: remove field
  • datasetID: complete later, leave empty now
  • datasetName: for consistency, I suggest:

Florabank2 - A grid-based database on the distribution of mosses in the northern part of Belgium (Flanders and the Brussels Capital region)

Not

FLORABANK 2: a grid-based database on the distribution of mosses in the northern part of Belgium (Flanders and the Brussels Capital region)

  • dataGeneralizations: are the data collected at a higher precision than IFBL square? If not, remove this field
  • catalogNumber: remove field
  • recordedBy: can we share this info? I so, I would use as seperator
  • individualCount: is this info available?
  • occurrenceStatus: add with present
  • occurrenceRemarks: it seems like a lot of this info could be translated to samplingProtocol:
losse waarnemingen -> casual observation
...
  • eventID: is there one?
  • verbatimEventDate: remove field. If a value is a true range (min != max), then write as such in eventDate
  • samplingProtocol: is it possible to provide something? See also occurrenceRemarks
  • locationID: is there a location id?
  • country: remove field
  • verbatimLocality: rename to locality
  • coordinateUncertaintyInMeters: only needed values are 707 (1 km) and 2828 (4 km)
  • verbatimSRS: is the datum of the IFBL known?
  • georeferenceRemarks: I would add coordinates are centroid of used grid square
  • taxonRank: lowercase, except for speciesAggregate (write as such)
  • nomenclaturalCode: remove field
@DimEvil
Copy link
Contributor

DimEvil commented Jun 17, 2022

  • language: en (not EN) or remove field
  • bibliographicCitation: remove field
  • datasetID: complete later, leave empty now
  • datasetName: for consistency, I suggest:

Florabank2 - A grid-based database on the distribution of mosses in the northern part of Belgium (Flanders and the Brussels Capital region)

Not

FLORABANK 2: a grid-based database on the distribution of mosses in the northern part of Belgium (Flanders and the Brussels Capital region)

  • recordedBy: can we share this info? I so, I would use as seperator
    -> option to use #, will check with Wouter
  • individualCount: is this info available?
    --> no, 'streeplijst, collection or herbarium' could set to 1
  • occurrenceRemarks: it seems like a lot of this info could be translated to samplingProtocol:
    --> let's try
losse waarnemingen -> casual observation
...
  • samplingProtocol: is it possible to provide something? See also occurrenceRemarks
    --> let's try
  • locationID: is there a location id?
    --> no, if there would be one, it would be the IFBL code, or maybe the IFBL ID
  • verbatimLocality: rename to locality
  • verbatimSRS: is the datum of the IFBL known? --> NO (i ll check with Wouter)
  • georeferenceRemarks: I would add coordinates are centroid of used grid square
  • taxonRank: lowercase, except for speciesAggregate (write as such)
  • nomenclaturalCode: remove field
    -> allé dan
  • eventID: is there one?
  • coordinateUncertaintyInMeters: only needed values are 707 (1 km) and 2828 (4 km)
    --> other values are more uncertain (707 --> 1000 'onzeker uurhok), 2828 --> 3500 'onzeker uurhok')

@peterdesmet
Copy link
Member Author

Let me know when data are available to be whipped again.

@DimEvil
Copy link
Contributor

DimEvil commented Jun 23, 2022

No eventID's identified

@peterdesmet
Copy link
Member Author

peterdesmet commented Jun 23, 2022

  • rightsHolder: add with INBO
  • individualCount: should all records be set to 1 (current implementation)
    --> yes
  • occurrenceRemarks: was it intended to remove this field
    -> yes, but on second tought I keep this
  • samplingProtocol: this is currently quite messy, I would use controlled values (to be discussed with Wouter)
    • casual observation
    • herbarium
    • digital checklist
    • checklist
    • ...
      --> I can't say Herbarium is a samplingProtocol --> herbarium sampling
      --> I see the light
  • taxonRank: contains veriety
  • eventDate: write single dates as single date: 2002-04-27/2002-04-27 -> 2002-04-27

@DimEvil
Copy link
Contributor

DimEvil commented Jun 27, 2022

eventDate: write single dates as single date: 2002-04-27/2002-04-27 -> 2002-04-27 --> won't fix

  • rightsHolder: add with INBO

  • individualCount: should all records be set to 1 (current implementation)
    --> yes

  • occurrenceRemarks: remarks in this field, as good as possible

  • samplingProtocol: this is currently quite messy, I would use controlled values (to be discussed with Wouter)

  • casual observation

  • observation

  • tally sheet

  • herbarium sampling

  • monitoring

  • digital tally sheet

  • taxonRank: contains veriety corrected to varietas

  • eventDate: write single dates as single date: 2002-04-27/2002-04-27 -> 2002-04-27 --> won't fix

@peterdesmet
Copy link
Member Author

Please use variety

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants