RANGES report

[Jegelewicz]

Is there any coordination regarding the requested RANGES report?

Second, as you have been warned, we really want to start producing and publishing our own Ranges Traits Dataset. To this end, we request that all Ranges participants submit spreadsheets for Y1 and Y2 before May 1st, 2025 (sooner is better, of course). If you have no way to separate your sheets into Y1 and Y2, that's fine, I'll take one master list - but be aware that we'll ask you again in a year for only those traits that you digitize in Y3.

What goes in the spreadsheet?

Attached is a CSV template that contains all of the fields you are welcome to submit. You may not have all of these fields, and that is perfectly OK. Don't lose sleep over it. There are, however, 8 required fields that all records should include. These are:
occurrenceID (or a DwC Triplet if your record has not been published or assigned a GUID yet)
catalogueNumber
scientificName
countryCode
InstitutionCode
trait name/type (see https://ranges-network.org/traits/)
measurement
units (If the units were recorded or are known, please include them. If your project/institutional protocols allow for you to infer the units with confidence, please include them. If there is significant doubt or if units are truly unknown, leave this field blank)
SPECIAL CONSIDERATIONS - if you have more than one trait to report for a given record, you may need to add more columns for trait name, measurement and units. If your CMS exports all of the trait data into a single field, that's ok too, just rename that field as "Traits" and we'll take care of the rest - you don't need to parse them. If you have other issues, please contact Dave and we'll find a solution.

To repeat, there are other fields in that template. If you have content for those fields and can add them easily, please do. If it will take a lot of effort to include the data in those additional fields, don't sweat it. The required fields are really what we're looking for here.

Ranges Traits Template.csv

This in particular seems odd

if you have more than one trait to report for a given record, you may need to add more columns for trait name, measurement and units.

and this is only generated for publication to GBIF

occurrenceID

I know there is a report created by MVZ - MVZ RANGES CSV but it is timing out when I attempt to use it for the UWBM:Mamm collection. In addition, the format is not as described above. Here is a small subset of records to demonstrate.

ranges_csv.csv

Any chance we can coordinate to make this easier for everyone and ensure that a report can be generated without timeout issues?

@bryansmclean
@jebrad
@jldunnum
@cjconroy

[mkoo]

I assume this came from @dbloom and @bryansmclean ? Is this something you want to coordinate at the Arctos level (ie get the tech team/dba/dusty involved?
Or Teresa, @Jegelewicz are you just wanting to coordinate between collections? I"m not sure but could be done via the attribute view/download ? If just the latter coordination, can I move to discussion for RANGES folks to discuss?

The MVZ ranges report is definitely a separate purpose as far as I know (for charting outliers I was told).

[Jegelewicz]

I assume this came from @dbloom and @bryansmclean ?
Yep

Is this something you want to coordinate at the Arctos level (ie get the tech team/dba/dusty involved?

There are 10 Arctos institutions involved - it seems like one solution should work for everyone.

I"m not sure but could be done via the attribute view/download?

I suppose, but I would like to know what others plan to do so that the responses from Arctos are all similar (and potentially easier to @dbloom to process?)

If just the latter coordination, can I move to discussion for RANGES folks to discuss?

Again, I suppose, but it isn't clear to me whether there should be a report/technical response.

[mkoo]

@dbloom as coordinator and @bryansmclean as lead PI, letting you guys take this one as a discussion ok?

[mkoo]

One suggestion: someone from a RANGES collection could try out the attributes download and create a workflow for the others to follow since a ranges template was provided. If it doesnt meet your needs, file a request. Document the workflow for the rest of the participants and next year's need (if needed). Let me know if you want to use the wiki here for that purpose.

[Jegelewicz]

@dbloom would something like this work?

UWBM_Mamm_JSON_Attributes.csv