Creative Commons - User contributions [en]

Data

2012-12-11T13:14:22Z

JonathanRees: move redirect info to top, following the wikipedia pattern for redirects (Alan R's suggestion)

''This page supersedes the 2006 document [[Databases and Creative Commons]].''

Much of the potential value of data is to society at large — more data has the potential to facilitate enhanced scientific collaboration and reproducibility, more efficient markets, increased government and corporate transparency, and overall to speed discovery and understanding of solutions to planetary and societal needs.

A big part of the potential value of data, in particular its society-wide value, is realized by use across organizational boundaries. How does this occur (legally)? Many sites give narrow permission to use data via terms of service. Much ad hoc data sharing occurs among researchers. And increasingly, open data is facilitated by sharing under public terms to manage copyright restrictions that might otherwise limit dissemination or reuse of data, e.g. [http://creativecommons.org/licenses/ CC licenses] or the [[CC0]] public domain dedication.

Many organizations, institutions, and governments are using CC tools for data. For case studies about how these tools are applied, see:

===[[Data_and_CC_licenses|Uses of CC Licenses with Data and Databases]]===
===[[CC0_use_for_data|Uses of CC0 with Data and Databases]]===

You can also read more about [http://creativecommons.org/weblog/entry/26283 Creative Commons' most up-to-date thinking on data and databases], and what you can do to contribute.

==Frequently asked questions about data==

==='''''Can databases be released under CC licenses?'''''===

Yes, CC licenses can be used on any copyrighted work, including a copyrighted database. A CC license may be applied to any or all copyrighted aspects of a database and its contents. See [[Data#How_do_I_apply_a_CC_legal_tool_to_a_database.3F|below]] for more information regarding how to provide clear notice of what is licensed. Any use of the licensed database or its contents that is restricted by copyright law requires compliance with the relevant license conditions (BY, SA, NC, ND). In their current version (3.0) CC licenses do not require compliance with the license conditions when only sui generis database rights (and not copyright) are implicated. Additionally, the international and "ported" version 3.0 licenses, excluding EU jurisdiction ports, do not grant any permissions where sui generis database rights are implicated. Please see [[Data#How_.28if_at_all.29_are_sui_generis_database_rights_addressed_in_CC_licenses.3F|below]] for more detail.

CC0, the public domain dedication, can also be used on databases. The effect is to waive all copyright and related rights in the database, placing it as close as possible into the worldwide public domain. In certain domains, such as science and government, there are important reasons to consider using tools like CC0. Waiving copyright and related rights eliminates all uncertainty for potential users, encouraging maximal reuse and sharing of information. Where waiver is not a viable option and some conditions on reuse are necessary, rights holders should [http://www.ivir.nl/publications/eechoud/CC_PublicSectorInformation_report_v3.pdf consider] using CC licenses that give the public more freedom to reuse and remix the content.

==='''''Which components of a database are protected by copyright?'''''===

With databases, there are likely four components to consider: (1) the database model or structure, (2) the data entry and output sheet, (3) field names, and (4) the data.

The '''database model''' is a specification describing how a database is structured and organized, including database tables and table indexes. The selection, coordination, and arrangement of the contents is subject to copyright if it is sufficiently original. The threshold of originality required for copyright is fairly low in many jurisdictions. For example, while courts in the United States have held that an alphabetical telephone directory did not have sufficient originality to merit copyright protection, an organized directory of Chinese-American businesses in a particular area did. These determinations are very fact-specific (no pun intended) and vary by jurisdiction.

The '''data entry and output sheets''' contain questions, and the answers to these questions are stored in a database. For example, a web page asking a scientist to enter a gene’s name, its pathway information, and its ontology would constitute a data entry sheet. The format and layout of these sheets are protected by copyright according to the same standard of originality used to analyze copyright in the database model.

'''Field names''' describe data sets. For example, “address” might be the name of the field for street address information. These are less likely to be protected by copyright because they often do not reflect originality.

The '''data''' contained in the database are subject to copyright if they are sufficiently creative. Original poems contained in a database would be protected by copyright, but purely factual data (such as gene names without more) contained in a database would not. Facts are not subject to copyright, nor are the ideas underlying copyrighted content.

==='''''How do I know whether a particular use of a database is restricted by copyright?'''''===

When the database structure or contents are subject to copyright, reproducing, distributing, or modifying the database will often be restricted by copyright law. If the database is released under a CC license, that means reproduction, distribution, or modification will likely require compliance with the relevant license conditions, including attribution.

However, it is important to note that some uses of a copyrighted database will not be restricted by copyright. It may be possible, for example, to rearrange or modify the uncopyrightable data in a way that does not implicate the copyright in the database structure. For example, while (as noted above) a court in the United States held that a directory of Chinese-American businesses was restricted by copyright, the same court went on to hold that a directory that duplicated hundreds of its listings was not infringing because the listings were categorized and arranged in a sufficiently dissimilar way. In those situations, compliance with the license conditions is not required unless the database contents are themselves restricted by copyright.

Similarly, even where database contents are subject to copyright and published under a CC license, use of the facts and ideas found in the contents will not require attribution (or compliance with other applicable license conditions), unless doing so implicates copyright in the database structure as explained above. This important limitation of CC licenses is reflected in the license deed, where it indicates that the license does not extend to those elements of the work in the public domain.

==='''''What are sui generis database rights?'''''===

Sui generis database rights are different from, but often overlap with, copyright. Sui generis database rights exist to recognize the investment required to compile a database, whether or not the database meets the originality requirement in copyright law. Established by [http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=CELEX:31996L0009:EN:HTML Directive 96/9/EC] of the European Parliament, sui generis database rights prohibit the extraction or reutilization of a substantial portion (defined in both qualitative and quantitative terms) of the contents of a database. The Directive has been implemented in the national legislation of all EU member countries. Outside of the European Union, similar database-like rights have been established in several countries, including Mexico and South Korea.

==='''''How (if at all) are sui generis database rights addressed in CC licenses?'''''===

The treatment of sui generis database rights varies among the CC version 3.0 licenses, but the practical result is always the same: compliance with the license conditions is not required where sui generis database rights - but not copyright - are implicated. This means that if someone takes a substantial portion of a CC-licensed database and uses it in a way that does not implicate copyright (e.g., by rearranging purely factual data), she does not have to attribute the licensor or comply with the other license conditions, even if the database is protected by sui generis database rights.

While this treatment is the same across all CC version 3.0 licenses, the reason for this outcome varies. In the ported 3.0 licenses ported to the laws of EU jurisdictions, works subject to copyright and/or sui generis database rights are licensed and subject to the CC license terms and conditions. In those ported licenses, however, the conditions of the license are explicitly waived when use of the licensed work only involves the exercise of database rights and not copyright.

By contrast, all other 3.0 licenses (including ported licenses for non-EU jurisdictions and the international licenses) do not license sui generis database rights at all. As a result, the license conditions do not (nor could they) attach to uses implicating database rights and not copyright. It also means a licensee may need separate permission if they plan to use the database in a way that implicates database rights (although there may arguably be an implied right to do so).

CC is [https://creativecommons.org/weblog/entry/29639 leaning toward] changing how its licenses treat sui generis database rights in version 4.0. If pursued, those rights would be fully licensed and subject to the same terms and conditions as copyright, without any waiver of the license conditions where only those rights are implicated. Read more about the issue -- including important limitations that would avoid imposing restrictions where those rights do not exist -- on the [[4.0/License subject matter|version 4.0 wiki]].

==='''''How do I apply a CC legal tool to a database?'''''===

Before making a database available under a CC license, a database provider must first make sure she has all rights necessary to do so. Often, the database provider is not the original author of the database contents, which may mean the database provider needs separate permissions from third parties before publishing the database under a CC legal tool. For more information, read our [[Before_Licensing|pre-licensing]] guidelines.

Also, the database provider must consider what elements of the database she wants to be covered by the CC legal tool and identify those elements in a manner that reusers will see and understand. Please see our [[Marking/Creators|marking page]] for more information on how to clearly distinguish unlicensed content.

Historical Data Pages

2012-12-11T13:09:57Z

JonathanRees: JonathanRees moved page Historical Data Pages to Databases and Creative Commons: match the name of the older page

#REDIRECT [[Databases and Creative Commons]]

Databases and Creative Commons

2012-12-11T13:09:42Z

JonathanRees: JonathanRees moved page Historical Data Pages to Databases and Creative Commons: match the name of the older page

For current information related to data sharing, see the [[Data]] page in this wiki.

The document "Databases and Creative Commons" prepared in 2006 that used to be available at the following URLs:
* http://sciencecommons.org/resources/faq/databases/,
* http://sciencecommons.org/databases/, or
* http://sciencecommons.org/data/dbfaq/

is superseded by the [[Data]] page in this wiki. If you seek the older document please consult
[http://web.archive.org/web/20110719001027/http://sciencecommons.org/resources/faq/databases/ the Internet Archive's copy of it].

Databases and Creative Commons

2012-12-11T13:07:13Z

JonathanRees: tweaking the wording, trying to figure out best way to do the discrimination

Data

2012-12-10T22:24:42Z

JonathanRees: direct people to historical document, if that's what they wanted

Much of the potential value of data is to society at large — more data has the potential to facilitate enhanced scientific collaboration and reproducibility, more efficient markets, increased government and corporate transparency, and overall to speed discovery and understanding of solutions to planetary and societal needs.

A big part of the potential value of data, in particular its society-wide value, is realized by use across organizational boundaries. How does this occur (legally)? Many sites give narrow permission to use data via terms of service. Much ad hoc data sharing occurs among researchers. And increasingly, open data is facilitated by sharing under public terms to manage copyright restrictions that might otherwise limit dissemination or reuse of data, e.g. [http://creativecommons.org/licenses/ CC licenses] or the [[CC0]] public domain dedication.

Many organizations, institutions, and governments are using CC tools for data. For case studies about how these tools are applied, see:

===[[Data_and_CC_licenses|Uses of CC Licenses with Data and Databases]]===
===[[CC0_use_for_data|Uses of CC0 with Data and Databases]]===

You can also read more about [http://creativecommons.org/weblog/entry/26283 Creative Commons' most up-to-date thinking on data and databases], and what you can do to contribute.

''If you were redirected here and were looking for the "Databases and Creative Commons" document prepared in 2006, please consult''
[http://web.archive.org/web/20110719001027/http://sciencecommons.org/resources/faq/databases/ ''the Internet Archive's copy of it''].

==Frequently asked questions about data==

==='''''Can databases be released under CC licenses?'''''===

Yes, CC licenses can be used on any copyrighted work, including a copyrighted database. A CC license may be applied to any or all copyrighted aspects of a database and its contents. See [[Data#How_do_I_apply_a_CC_legal_tool_to_a_database.3F|below]] for more information regarding how to provide clear notice of what is licensed. Any use of the licensed database or its contents that is restricted by copyright law requires compliance with the relevant license conditions (BY, SA, NC, ND). In their current version (3.0) CC licenses do not require compliance with the license conditions when only sui generis database rights (and not copyright) are implicated. Additionally, the international and "ported" version 3.0 licenses, excluding EU jurisdiction ports, do not grant any permissions where sui generis database rights are implicated. Please see [[Data#How_.28if_at_all.29_are_sui_generis_database_rights_addressed_in_CC_licenses.3F|below]] for more detail.

CC0, the public domain dedication, can also be used on databases. The effect is to waive all copyright and related rights in the database, placing it as close as possible into the worldwide public domain. In certain domains, such as science and government, there are important reasons to consider using tools like CC0. Waiving copyright and related rights eliminates all uncertainty for potential users, encouraging maximal reuse and sharing of information. Where waiver is not a viable option and some conditions on reuse are necessary, rights holders should [http://www.ivir.nl/publications/eechoud/CC_PublicSectorInformation_report_v3.pdf consider] using CC licenses that give the public more freedom to reuse and remix the content.

==='''''Which components of a database are protected by copyright?'''''===

With databases, there are likely four components to consider: (1) the database model or structure, (2) the data entry and output sheet, (3) field names, and (4) the data.

The '''database model''' is a specification describing how a database is structured and organized, including database tables and table indexes. The selection, coordination, and arrangement of the contents is subject to copyright if it is sufficiently original. The threshold of originality required for copyright is fairly low in many jurisdictions. For example, while courts in the United States have held that an alphabetical telephone directory did not have sufficient originality to merit copyright protection, an organized directory of Chinese-American businesses in a particular area did. These determinations are very fact-specific (no pun intended) and vary by jurisdiction.

The '''data entry and output sheets''' contain questions, and the answers to these questions are stored in a database. For example, a web page asking a scientist to enter a gene’s name, its pathway information, and its ontology would constitute a data entry sheet. The format and layout of these sheets are protected by copyright according to the same standard of originality used to analyze copyright in the database model.

'''Field names''' describe data sets. For example, “address” might be the name of the field for street address information. These are less likely to be protected by copyright because they often do not reflect originality.

The '''data''' contained in the database are subject to copyright if they are sufficiently creative. Original poems contained in a database would be protected by copyright, but purely factual data (such as gene names without more) contained in a database would not. Facts are not subject to copyright, nor are the ideas underlying copyrighted content.

==='''''How do I know whether a particular use of a database is restricted by copyright?'''''===

When the database structure or contents are subject to copyright, reproducing, distributing, or modifying the database will often be restricted by copyright law. If the database is released under a CC license, that means reproduction, distribution, or modification will likely require compliance with the relevant license conditions, including attribution.

However, it is important to note that some uses of a copyrighted database will not be restricted by copyright. It may be possible, for example, to rearrange or modify the uncopyrightable data in a way that does not implicate the copyright in the database structure. For example, while (as noted above) a court in the United States held that a directory of Chinese-American businesses was restricted by copyright, the same court went on to hold that a directory that duplicated hundreds of its listings was not infringing because the listings were categorized and arranged in a sufficiently dissimilar way. In those situations, compliance with the license conditions is not required unless the database contents are themselves restricted by copyright.

Similarly, even where database contents are subject to copyright and published under a CC license, use of the facts and ideas found in the contents will not require attribution (or compliance with other applicable license conditions), unless doing so implicates copyright in the database structure as explained above. This important limitation of CC licenses is reflected in the license deed, where it indicates that the license does not extend to those elements of the work in the public domain.

==='''''What are sui generis database rights?'''''===

Sui generis database rights are different from, but often overlap with, copyright. Sui generis database rights exist to recognize the investment required to compile a database, whether or not the database meets the originality requirement in copyright law. Established by [http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=CELEX:31996L0009:EN:HTML Directive 96/9/EC] of the European Parliament, sui generis database rights prohibit the extraction or reutilization of a substantial portion (defined in both qualitative and quantitative terms) of the contents of a database. The Directive has been implemented in the national legislation of all EU member countries. Outside of the European Union, similar database-like rights have been established in several countries, including Mexico and South Korea.

==='''''How (if at all) are sui generis database rights addressed in CC licenses?'''''===

The treatment of sui generis database rights varies among the CC version 3.0 licenses, but the practical result is always the same: compliance with the license conditions is not required where sui generis database rights - but not copyright - are implicated. This means that if someone takes a substantial portion of a CC-licensed database and uses it in a way that does not implicate copyright (e.g., by rearranging purely factual data), she does not have to attribute the licensor or comply with the other license conditions, even if the database is protected by sui generis database rights.

While this treatment is the same across all CC version 3.0 licenses, the reason for this outcome varies. In the ported 3.0 licenses ported to the laws of EU jurisdictions, works subject to copyright and/or sui generis database rights are licensed and subject to the CC license terms and conditions. In those ported licenses, however, the conditions of the license are explicitly waived when use of the licensed work only involves the exercise of database rights and not copyright.

By contrast, all other 3.0 licenses (including ported licenses for non-EU jurisdictions and the international licenses) do not license sui generis database rights at all. As a result, the license conditions do not (nor could they) attach to uses implicating database rights and not copyright. It also means a licensee may need separate permission if they plan to use the database in a way that implicates database rights (although there may arguably be an implied right to do so).

CC is [https://creativecommons.org/weblog/entry/29639 leaning toward] changing how its licenses treat sui generis database rights in version 4.0. If pursued, those rights would be fully licensed and subject to the same terms and conditions as copyright, without any waiver of the license conditions where only those rights are implicated. Read more about the issue -- including important limitations that would avoid imposing restrictions where those rights do not exist -- on the [[4.0/License subject matter|version 4.0 wiki]].

==='''''How do I apply a CC legal tool to a database?'''''===

Before making a database available under a CC license, a database provider must first make sure she has all rights necessary to do so. Often, the database provider is not the original author of the database contents, which may mean the database provider needs separate permissions from third parties before publishing the database under a CC legal tool. For more information, read our [[Before_Licensing|pre-licensing]] guidelines.

Also, the database provider must consider what elements of the database she wants to be covered by the CC legal tool and identify those elements in a manner that reusers will see and understand. Please see our [[Marking/Creators|marking page]] for more information on how to clearly distinguish unlicensed content.

Databases and Creative Commons

2012-12-10T22:14:36Z

JonathanRees: fix bad line break

For current information related to data sharing, see the [[Data]] page in this wiki.

If you were redirected to the [[Data]] page from one of these URLs:
* http://sciencecommons.org/resources/faq/databases/,
* http://sciencecommons.org/databases/, or
* http://sciencecommons.org/data/dbfaq/
and wish to refer to the document prepared in 2006 that used to be available at those locations, please consult
[http://web.archive.org/web/20110719001027/http://sciencecommons.org/resources/faq/databases/ the Internet Archive's copy of it].

Databases and Creative Commons

2012-12-10T22:12:56Z

JonathanRees: Disambiguation page for old Science Commons database FAQ

4.0/Treatment of adaptations

2011-11-29T21:13:16Z

JonathanRees: /* Proposals for simplifying license compliance in 4.0 */ The do-nothing proposal

{{4.0 Issue}}

'''Summary''' = Four licenses in the CC license suite -- CC BY, CC BY-SA, CC BY-NC, and CC BY-NC-SA -- allow licensees to create adaptations of the licensed work. By definition, an adaptation constitutes the new contributions by the person adapting the work and does not extend to the preexisting material.<ref>Article 2(3) of the Berne Convention: “Translations, adaptations, arrangements of music and other alterations of a literary or artistic work shall be protected as original works ''without prejudice to the copyright in the original work.''” (emphasis added) </ref> Accordingly, when an adaptation of a CC-licensed work is created and licensed, the new license only applies to the adapter’s new contributions and not the original content. The original work is licensed to the downstream user directly from the original author. This is because CC licenses do not allow sub-licensing.<ref>See section 8(b) of CC BY: “Each time You Distribute or Publicly Preform an Adaptation, Licensor offers to the recipient a license to the original Work on the same terms and conditions as the license granted to You under this License.”</ref> In other words, when someone uses an adapted work, they are often technically subject to two licenses, one for the adaptation and one for the original work. This nuance raises some complications with respect to the way CC licenses operate.

== How to license adaptations ==

When a licensee creates an adaptation of a CC-licensed work, he is required to release adaptations under the same license if the original work is licensed with a ShareAlike condition. But if the the original is licensed under CC BY or CC BY-NC, there is no express requirement to license adaptations under particular terms and conditions. CC’s [[FAQ]] state that adaptations must be released under a license at least as restrictive as the original, but this obligation is not explicit in the license.

Rather, to create an adaptation of a work licensed CC BY, the license says the adapter must attribute the original work, identify that his new work is an adaptation, and include the URI for the license under which the original is released. If the creator of the adaptation complies with these conditions, he may believe he is free to release his adaptation under any license, including CC0, or keep all rights reserved.

Similarly, to create an adaptation of a work licensed CC BY-NC, the license says the adapter must meet the same requirements as BY, but also avoid using the original work for commercial purposes. If the creator of the adaptation complies with these conditions, including using his adaptation for non-commercial purposes only, he may believe he can license his adaptation without the NC condition.

CC’s license text has been criticized on this point for the following reasons:
# Because the license text does not explicitly dictate how adaptations must be licensed in CC BY and CC BY-NC, it is open to an interpretation that allows adaptations to be released under a less restrictive license, which may contradict the intentions of licensors.
# If adaptations are released under a different license than the original, it complicates the license obligations of downstream users as explained in detail below.

=== Proposal for dictating how adaptations are licensed in 4.0 ===

* '''Add explicit requirement to BY and BY-NC stating that adaptations of licensed work must be released under a license with at least the same conditions as the original work.'''
** Pros:
** Cons
**Other comments:

== License obligations of downstream users ==

As explained above, when someone creates an adaptation of a CC-licensed work and licenses it, the license on the adaptation only covers the adapter’s contributions and does not extend to the original content. To the extent the original work remains distinguishable in the adaptation, the original is licensed to the downstream user directly from the original licensor. In other words, the person using the adapted work is the licensee under two separate licenses -- one from the adapter with respect to the new elements (i.e. the adaptation), and one from the original creator with respect to the original.

This creates a number of complications:
* '''definition of “work”''': because CC licensors are not obligated to identify exactly what “work” they are licensing, users of the adapted work may not be able to determine what elements of the literary or artistic work are original to the adapter
* '''attribution stacking''': the user of the adapted work must attribute the licensor of the adaptation and the licensor of the original work to the extent she uses the work in a way that implicates the copyright in both
* '''conflicting obligations''': if the adaptation is licensed under a different license than the original work, the user of the new work may be subject to conflicting license obligations when using the adapted work

=== Proposals for simplifying license compliance in 4.0 ===
[Note: these proposals are not necessarily mutually exclusive]

* '''Require all licensors to fill in the “definition of work” to identify the elements covered by the license before applying any CC license.'''
** Pros:
** Cons
**Other comments:

* '''Require licensors of works that are adaptations of pre-existing works to include a clear notice that the license to the original work may also apply to those who use the adaptation.'''
** Pros:
** Cons
**Other comments:

* '''Add explicit requirement to all licenses stating that adaptations of licensed work must be marked to distinguish new content from the original work.'''
** Pros:
** Cons
**Other comments:

* '''Require licensors of works that are adaptations of pre-existing works to copy/paste (or otherwise specify) attribution requirements for the original works in a fixed location (to ease compliance by licensees with all applicable licenses).'''
** Pros:
** Cons
**Other comments:

* '''Clarify and amplify the status of adaptations within the license text without adding any of the above new conditions to the license; at the same time publish a best practices tutorial note explaining the nature of adaptations and the highlighting the need to call out all applicable licenses when publishing an adapted work, so that users are made aware of all the conditions that apply (not just those related to the adaptation).'''
** Pros:
** Cons:
** Other comments:

''[Please add other proposals here]''

== Related debate ==
''We encourage you to sign up for the license discussion mailing list, where we will be debating these and other 4.0 proposals. HQ will provide links to related email threads from the license discussion mailing list here.''

== Relevant references ==
''Please add citations that ought inform this 4.0 issue below.''

== Notes ==
<references/>

Talk:Case Studies

2011-07-18T22:31:44Z

JonathanRees:

Write in here if you have [[Casestudies/HOWTO|unanswered questions]] about adding a [[Case_Studies|case study]] or if you have a request.

== Thoughts on promotion & further development ==

What we need is a way to present them on different websites. As a start, a CC affiliate page should be able to display a widget that shifts or randomly picks case studies and displays an elegant graphic / logo + short text. At best, these would be varied with regard to content and geography. A more advanced version would allow anyone to display such widget - and maybe personalize it: only CC BY content, only music and literature, only asian, and so on. --[[User:Michelle Thorne|Michelle Thorne]] 16:33, 29 July 2010 (UTC)

== WANTED: ITETHIC ==

See http://itethic.pbwiki.com I'm trying to add the Creative Commons content from the ITETHIC class [[User:Pageman|pageman]] 22:27, 8 February 2009 (UTC)
:I left you a message on your user talk page -- you have to confirm your email address. [[User:Mike Linksvayer|Mike Linksvayer]] 22:39, 8 February 2009 (UTC)

== WANTED: Chris Kelty/2bits ==

See http://savageminds.org/2009/01/24/two-bits-at-six-months/ and http://savageminds.org/2009/01/30/two-bits-smackdown-author-vs-lazyweb/ for some relevant observations/data --[[User:Mike Linksvayer|Mike Linksvayer]] 03:16, 31 January 2009 (UTC)

== WANTED: Prelinger Archives ==

Old interview at http://creativecommons.org/weblog/entry/7064

Case study should be up to date and explain the role of the public domain in enabling the business. --[[User:Mike Linksvayer|Mike Linksvayer]] 17:28, 4 February 2009 (UTC)

== WANTED: Wikitravel and Wikitravel Press ==

Nice roundtrip story -- free content bought by company even though they could have copied it -- [http://gondwanaland.com/mlog/2006/10/10/community-the-new-ip/ the community of maintainers is the hard to replicate thing] -- then the original founders started another company to print books based on the same content, Wikitravel Press. --[[User:Mike Linksvayer|Mike Linksvayer]] 18:51, 8 February 2009 (UTC)

== WANTED: Jeremy Keith ==

Photo used in Iron Man http://creativecommons.org/weblog/entry/11118

Q&A about his CC experiences http://adactio.com/journal/1549

--[[User:Mike Linksvayer|Mike Linksvayer]] 18:51, 8 February 2009 (UTC)

==WANTED: Uwe Hermann ==

As user of CC licensed music http://www.hermann-uwe.de/podcast

And as publisher of CC licensed photos; he has tracked reuse http://www.hermann-uwe.de/blog/list-of-my-creative-commons-licensed-photos-being-used-elsewhere

Mentions on CC blog http://creativecommons.org/?s=hermann

--[[User:Mike Linksvayer|Mike Linksvayer]] 18:51, 8 February 2009 (UTC)

==WANTED: Mercy Corps==
Example case of CC0
--[[User:Michelle Thorne|Michelle Thorne]] 10:20, 17 April 2009 (UTC)

==WANTED: Charis Tsevis==
Commercially successful photoshop artist, published in Time, Elle, and more. See Flickr stream: http://www.flickr.com/photos/tsevis/
--[[User:Michelle Thorne|Michelle Thorne]] 09:37, 27 April 2009 (UTC)

==WANTED: Government use of CC==
http://wiki.creativecommons.org/Government_use_of_CC_licenses -- any or all!
--[[User:Michelle Thorne|Michelle Thorne]] 09:29, 6 May 2009 (UTC)

== VEB Leipzig ==

full-length films (Die Letzte Drogge and Route 66)
http://www.vebfilm.net/
--[[User:Michelle Thorne|Michelle Thorne]] 09:24, 15 June 2009 (UTC)

== ProPublica ==
"The Los Angeles Times, Mother Jones, USA Today, Salon, Politico, and Huffington Post published our work since May 1. "

http://www.propublica.org/article/how-you-or-your-newsroom-can-republish-propublicas-stories-515
--[[User:Michelle Thorne|Michelle Thorne]] 09:24, 15 June 2009 (UTC)

== Al Jazeera CC Repository ==
http://cc.aljazeera.net/
--[[User:Michelle Thorne|Michelle Thorne]] 09:24, 15 June 2009 (UTC)

== WANTED: Pacific.Scoop ==

'''Project:''' Pacific.Scoop

'''Person/org:''' Pacific Media Centre, Creative Industries Research Institute, AUT Communications, Auckland University of Technology

'''Country:''' New Zealand

'''Licence:''' CC BY-NC-ND 3.0 New Zealand

'''Medium:''' Online news media

'''Contact details:''' http://pacific.scoop.co.nz, mailto:pmc@aut.ac.nz

--[[User:Elliott bledsoe|Elliott bledsoe]] 00:03, 3 March 2010 (UTC)

== WANTED: Now and Then ==

'''Project:''' Now and Then

Now and Then is a community heritage website that enables local communities to record, explore and share information about their history and life today.

'''Person/org:''' Collections Council of Australia

'''Country:''' Australia

'''Licence:''' CC BY-SA 2.5 Australia

'''Medium:''' Wiki

'''Contact details:''' http://www.nowandthen.net.au, mailto:wikis@collectionscouncil.com.au

--[[User:Elliott bledsoe|Elliott bledsoe]] 00:45, 3 March 2010 (UTC)

== WANTED: South East Asia Satellite Data DVD ==

'''Project:''' South East Asia Satellite Data DVD set for the International Forest Carbon Initiative

'''Person/org:''' Geoscience Australia

'''Country:''' Australia, South East Asia

'''Licence:''' CC BY 2.5 Australia

'''Medium:''' DVD, data

--[[User:Elliott bledsoe|Elliott bledsoe]] 02:16, 3 March 2010 (UTC)

== WANTED: Mashup Australia ==

'''Project:''' Mashup Australia competition

'''Person/org:''' Government 2.0 Taskforce

'''Country:''' Australia

'''Licence:''' CC BY 2.5 Australia

'''Contact details:''' http://mashupaustralia.org

--[[User:Elliott bledsoe|Elliott bledsoe]] 02:22, 3 March 2010 (UTC)

== WANTED: Wholesale Meat Music ==

'''Person/org:''' Wholesale Meat Music

Independent Adelaide based grunge/indie/experimental record label

'''Country:''' Australia

'''Licence:''' CC BY 2.5 Australia

'''Medium:''' Music, record labels

--[[User:Elliott bledsoe|Elliott bledsoe]] 00:15, 4 March 2010 (UTC)

== WANTED: Slow Release ==

'''Project:''' Slow Release

Slow Release is an online record label and store . Select audio works published by Slow Release Records are licensed under a Creative Commons Attribution-Noncommercial-No Derivative Works 2.5 Australia License. See http://slowrelease.waapamusic.com/creative-commons

'''Person/org:''' [http://www.waapa.ecu.edu.au Western Australian Academy of Performing Arts], [http://www.ecu.edu.au Edith Cowan University]

'''Country:''' Australia

'''Licence:''' CC BY-NC-ND 2.5 Australia

'''Medium:''' Music

'''Contact:''' http://slowrelease.waapamusic.com

--[[User:Elliott bledsoe|Elliott bledsoe]] 10:53, 8 March 2010 (UTC)

== WANTED: Michigan Digital Cutlure Books ==

http://www.digitalculture.org/books

All under BY-NC-* licenses AFAICT, from UMich Press.

--[[User:JonathanRees|Jonathan Rees]] 18 July 2011

== WANTED: Open Access Publishers ==

They all use CC-BY. [http://www.biomedcentral.com/ BioMed Central]; [http://www.plos.org/ PLoS]; [http://www.hindawi.com/ Hindawi]

--[[User:JonathanRees|Jonathan Rees]] 18 July 2011

== WANTED: Khan Academy ==

http://khanacademy.org/ - the web pages are marked CC BY-NC-SA, and my guess is that this applies to the embedded videos as well.

--[[User:JonathanRees|Jonathan Rees]] 18 July 2011

Talk:Case Studies

2011-07-18T22:30:18Z

JonathanRees: /* WANTED: Michigan Digital Cutlure Books */

Write in here if you have [[Casestudies/HOWTO|unanswered questions]] about adding a [[Case_Studies|case study]] or if you have a request.

== Thoughts on promotion & further development ==

What we need is a way to present them on different websites. As a start, a CC affiliate page should be able to display a widget that shifts or randomly picks case studies and displays an elegant graphic / logo + short text. At best, these would be varied with regard to content and geography. A more advanced version would allow anyone to display such widget - and maybe personalize it: only CC BY content, only music and literature, only asian, and so on. --[[User:Michelle Thorne|Michelle Thorne]] 16:33, 29 July 2010 (UTC)

== WANTED: ITETHIC ==

See http://itethic.pbwiki.com I'm trying to add the Creative Commons content from the ITETHIC class [[User:Pageman|pageman]] 22:27, 8 February 2009 (UTC)
:I left you a message on your user talk page -- you have to confirm your email address. [[User:Mike Linksvayer|Mike Linksvayer]] 22:39, 8 February 2009 (UTC)

== WANTED: Chris Kelty/2bits ==

See http://savageminds.org/2009/01/24/two-bits-at-six-months/ and http://savageminds.org/2009/01/30/two-bits-smackdown-author-vs-lazyweb/ for some relevant observations/data --[[User:Mike Linksvayer|Mike Linksvayer]] 03:16, 31 January 2009 (UTC)

== WANTED: Prelinger Archives ==

Old interview at http://creativecommons.org/weblog/entry/7064

Case study should be up to date and explain the role of the public domain in enabling the business. --[[User:Mike Linksvayer|Mike Linksvayer]] 17:28, 4 February 2009 (UTC)

== WANTED: Wikitravel and Wikitravel Press ==

Nice roundtrip story -- free content bought by company even though they could have copied it -- [http://gondwanaland.com/mlog/2006/10/10/community-the-new-ip/ the community of maintainers is the hard to replicate thing] -- then the original founders started another company to print books based on the same content, Wikitravel Press. --[[User:Mike Linksvayer|Mike Linksvayer]] 18:51, 8 February 2009 (UTC)

== WANTED: Jeremy Keith ==

Photo used in Iron Man http://creativecommons.org/weblog/entry/11118

Q&A about his CC experiences http://adactio.com/journal/1549

--[[User:Mike Linksvayer|Mike Linksvayer]] 18:51, 8 February 2009 (UTC)

==WANTED: Uwe Hermann ==

As user of CC licensed music http://www.hermann-uwe.de/podcast

And as publisher of CC licensed photos; he has tracked reuse http://www.hermann-uwe.de/blog/list-of-my-creative-commons-licensed-photos-being-used-elsewhere

Mentions on CC blog http://creativecommons.org/?s=hermann

--[[User:Mike Linksvayer|Mike Linksvayer]] 18:51, 8 February 2009 (UTC)

==WANTED: Mercy Corps==
Example case of CC0
--[[User:Michelle Thorne|Michelle Thorne]] 10:20, 17 April 2009 (UTC)

==WANTED: Charis Tsevis==
Commercially successful photoshop artist, published in Time, Elle, and more. See Flickr stream: http://www.flickr.com/photos/tsevis/
--[[User:Michelle Thorne|Michelle Thorne]] 09:37, 27 April 2009 (UTC)

==WANTED: Government use of CC==
http://wiki.creativecommons.org/Government_use_of_CC_licenses -- any or all!
--[[User:Michelle Thorne|Michelle Thorne]] 09:29, 6 May 2009 (UTC)

== VEB Leipzig ==

full-length films (Die Letzte Drogge and Route 66)
http://www.vebfilm.net/
--[[User:Michelle Thorne|Michelle Thorne]] 09:24, 15 June 2009 (UTC)

== ProPublica ==
"The Los Angeles Times, Mother Jones, USA Today, Salon, Politico, and Huffington Post published our work since May 1. "

http://www.propublica.org/article/how-you-or-your-newsroom-can-republish-propublicas-stories-515
--[[User:Michelle Thorne|Michelle Thorne]] 09:24, 15 June 2009 (UTC)

== Al Jazeera CC Repository ==
http://cc.aljazeera.net/
--[[User:Michelle Thorne|Michelle Thorne]] 09:24, 15 June 2009 (UTC)

== WANTED: Pacific.Scoop ==

'''Project:''' Pacific.Scoop

'''Person/org:''' Pacific Media Centre, Creative Industries Research Institute, AUT Communications, Auckland University of Technology

'''Country:''' New Zealand

'''Licence:''' CC BY-NC-ND 3.0 New Zealand

'''Medium:''' Online news media

'''Contact details:''' http://pacific.scoop.co.nz, mailto:pmc@aut.ac.nz

--[[User:Elliott bledsoe|Elliott bledsoe]] 00:03, 3 March 2010 (UTC)

== WANTED: Now and Then ==

'''Project:''' Now and Then

Now and Then is a community heritage website that enables local communities to record, explore and share information about their history and life today.

'''Person/org:''' Collections Council of Australia

'''Country:''' Australia

'''Licence:''' CC BY-SA 2.5 Australia

'''Medium:''' Wiki

'''Contact details:''' http://www.nowandthen.net.au, mailto:wikis@collectionscouncil.com.au

--[[User:Elliott bledsoe|Elliott bledsoe]] 00:45, 3 March 2010 (UTC)

== WANTED: South East Asia Satellite Data DVD ==

'''Project:''' South East Asia Satellite Data DVD set for the International Forest Carbon Initiative

'''Person/org:''' Geoscience Australia

'''Country:''' Australia, South East Asia

'''Licence:''' CC BY 2.5 Australia

'''Medium:''' DVD, data

--[[User:Elliott bledsoe|Elliott bledsoe]] 02:16, 3 March 2010 (UTC)

== WANTED: Mashup Australia ==

'''Project:''' Mashup Australia competition

'''Person/org:''' Government 2.0 Taskforce

'''Country:''' Australia

'''Licence:''' CC BY 2.5 Australia

'''Contact details:''' http://mashupaustralia.org

--[[User:Elliott bledsoe|Elliott bledsoe]] 02:22, 3 March 2010 (UTC)

== WANTED: Wholesale Meat Music ==

'''Person/org:''' Wholesale Meat Music

Independent Adelaide based grunge/indie/experimental record label

'''Country:''' Australia

'''Licence:''' CC BY 2.5 Australia

'''Medium:''' Music, record labels

--[[User:Elliott bledsoe|Elliott bledsoe]] 00:15, 4 March 2010 (UTC)

== WANTED: Slow Release ==

'''Project:''' Slow Release

Slow Release is an online record label and store . Select audio works published by Slow Release Records are licensed under a Creative Commons Attribution-Noncommercial-No Derivative Works 2.5 Australia License. See http://slowrelease.waapamusic.com/creative-commons

'''Person/org:''' [http://www.waapa.ecu.edu.au Western Australian Academy of Performing Arts], [http://www.ecu.edu.au Edith Cowan University]

'''Country:''' Australia

'''Licence:''' CC BY-NC-ND 2.5 Australia

'''Medium:''' Music

'''Contact:''' http://slowrelease.waapamusic.com

--[[User:Elliott bledsoe|Elliott bledsoe]] 10:53, 8 March 2010 (UTC)

== WANTED: Michigan Digital Cutlure Books ==

http://www.digitalculture.org/books

All under BY-NC-* licenses AFAICT, from UMich Press.

== WANTED: Open Access Publishers ==

They all use CC-BY. [http://www.biomedcentral.com/ BioMed Central]; [http://www.plos.org/ PLoS]; [http://www.hindawi.com/ Hindawi]

== WANTED: Khan Academy ==

http://khanacademy.org/ - the web pages are marked CC BY-NC-SA, and my guess is that this applies to the embedded videos as well.

Staff/2010-06-30

2010-06-29T19:35:58Z

JonathanRees:

== Call info ==

== Staff Updates ==

=== Nathan Kinkade ===
* I have finally finished finding, resolving and cleaning up the data for several bugs in CiviCRM and our custom one-click donation code.
* I just lately upgraded our Drupal install to version 6.17 (from 6.15). Drupal runs http://support.creativecommons.org. Still need to upgrade a couple modules.
* I'm currently upgrading our WordPress install (runs creativecommons.org) to version 3.0, and am working through some potential problems with our theme and/or a custom plugin that isn't working with the latest version.
* Mentoring a Google Summer of Code student developing a [http://labs.creativecommons.org/2010/05/24/gsoc-project-introduction-cc-wordpress-plugin/ CC WordPress plugin].
* Answering emails to info@creativecommons.org

=== Cameron Parkins ===

* Finished design primer
* Met w/ Creative Migration about integrating CC-licensing across their distribution plan for documentary work
* Originating contacts for ease of use
* Assisting with various fundraising tasks AD delegates me
* Worked w/ Protagonize to help flesh out CC licensing options
* Assisted TicTacDo w/ licensing questions
* ASCAP web roundup assistance for ES

=== Alex Roberts ===

* Launched supporter analytics page - https://support.creativecommons.org/figures
* Launched beta of new search - http://labs.creativecommons.org/demos/search
* Updating, improving, and testing various parts of the support site
* Fall fundraising campaign development
* Newsletter revamping and development

=== Mike Linksvayer ===

* At [http://communia2010.org COMMUNIA] in Turin, meeting with a number of CC leads from affiliates in the region, especially with regards to Europeana, public domain, collecting societies, OER, metadata, affiliate upgrades, grant proposals review and planning [http://wikimania2010.wikimedia.org/wiki/Submissions/Creative_Commons_global_affiliate_network%E2%80%93origin,_role,_future,_including_collaboration_and_shared_learnings_with_Wikimedia_chapters Wikimania presentation] with Alek Tarkowski (CC Poland) and Michelle Thorne begin_of_the_skype_highlighting end_of_the_skype_highlighting begin_of_the_skype_highlighting end_of_the_skype_highlighting begin_of_the_skype_highlighting end_of_the_skype_highlighting.
* Writing proposals for collaboration with related organizations.

=== Timothy Vollmer ===

* attending uspto-ntia symposium: copyright policy, creativity & innovation in the internet economy - july 1
* OER Advocacy Coalition monthly call we discussed Common Core Standards and potential for integration with OER - discussing next steps
* iNACOL K-12 OER survey sent out and responses trickling in - 48 so far
* Wayne Mackintosh OER Policy interview up - http://creativecommons.org/weblog/entry/22470
* spec-ing out CC materials for inclusion in potential OER toolkit for educational technology directors
* meeting up with Michael Edson from Smithsonian to discuss OER aspects of Smithsonian Commons project

===Kaitlin Thaney===

* Last week at CC - very bittersweet. will miss you guys and gals. :)
** lots of transition emails
** handing over reigns to grant management, other tasks, programmatic work
* Sage
** second Workstream telecon, already starting to prepare for next year of work on issues such as citation, standards, tools and internationalization for global data sharing. public engagement group is new this year, and a very important component moving forward.
* Semantic Resources Collaboration
** prepping with the team a means of moving forward and achieving pre-established goals / deliverables.
* Grant renewals, grant renewals, grant renewals.
* Sent out next funder dispatch. You can find an archive of them here: http://sciencecommons.org/resources/funder/dispatches/ and more at http://sciencecommons.org/resources/funder/
* Logistical tidying up. Shipping SC Cambridge office boxes to SF headquarters, goodbyes, etc.

===Tal Niv===
* Writing and rewriting the general structure for the CC-C(ontribution) white paper
* Working my way through it – starting to draw up an outline for each chapter.
* Setting on a theoretical infrastructure
**institutional analysis
**transaction cost economics,microanalysis
**art as innovation
* Laying out the data requirements for project.
* Getting more in depth input from CC-people on their respective field.

=== Christopher Webber ===

* Did thorough testing and fixing various issues for the (re)launch of the "Sanity" branch of the Creative Commons license engine
** Fixed some bugs in RDF tooling where defaultLanguage was not set and `./bin/license add` wouldn't add the jurisdiction field.
** Some pages were missing ability to set target language via lang query parameter.
** Found a bug in the CC0 email-me-this-output feature where it gave the string representation of the license.title method instead of actually calling it and printing the output.
** Sending email from CC0 page would redirect to /ccengine-fcgi/* kind of url when mounted that way (which the user shouldn't actually see because of the aliasing). Fixed that.
** After i18n update of formatters, were missing the image header (unit tests didn't catch this, so I didn't realize it sooner). Resolved.
** CC0 partner page was missing.
** CC0 RDF was missing the foaf:logo assertions. Added.
** Some pages not supporting RTL correctly. Resolved.
** A couple of <br />'s missing in the new i18n'ified formatter output
** /licenses/publicdomain/ was broken
* Bugfixing a number of issues with new formatter in cc.license
** Various fields not escaped
** dc:type / format wasn't going through in rendered output. The formatters, instead of accepting the actual dc:type (like MovingImage), expected other names like 'video', which it would thus transform into MovingImage.
** There was no public domain formatter in new cc.license, was mistakenly using the normal HTMLFormatter. Resolved and updated sanity cc.engine
** Mapping of work_info -> work_dict incorrect in cc.engine, meaning some useful information was missing from RDFa output
* Did a bunch of thorough testing to make sure all was good in sanity branch of cc.engine
* Launched cc.engine sanity. A few bumps while re-launching, but we're running the new engine, and all looks good now.
* Sometimes sanity was being slow to come up when restarting cc.engine w/ fcgid. Turns out we had MaxProcessCount at 500... heh. Moved it down to 25 and sanity starts up fast now.
* Sent a couple of emails about post-sanity license engine launch
** What was discovered while testing sanity before launch
** How to make license.rdf & cc.i18npkg deployment easier to servers
* GSOC mentoring Akila on his CC OpenOffice.org plugin

=== Alea Garbagnati ===

* Met with Lila to discuss the progress of the FAQ Project
* Finalized re-categorization of FAQs for the FAQ Project
* Set up Google Documents for updating each category of FAQs
* Working on first round of edits for the first two categories of FAQs

=== Aurelia J. Schultz ===
* Jurisdiction Team revamp with Diane and Michelle
* Internet Services Policy draft
* Porting - review of 2 jurisdiction's draft licenses
* Africa - communications re: Catalyst Grant Proposals

=== Reg Leones ===
* Reviewed CC license porting process
* Identified legal concepts and license terms of interest in the Unported BY-NC-SA 3.0 legal code
* Pre-Porting Questionnaire updates
* Preliminary comparative review of BY-NC-SA 3.0 legal codes in Netherlands, Spain, UK and Australia.

=== Melissa Reeder ===
* Managing Catalyst Campaign - ends June 1st
* Planning meetings and dinners for Joi and key constituents
* Continuing to manage annual campaign planning - runs from Oct. 1 - Dec. 31st with goal of raising $550,000
* Facts and figures page now live! https://support.creativecommons.org/figures also working on integrating analytics into everything development
* Helped submit organizational effectiveness grant proposal to Hewlett for board training and capacity building
* General grant management duties, day to day, etc.

=== Jonathan Rees ===

* Reviewed my overall work portfolio with John W.
* Library Linked Data W3C interest group - joined telecons.
* Semantic Resources project:
** meetings
** worked with Tim D on characterizing mouse strains and 'central dogma' ontology
** started thinking about task list for final report
** discussed annotation ontology with Paolo
* W3C TAG:
** Persistent linking: went over outline of report on architecture of 'persistence' with Larry Masinter
** Took another look at Memento, implications for 'HTTP semantics'
* Discussed provenance with Alan, Mike, & Nathan

== Alex Kozak ==

* Finishing up the SJ 2.0 report for submission to journal this coming Monday.
* Building the Jurisdiction Databse and License Porting databse on the CC wiki. It will be 1) a database of jurisdictions and some useful metadata about them, and 2) a connected database of CC license porting data in each jurisdiction (what legal issues arose, how the license defines X, etc.)
* Catalyst grant application help and grant page changes.
* Wrote a [http://creativecommons.org/weblog/entry/22500 post] about [http://discovered.creativecommons.org/search/ DiscoverEd] and the code sprint in Michigan (also see [http://labs.creativecommons.org/2010/06/18/discovered-code-sprint-day-3/ CC Labs]).
* DiscoverEd crawl has stalled due to a bug, hoping to run that soon. Need to work on separating discovered.cc.org from DiscoverEd in the documentation, and migrate this whiteboard photo of the DiscoverEd architecture to a wiki page.
* Misc. Calidornia Digital Textbook Initiative conversations, meeting next week.
* Discussing submitting recommendations re: metadata and Common Core ed. standards.
* Public metadata q/a

== Jane Park ==

*catching up on email and getting up to speed on new developments from vacation
*editing tvol's OER Policy Interview with Wayne Macintosh
*exploring CC license integration with Conspiracy for GOOD folks
*correspondence with bloggers who announced the Catalyst Campaign
**updating database of blogger outreach
*ongoing co-planning of Drumbeat NYC
*fleshing out CC use cases for a design primer
*beginning to work on integrating relevant ccLearn documents into wiki.cc.org/Marking and revamping in general for greater clarity, effectiveness
*miscellaneous communications, blogging, tweeting, news

== Allison Domicone ==

* Planning and publicizing next CC Salon on July 6; targeted outreach to relevant organizations involved in innovative online and offline sharing/collaboration
* Developing new strategies for the CC newsletter to make it more interesting and engaging
* Planning for our fall fundraising campaign
* Ongoing volunteer coordination. We have volunteers helping to fulfill store orders and mail thank-you letters to donors, as well as helping to do research and database clean-up.

Staff/2010-06-30

2010-06-29T19:34:07Z

JonathanRees: /* Allison Domicone */

== Call info ==

== Staff Updates ==

=== Nathan Kinkade ===
* I have finally finished finding, resolving and cleaning up the data for several bugs in CiviCRM and our custom one-click donation code.
* I just lately upgraded our Drupal install to version 6.17 (from 6.15). Drupal runs http://support.creativecommons.org. Still need to upgrade a couple modules.
* I'm currently upgrading our WordPress install (runs creativecommons.org) to version 3.0, and am working through some potential problems with our theme and/or a custom plugin that isn't working with the latest version.
* Mentoring a Google Summer of Code student developing a [http://labs.creativecommons.org/2010/05/24/gsoc-project-introduction-cc-wordpress-plugin/ CC WordPress plugin].
* Answering emails to info@creativecommons.org

=== Cameron Parkins ===

* Finished design primer
* Met w/ Creative Migration about integrating CC-licensing across their distribution plan for documentary work
* Originating contacts for ease of use
* Assisting with various fundraising tasks AD delegates me
* Worked w/ Protagonize to help flesh out CC licensing options
* Assisted TicTacDo w/ licensing questions
* ASCAP web roundup assistance for ES

=== Alex Roberts ===

* Launched supporter analytics page - https://support.creativecommons.org/figures
* Launched beta of new search - http://labs.creativecommons.org/demos/search
* Updating, improving, and testing various parts of the support site
* Fall fundraising campaign development
* Newsletter revamping and development

=== Mike Linksvayer ===

* At [http://communia2010.org COMMUNIA] in Turin, meeting with a number of CC leads from affiliates in the region, especially with regards to Europeana, public domain, collecting societies, OER, metadata, affiliate upgrades, grant proposals review and planning [http://wikimania2010.wikimedia.org/wiki/Submissions/Creative_Commons_global_affiliate_network%E2%80%93origin,_role,_future,_including_collaboration_and_shared_learnings_with_Wikimedia_chapters Wikimania presentation] with Alek Tarkowski (CC Poland) and Michelle Thorne begin_of_the_skype_highlighting end_of_the_skype_highlighting begin_of_the_skype_highlighting end_of_the_skype_highlighting begin_of_the_skype_highlighting end_of_the_skype_highlighting.
* Writing proposals for collaboration with related organizations.

=== Timothy Vollmer ===

* attending uspto-ntia symposium: copyright policy, creativity & innovation in the internet economy - july 1
* OER Advocacy Coalition monthly call we discussed Common Core Standards and potential for integration with OER - discussing next steps
* iNACOL K-12 OER survey sent out and responses trickling in - 48 so far
* Wayne Mackintosh OER Policy interview up - http://creativecommons.org/weblog/entry/22470
* spec-ing out CC materials for inclusion in potential OER toolkit for educational technology directors
* meeting up with Michael Edson from Smithsonian to discuss OER aspects of Smithsonian Commons project

===Kaitlin Thaney===

* Last week at CC - very bittersweet. will miss you guys and gals. :)
** lots of transition emails
** handing over reigns to grant management, other tasks, programmatic work
* Sage
** second Workstream telecon, already starting to prepare for next year of work on issues such as citation, standards, tools and internationalization for global data sharing. public engagement group is new this year, and a very important component moving forward.
* Semantic Resources Collaboration
** prepping with the team a means of moving forward and achieving pre-established goals / deliverables.
* Grant renewals, grant renewals, grant renewals.
* Sent out next funder dispatch. You can find an archive of them here: http://sciencecommons.org/resources/funder/dispatches/ and more at http://sciencecommons.org/resources/funder/
* Logistical tidying up. Shipping SC Cambridge office boxes to SF headquarters, goodbyes, etc.

===Tal Niv===
* Writing and rewriting the general structure for the CC-C(ontribution) white paper
* Working my way through it – starting to draw up an outline for each chapter.
* Setting on a theoretical infrastructure
**institutional analysis
**transaction cost economics,microanalysis
**art as innovation
* Laying out the data requirements for project.
* Getting more in depth input from CC-people on their respective field.

=== Christopher Webber ===

* Did thorough testing and fixing various issues for the (re)launch of the "Sanity" branch of the Creative Commons license engine
** Fixed some bugs in RDF tooling where defaultLanguage was not set and `./bin/license add` wouldn't add the jurisdiction field.
** Some pages were missing ability to set target language via lang query parameter.
** Found a bug in the CC0 email-me-this-output feature where it gave the string representation of the license.title method instead of actually calling it and printing the output.
** Sending email from CC0 page would redirect to /ccengine-fcgi/* kind of url when mounted that way (which the user shouldn't actually see because of the aliasing). Fixed that.
** After i18n update of formatters, were missing the image header (unit tests didn't catch this, so I didn't realize it sooner). Resolved.
** CC0 partner page was missing.
** CC0 RDF was missing the foaf:logo assertions. Added.
** Some pages not supporting RTL correctly. Resolved.
** A couple of <br />'s missing in the new i18n'ified formatter output
** /licenses/publicdomain/ was broken
* Bugfixing a number of issues with new formatter in cc.license
** Various fields not escaped
** dc:type / format wasn't going through in rendered output. The formatters, instead of accepting the actual dc:type (like MovingImage), expected other names like 'video', which it would thus transform into MovingImage.
** There was no public domain formatter in new cc.license, was mistakenly using the normal HTMLFormatter. Resolved and updated sanity cc.engine
** Mapping of work_info -> work_dict incorrect in cc.engine, meaning some useful information was missing from RDFa output
* Did a bunch of thorough testing to make sure all was good in sanity branch of cc.engine
* Launched cc.engine sanity. A few bumps while re-launching, but we're running the new engine, and all looks good now.
* Sometimes sanity was being slow to come up when restarting cc.engine w/ fcgid. Turns out we had MaxProcessCount at 500... heh. Moved it down to 25 and sanity starts up fast now.
* Sent a couple of emails about post-sanity license engine launch
** What was discovered while testing sanity before launch
** How to make license.rdf & cc.i18npkg deployment easier to servers
* GSOC mentoring Akila on his CC OpenOffice.org plugin

=== Alea Garbagnati ===

* Met with Lila to discuss the progress of the FAQ Project
* Finalized re-categorization of FAQs for the FAQ Project
* Set up Google Documents for updating each category of FAQs
* Working on first round of edits for the first two categories of FAQs

=== Aurelia J. Schultz ===
* Jurisdiction Team revamp with Diane and Michelle
* Internet Services Policy draft
* Porting - review of 2 jurisdiction's draft licenses
* Africa - communications re: Catalyst Grant Proposals

=== Reg Leones ===
* Reviewed CC license porting process
* Identified legal concepts and license terms of interest in the Unported BY-NC-SA 3.0 legal code
* Pre-Porting Questionnaire updates
* Preliminary comparative review of BY-NC-SA 3.0 legal codes in Netherlands, Spain, UK and Australia.

=== Melissa Reeder ===
* Managing Catalyst Campaign - ends June 1st
* Planning meetings and dinners for Joi and key constituents
* Continuing to manage annual campaign planning - runs from Oct. 1 - Dec. 31st with goal of raising $550,000
* Facts and figures page now live! https://support.creativecommons.org/figures also working on integrating analytics into everything development
* Helped submit organizational effectiveness grant proposal to Hewlett for board training and capacity building
* General grant management duties, day to day, etc.

== Alex Kozak ==

* Finishing up the SJ 2.0 report for submission to journal this coming Monday.
* Building the Jurisdiction Databse and License Porting databse on the CC wiki. It will be 1) a database of jurisdictions and some useful metadata about them, and 2) a connected database of CC license porting data in each jurisdiction (what legal issues arose, how the license defines X, etc.)
* Catalyst grant application help and grant page changes.
* Wrote a [http://creativecommons.org/weblog/entry/22500 post] about [http://discovered.creativecommons.org/search/ DiscoverEd] and the code sprint in Michigan (also see [http://labs.creativecommons.org/2010/06/18/discovered-code-sprint-day-3/ CC Labs]).
* DiscoverEd crawl has stalled due to a bug, hoping to run that soon. Need to work on separating discovered.cc.org from DiscoverEd in the documentation, and migrate this whiteboard photo of the DiscoverEd architecture to a wiki page.
* Misc. Calidornia Digital Textbook Initiative conversations, meeting next week.
* Discussing submitting recommendations re: metadata and Common Core ed. standards.
* Public metadata q/a

== Jane Park ==

*catching up on email and getting up to speed on new developments from vacation
*editing tvol's OER Policy Interview with Wayne Macintosh
*exploring CC license integration with Conspiracy for GOOD folks
*correspondence with bloggers who announced the Catalyst Campaign
**updating database of blogger outreach
*ongoing co-planning of Drumbeat NYC
*fleshing out CC use cases for a design primer
*beginning to work on integrating relevant ccLearn documents into wiki.cc.org/Marking and revamping in general for greater clarity, effectiveness
*miscellaneous communications, blogging, tweeting, news

== Allison Domicone ==

* Planning and publicizing next CC Salon on July 6; targeted outreach to relevant organizations involved in innovative online and offline sharing/collaboration
* Developing new strategies for the CC newsletter to make it more interesting and engaging
* Planning for our fall fundraising campaign
* Ongoing volunteer coordination. We have volunteers helping to fulfill store orders and mail thank-you letters to donors, as well as helping to do research and database clean-up.

== Jonathan Rees ==

* Reviewed my overall work portfolio with John W.
* Library Linked Data W3C interest group - joined telecons.
* Semantic Resources project:
** meetings
** worked with Tim D on characterizing mouse strains and 'central dogma' ontology
** started thinking about task list for final report
** discussed annotation ontology with Paolo
* W3C TAG:
** Persistent linking: went over outline of report on architecture of 'persistence' with Larry Masinter
** Took another look at Memento, implications for 'HTTP semantics'
* Discussed provenance with Alan, Mike, & Nathan