search

carpentries / amy

A web-based workshop administration application built using Django.
https://amy.carpentries.org
MIT License
110 stars 72 forks source link

Track scientific domain(s) of a workshop #1163

Closed anenadic closed 1 year ago

anenadic commented 7 years ago

This field should be a list selected from a multiple choice pre-defined set of values and would denote the scientific area(s) the students are coming from (should support multiple choices for workshops where students come from multiple domains).

The rationale behind this is that we (Software Sustainability Institute) often need to show numbers of people we trained or reached per domain (and would need to be able to link a domain with a funding body).

chrismedrela commented 7 years ago

This field should be a list selected from a multiple choice pre-defined set of values

@anenadic What is the pre-defined set of values? Is it the same as KnowledgeDomain records, that is:

anenadic commented 7 years ago

That classification would be a great start. Can it have some minimal changes/additions and I assume it would have to go through a consultation process? I could come back with some proposed modifications in the case we have any. Thanks for responding quickly.

It would also be good to have the same field for requests, and then move that over to events. So in the case the request does not go through to the event stage we still have a record of the domain. I could open a separate issue for this if need be.

chrismedrela commented 7 years ago

@anenadic both training and workshop requests do have a field for KnowledgeDomain (TrainingRequest.domains and EventRequest.attendee_domains). Do we need something similar for DC self-organized workshops requests?

Can it have some minimal changes/additions and I assume it would have to go through a consultation process?

Sure, just keep in mind that the same set of options is reused on training request form ("areas of expertise") and swc/dc workshops request form ("Domains or topic of interest for target audience").

maneesha commented 5 years ago

As I'm going through old issues here, I'd like to open discussion on whether we need to open discussion on the domain fields listed here. See also the issue raised here #1299 and #1195 .

Are the domains as listed here comprehensive and reflective of our community? Do we need to re-evaluate these categories?

pbanaszkiewicz commented 5 years ago

Possible ref: #1195

ErinBecker commented 5 years ago

@kariljordan did a lot of work about a year ago determining the appropriate domain categories to use across all of our surveys. We should use whatever categories were decided upon at that time for all of our systems. Keeping things consistent will allow us to compare data across our systems (and changing the categories will make it much more difficult to compare data across time).

kariljordan commented 5 years ago

Back when we ran the survey language focus group, @anenadic put together a research domain classification spreadsheet "that contains all different classifications for countries such as the US, Canada, Australia, South Africa, UK and any other that you think needs including and also compare it with the current classification from Carpentry surveys and AMY classification or requests/workshops." The domains in our surveys were compared with what's in AMY and the most frequent domains that came up in the "other" field in our survey. Check out the comment in the pre-survey google document, and I'll ask @maneesha to weigh in as well when she's back from holiday. I'm happy to revisit the domains before the end of the year because we will be releasing learner assessment reports in Q4. After that release would be a great time to make any revisions that we need to our surveys.

maneesha commented 2 years ago

Currently we only ask this in the workshop inquiry form, not the request or self organized forms. Leaving this issue open to consider why and how we may want to track this information.

maneesha commented 1 year ago

Closing as stale