Comments (5)
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.
from lc-fair-research.
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?
from lc-fair-research.
I have opened issues to discuss the learning objectives per Episode. That might ease the way of working with them.
from lc-fair-research.
As a reminder: Learning objectives are the highest level and focus on what the learner will learn (see comment from Liz in issue #8 ).
from lc-fair-research.
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.
from lc-fair-research.
Related Issues (20)
- Populate learning objectives for Episode 5 - Reusable HOT 5
- Populate learning objectives for Episode 6 - Licenses HOT 4
- Populate learning objectives for Episode 7 - Assessment HOT 5
- Change "Scientific lifecycle" to "research lifecycle" HOT 9
- Exercise ideas for Episode 2 - Findable HOT 1
- Should software be integrated throughout the whole lesson? HOT 4
- Research Life cycle Headings & Key Points HOT 7
- Ask contributors to use persistent identifiers (like DOIs) in lesson contents HOT 1
- Lesson Contribution - Data and Software Management Plans
- Challenge-Findable HOT 7
- Challenge-F2/F3-Metadata
- Challenge-ORCID-Findable lesson
- Exercise ideas for Accessible
- Exercise idea for Reusable HOT 3
- Additional examples for Choosing the Right Repository in episode 2- Findable
- Exercise idea for Interoperability HOT 3
- Broken links in CONTRIBUTING.md
- Typo in Top 10 FAIR Data and Software Things: Nanotechnology (checkout) HOT 1
- Lesson Contribution: Introduction
- Need jump lists (anchors) for headings
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from lc-fair-research.