November 2023 - tdwg-humboldt

Humboldt Task Group Meeting Wed 8 Nov 2023, 12:00 UTC
by Yanina Sica 18 Dec '23

18 Dec '23

Hi team, Tomorrow we are meeting at *12:00 UTC*. Search for your local time here <https://www.timeanddate.com/worldclock/converter.html?iso=20231101T120000&p…> or google it because I am quite bad at this! We need to *finish revising ALA's feedback <https://docs.google.com/document/d/1OxJ_H5vBd9pucjdgQDa6qMaQKl4O89gf/edit> *(starting from Plural Terms on page 10). In order to properly respond to one of their comments,* please revise this document <https://docs.google.com/spreadsheets/d/1AbUUKDkgilbtHu9Dh_5V2dnOeQNbKBcRo4d…> (column F) and make sure that the only terms that need to reflect INTENT* are denoted as 'design' in column F. I forgot to send a summary from last week but here it goes: - Kate is moving all ALA comments to GitHub issues - Steve will create an issue about the need to remove BCO as mandatory controlled vocabulary for eco:inventoryTypes - Yani will create humboldt terms templates - Ani will get iDiv people to provide feedback For the future, is anybody interested in starting a new TDWG Task Group that looks into organizing a controlled vocabulary for inventoryTypes, protocols, etc? All the best! See you soon Yani <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#m_106701344745361604_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

5 7

Re: [tdwg-humboldt] FW: Humboldt Task Group Meeting Wed 29 Nov 2023, 12:00 UTC
by John Wieczorek 03 Dec '23

03 Dec '23

Thanks Steve for this update and the effort. It would be good to have recognition of acceptance from an ALA representative in the respective Github issues for all resolutions proposed by the Task Group. That would leave all open issues with clear status with respect to consensus. On Wed, Nov 29, 2023 at 11:37 AM Baskauf, Steven James < steve.baskauf(a)vanderbilt.edu> wrote: > Sorry, I just did “reply-all”. > > s > > > > -- > > Steven J. Baskauf, Ph.D. he/him/his > > Data Science and Data Curation Specialist / Librarian III > > Digital Lab, Jean & Alexander Heard Libraries, Vanderbilt University > > Nashville, TN 37235, USA > > > > Biodiversity Information Standards (TDWG) Executive Committee/Technical > Architecture Group Chair > > https://baskauf.github.io/ > > > > > > *From: *Baskauf, Steven James <steve.baskauf(a)Vanderbilt.Edu> > *Date: *Wednesday, November 29, 2023 at 8:03 AM > *To: *Humboldt Core TG <tdwg-humboldt(a)lists.tdwg.org>, Wesley M. > Hochachka <wmh6(a)cornell.edu>, John Wieczorek <tuco(a)berkeley.edu> > *Subject: *Re: [tdwg-humboldt] Humboldt Task Group Meeting Wed 29 Nov > 2023, 12:00 UTC > > Hi Yani et al., > > > > Peter, Rob S., and I met this morning and thrashed our way through the > Miscellaneous section from ALA in the Google doc > https://docs.google.com/document/d/1OxJ_H5vBd9pucjdgQDa6qMaQKl4O89gf/edit?u… > that you referred to in your email below. > > > > In the Miscellaneous section, we believe that we have addressed the issues > that were raised; for each of them there is a description of our conclusion > in the notes (following “Steve:” in each case). In each of the cases, we > concluded that no action was required based on the reasons we gave. We > spent quite a bit of time discussing whether the term > samplingEffortProtocolReferences should be added. Our conclusion was that > it should not, since the specific amount of effort applied in a particular > survey would often be unique to that survey and therefore not likely to > actually be published anywhere. It’s really a specialization of a published > protocol that would be cited in protocolReferences. If for some reason > multiple users found a real need for the term it could be added later using > the normal DwC term addition process. If you concur with this reasoning, > then Issue #87 would need to be closed without taking action. > > > > Based on discussion in previous meetings, we concurred that adding > verbatimTargetScope was probably necessary, so we also created the new term > verbatimTargetScope in Issue #96 https://github.com/tdwg/hc/issues/96. > > > > We pressed on with the discussion beyond the normal meeting time in order > to wrap this up. We were in agreement that it would be really desirable to > have this done by the end of calendar 2023. Yani, if you can verify that > we’ve actually addressed all of the issues that ALA raised and ping John > about that, we can set the 30 day clock running prior to the end of > November. That would allow us to submit before or soon after Jan 1. Once > the clock is running, Yani, John, and Steve could be working on making sure > that the spreadsheet is up to date with any changes that we made so that > the QRG and List of Terms can be updated for final submission by the DwC > Maintenance Group to the Executive for ratification. > > > > We are so close! > > Steve > > > > -- > > Steven J. Baskauf, Ph.D. he/him/his > > Data Science and Data Curation Specialist / Librarian III > > Digital Lab, Jean & Alexander Heard Libraries, Vanderbilt University > > Nashville, TN 37235, USA > > > > Biodiversity Information Standards (TDWG) Executive Committee/Technical > Architecture Group Chair > > https://baskauf.github.io/ > > > > > > *From: *tdwg-humboldt <tdwg-humboldt-bounces(a)lists.tdwg.org> on behalf of > Yanina Sica <yanina.sica(a)gmail.com> > *Date: *Tuesday, November 28, 2023 at 4:47 AM > *To: *Humboldt Core TG <tdwg-humboldt(a)lists.tdwg.org>, Wesley M. > Hochachka <wmh6(a)cornell.edu>, John Wieczorek <tuco(a)berkeley.edu> > *Subject: *[tdwg-humboldt] Humboldt Task Group Meeting Wed 29 Nov 2023, > 12:00 UTC > > Dear all, > > > > End of the year is getting closer and many people will start going on > holidays. We still have some things to discuss but let's aim to finish them > this week. *The goal is to submit all our responses to the GitHub issues > and potential new terms or changes by end Nov or beginning Dec. After > this, the clock will restart and we will have to wait for another month > before ratifying. * > > > > In order to be effective over the next week, *I will ask you to share > your comments (either in the meeting or over email) about a few points:* > > - Please review the *Miscellaneous* section from ALA (page 16 here > <https://docs.google.com/document/d/1OxJ_H5vBd9pucjdgQDa6qMaQKl4O89gf/edit> > ). > - Please revise the *new term proposed* (see below) about reporting of > scope in a more descriptive way. This term should be used as a last resort > and in no way should replace the other scope trms. This term will allow to > capture targets that are not included in the more explicits target scopes > (e.g. targetTaxonomicScope) at least until new target scopes are proposed, > and give more flexibility in the scope reporting, that is why we propose to > include it as a verbatim term. This term will not allow completeness or > absence inference. > > > - New term: eco:verbatimTargetScope > - Definition: ‘The verbatim original description of the dwc:Event > scope.’ > - Comments: ‘Recommended best practice is first to populate > explicit scope terms to the fullest extent possible (e.g. > eco:targetTaxonomicScope). It is not recommended to use this term in > assessing absence or completeness.’ Scope of last resort! :) > - Examples: ‘small mammals’; ‘freshwater macroinvertebrates’; ‘dead > animals’ > > *Peggy*, do you think you can join our next meeting? If not, can you > suggest some time slots that work for you? I know it will be hard to > coordinate a time that works for everybody and you have already spoken with > Peter but it might be nice for some of us to meet with you and discuss your > very appreciated feedback. In the meetine, we have collected some thoughts > in this document > <https://docs.google.com/document/d/1OxJ_H5vBd9pucjdgQDa6qMaQKl4O89gf/edit> > . > > > > Unfortunately, I will not be able to meet this week. My flight to > Argentina got cancelled and now I am travelling tonight and will not be in > time for our meeting. > > > > All the best! > > > > Yani > > > > > > > > Yani >

