Thank you so much Steve! This is very useful indeed! I can see you are ahead of us in some parts but learning about your timelines can help us understand how long this process takes, so I really appreciate it!
I will send an email today with the timeline we discussed in our last HC meeting for everybody to review. Happy to discuss it this Wednesday!
cheers!
Yani
On Wed, Jan 5, 2022 at 12:13 PM Baskauf, Steven James < steve.baskauf@vanderbilt.edu> wrote:
For reference, here's the reporting form we created for test implementers to give us feedback: https://github.com/tdwg/ac/blob/master/views/views_controlled_vocabularies_i... This is just a PDF -- when they fill it out, it will be a Google Form.
The feedback questions are related to the list of final requirements https://github.com/tdwg/ac/blob/master/views/final-requirements.md and to the specific mechanisms by which we make the vocabularies available (CSV, JSON, Markdown).
The specific testing instructions are at the link I shared in the chat at today's meeting: https://docs.google.com/document/d/1d_YMSqwSrnUEaiaR9yHcOy48cYm4eMWprPeerQes...
At our meeting today, we settled on the following timeline:
- Send email to potential implementers 10 January. (Potential
implementers were already identified over the past 6 months. Right now we have about 7 confirmed and 12 possible but unconfirmed implementers.)
Hold practice workshop 9 February
Deadline to complete testing 31 March
We don't have the timeline settled after that, but after 31 March we would use the data collected from the Google Form to create the Implementation Experience Report ( https://github.com/tdwg/vocab/blob/master/vms/maintenance-specification.md#4...), which we hope to develop into a BISS article. I would anticipate that at least the draft document could be completed by the end of April. If that's true, then the Audubon Core Maintenance Group could potentially hold public comment during May, with the Task Group activities completed by the end of the summer and prior to the TDWG annual meeting.
Obviously, Humboldt Core has a completely different set of issues, but I thought it might be useful for you to see what another group who is at a similar stage in the process is doing. The main place where we are probably significantly ahead of you is in identifying and getting commitments from test implementers. That takes a bit of time to identify the right people and for them to understand what you are trying to do enough to get them to commit.
Steve
--
Steven J. Baskauf, Ph.D. he/him/his
Data Science and Data Curation Specialist / Librarian III
Jean & Alexander Heard Libraries, Vanderbilt University
Nashville, TN 37235, USA
Office: Eskind Biomedical Library, EMB 111
Phone: (615) 343-4582
https://my.vanderbilt.edu/baskauf/
tdwg-humboldt mailing list tdwg-humboldt@lists.tdwg.org http://lists.tdwg.org/mailman/listinfo/tdwg-humboldt