[dataset]: Puget Sound Zooplankton Monitoring Program dataset

[emiliom]

Dataset Name

pszmp (Puget Sound Zooplankton Monitoring Program)

Link to DwC Data Files

https://github.com/nanoos-pnw/obis-pszmp/tree/main/aligned_csvs

Link to Scripts

https://github.com/nanoos-pnw/obis-pszmp/

Link to "raw" Data Files

https://github.com/nanoos-pnw/obis-pszmp/tree/main/sourcedata

Describe your dataset and any specific requests.

See the README file on the dataset GitHub repository, and also the detailed Data processing steps and code document on the same repo. I'm already generating the three DwC eMoF extension tables (event, occurrence and emof) and may have a "final draft" in a couple of weeks. This zooplankton dataset is very similar to another one I recently published on OBIS, https://obis.org/dataset/5463caa4-b929-477f-ae6c-7007b6d91baa. For reference, see #168 for previous discussions and review of that dataset.

I don't have specific requests yet (I've had some questions already addressed via Slack 😉 ), but wanted to flag the dataset now via an issue.

[emiliom]

I've created a new dataset ("resource") on the USGS IPT, uploaded the 3 aligned csv's and set up the Darwin Core Mappings. That all went without any issues. However, in the Resource listing, this resource is shown as having 0 records:

When I click on the 0 value in that listing, I get an error report:

Is this an error with the aligned csv's, or a consequence of the fact that I've only populated a small subset of the metadata?

[albenson-usgs]

I think it might help to clarify what usually happens with a publicly available published resource. When you click the number that's there with a publicly available published resource it takes you to the "Data Records" section of the resource page (e.g. https://ipt-obis.gbif.us/resource?r=18s_monterey_bay_time_series_edna#anchor-dataRecords) so it's an anchor to the dataRecords section. Because your resource is not public and hasn't been published when you click that it takes you nowhere because the dataRecords section doesn't exist yet. It's worth noting that this only happens for you and the admins of the IPT because the resource is not publicly visible so no one else experiences this behavior.

I tested what happens when a resource is published and has zero records like this one:

and what happens in that case is it just takes you to the top of the resource https://ipt.gbif.us/resource?r=akepic#anchor-dataRecords. I do like that behavior better but I think it might be best if a resource has 0 records if it just wasn't clickable or some other behavior. @sformel-usgs might want to post a bug report in the IPT GitHub.

All of that to say your resource is totally fine and you can safely ignore this error message.

[emiliom]

Thanks for the explanation @albenson-usgs ! Ultimately, my main concern was to know if there was something wrong with my draft resource, so I'm glad there isn't -- or, more accurately, the system isn't telling me that something is wrong 😜

[sformel-usgs]

I'm closing this. I don't think this merits a bug report, but let me know if you feel strongly otherwise.

[emiliom]

I'm totally fine with closing it. I'll just note that I originally opened the issue not as a bug report, but b/c in the past we were encouraged to create an issue for new datasets that were being aligned. I think the intent was to have the issue serve as a heads-up and as a mechanism for exchanges and comments as needed (though that happens more often on Slack, at least for me). The traffic on this issue has been minimal, though.

[MathewBiddle]

@emiliom hit the nail on the head. I'd like to keep this issue open until these data have been shared with OBIS and GBIF. Once shared, we can add links to those resources and close the issue.

Thanks!

[github-actions]

Thank you for identifying this dataset for mobilization. The workshop hosts wanted to check in. Is there anything you need help with in order to mobilize this dataset to OBIS? If you would like assistance from an OBIS node you can find node contacts listed here.