-
Notifications
You must be signed in to change notification settings - Fork 0
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
Dataset - High performance liquid chromatography (HPLC) phytoplankton pigment timeseries for the northern Salish Sea and central coast, British Columbia #106
Comments
Thanks for this submission @jdelbel - I will have a look at it on Monday. As discussed, until the data is available on the Hakai ERDDAP Server, you could indeed link to the Hakai Data Portal and indicate that your data is available upon request (unless @JessyBarrette you have any other suggestions?) Alternatively, you could create a private GitHub repository with the Hakai-dataset-template and store your dataset on there with the relevant documentation, and link to that repo. |
The ERDDAP dataset is already available for this dataset and is available on the development erddap here: |
Related to HakaiInstitute/hakai-erddap#151 |
The ERDDAP dataset is ready just need to sync the metadata and push it to production erddap. |
@jdelbel some comments:
|
It wouldn't let me click the check boxes. I made the requested changes to the title and abstract. Your changes look good. This link https://catalogue.hakai.org/erddap/tabledap/HakaiHPLCResearch.html is coming up as not found. |
Yes I haven't pushed to production yet
You can find it for for now at
https://goose.hakai.org/erddap/tabledap/HakaiHPLCResearch.html
<https://catalogue.hakai.org/erddap/tabledap/HakaiHPLCResearch.html>
*Jessy Barrette M.Sc.*
*Marine Data and Instrumentation Specialist*
Hakai Institute <https://www.hakai.org/> | CIOOS Pacific
<https://cioospacific.ca/> | CIOOS <https://cioos.ca/> |
***@***.*** | (C) (418) 999-5745
Le lun. 22 juill. 2024 à 15:41, jdelbel ***@***.***> a écrit :
… It wouldn't let me click the check boxes.
I made the requested changes to the title and abstract. Your changes look
good.
This link
https://catalogue.hakai.org/erddap/tabledap/HakaiHPLCResearch.html is
coming up as not found.
—
Reply to this email directly, view it on GitHub
<#106 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHICYONSR6YA22MJHTX465DZNVN7HAVCNFSM6AAAAABLE74RX2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENBTGY4DKMRQGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Nice, yeah I realized that after I sent the message. Thanks Jessy. |
It's looking good @jdelbel - few minor things:
|
related to HakaiInstitute/hakai-erddap#196 |
Thanks @timvdstap
|
Why are the click boxes so glitchy - it won't let check yours and it gives me a huge sense of satisfaction to tick things off, haha. |
As far as I'm concerned it's all good, it was more the consistency that I was thinking about.
That makes sense to me!
I still saw the portal listed as Primary Resource, but I removed it now. Where possible we try to make sure resource links go to specific datasets, rather than 'generic' platforms or portals. Once https://catalogue.hakai.org/erddap/tabledap/HakaiHPLCResearch.html is pushed to production and 'live', please add the publication date to the record. I can then publish the record to the Hakai Catalogue and make sure that the DOI is 'Findable' as well. :) |
Hey @jdelbel hope you had a great vacation! Just tagging you here to put it on your radar :-) |
Thanks @timvdstap. I saw an update from Jessy on August 26th showing that it was pushed to production. Can you confirm if that is correct date to add to the record. Oddly, I no longer see the record within my account on the intake form, which looks like it has changed since my last sign on. Where can I access the form to make the change? Also, currently no data is being pushed to erddap. I can't remember what filters Jessy had applied for deciding which data should be pushed. Can we review this and then I can make the changes so data become available? |
@fostermh Thanks :). Weird my old link didn't go that. |
Hey @jdelbel I'm not sure what filters Jessy was applying. It seems like the most recent data is from May 28, 2024, is that accurate? |
@timvdstap Ok, the publication date has been added. May 28th, 2024 is the last data we received from the analysis lab. We send out 2x shipments per year - one in June and the other in December. We get results back from the second shipment in Feb of the following year. I need time to QA/QC the data requiring other phyto data-types. Thus, I think we should publish to the end of the prior year. That would mean we could now publish to the end of 2023. Also, I think the all_chl_a_flag should be AV and the quality level "Principal Investigator". I need to update these, but can do so quickly. How does that sound? |
I'm looping in @fostermh here, because I'm not sure how to publish data only to 2023-12-31, as opposed to it currently being 2024-05-28. I think I'm confused about the difference between 'published' and 'pushed to production': So if I understand correctly, the HakaiHPLCResearch data on ERDDAP, that includes the data till May 2024 is 'pushed to production' but that doesn't mean that it's published/openly available through our ERDDAP server? It's like an interim version (available only to Hakai?), and from this production we should select the data till 2023-12-31 to publish openly? |
In theory, I could control what is openly available through the flagging and quality level if those are included as filters. This was the approach that Jessy was taking, but not sure how this was done on the backend. |
Currently the hplc output from out database that comprises the relevant ERDDAP dataset is limited to anything with results. If you would like, I can easily change that to be anything with a Quality Level of 'Principal Investigator' which would imply that @jdelbel you had reviewed and signed off on it. |
Admittedly I'm not fully sure what the next steps are for this record, so please correct me if where I'm wrong:
|
Yes, I agree with the PI criteria threshold for publication. Good on my end to make that change. @timvdstap "push the public data to ERDDAP" - Does this mean actually adding quality level "PI" so the data are pushed? Otherwise, looks good to me and will work on the update and final review. |
That's a good question, I'm actually not sure what the process of publishing data to ERDDAP looks like at a technical level, likely @fostermh will know. My guess is indeed that if you add PI as quality level, that would satisfy the established criteria and it would automatically get pushed to the Hakai ERDDAP Server (though not sure of the frequency). |
Ok, that will be good to know as I am unclear as well. |
the HPLC view has been updated to require a quality level of 'Principal Investigator' or 'Technicianmr'. I also limited the output to rows flagged as 'AV'
The erddap dataset will refresh nightly. |
Sounds good, thanks for doing that @fostermh! Will I need to update the link in the metadata record or is https://catalogue.hakai.org/erddap/tabledap/HakaiHPLCResearch.html accurate still? |
same link as before. no change is needed. |
@jdelbel The https://catalogue.hakai.org/erddap/tabledap/HakaiHPLCResearch.html is now live, showing anything that is flagged as 'AV' and has a quality level of PI or Technicianmr. If it looks all good to you I will go ahead and publish the record to the Hakai Catalogue and make the DOI findable in DataCite. edit: It seems like a lot of quality_level is set to |
@timvdstap I reviewed the metadata record and made a few small changes, but looks good now. Yes, I can start re-flagging data this afternoon. I found something I missed - from 2015 through 2016, DFO-IOS analyzed QU39 surface samples for us (0m) using a different analysis method. Do you think this would go into a different record or could I just make a small addition to the description of the existing record so that these data can be included. The different analysis method means that there are some different pigments that were measured. |
@fostermh Tim and I discussed and we think the DFO analyzed data should be a different record as it was done with a different analysis method (see above). Can you add an additional filter to the current HPLC pipeline so that it only pushes "analyzing_lab" == "USC"? It's nice we have that column to help us differentiate. |
sure, done. |
@jdelbel Just confirming that the metadata also reflects the fact that 2015/2016 DFO-IOS data is not included? |
@timvdstap is this necessary? The DFO-IOS data is from 0m depth and the metadata description says the data are 5m depth from 2015-2018 and then 0,5,10,20m from 2019 onwards. Easy to add though - could be nice to link it somehow saying there is a complementary 0m data set available here... |
Sorry I phrased that poorly, I meant to say that if the metadata previously made specific mention of the fact that it includes DFO-IOS data from 2015/2016, that we should make sure that's revised now that the data is omitted. I agree that it would be nice to link to the complementary 0m dataset in the future, but that shouldn't be a barrier to publishing this record. Let me know when you've finished the reflagging and we can publish the record :) |
I've re-flagged pretty much everything from the oceanography core stations until the end of 2022. There are a few points prior to 2022 that need some historical metadata QC, which the technicians are working on, but it is a marginal number. I think there is enough now to publish the record. Let me know if that works @timvdstap. |
Nice work @jdelbel ! I've published the record, should be on the catalogue shortly :) will re-open this issue in case there's anything wrong. |
High performance liquid chromatography (HPLC) phytoplankton pigment timeseries for the northern Salish Sea and central coast, British Columbia
https://hakaiinstitute.github.io/hakai-metadata-entry-form/#/en/hakai/7U7b8oPpeTN6gjvXlUCTGJr5pga2/-O25qzW3OpioeACGpRHl
Best Practices Checklist
In General
Data Identification
Dataset title:
Abstract
DOI
Spatial
Contact
Resources
The text was updated successfully, but these errors were encountered: