-
-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Learner personas for FAIR lesson #12
Comments
There are some Library Carpentry learner profiles at https://pad.carpentries.org/lc-learner-profiles |
Good that you mention Data Stewards, that would be a good one to add! |
I would be in favour of focusing on librarians, data stewards and other research supporters first, as that would be consistent with Library Carpentry's core audience. There would certainly be an argument for producing a sibling lesson for Data Carpentry with more of a researcher focus. |
It depends on the entry barrier. If it is basic knowledge it can be used for broad audiences |
I gather that in one of the zoom handover calls there was discussion about using the instructor notes to direct people wanting to teach this lesson. FAIR tends to bring a few different stakeholders together:
|
+1 for the three profiles outlined by @ragamouf . I would just suggest an edit to the researcher/data steward one... What can I do now to make my data FAIR? |
Also agree w/ @ragamouf's list 😃 Where would the profiles live? Could be a new learner profiles .md file in the .extras folder/menu? |
Some of us teach postgraduate students and researchers, some of us teach librarians, some of us teach data stewards and people supporting research infrastructure.
We know that it's good to have a crossover audience who can inform each other, but without detailed knowledge of our different learner profiles, it's difficult to diagnose exactly the problems we want to fix.
Fleshing out learner personas will help us understand our target audience and better understand which activities are best going to suit them.
The text was updated successfully, but these errors were encountered: