taxonworks
taxonworks copied to clipboard
DwC Export - map minimumDepthInMeters and verbatimDepth [Was: Depth (DWC term) needed in Collecting Event model]
As a curator, I need to record depth as defined here: http://rs.tdwg.org/dwc/terms/minimumDepthInMeters and here: http://rs.tdwg.org/dwc/terms/maximumDepthInMeters
It would also be helpful to have verbatimDepth: http://rs.tdwg.org/dwc/terms/verbatimDepth
This will be needed for freshwater biodiversity studies as well as marine.
@tmcelrath Please add this as a custom Predicate. I will add the mapping to the export.
Added. Looks pretty clunky though (e.g. verbatimDepth not in verbatim column)
I suppose we could examine the label and move the field over. Not sure if that would feel that much less clunky though. Maybe ultimately we need a seperate custom fields column all-together if they reach a certain size.
Reopening because some people are being crabby. :crab:
I'm not a programmer. I'm a taxonomist. Soooo... I have no idea how to add a custom predicate...
I'm not a programmer. I'm a taxonomist. Soooo... I have no idea how to add a custom predicate...
Greetings @rlasleyjr I can walk you through that. It's partially covered (needs more info) in the current documentation. I'm not a programmer either ... :-D
Briefly, for most records in TaxonWorks you can:
- add a property (a field you need) and then add and store the value that goes with it.
- even nicer, you can (if it exists) add a URL to point to the property as it exists in a given standard. This allows your data to be aggregated meaningfully / clearly in places like GBIF.
Here's an example for you.
- Find the
Task
calledManage controlled vocabulary terms
-
You'll see the following when you open this task. (You'll note you can add other things, in a similar manner).
-
For your exact case here using
minimumDepthInMeters
Note I had to click
Create
to make the newpredicate
. It's now going to be available for you to use where you need it in TaxonWorks (see next). -
Once you've added your
Predicates
, you'll want to use them. Here's an example.
- For a given
CollectingEvent
(see below) you want to specify theminimumDepthInMeters
. -
Click
to open theRadial Annotator
5.Select
the Data Attributes
option. You'll see all the data attributes (properties, predicates) you've added.
-
Click
on thePredicate
you want - Enter the
value
for thePredicate
(in this case some number indicating the minimum depth in meters -
Click
Create
- These can then be mapped so that when you export your data (say, to GBIF) these
Predicates
along with their declared values, go out too.
Lemme know if you have questions.
@rlasleyjr please also see our online documentation for more about what you can do with the entirety of the Manage controlled vocabulary task
And, you will discover, that you can modify your data entry forms (say, for CollectingEvent or CollectionObject) to show the desired attributes so that you can add values there. To figure this out (AFTER you've added your desired data attributes):
-
go to the
header menu
-
click on
Project
-
on the left side of the screen, click
Preferences
-
you'll see
Project: customize attributes
-
there you can select the data model (e. g. Collecting Event) and the
data attributes
(aka fields) you want to appear on yourEdit Collecting Event
form.
Excellent! Sorry for being crabby (again). That was very helpful.
One thing... I created the predicate minimumDepthInMeters first and then maximumDepthInMeters. This resulted in maxDepth being above minDepth in Custom Attributes in Collecting Event. Checking the "Reorder fields" box did not allow me to put minDepth above maxDepth. Eventually, I solved it by deleting both, and creating maxDepth first. It was important to me that minDepth gets entered before maxDepth, to avoid confusion or entering the wrong value first. Maybe I don't know how to otherwise reorder Custom attributes? Anyway, thanks again, and I'll do a better job of checking the online doc next time.
If you go to Project preferences (top right button), you can select preferences, and reorder predicates there.
Thank you