This article is on the right track but doesn't investigate the subject to sufficient depth. Nadine Schroeder correctly identifies a need for version control in open educational resources (OER) and suggests that a mechanism similar to that used in GitHub, a software versioning platform, might be the answer. There are two issues, to my mind. First, it's not easy to learn how to use GitHub; even simple operations (such as uploading a recent version to the platform) require a sequence of steps. Second, the version numbering system in GitHub, which is described in the article, is superficial. What is actually keeping track of updates and versions in Git is a combination of content-based addressing and a directional acyclic graph (DAG). That's what I propose for OERs in my 2019 article. Either way, though, for such a system to be useful to academics, it needs to be as near to one-click submission as possible, with the mechanics hidden behind the interface.
Today: 1 Total: 18 [Direct link] [Share]
