Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Add a field for workshop type #1087
As we have more offerings of types of workshops, even within SWC and DC, it would be very useful to be able to track workshop type. We need this to track how often we're teaching certain materials for reporting and for maintenance.
For Data Carpentry those would be things like Ecology-R, Ecology-Python, Genomics, Geospatial, etc.
SWC could have R, Python, MATLAB
Using this framework we could also add Library Carpentry workshops.
I think this is really important but I'd want to brainstorm with others how to do it.
For example, someone might teach DC Ecology-R but also touch on Python. Someone might teach SWC Python and also SQL. Ideally I want to track how often our stardard lessons are taught, but also what kind of deviation there is from that.
There's also the question of the overhead in actually recording this. Can we add this to the workshop github page's metadata? For example:
I think we just need an enumeration of modules taught, not necessarily the "leading theme".
I submitted the mechanics for capturing the lessons being taught via yaml headers in
I think we have two motivations for it now and it might be time to bring it back. I can also see how the
If I were to bring it back I'd suggest we use the actual github repo slugs like:
History of my PR which was eventually rolled back:
Full PR here: swcarpentry/DEPRECATED-bc#415
referenced this issue
Dec 2, 2016
In the Data Carpentry workshop template, we do have the 4 topics in the YAML header and they populate the schedule
I agree pulling the modules in from the workshop template makes a lot of sense.
I think we will also want to be able to note the overall type of workshop, e.g. Genomics Data Carpentry, Python Software Carpentry, R Ecology Data Carpentry, so maybe that could be in the YAML headers as well, but it also might want to be something we note at the time of the workshop request. So, I don't know if that would have to be handled differently.
Besides YAML headers, I've also tried to get this into something machine-readable with wking/swc-setup-installation-test#9. But that's still floating, because I haven't been able to convince lesson maintainers (or third parties) to write the per-lesson