Some Collecting Event enhancements..

[lvhart2]

Feature or enhancement

This would include the Collecting Event section in CSD and perhaps New Collecting Event task as well.

1. When I digitize a specimen, I want to be able to enter a separate Reared/Emerged date for the specimen. Currently we do not have this capability. This would be helpful for studying the phenology of a group of insects. The field to enter the emerged date I would like to look like the Start Date under Parsed in CSD, not just a text field to type it in.

2. When I digitize a specimen, I want to be able to enter in a separate field the public land or park included in a locality. This is helpful when we need to filter by a specific location and for writing proposals to state/federal agencies.

3. Can we possibly change BodyOfWater field under Custom Attributes to say waterBody (DwC term)? Just for some consistency. That would be helpful.

Location

CSD & New Collecting Event

Screenshot, napkin sketch of interface, or conceptual description

No response

Your role

Insect Collection Assistant

[mjy]

@lvhart2 I'll show you how to do some of this today at the Collection meeting.

[lvhart2]

Ok thanks!!

[debpaul]

@lvhart2 you wrote:

2. When I digitize a specimen, I want to be able to enter in a separate field the public land or park included in a locality. This is helpful when we need to filter by a specific location and for writing proposals to state/federal agencies.
3. Can we possibly change BodyOfWater field under Custom Attributes to say waterBody (DwC term)? Just for some consistency. That would be helpful.

I can help you with these two issues. Come see me at your convenience.

Then for number 2:

• [ ] We can add a Data Attribute for "Nearest Named Place" (old term from HISPID standard) OR we might choose dc:Location http://purl.org/dc/terms/Location which is defined as: A spatial region or named place.
  • See DCMI Metadata Terms Location http://purl.org/dc/terms/Location (From DCMI Metadata Terms Location
• You can then use this to sort / find specimens from this named place. Note well, sometimes it takes a bit of thought / care to apply this field. Specimens collected "NOW" from a certain named place (e. g. like a State Park or Wildlife Refuge) ... can get confusing when digitizing legacy data. That is, in the past, a State Park or Wildlife Refuge may not have existed. But when you georeference, you might NOT want to put nearest named place necessarily as that entity didn't exist when that specimen was collected. This is something to think about when you filter as well. Can get tricky. (A spatial search will gather all the specimens from that "place" but they may have been collected w/o a permit, for example, b/c one wasn't needed "then").

For number 3:

• [ ] Let's look at it together. There are 2 things to think about
  • what the screen says (the "label") in TaxonWorks
  • what does the data map to when we export (we'd want dwc:waterBody for the data going out).
  • as to whether it says "DwC term" on the screen, do note that what we do here, is map that Data Attribute to its Darwin Core concept using an "IRI" (like a URL, sort of) when we create the Data Attribute.
  • in this case dwc:waterBody IRI is http://rs.tdwg.org/dwc/terms/waterBody
    • It's this mapping that helps us know what to do with this data when we export it

[debpaul]

@mjy please review my answer for number 2 above. I would map this Data Attribute "Park" term to dc:Location. Then I don't know what to expect on export.
A. If downloading from TaxonWorks, I'm guessing we'd get the data attributes in our download B. If creating an export to DwC-A format, then non-dwc terms would not be present? (Nearest Named Place concept is not in DwC). How then, to get this location data out to GBIF? (Maybe? from buffered fields, until parsed? using dwc:verbatimLocality perhaps)? C. Is it something to consider discussing with Ed to change the term to something broader like, Nearest Named Place. As not all these places will be parks.

[lvhart2]

@lvhart2 you wrote:

2. When I digitize a specimen, I want to be able to enter in a separate field the public land or park included in a locality. This is helpful when we need to filter by a specific location and for writing proposals to state/federal agencies.
3. Can we possibly change BodyOfWater field under Custom Attributes to say waterBody (DwC term)? Just for some consistency. That would be helpful.

I can help you with these two issues. Come see me at your convenience.

Then for number 2:

• [ ] We can add a Data Attribute for "Nearest Named Place" (old term from HISPID standard) OR we might choose dc:Location http://purl.org/dc/terms/Location which is defined as: A spatial region or named place.

  • See DCMI Metadata Terms Location http://purl.org/dc/terms/Location (From DCMI Metadata Terms Location
• You can then use this to sort / find specimens from this named place. Note well, sometimes it takes a bit of thought / care to apply this field. Specimens collected "NOW" from a certain named place (e. g. like a State Park or Wildlife Refuge) ... can get confusing when digitizing legacy data. That is, in the past, a State Park or Wildlife Refuge may not have existed. But when you georeference, you might NOT want to put nearest named place necessarily as that entity didn't exist when that specimen was collected. This is something to think about when you filter as well. Can get tricky. (A spatial search will gather all the specimens from that "place" but they may have been collected w/o a permit, for example, b/c one wasn't needed "then").

For number 3:

• [x] Let's look at it together. There are 2 things to think about

  • what the screen says (the "label") in TaxonWorks

  • what does the data map to when we export (we'd want dwc:waterBody for the data going out).

  • as to whether it says "DwC term" on the screen, do note that what we do here, is map that Data Attribute to its Darwin Core concept using an "IRI" (like a URL, sort of) when we create the Data Attribute.

  • in this case dwc:waterBody IRI is http://rs.tdwg.org/dwc/terms/waterBody

    • It's this mapping that helps us know what to do with this data when we export it