3 3

Humboldt Task Group Meeting Wed 29 Nov 2023, 12:00 UTC
by Yanina Sica 29 Nov '23

29 Nov '23

Dear all, End of the year is getting closer and many people will start going on holidays. We still have some things to discuss but let's aim to finish them this week. *The goal is to submit all our responses to the GitHub issues and potential new terms or changes by end Nov or beginning Dec. After this, the clock will restart and we will have to wait for another month before ratifying. * In order to be effective over the next week, *I will ask you to share your comments (either in the meeting or over email) about a few points:* - Please review the *Miscellaneous* section from ALA (page 16 here <https://docs.google.com/document/d/1OxJ_H5vBd9pucjdgQDa6qMaQKl4O89gf/edit> ). - Please revise the *new term proposed* (see below) about reporting of scope in a more descriptive way. This term should be used as a last resort and in no way should replace the other scope trms. This term will allow to capture targets that are not included in the more explicits target scopes (e.g. targetTaxonomicScope) at least until new target scopes are proposed, and give more flexibility in the scope reporting, that is why we propose to include it as a verbatim term. This term will not allow completeness or absence inference. - New term: eco:verbatimTargetScope - Definition: ‘The verbatim original description of the dwc:Event scope.’ - Comments: ‘Recommended best practice is first to populate explicit scope terms to the fullest extent possible (e.g. eco:targetTaxonomicScope). It is not recommended to use this term in assessing absence or completeness.’ Scope of last resort! :) - Examples: ‘small mammals’; ‘freshwater macroinvertebrates’; ‘dead animals’ *Peggy*, do you think you can join our next meeting? If not, can you suggest some time slots that work for you? I know it will be hard to coordinate a time that works for everybody and you have already spoken with Peter but it might be nice for some of us to meet with you and discuss your very appreciated feedback. In the meetine, we have collected some thoughts in this document <https://docs.google.com/document/d/1OxJ_H5vBd9pucjdgQDa6qMaQKl4O89gf/edit>. Unfortunately, I will not be able to meet this week. My flight to Argentina got cancelled and now I am travelling tonight and will not be in time for our meeting. All the best! Yani Yani

2 1

interest in new TDWG Task Group that looks into organizing a controlled vocabulary for inventoryTypes, protocols, etc
by Bayer, Jennifer M 08 Nov '23

08 Nov '23

Hello I joined this group a few months ago to learn more about Humboldt Core and to see how it would become a Darwin Core extension. My general interest is to learn more about development of data standards as well as helping users apply standards. I work in the USA Pacific Northwest, where endangered salmon species drive a lot of data collection (animal populations, freshwater habitat conditions, as well as marine environmental conditions), which is primarily used for resource management decisions and we are striving to make that data more accessible and reusable. I look forward to seeing the materials you all are working on to support use of Humboldt Core and I would be interested in participating in a future effort related to developing a controlled vocabulary for inventoryTypes, protocols, methods. Thanks for letting me follow along your recent work and apologies for not introducing myself earlier. best regards, Jen Bayer Jennifer Bayer<https://www.usgs.gov/index.php/staff-profiles/jennifer-m-bayer#:~:text=Jen%….> (she/her) PNAMP Coordinator, Forest and Rangeland Ecosystem Science Center U.S. Geological Survey 503.201.4179 Pacific Northwest Aquatic Monitoring Partnership<http://www.pnamp.org/> ________________________________ From: tdwg-humboldt <tdwg-humboldt-bounces(a)lists.tdwg.org> on behalf of tdwg-humboldt-request(a)lists.tdwg.org <tdwg-humboldt-request(a)lists.tdwg.org> Sent: Wednesday, November 8, 2023 4:00 AM To: tdwg-humboldt(a)lists.tdwg.org <tdwg-humboldt(a)lists.tdwg.org> Subject: [EXTERNAL] tdwg-humboldt Digest, Vol 36, Issue 2 This email has been received from outside of DOI - Use caution before clicking on links, opening attachments, or responding. Send tdwg-humboldt mailing list submissions to tdwg-humboldt(a)lists.tdwg.org To subscribe or unsubscribe via the World Wide Web, visit https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.tdw…<https://lists.tdwg.org/mailman/listinfo/tdwg-humboldt> or, via email, send a message with subject or body 'help' to tdwg-humboldt-request(a)lists.tdwg.org You can reach the person managing the list at tdwg-humboldt-owner(a)lists.tdwg.org When replying, please edit your Subject line so it is more specific than "Re: Contents of tdwg-humboldt digest..." Today's Topics: 1. Humboldt Task Group Meeting Wed 8 Nov 2023, 12:00 UTC (Yanina Sica) ---------------------------------------------------------------------- Message: 1 Date: Tue, 7 Nov 2023 15:11:57 +0100 From: Yanina Sica <yanina.sica(a)gmail.com> To: Humboldt Core TG <tdwg-humboldt(a)lists.tdwg.org> Subject: [tdwg-humboldt] Humboldt Task Group Meeting Wed 8 Nov 2023, 12:00 UTC Message-ID: <CALzHwpL=hk_Z06TZK1-rHn0Fz5ujK6TYCV4uN1Bj3mLEjcvT+A(a)mail.gmail.com> Content-Type: text/plain; charset="utf-8" Hi team, Tomorrow we are meeting at *12:00 UTC*. Search for your local time here <https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.timea…<https://www.timeanddate.com/worldclock/converter.html?iso=20231101T120000&p…>> or google it because I am quite bad at this! We need to *finish revising ALA's feedback <https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.goog…<https://docs.google.com/document/d/1OxJ_H5vBd9pucjdgQDa6qMaQKl4O89gf/edit>> *(starting from Plural Terms on page 10). In order to properly respond to one of their comments,* please revise this document <https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.goog…<https://docs.google.com/spreadsheets/d/1AbUUKDkgilbtHu9Dh_5V2dnOeQNbKBcRo4d…>> (column F) and make sure that the only terms that need to reflect INTENT* are denoted as 'design' in column F. I forgot to send a summary from last week but here it goes: - Kate is moving all ALA comments to GitHub issues - Steve will create an issue about the need to remove BCO as mandatory controlled vocabulary for eco:inventoryTypes - Yani will create humboldt terms templates - Ani will get iDiv people to provide feedback For the future, is anybody interested in starting a new TDWG Task Group that looks into organizing a controlled vocabulary for inventoryTypes, protocols, etc? All the best! See you soon Yani <https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.avast…<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…>> Virus-free. https://gcc02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.avast.…<http://www.avast.com/> <https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.avast…<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…>> <#m_106701344745361604_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

1 0