learn.5tein.com Jared Stein's grad-school-community blog on teaching and learning.

IPT 692R Notes – Thurs, Feb 12, 2009

Today’s session of BYU’s IPT 692R was a collaborative workshop day. The following are merely my contributions to the Google Doc, posted as per Dr. Wiley’s request:

Process

In order to notify faculty of open publishing, during the CTL design process faculty will be asked to sign the BYU OER Participation form. This form will:

• Describe the BYU OER project and the mission of CTL
• Acknowledge BYU ownership of IP produced by or in conjunction with CTL
• Explain CC By-NC-SA license
• Describe possible OER usage

Faculty who sign the BYU OER Participation form acknowledge the aforementioned and may choose to have their name (along with BYU and CTL) attributed to the OER. Faculty may opt out of attribution or not sign the form, however such refusal will not alter BYU’s ownership of CTL-produced IP or CTL’s ability to publish and share the CTL product as OER.

Technology

(The following is hypothesis only at this stage)

CTL OER products will be stored on a publicly accessible BYU OER web site (powered by Equella). The web site will:

• provide search features based on title, description, and other metadata
• list OER by topic or academic department
• attribute OER to BYU, CTL, and faculty contributor(s)
• demonstrate OER
• ? support direct linking to instances of OER
• support downloading of OER as modular packages
• ? provide source code or raw data of OER where applicable
• ? support community interaction by allowing user
• ? allow registered user commenting on OER
• ? allow registered user keyword tagging of OER

IPT 692R Notes – Tuesday, Feb 10, 2009

At the start of today’s class session of Dr. David Wiley’s IPT 692R at BYU, Aaron offered thanks for tithe payer contributions to BYU. In response David shoots, “Let’s figure out a way to give the tithe payer a little something back.”

SPARC provides a form that faculty can sign and send with manuscript publishing agreement we need a NSF mandate to automatically

This Week’s Challenge

Figure out how to put Center for Teaching and Learning resources into a library for open sharing.

1. Faculty disclosure in CTL process
2. License recommendation / “default” IP policy with override for third party publishing
3. Figure out Equella thing for publishing

Jon Mott recommends Equella for publishing platform. Equella is a CMS built by post-Bb guys, The Learning Edge International (JMS: Is it CMS or LMS? Sounds like the latter). An experimental Equella environment is available at BYU. “Activity assembler” available for sequencing LOs. Bill Lundt can talk about it.

(JMS: All these LMS innovators [GoCourse, eInstructure, Equella] had better consider what their “moat” will be to beat out Bb, D2L, Angel, Moodle, etc.)

IP Licensing

In context of CTL “walk-in” center, What license do we recommend? (JMS: Is CTL able to license materials? Does BYU have/need a process for approving CC licensing? I suppose we will find out…)

Perhaps CC By-NC (I am currently anti-SA, but that might change).

Dr. Wiley suggests SA may not be terribly meaningful. John Hilton gave a good case study, paraphrased:

If I publish By-NC then someone takes and remixes the content, s/he is not obligated to release under By-NC because of lack of the SA, so could a derivative version be licensed as By and then commercialized? Seems like the answer is yes.

(JMS: This sounds like a good thing to me as a creator. I only want to disallow commercialization of copies, but not necessarily of significantly altered works, remixed works, or derivatives.)

Justin: If NC then Creative Works Office doesn’t have to get involved(?)

(JMS: When in flow workers seem exceedingly efficient. How do we foster a work environment that inhibits interruption of workers’ flow?)

Documentary Filmmaker’s Guide to Fair Use

Here’s what we’re going to claim as Fair Use. If anyone has a problem with it, they can deal with us as a whole.

Movement amongst higher ed institutions in the works to apply Fair Use to media held within an OER (without altering the license of the © work).

Fair Use

1. Purpose (educational non-profit)
2. Nature of copyrighted (e.g. factual vs creative works)
3. Amount and significance
4. Impact of the use on potential market

BYU Center for Teaching and Learning Walk-In Center

• Anything within scope of employment belongs to creator.
• Anything created with any additional BYU resources, such as CTL staff, belongs to BYU.

CTL OER as default: we will share, but faculty may opt-out. Would such a form hurt the culture of BYU? Justin suggests a one-time form to opt-in.

CTL has 40-50 new projects a month, e.g. scanned images, PPT backgrounds, Flash animations, video, et c.

What about intentionality? Capture directions for use? Do we preserve teaching info as metadata? CTL Tracker tracks information. What about forum/discussion area for teacher-contributed suggestions for use? Could be. I’m seeing this like a Podcast on a blog platform.

(JMS: The CTL Tracker sounds like a great way to start and track a new project. Sounds like my original course design mapping app, but better. I wonder what software they use? Something home-grown? We need one of these, similar to our dP but more expansive, updating everthing such as Google Spreadsheet. How could dP be mod’ed to facilitate this?)

Independent Study might be able to contribute 10hrs a week to uploading OER to platform.

We could/should also go back in time to get permission on existing materials because there are so many great materials. Also, we could get MBA students working on case studies, Engineering students working on problem-based learning scenarios. (JMS: I’m feeling overwhelmed by the availability of resources her.)

(JMS: At UVU could we get a temporary blanket approval for OER from the President’s office, e.g. to say, From May 2009 – April 2010 we authorize all UVU-owned, DE-developed learning materials to be licensed under a CC license for use as OER. Renewable with signatory.)

(JMS: Seems like the first hurdle that we are skipping is getting BYU approval for CC licensing of CTL materials. Will this be done from CTL up?)

Seth: wants to go back to Equella and the importance of metadata. I agree, but the technical aspects of this seem far more easily manageable than the licensing process, which frightens me.

Tracker creates a new folder for each project. When project is completed it creates an archive folder. Completed product is moved physically and project folder is deleted. Is there a readme? No, you find data through the Tracker. Tracker stores faculty information. (JMS: How would we do this with dP? Is it built-in?) JMS: Could tracker take stored info and spit out a readme? Why not?

Could we provide both final file and source file(s)? 4 Rs. These would be uploaded/handed off to (OER) librarian for archiving and indexing. (JMS: Does DE need to get UVU librarians involved? Who is the institutional librarian at UVU? Jean D’emall might be or might know.

(ClassTop’s plugin uses Facebook to reuse OER and create self-organizing learning communities.)

Do we need to actually ask faculty to opt-in, or does this wrongly imply that faculty own the materials (in conflict with BYU IP policy)?

In an opt-in form we articulate that the materials are BYU owned under IP policy and that faculty acknowledge this when opting-in. We would do so as a professional courtesy, for even though faculty do not own this, they think they do. We are at the early stage of nurturing a cultural shift towards openness. Baby steps.

Is that Tracker software open source? (JMS: I might be able to mod it as suggested if UVU can have a license to the software. Will follow up at CTL afterwards)

Clarified that we will draft the document for CTL to request upper administrative permission to license ALL CTL-products as OER.

Spend Thursday as a group writing proposal document.

Class has moved from Know and Understand to Analyze and Apply.