Click. Connect. Learn.

All posts in Open content + textbooks

Re-usable content, back to the basics, and knowing your tools

I've been on this kick lately of looking at the original architects of the web and what people were doing at that time. This picked up steam in January, 2013, right after our Open Content Authoring Day at EduCon when we started looking at the needed structure to support flexible open content authoring. This led to looking at the origin of REST; the functionality is available in the HTTP standard, but over time we (meaning a lot of people doing web development) just ignored it because of imperfect implementations and assuming everything was HTML, and (un)fortunately things have mostly worked.

There are some issues with how people currently imagine web apps because we:

  • Bolted on a lot of "features" that broke or hid the underlying methods and protocols;
  • We assumed everything was HTML;
  • And as a result created content with embedded markup.

As we move forward, we should think about HTML, JSON, etc. as delivery types not working types. That is, HTML and JSON are presentation issues, not editorial issues. This is the initial thought process we need when working with chunks. I say initial because we will likely expand and include methods or techniques to apply some structure around disparate chunks, but that is secondary to creating re-usable chunks and requires additional structure that is not intrinsic to the content itself. Concentrating on an API first should help us, and reviewing the original intent of the architects regarding REST APIs can provide insight into working with the tools we have rather than things working despite the tools we have.

This article, from 1997, has a lot of good thought around content, structure, and related issues. Fortunately, the transpublishing issues mentioned in the article are not as relevant to work with open content.

This piece, from 1999 (and again from Ted Nelson), defines the roots of some of the problems we have yet to shake. The more things change, the more they stay the same.

Except, unfortunately, some things that should never change often do - like URLs. In 1998 Tim Berners Lee explained that Cool URIs don't change. He even explains content negotiation, which can be used to help manage URIs and avoid exposing implementation details.

In order to progress we need to review our assumptions. As a trivial example when we see things like; 'page.html', 'page.php', or 'page.asp' show up in URLs we have to stop and think "why are we exposing implementation details?"

These problems are tricky to solve and some would argue all abstractions are leaky, and thus any implementation is going to expose some level of implementation detail. Regardless of whether or not that view is reflective of reality, each level of implementation detail that we do expose limits our choices for changing our implementation in the future.

As we move forward with the development of a better open content authoring platform, the mistakes of the past and present are close by. Architectural habits, and exposed implementations became an unquestioned part of system design. This is to the detriment of software getting built, and to the detriment of the people working with the software. Getting back to the basics avoids making the same mistakes.

I Have Some Word Docs...

A question we are asked on a fairly regular basis is:

I have a bunch of resources saved in Word docs. How can I release these as open content?

It's a pretty straightforward question, and one version of an answer is:

  1. Specify a license; and
  2. Publish your content online in something like Google Drive or Dropbox.

However, there are details and decisions buried in the steps outlined above that make this seemingly straightforward answer remarkably serpentine. This blog post is an effort to collect up some of the the various possible answers to that question in a single place.

Specify A License

First, the easy part: if you are the primary author of the work, and/or your work uses/remixes openly licensed content, all you need to do to make your content open content is choose a license, and specify how you want to be attributed. Then, include the license and your attribution information with your work, and voila! Done.

For example, this blog post (and all blog posts on FunnyMonkey.com) is licensed under a Creative Commons Attribution Share-Alike license. On my personal work, I ask that people link back to the FunnyMonkey home page.

So, my attribution text would look like:

This work is licensed under a Creative Commons Attribution Share-Alike license. If you reuse this work, please attribute authorship to Bill Fitzgerald at http://funnymonkey.com.

This formula will work as a start: This work is licensed under LICENSE. If you reuse this work, please attribute authorship to AUTHOR NAME at SOME LOCATION.

For people who want to learn more about the process and see more options, Creative Commons offers a form that will help with selecting a license and generate this text for you.

Publishing the Content

Once you have a license and attribution text for your work, the only piece that's left is publishing your work. As mentioned above, putting docs into something like Google Drive and DropBox is a viable option. People can access the work, and they can grab a copy of it themselves. Regardless of what you use, however, you want to make sure that it does not convert your content into a format that is more difficult to reuse than what you are starting with.

The choice of where you publish your content online has implications for two facets that are important when working with open content:

  • Ease of discovery - or, how easily can someone find your content via search; and
  • Ease of reuse - or, how easily someone can use or remix some of your content into a new work.

There are a couple nice things about throwing your content online in something like Google Drive or Dropbox. First, it's fast, and this implies a level of convenience. Second, it's easy, and many people know how to copy something from Google Drive or download something from Dropbox.

However, neither Google Drive or Dropbox is that good when it comes to ease of discovery. Additionally, using a proprietary service means that your content lives at someone else's place, rather than at a space you control.

An option that both increases the discoverability of your content and allows you greater control over where your content resides is to set up a blog using something like Wordpress. If you start with their service, you can choose to migrate to your own hardware at a later date. But, the most important element of using something like Wordpress is that you can publish summaries of your content as blog posts (which will make your content easy to find) and then upload the individual word doc containing the lesson.

Then, when you have all of your content uploaded with explanatory summaries, you can create a meta-post that links all the pages of your content. This combination takes more time, but it increases the likelhood of someone finding and understanding your work. An additional advantage of using blog software to share your content is that it provides a means for people interested in collaborating on the work an easy means to contact you.

It's also worth noting that uploading word docs should be viewed as a transitional step, and that the eventual goal should be text and supporting media that can be browsed online. However, the conversion from a doc stored in Google Docs, Word, or Libre Office takes time, and for many people that time can make the difference between sharing and not sharing.

An additional step to help other people find your work includes adding an entry in OER Commons. OER Commons acts as a clearinghouse for all types of OER, so being listed here will help more people find your work. Listing your work on OER Commons is a viable option whether your work is stored in Google Docs, Dropbox, Wordpress, or some other site.

Closing Thoughts

In closing, if you have directories full of work that you have created and want to share as open content, the shortest, fastest path to doing so is to put the work online in something like Google Drive or Dropbox. While these services are fast and convenient, they are also less than ideal when it comes to supporting community around open content, and reuse of open content.

Using blogging software to share content makes it easier for other people to find content, and starts to incorporate the possibility of collaborating with other people on maintaining the content.

For those looking to get started sharing open content, though, the only way to get it wrong is to not share. Choose a license, and get it on the web. The only way to ensure that your content has a limited impact is to not share in the first place.

The Web Is Your MOOC, and Portfolios To The Rescue

I'm getting ready to head in to DrupalCon, where over the next few days I'll be talking education and open learning with anyone who is interested.

And as I'm heading in, I have MOOCs on the brain - not because I'm particularly a fan of MOOCs, but because of the tendency to take a great thing (in this case, information and interpersonal exchanges distributed broadly over the web) and reduce it into something that feels more manageable, but is ultimately something lesser (in this case, MOOC platforms). More on this later.

The Web Is Your MOOC

Part of the reason that I'm thinking these thoughts prior to heading into DrupalCon is that I've long held the notion that open source communities have been engaging in effective peer-supported learning, even while many for-profit companies and academic communities have been struggling to distill the process of peer-supported learning into something resembling a replicable product. From having participated in and built many types of learning communities over the years, simpler is often better - many open source communities have done amazing work with listservs and issue queues, and many more feature-rich platforms have withered because, over time, a site owners "must-have" feature is the post launch usability nightmare. There's a moral in there about user-centered design and user testing, but that's a subject for another post.

