Skip to content
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

Define target group(s) and find a categorizaion system to match resources #6

Closed
matthiasfromm opened this issue May 12, 2016 · 3 comments

Comments

@matthiasfromm
Copy link
Collaborator

With an open science training there are possibly different target groups that have different interests in open science and thus require different scopes and/or motivation (undergraduate students, PhD's, senior researchers all have their own view). It might be worth thinking about defining the "relevant" target groups and make material available that caters the different needs (maybe also in recombination of various material).

This issue is closely related to #4.

Furthermore it might be helpful to work on a categorization system to mark which material is reasonable for which target group. This could be done by tags, icons or badges - similar to the idea behind Open Badges, or the badge system that the Association for Psychological Science has implemented with the Open Practices.

@aleimba
Copy link
Collaborator

aleimba commented May 23, 2016

I think we all agree that our main target will be university-associated folks. However, I think the motivation/troubles of different "career stages" at the university are very overlapping. Nevertheless, a badge system is useful.

But, I see bigger differences for different scientific fields. E.g. life scientists will have a big focus on open data (with big data issues), whereas social scientists might be more interested in publishing open and collaborative books etc.

@matthiasfromm
Copy link
Collaborator Author

Absolutely right @aleimba! I think with a clever badge system we could look into using both elements of the badge (the icon and the colour) to indicate different things e.g. the discipline and the "level" or target group or "type of content".

@matthiasfromm
Copy link
Collaborator Author

Closing this issue since it is divided into 2 individual ones - #36 and #37.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants