Open mbjones opened 1 year ago
Here is some information about how the Data Carpentries, NEON lectures, Earth Lab Lessons, and the Data Management Training Clearinghouse (DMTC) add metadata for archiving and organizing their modules.
Date Carpentries lessons are organized into episodes.
Each episode’s YAML header must contain: the episode’s title time estimates for teaching and exercises motivating questions lesson objectives a summary of key points
For example, this is the YAML for the Using RMarkdown episode:
---
source: Rmd
title: "Using RMarkdown"
teaching: 10
exercises: 2
questions:
- "How to write a lesson using RMarkdown?"
objectives:
- "Explain how to use RMarkdown with the new lesson template."
- "Demonstrate how to include pieces of code, figures, and challenges."
keypoints:
- "Edit the .Rmd files not the .md files"
- "Run `make serve` to knit documents and preview lesson website locally"
---
NOTES:
I really like the teaching
and exercises
timing information. It could also serve to distinguish between modules where participants mostly work on exercises and modules where there’s more lecturing. However, I would change teaching
and exercises
to something like teaching-time
and exercises-time
to make it explicit it is the timing (at first I thought exercises: 2 meant there were 2 exercises).
NEON teaching modules are part of the Quantitative Undergraduate Biology Education and Synthesis (QUBES) lesson repository. According to their website,
The QUBES platform hosts hundreds of teaching materials, reference materials, and cloud-based software free to use and adapt using open Creative Commons licenses.
In the filters tab in the QUBES lesson browser, there are three main tags associated with each lesson. These are the tags with the corresponding subtypes:
Resource Type:
Audience level:
Activity length:
Other less used tag categories are:
The NEON teaching modules use the first three tags and call these “alignments”. Here's an example module. Most modules have further subcategories for each alignment. For example:
Audience Level
Resource Type
The NEON teaching modules also include a citation with information about author, year of publication, title, version number and doi. Example:
Lesley Bulluck (2019). Testing hypotheses about the role of wildfire in structuring avian communities. NEON Faculty Mentoring Network, (Version 2.0). QUBES Educational Resources. doi:10.25334/R2S1-4S62
NOTES: I really liked the core three alignments: audience level, resource type and activity length. The activity length could complement the other time-tracking metadata about lecturing and exercises. I was surprised the “software used” tag wasn’t as used. This would be good to include for us too. Having software used = None for non-technical modules could also be an option.
The Earth Lab only hosts resources developed by Earth Lab at University of Colorado, Boulder. The lessons are organized into the following topics:
LESSONS BY TOPIC:
NOTES: Having a topic tag could be good and these are some possible values for it.
According to their website:
Data Management Training Clearinghouse (DMTC) is a registry for excellent online learning resources focusing on data skills and capacity building for research data management, data stewardship and data education.
Learning resources can be browsed using the following filters:
Filters
Additionally, these are the tags from the metadata Matt shared:
NOTES: Many of the tags in the complete metadata are about submission to the module to DMTC, so these would be needed. Others, like access_cost, license, language_primary, and language_secondary, will probably be the same for all the modules we develop, so we could keep these out for now. Keywords, target_audiece, completion_time, and title are some we could add right away. Once the module becomes stable we could include url, citation and authors.
We could add metadata in stages. To begin, these could be some informative tags that align well with the previous learning materials repositories:
I looked through Earth Lab’s GitHub. The lessons can be found in the _posts
folder. This is an example:
yml header:
layout: single category: courses title: "Time Series Data in Python" permalink: /courses/use-data-open-source-python/use-time-series-data-in-python/ week-landing: 1 modified: 2020-09-11 week: 1 sidebar: nav: comments: false author_profile: false course: "intermediate-earth-data-science-textbook" module-type: 'session'
From these I’d suggest we add ‘course’ and, maybe, ‘permalink’ (url) (at least when we have a rendered final version of the lessons).
Hi @mbjones . Here's a sample yaml file for the sections, let me know what you think:
https://github.com/cyber2a/cyber2a-course/blob/main/section_metadata_blank.yml
It might be a bit too long to copy have it at the beginning of each lesson. Is it possible to have a separate .yml file associated with lesson's .qmd file?
Good question. I don't know if you can include another file.
We will want to distribute our lessons widely, and it will be helpful to have structured metadata for the lessons to be used in search and discovery. The ESIP Data Management Training Clearinghouse has an established metadata vocabulary for courses, and would make a good starting point for our work -- see below for an example of that metadata. But we also should evaluate metadata vocabularies used in other related initiatives, including the Carpentries (see their example format for lessons), the NEON modules, and EarthLab courses.
Here's an example metadata record from the DMTC for a DataONE lesson on metadata:
Each lesson in the DMTC has an identifier, and with that , you can downloaded the lesson metadata from the DMTC API (see DMTC API documentation) using the following command: