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

Populate learning objectives across all episodes #9

Open
ragamouf opened this issue Aug 5, 2020 · 5 comments
Open

Populate learning objectives across all episodes #9

ragamouf opened this issue Aug 5, 2020 · 5 comments
Assignees

Comments

@ragamouf
Copy link
Collaborator

ragamouf commented Aug 5, 2020

Determining learning objectives will help how the content on each page is shaped.

Learning objectives could be drawn from any number of existing FAIR training materials.

@ragamouf ragamouf self-assigned this Aug 20, 2020
@kmhettne kmhettne self-assigned this Aug 26, 2020
@ragamouf
Copy link
Collaborator Author

ragamouf commented Aug 27, 2020

I've submitted a pull request with learning objectives for eps 2-5 (ie F,A,I,R) and assigned @kmhettne as the reviewer - does that work as a convention?

@linajandren
Copy link

I've been looking through the learning objectives posted this morning and I think they are a great start but we need to think a little more about how to phrase them. Most of the learning objectives, especially for Findable and Accessible are phrased as something the learner should be able to do after completing the course. (Example: Articulate the role of data repositories in enabling FAIR data - I could say "After the course, the learner should be able to articulate the role of data....") Some though, especially for the Interoperable episode, are phrased as things to do during the course (Example: Demystify the term 'interoperability' - if I want the learner to be able to do that after the workshop that would be rather high level). I guess it comes down to if the objectives are written as learner objectives or course objectives, and both could be done. But right now it's a little bit of both, and I believe it would be better if we kept to one of them.

@kmhettne
Copy link
Collaborator

I have opened issues to discuss the learning objectives per Episode. That might ease the way of working with them.

@kmhettne
Copy link
Collaborator

As a reminder: Learning objectives are the highest level and focus on what the learner will learn (see comment from Liz in issue #8 ).

@ragamouf
Copy link
Collaborator Author

I agree that it's useful to disambiguate the overall course or lesson objectives from the individual objectives for each episode. I don't really mind if we call them learning objectives or leearner objectives. The purpose at the episode level is to indicate the work and activities ahead in that particular episode.

So i think we should take it on to ensure that the objectives within each episode stay within those bounds, and we can amend these where it's appropriate to do so.

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

No branches or pull requests

3 participants