Open scottveirs opened 1 year ago
scottveirs
commented
1 year ago @git-steb bumping this inquiry...
Having noted the distribution of examples in the current (as of 9/6/23) version of the viewer in the shared Gsheet of SRKW signal statistics (see new column J).
scottveirs
commented
9 months ago Hey @git-steb -- I'm getting ready to "publish" a new SRKW whistle catalog with an undergrad from Middlebury, Lucy Day (@LucyDay2001). We are curious this week to know the latest HALLO/DFO thinking about how to release a new version of the SRKW call audio files that John and James have curated so meticulously.
In the longer-run, I'm interested in setting the stage for eventually (in 2025? a few years from now?) being able to add to the 2023-24 call samples, including bringing in some US bioacousticians like Val (@veirs), David Bain, and Monika Wieland Shields to inform future categorization, nomenclature decisions, etc.
What do you (all) think about building a general SRKW signal archive over in the Orcasound organization on Github to hold not only SRKW calls, but also other signal types like whistles, clicks, and maybe eventually things like percussive sounds and DTAG samples of prey capture/consumption sounds?
I've just released a first version of such a repo at orcasound/signals-srkw that includes the historic (2002, 2018) SRKW "Ford-Osborne tapes." I'm think it could make sense to release a new version of it next month once Lucy has her whistles uploaded to it and John+Monika and any other interested collaborators agree with her examples.
Subsequently, we could release yet another version with the revised (2024) SRKW call samples -- when/iff @JKBF and James are ready to share the audio files in a public repo (in addition to the now public deployed catalogue app and associated public repo)...
Let me know what you think!
P.S. If we go this route, it might be smart to re-name this repo more generically, e.g. "signal-catalog-viewer" rather than just "call-catalog-viewer"...
@git-steb Can you remind me and @veirs where the image and audio files will be stored?
I think the plan was to create a separate repository to hold such media? And then (auto?) generate a yaml file that would list all the resources in a catalog (SRKWs initially, but eventually other ecotypes, and then species)?
With more insights into your plan for deploying the viewer and media as separate repos, we could reformat parts of Emily's humpback catalogue repo to have a consistently-organized media folder...