But getting back to MOOCs, the early MOOCs - the ones run by Stephen Downes, Alec Couros, Dave Cormier, George Siemens, (and yes, I know I'm forgetting people - please fill in the gaps in the comments) etc - encouraged participation from anywhere. If you had a blog with an RSS feed, you were in. Participants remained in control of their work (depending, of course, on the publishing tool they were using. Open source platforms generally offer more options for data ownership and portability than their closed brethren). The MOOC was like a marauding mob of information, with the potential to sprout anywhere.

It's All About The Portfolio

In the post-lifestream, post-MOOC era, it's been rare to see much excitement about portfolios. This doesn't surprise me, because like all good ideas, portfolios have been around for a while, and thus lack the shiny newness that generates great marketing copy. However, the need for the concept hasn't diminished - any time you see a site that promises to collect the sources of your learning into a single location, so you can show your employers what you know! - you should think, "portfolio." All of the sites that promise to simplify collecting and curating your digital footprint? Portfolios. A lot of the conversations around documenting and receiving credit for informal learning have their roots (and possibly solutions) in portfolios.

In the conversations we have had about portfolios over the years, we have seen three main barriers, or areas of misunderstanding:

  • Distinguishing between a working and a presentation portfolio: simply put, the working portfolio is a running collection of just about everything you do. The presentation portfolio is a selection of elements from the working portfolio selected for a specific purpose. Portfolios can serve different purposes for different reasons, and the relationship between the working portfolio and the presentation portfolio is key.
  • Portfolios need care and feeding over time: as mentioned before, the working portfolio is messy. Periodically, the working portfolio needs to be pruned and cleaned up. But, messy is great, and if it's not messy, that could be a sign that things aren't working as they should.
  • Ownership and control of the portfolio: because most portfolio implementations are paid for by an organization, the organization usually controls access to the portfolio and any information in it. Organizational control is also seen as an essential element to assessment. However, this flies in the face of learner control and ownership of the means by which they learn. Ultimately, this is a data portability issue with implications for the learning experience. More on this later.

Concluding Thoughts

One of the things that has been particularly underwhelming about the corporate MOOCs that have cropped up is their uncanny resemblance to an LMS with an open enrollment policy. While there are many differences between the platform-stylehttps://chronicle.com/article/Providers-of-Free-MOOCs-Now/136117/ MOOCs and the original versions, the lack of learner control is a key element. Like Vegas, work in a MOOC stays in a MOOC (unless, of course, a company pays money to study student data).

In the platform-style MOOCs, the open web is missing. From a learner perspective, the portfolio is MIA. For a learner, throwing the evidence of your learning into a space that someone else controls isn't a viable long term strategy.

So, if you're at DrupalCon and want to talk open learning, let's make some time and sit down together. Open source, and the methodologies that support sustainable open source development, have a lot in common with open learning. I'd love to hear what other people are doing in this space.

Simple Is Usable, or Why Friends Don't Let Friends Apply Metadata Prematurely

As part of our work on open content, and how to design systems that support authoring and translation that are both useful and usable, we have been thinking about the role of metadata and, by extension, search. This post contains some incomplete thoughts - a line in the sand, more than anything - and, six months from now, will provide something for all of us to laugh at. Possibly, we will all be able to laugh at this sooner than that. Time can be cruel.

In other words, I am firmly reserving the right to recant any or all of what I'm saying here. I'd love to hear different viewpoints on this.

Keep Data Simple

This sounds - and is - pretty basic, right up until it's time to implement an actual system. However, as soon as it's time to build a system, people "just need this one field."

In building data systems, additional fields are the equivalent of scope creep.

faceted

Humans Should Only Enter Metadata In Precisely Defined Circumstances

We'll get to this in more detail later in this post, but whenever possible, metadata should de derived from the data.

In some cases, this is simple: the author of a piece of content is easy to derive. Ditto for the date a piece was created.

A good example of metadata that should be entered by a human is a license.

But, in the case of a person remixing data that uses different licenses, the pool of possible licenses for the remix should be derived.

Your Picture Is My Image Is Her Binary

A system-defined metadata can be useful, but it will be most useful for the people who designed and built the system, as they are the ones who define the system-specific meanings of the metadata terms.

In other words, your metadata will be useful to you, but it might not be useful to your users. For better or worse, metadata is rooted in language, and words carry baggage and connotations that, among a large group of individuals, make a universal meaning elusive at best.

With this in mind, the "best" metadata is often good search.

But Community Tagging Is Awesome

No, it isn't. Community tagging creates the appearance of structure and organization when what you really have is a chunky stew of chaos.

If you can get enough people contributing tags, then - maybe - you will be able to pull some signal from the noise, but that also assumes a large number of people and a robust search technology.

Faceted Search: Blech or Ugh?

In designing search systems for sites, faceted search can be useful at providing structure when sifting through content. However, is faceted search something that we actually appreciate,or something that we have grown accustomed to?

On Google, how often do you use faceted search, or go beyond the options that you can access via the advanced search UI?

If faceted search went away, or was replaced with facets generated from metadata that could be derived from the core dataset, what would be lost? Anything?

Look at your search habits. Identify if or when faceted search saved you time. In situations when you use faceted search, was faceted search essential, or could it have been replicated by full text search?

Search Has Its Limitations

But with all that said, search has its limitations.

Understanding how stemming works (or doesn't work) is essential to interpreting the results we get.

And this is more complex when we work with translated content in multiple languages.

"Just In Time" Metadata

There are times and places where good, structured metadata is essential. By separating out the metadata requirements from the actual dataset (and keeping the core data as simple as possible) you help ensure that the quality of your underlying data remains high.

Implementing a metadata structure around data is firmly in the domain of a context-specific application.

In terms of open educational resources, this allows for easier reuse of the data. If a piece of content was written in the US, a school looking to resuse that content in the UK won't care about the Common Core alignment of the resource.

To put this another way, inflicting a metadata standard on your data (as opposed to applying metadata within an application that uses the data) makes your data both less portable and less useful.

Portability

In listening to people who are writing and using open content, a key barrier we hear about repeatedly is portability (there are others as well, and these other issues will get their own posts).

A barrier to portability - and really, to the usability of authoring and translation platforms that support open content - is the premature and often unnecessary application of metadata into the underlying data. If we keep the data as clean as possible - which means resisting the urge to apply metadata without a compelling need - we can simplify both portability and usability. Metadata should be applied as part of an application that uses the data, when there is a clearly defined need to catagorize the data. And then, the categorization should be done by people who know what they are doing.

It doesn't matter how good your categorization system is if it is applied to your data inconsistently, and/or if no one uses your data.

Image Credit: "faceted" taken by jenny downing, published under an Attribution license.

Open Educational Resources, Professional Development, and Public Money

Yesterday, Darren Draper put out a post expressing some concerns with Teachers Pay Teachers. Shortly after putting out that post, Darren was forced to don his flame-and-troll-proof suit, as the comment thread got, well, interesting.

I'll get to the discussions in the comment thread later in this post, as a majority of the comments are illustrative of a small part of a larger problem.

OpenWashing, Teachers Pay Teachers Edition

Teachers Pay Teachers markets itself as "An open marketplace for educators where teachers buy, sell and share original teaching resources." In this context, Teachers Pay Teachers (or, TpT) provides a clear example of how the word "open" has been mangled beyond recognition.

Money

For those of us working in open source and open content, our notions of openness generally share some common pedigree with the four freedoms of free software, the definition of Open Source, and the Creative Commons licenses. It's worth noting that, even within these broad definitions, there is often vehement disagreement as to what constitutes open. However, even while acknowledging that there is no universally accepted definition of what "open" really is, it's still safe to say that TpT isn't it.

"Open" does not equal "being on the internet."

TpT is a marketplace, and this is fine, but a marketplace that anyone can enter isn't an "open" space, at least not in the context of Open Educational Resources. TpT puts technically unneeded barriers in the way of reusing content; the most obvious of these barriers is the need for a login even to download a free resource. The business need of TpT (collect contact info) is in direct conflict with greater openness, and TpT lets the business need trump the tendency to be more open.

And, of course, this is fine - it's just not open. If, however, your actual practice conflicts with your marketing catchphrase, that's not good.

I'll return to the TpT at the end of this post, but now, we're going to jump into Darren's post.

Private Time, Public Money

Darren lays out seven reasons why he struggles with TpT. I'm highlighting 5, 6, and 7, below:

5. Public school teachers are paid by the taxpayers - with public funds - to work during specific hours of the day.
6. The computer and other equipment used by public school teachers were all likely purchased by the taxpayers, using public funds.
7. It is my belief that classroom activities, assessments, games, handouts, outlines, posters, printables, research, worksheets, and the like - that have been created by a public educator during work time or with school-owned equipment - belong to the public and should therefore be licensed with an appropriate, open license. Resources created with public funds should neither be bought nor sold by teachers because they were never the teacher's to sell in the first place. Because these resources were created with public funds, they belong to the public.

I checked the comment thread on Darren's post before staring to write this response. When I looked, there were 34 comments - 19 of those comments focused on when content was created - and this is illustrative of the larger problem.

The question of who owns teacher-created content - and the nuances of the time of day and equipment used to create the content - came up in several of the Open Content Authoring events we ran over the last several months.

Our advice to this question in the short term:

  • Work on your curricular material outside of school hours, and use your personal account. Store a copy on personal hardware (an external hard drive, a personal blog, a personal Google Apps account, etc);
  • Let your district know that their policy on intellectual property creates an unnecessarily adversarial relationship around curriculum planning;
  • Let your district know that their policy on intellectual property creates a disincentive to you doing your best work, as the only way you can maintain ownership over your work is to do it outside "normal" working hours on your own equipment;
  • If you belong to a union, bring this to union leaders as an issue that needs to be on the table as part of contract negotiations;
  • Incorporate a piece of Creative Commons Licensed content into EVERYTHING you do for your work - make sure it is licensed under the Share-Alike clause. This means that your District can claim ownership of it, but that due to the nature of the license, you (and anyone else) is free to reuse it under the terms of the CC license.

In Darren's comment thread, the fact that so many commenters were fixated on the timing issue flags the reality that people are having a hard time seeing the forest for the trees. Fighting about the time of day when you are allowed to maintain control of your creative output means that you are living in the box that people laid out for you. Fighting about the time of day when you can do your work means that your perspective is limited at the outset. This comment illustrates the predicament perfectly:

I was so with you on this post, until it hinted that items were most likely being created on school time and/or with school equipment. I would encourage you to spend a week with me to see that I don't have enough hours in my "school day" prep time to make my weekly schedule, copy/assemble resources, grade papers, record grades, communicate with parents, and supervise my students during additional remediation opportunities. I consider myself lucky to sneak in a second bathroom break each day! :)
All of my TpT products are made by me, at home, on my personal equipment with software I've purchased myself (my classroom computer is a desktop that is over 8 years old) .That's *after* I have spent numerous additional hours per week grading papers, inputting grades, and emailing parents (from home, on my own computer). My dear husband can attest to the hours he has spent helping me cut, laminate, recut, and assemble centers for my kiddos.

The workload issues here sound very typical of most teachers that I know. There is not enough time in the workday to cover their professional responsibilities, so work comes home. Work spills into weekends. Budgets for supplies have been slashed, so teachers buy supplies out of their own pocket. School equipment is outdated or locked down to the point of unusable, requiring much prep to take place outside of school networks, on non-school machines. Teaching doesn't fit into the hours defined in most contracts, and teachers put in significant time outside of traditional working hours, in addition to spending their own money on class supplies.

And this is the conversation we should be having: why are teachers expected to power the underfunded mandates of increased reporting in the era of high stakes testing, with fewer resources, less support, in a work day that doesn't have room for all the demands on teacher time? Districts that have policies that claim ownership of teacher intellectual property are perpetuating that absurdity, and this absurdity needs to be addressed and clarified in employment contracts. Unions need to make this an issue as well.

Lessons Are Not The Ultimate Goal

The problem - and a shortcoming - of both traditional textbooks and content silos like TpT is that they treat a lesson as the stopping point. This makes sense for them, because both textbook companies and TpT make money from distribution. If there is no sale, there is no revenue. From a business place, this makes perfect sense.

Creating and using open content approaches the same problem - how do I get the best possible material to my class - from a different place. Teachers can use open content exactly as they would use a textbook, or a piece of content purchased from TpT; for many people, that is where their understanding of open content ends. However, that vision of open content is incomplete, and rooted in our habits of using material with restrictive licensing.

There are different levels of using open content; teaching lessons that use open content is the starting point. Remixing material that incorporates two or more openly licensed sources is a next step. Releasing that remixed version is the next step. Collaborating with other people to edit and remix content is an additional level of involvement.

And, if you look at the trajectory of using open content, it resembles the trajectory of learning. It's not a transaction (go here, buy this) - it's a series of interactions of increasing complexity, each of which requires judgment and expertise. Over time, building and using open content develops a professional network and a collection of domain level experts to work with. Working with people to create open content is some of the best ongoing professional development out there, and districts would be wise to embrace and support this reality. Rather than make absurd claims over ownership of teacher IP, they could divert some professional development money into supporting teacher time in a facilitated authoring process that spanned the course of a year. The resulting material could be released under a Creative Commons license, ensuring that teachers and the district were given the appropriate credit for their role in creating and funding the work, and material created with public money would remain available for public use.

Image Credit: "Money, get away!" taken by kiki follettosa, published under an Attribution Non-Commercial Share-Alike license.

I Don't Want To Make Too Much Out Of This, But...

At the outset, I want to make it clear that this blog post is not intended to be a comprehensive survey of all things related to Open Educational Resources at the US Federal level.

But with that said, from a high level, it's interesting seeing the move toward Open Educational Resources, and how they are referenced more frequently as both criteria for grants and as a deliverable of these grants.

At http://whyopenedmatters.org/ the Federal Department of Education is helping with outreach to articulate why OER's work.

In 2011, in a joint program between the Departments of Labor and Education, 2 Billion dollars were put toward a program that explicitly required materials produced be licensed under the Creative Commons Attribution license. In February, 2012, a second wave of funding was announced for the program.

And, in a related note, the inclusion of OERs is now listed as a priority for the Discretionary Grant Programs - broadly speaking, this means that Federal grant applications that explicitly reference OERs as part of the grant deliverables mayhave a better chance than other proposals.

Given this general trend at the Federal level, I wonder if/when this will translate into changes at the local level. For example, given the amount of public money being given each year to textbook companies to get proprietary content, why shouldn't there be a directive stating that public money should be spent on acquiring openly licensed content?

At the very least, the trend toward a broader support and use of OER should diminish support for school districts trying to claim copyright over teacher's work.

Understanding Open Content By Talking About Good Teaching

On Saturday, March 9th, we held an Open Content authoring day in San Francisco. It's the second we've put on this year, and for those interested, we have a third coming up in Portland, OR on April 6th.

The San Francisco meetup was held on the campus of Lick Wilmerding, made possible thanks to Jonathan Mergy. In the morning of the meetup in San Francisco, we spent some time working with the participants on converting existing lessons - stored in word docs, google docs, or as collections of files - into more granular, more easily reusable, chunks of information.

The work of transitioning existing instructional material into reusable open content is largely organizational, and involves reviewing and editing existing material to ensure that it is well organized and coherent. However - and this point cannot be emphasized enough - this review and editing process results in better material. This is something that, in an ideal world, would happen anyways. This review should be viewed through the lens of supporting better instructional design, and should be incorporated as part of ongoing teacher professional development. The process of organizing a lesson to make it easier to reuse as open content is EXACTLY THE SAME as reviewing a lesson to make sure it is coherent.

In the afternoon, the discussion included sketching out a rough road map for an entire school to transition to a broader, more regular use of open content. The key element in this transition involves reinforcing the idea that the process of creating open content is identical to the process of creating any other type of content - the only substantial difference is the license that is applied to the work. It sounds obvious, but when discussing open content, the notion of openness - and the new horizons implied by the philosophical shift in focus - often distract us from the familiar act of creating useful educational material.

The starting point for individual teachers, a department, or an entire school is exactly the same: the individual lessons that teachers have already created, currently stored on hard drives, in Google docs, in notebooks, and/or in filing cabinets. These lessons exist; many of them have been tested and revised multiple times. Cleaning up this existing source material - a practice that leads to better instructional design, and a practice that should be happening anyways - provides a starting point. It's also worth noting that teachers working in groups, revising the lessons of their colleagues, provides natural opportunities for peer mentoring.

In an earlier post, we talked about the steps involved in creating open content. Working teachers have already done the first steps. Most are at the point where they can edit and revise to make their work clearer - and, as a side benefit, easier to reuse.

Teachers have lessons and other educational materials. They create them regularly, and use them every day.

Like just about anything, this material can benefit from review, and this review can include reorganization into a structure that makes it easy to reuse the lessons.

Once the lessons have been edited and restructured, they can be sequenced into a unit or a course. At this point, the goals of the unit or course can be used to determine what additional material, if any, is needed to round out the work. If any new material is needed, it can be created, or sourced from other openly licensed content.

In practice, this would look something like this:

A General Open Content Roadmap

The review process - steps 2 and 3, where existing lessons are converted into smaller, more granular components, would occur periodically throughout the year. The process of sequencing the lessons - step 4 - would occur less regularly - perhaps 2-3 times a year - with a semi-annual review session - step 5 - dedicated to cleaning up full courses by filling in any gaps that aren't met with the material that has already been created. This way, the work unfolds gradually, and is a natural extension of the work already required to teach a course, and to prepare for upcoming classes. The process can be sped up, of course, but that requires more focused time, and people who have both the content area expertise and the available time to do the work. If this was implemented at the department level - with all teachers in a department collaborating over the course of a year on focused lesson cleanup - the first year would produce a solid body of work, and the second year could allow for greater levels of experimentation and sophistication - for example, Chemistry and Biology teachers and students could generate some 3d molecular models that could be incorporated into science texts.

But in any case, when we talk about creating open content, the discussion needs to be framed around the act of creating. Teachers are already doing this work, and many teachers are already on board with sharing their work to benefit others. However, we have found calling this process "creating open content" confuses the issue. When we are introducing people to the concept of open content, we need to talk less about the licensing issues, and more about sound instructional design. It sounds counter-intuitive, but we have found that by reinforcing what teachers know, and how that pre-existing knowledge dovetails cleanly with the new concept of open licensing, people understand the new concept - open licensing - more fully, even though we talk about it less. Open content is good teaching, and this is the discussion that we need to be having.

The Write Stuff, Portland - April 6

On April 6th, at Meriwether Lewis School, in Portland, OR, we will be hosting an open content authoring event. The event will be run unconference style, where participants will be able to work with peers as they research, create, and revise educational material. The day is free to attend, and lunch will be provided.

Eventbrite - The Write Stuff - Portland 2013

Based on past events we have run, we anticipate that most participants will be interested in one of five related tracks:

  • People looking to revise individual lessons;
  • People building/creating complete courses;
  • People supporting teachers/departments as they create their learning resources;
  • People who are not working on anything specific, but want to help convert existing openly licensed content into a more usable format;
  • People looking to learn more about open licensing, and how transitioning to open content can save money, increase teacher effectiveness, and be incorporated into ongoing teacher professional development.

If you are currently working on any curriculum, bring any resources you have collected, and we will work on these resources during the day. While there will be opportunities to discuss the philosophy behing open content, the main focus of these days is on the work: how can people get more benefit from the same effort by using a more open approach to their content?

If you are not working on any specific project, but want to work with a community of educators on creating open content, please come! There is a huge body of information that is high quality, but is not in a format or structure that supports reuse. With some time and work, we can fix that.

If your role in the educational world is to provide a vision for your organization, a portion of the day will also be dedicated to looking at how using open content can serve as a catalyst for transformation within a school. One of the things we will focus on is a recurring theme that we have seen as we have talked with teachers about open content: the planning process that every teacher does as they prepare for class is nearly identical to the the planning process for creating open content. The benefits of open content, however, accrue over time. Working with open content creates the implicit expectation that collaboration with peers is a normal and expected part of the preparation process.

This day is being organized by Bill Fitzgerald, Jeff Graham, and Andrea Burton, from FunnyMonkey. Tim Lauer has graciously allowed us to hold this event at Meriwether Lewis Elementary, and Rachel Wente-Chaney has arranged for lunch for all participants, sponsored by the Oregon Virtual School District.

So, what are you waiting for? Sign up to let us know you are coming, and we look forward to seeing you there!

Pre-requisites To Making The Most Of An Open Content Authoring Day

If you are thinking about going to an open content authoring day, here are some tips to help you get the most from the day:

  • Identify what you want to get from the day ahead of time. The authoring events are a mix of community work days and a maker space, and knowing what you want to do with your time will help you make the most of the day.
  • If your goals for the day include working on a specific project, try and make progress on your working outline and your initial research before the event. This way, during the event, you can work with other participants on structure, editing, and other elements of the project where you will benefit from outside review.
  • Glass blower
  • If your goals for the day don't include working on a specific project, that's fine - one of the other ways that you can participate in an open content authoring day is by helping to clean up existing open content that has been released in clumsy formats (pdfs, word docs, powerpoint, etc).
  • If your goal for the day is to learn more about open content, that's fine as well - most events will have an intro session on open content, but then you will get the chance to learn by doing. The open content authoring days have more in common with Project-based Learning or Maker events than with traditional lecture.
  • Identify potential partners - if you think that someone else might be working on a similar concept (or might be interested in working on a similar concept) ask them. If you can assemble a working group prior to the event, you will be better prepared to make the most of in-person meeting of the open content event.

Based on feedback we have gotten from other open content events we have run, we put together a series of posts to help provide background information for people authoring open content. This documentation works equally well for people looking to author open content on their own, with a small group in their school or organization, or for people attending open content authoring days.

But really, the short version of this post is that if you are coming to an open content authoring day, that's awesome. Talk about it. Talk about the work you want to do there. During the day, start the planning for the next one. Identify people you might want to work with to collaborate on a year long project where you each save ten of your best ideas, and then, over the summer, get together to refine that group of great ideas into the best open educational resource ever. The open content days are group work days, but as educators, every day is a work day. Using the ethos of open content, infused with the learn while doing of Project Based Learning, flavored with some of the inventiveness and freedom to experiment that comes from Maker spaces, let's see what we can build.

Image Credit: "Working - Glass Blower" taken by Bob Jagendorf, published under an Attribution Non Commercial license.

Open Content: Licensing, Attribution, and Reuse

Nearly every time we talk about open content, we are asked about licensing, reuse, and the possible risks of reuse. It's a complicated issue, but it is definitely worth noting that using Creative Commons licensed material is significantly less complex than traditional copyright. With authoring events coming up in Portland and San Francisco, we wanted to look at the resources that already existed to explain licensing, and come up with as simple a guide to licensing and reuse as possible.

This post is not intended to be a comprehensive review of either Creative Commons or traditional copyright. The purpose of this post is to provide people writing open content with some sound guidelines for using and remixing content.

Creative Commons Licensing: An Overview

Every one of the six Creative Commons license requires attribution of the original source, and we will look at attribution later in this post. In addition to attribution, a Creative Commons license can reserve the following rights for the author (or place the following obligations on people reusing the content):

  • Non-Commercial - work released under the NC license cannot be used in a commercial endeavor without the permission of the original creator;
  • Share Alike - when a work is released under the SA license, it requires that any future work that incorporates the original must be released under a comparable license;
  • No Derivatives - work released under the ND license cannot be altered or modified when it is reused.

Molly Kleinman has a series of posts on the details of using the Non-Commercial, the Share-Alike, and the No Derivatives licenses.

The public domain is another option; licensing your work in the Public Domain allows anyone, anywhere, to use your work in any way they see fit, without any obligation to attribute you as the original source.

A central reason that Creative Commons licensing gets confusing for people is that thinking about the license requires that we consider two different events: the initial act of creation; and how the initial work can be reused and adapted over time.

Remixing Work and License Compatibility

When we are creating open content, we will likely encounter - and want to use - content that has been licensed under several different licenses. When we are remixing a work and building on other openly licensed work, we need to consider the licenses of our source material as we choose the license of our new work. The chart included below (adapted from the Creative Commons FAQ on licensing work from multiple sources) shows how mixed licenses can be used.

Compatibility chart Licenses that may be used for a derivative work or adaptation
BY BY-NC BY-NC-ND BY-NC-SA BY-ND BY-SA PD
License of original work PD YES YES YES YES YES YES YES
BY YES YES YES YES YES YES  
BY-NC   YES YES YES      
BY-NC-ND              
BY-NC-SA       YES      
BY-ND              
BY-SA           YES  

As the chart shows, if a piece of source material is licensed under a Non-Commercial license, any work built on that would need to be Non-Commercial as well. When choosing a license, we are limited by the licenses of the work we are looking to incorporate. If a derived work uses information licensed under either of the Share-Alike licenses, the resulting work must also use the Share-Alike license. Accordingly, the license we choose will place similar limits on future uses of our work.

This isn't a bad thing, and to all the people who are saying that this is complicated: yes, but it is much more flexible and humane than the existing copyright system. At the end of this piece, I will demonstrate how to use this chart to navigate remixing different sources.

For additional information on reusing material licensed under different licenses, see Resolving License Conflicts When Authoring Open Content.

Attribution

Attribution is required under all Creative Commons licenses, and it is also just basic scholarship.

To attribute a work used in your open content, include the following information:

  • The author's name or pseudonym;
  • A link to the original work; if the resource isn't available online, then information (like publication date, publisher, magazine name, etc) to help someone else find and use the resource;
  • The title of the original work;
  • The license of the original work, with a link to the license, where possible;
  • If available, any applicable copyright dates.

Molly Kleinman has a good writeup on attribution, with examples.

This information can be collected at the end of your post, in a list of works cited and a list of works consulted.

Of these two lists, the list of works cited is the one that matters for choosing a license. When writing online, arguably, the list of works consulted can be inferred from the list of external links on a page.

At the end of this post, I include a list of works cited and a list of works consulted.

List of works remixed

In this post and our companion post on resolving licensing conflicts, we incorporated and reworked material sections from the three works listed above. Two of the works are licensed under the CC-BY license, and one is licensed under the CC-BY-SA license.

Using the matrix included above, we see that the CC-BY posts can be remixed into derivative works using many different licenses.

Our third work is licensed under a CC-BY-SA license; from looking at the matrix, we see that CC-BY works can be remixed into CC-BY-SA. Accordingly, the only choice on this post is CC-BY-SA. Given that this is the license we like to use, this works well.

List of works consulted

The list of works consulted does not affect the license used when publishing a work. When writing for the web, the list of works consulted can generally be inferred from the links in the post. In addition to the works linked in this post, we also read through the information in the posts listed below.

In addition to the posts listed below, Karen Fasimpaur provided some incredibly useful guidance with finding some of the resources used in this post.

Closing Notes

Questions about licensing have been one of the thornier elements to creating and reusing open content. However, with the large and growing body of high quality openly licensed resources that are available, navigating licenses is becoming easier. A goal of Creative Commons licensing is to facilitate sharing and reuse, and this is a fundamental shift in how we traditionally think about licensing.

Syndicate content