Speaker: Liane Taylor
Don’t make it into a spreadsheet when creating model licences. Think creatively. Check lists, ERM records, HTML pages, etc. Does it need to be shared? Will you be copying from it to send to licencors for negotiation? Also, find out if there is standard language for IT that your institution uses. Review model licenses from the field.
LibLicense (2008) is a great site for model licenses and examples, but instead of keeping it up to date, Ann Okerson has updated NERL (11/2012), so that’s the most recent example to use. Licensing Models (10/2009) was created by John Cox to host a series of model licenses based on library type, and has been kept updated. California Digital Library licensing kit is from 2011, but is mostly kept current. Taylor has compiled how each model handled each section, and will be making it more public soon.
Things are changing, though, and we’re licensing new things that we don’t yet know how to handle them. Data, images, streaming collections, etc. When exceptions become the rule, what do we do?
If you have all of this figured out, put it out there in a discoverable way so the rest of us don’t spin our wheels reinventing your brilliance. Community! Communication! Collaboration!
Do we need to have new standard licensing language for….? Autorenewal — replace it with language about mutual written agreement. Alumni might have access three months post graduation because of the way IT is set up, which might be a license violation. New vendors might not be familiar with libraries and who our authorized users might be. New uses/rights: repository, text mining, use on website/promotional materials, rip & stream on secure server, cloud hosting/distribution of CD-ROMs.
Where do we go from here? How do we as a community keep our resources up to date? Should we have more of a shared collection of exceptions? What can we do to help each other?