https://wiki.creativecommons.org/api.php?action=feedcontributions&user=Couponcode&feedformat=atomCreative Commons - User contributions [en]2024-03-28T20:35:11ZUser contributionsMediaWiki 1.30.0https://wiki.creativecommons.org/index.php?title=Kenya&diff=97334Kenya2014-03-05T17:55:38Z<p>Couponcode: </p>
<hr />
<div>{{Jurisdiction<br />
|jurstatus=Active<br />
|country code=ke<br />
|twitter=http://twitter.com/CCKenya<br />
|region=Africa<br />
|affiliated=CIPIT, Strathmore Law School<br />
|affurl=http://www.cipit.org<br />
|afffocus=Intellectual Property, Information Technology<br />
|afftype=academic institution<br />
|affiliated2=National Council of Law Reporting<br />
|affurl2=http://www.kenyalaw.org<br />
|afffocus2=Kenyan Courts and Laws<br />
|afftype2=governmental body<br />
|plead1=Michael Murungi<br />
|pemail1=mmurungi@kenyalaw.org<br />
|ptitle1=Chief Executive, National Council for Law Reporting<br />
|plead2=Isaac Rutenberg<br />
|pemail2=iruten@gmail.com<br />
|ptitle2=Director, CIPIT<br />
|plead3=Lillian Makanga<br />
}}<br />
AFFILIATE TEAM ROADMAP, CREATIVE COMMONS<br />
Jurisdiction: Kenya (East Africa - Africa)<br />
Date submitted: 6 March 2013<br />
Timespan of this roadmap: January 2013 to December 2013<br />
<br />
Public lead: Centre for Intellectual Property and Information Technology law (CIPIT)<br />
<br />
Dr. Isaac Rutenberg [Intellectual property and Social media] (Director and Lead Consultant) holds a J.D. from Santa Clara University School of Law (California, 2011) and a Ph.D. in Chemistry from California Institute of Technology (2005). He is a Registered Attorney with the California State Bar and he is registered to practice before the US Patent and Trademark Office.<br />
<br />
Lillian Makanga Wothaya [Research and evangelism] holds an LLB (Hons) degree from the Catholic University of Eastern Africa (CUEA) a post graduate diploma in law from the Kenya School of Law and currently awaiting admission to the Bar as an Advocate of the High Court of Kenya. She has previously worked at MMC Africa Advocates where she gained experience in the practice of Intellectual Property Law as well as other legal disciplines. As part of CIPIT she is involved in the IP Clinic which provides legal advice and cost effective solutions to innovators on all aspects of their IP Rights. In addition, she analyses developments in Kenyan and International IP Case law as well as the implications on the Intellectual Property Landscape.<br />
<br />
Douglas Gichuki [Open data and IT policy] (Research Fellow and Assistant Lecturer). Mr Gichuki holds an LLB degree from CUEA and an LLM in Intellectual Property, Information Technology and Internet Law from Norwich Law School (UK). His doctoral research focuses on legal frameworks for financing small to medium enterprises in technology.<br />
<br />
Pelase Visit:<br />
<br />
* [http://adrian-fh98.web.unair.ac.id/ Informasi Umum]<br />
* [http://www.tokobungasabana.com Toko Bunga]<br />
* [http://andreweweww.wordpress.com/ Curhat Blog]<br />
* [http://mariposa-store.com/ Jual Sepatu Online]<br />
<br />
Legal lead: National Council for Law Reporting<br />
<br />
Mr . Michael Murungi [Information technology specialist] is a manager, law reporter and ICT legal expert from Kenya. He is the Chief Executive/Editor of Kenya’s National Council for Law Reporting, the official publisher of Kenya’s public legal information, including the decisions of the superior courts of Kenya and the Laws of Kenya. He is the author of Cyber Law in Kenya and Kenya's designated contributor to Wolter Kluwer’s International Encyclopaedia of Cyberlaw. He has been a legal columnist for CIO, East Africa’s premier ICT magazine and a lecturer in cyberlaw at the Catholic University of Eastern Africa. He made key contributions towards the enactment of the Kenya Communications (Amendment) Act, 2009. He has undertaken local and international consultancy and speaking engagements. Michael holds a Masters Degree in ICT law and has professional training in legal practice, management and arbitration<br />
<br />
Mr. Alex Gakuru [Regional coordinator Africa] is the Founder and Chair of ICT Consumers Association of Kenya, an ICT consumer rights advocacy group. He is the Executive Director-Content Development and Intellectual property (CODE-IP) Trust, a non-profit organization focusing on creating an enabling environment for local content development and its intellectual property protection. He is an assertive advocate of consumer rights and he represents consumer interests through various platforms locally and internationally. He is an Elected Council Member at the Free and Open Source Software Foundation for Africa and he took part in global Internet Policy formulation as the elected Africa’s representative at ICANN’s Non-Commercial Users Constituency Executive Committee (NCUC). His NCUC term ended in December 2013. Since August 2012, he is the Regional Coordinator – Africa for Creative Commons.<br />
<br />
Sponsor :<br />
- [http://techpromocodes.com Technology Promo]<br />
<br />
Date of latest MOU in jurisdiction N/A<br />
<br />
<br />
Vision<br />
<br />
Why is Creative Commons important for the jurisdiction? <br />
<br />
Kenya is home to a thriving cultural industry. These varied creatives require access to shareable resources that facilitate remixing and creativity. It is, however, important to deepen the understanding of new users in Kenya of CC licenses and their usefulness. The increasing use of CC licenses in Kenya will help enhancing the visibility and accessibility of Kenyan creativity in the global networked space. <br />
<br />
Kenya is also home to a vibrant if querulous democracy. We are a multi ethnic society comprising 42 odd communities. We hope to harness the wealth that can come from such cultural and linguistic diversity through the creative commons movement. Kenyans are marked in their early adoption of technology to enhance the democratic discourse, examples of these include the shoot from the hip activism of #KOT (Kenyans On Twitter). We hope to use CC licensing in Kenya to support newly realisable democratic freedoms through new media conversation and mobilizing and by enabling wide-spread access to knowledge and information.<br />
<br />
<br />
What do you think makes a successful jurisdiction project?<br />
<br />
A successful jurisdiction project effectively promotes the use of CC licenses in their jurisdiction for the benefit of the various communities in the country. We wish to do this by bringing what is good of these communities to the wider African and global market; translating CC license deeds into local languages is in our opinion key for achieving this. <br />
<br />
<br />
How do you see the jurisdiction project contributing to the CC Affiliate Network? <br />
<br />
We want to help adding to the commons local content and a variety of indigenous and contemporary Kenyan works available under CC licenses.<br />
<br />
<br />
<br />
Community<br />
<br />
Describe the communities that are currently active in the project. <br />
<br />
1. Educational institutions – schools, universities, colleges, etc.<br />
2. Libraries <br />
3. Cultural institutions – museums, galleries, etc. <br />
4. Government organizations <br />
5. Technology-based companies<br />
6. Open data and technology-focused communities <br />
7. Professional Associations & non-profits <br />
8. Creators – artists, photographers, media producers. <br />
<br />
<br />
How will you continue to engage with these communities? <br />
<br />
We will increase our engagement through: Conference talks & workshops, a Kenyan CC website, Twitter, supporting interested parties with implementing CC licenses. <br />
<br />
<br />
Describe the communities (existing or new) that you plan to focus on during the timeframe covered by this roadmap? <br />
<br />
Target organizations: Bloggers Association of Kenya; KECOBO; The Creativez; Power 254, Media houses; technology hubs such as iHub; Universities; and civil society such as FOSSFA.<br />
<br />
<br />
How do you plan to engage with these communities? <br />
<br />
• Use of social media to establish a linked CC Kenya affiliate <br />
• Implementation of a Creative Commons website <br />
• Case studies and showcase examples <br />
• Compilation of list of Kenyan organizations & individuals using Creative Commons <br />
• Development of a copyright, open licensing course delivered online and face-to-face at the CIPIT<br />
• Open licensing salons, webinars, conference presentations, and events <br />
• FAQ, how-to’s and practical guides to aid decision making and implementation <br />
• Policy guidelines and recommendations <br />
• Development and profiling of business models related to use of Creative Commons, for instance the freemium model. <br />
• Making the case to government institutions for an open license for government content by using the National Council for Law Reporting as a demonstrative case study. <br />
<br />
<br />
<br />
<br />
Priority Goals<br />
<br />
What are the most important focus areas on which the Affiliate Team will work during this time period? <br />
<br />
Focus area: Outreach and deepening license knowledge and use<br />
<br />
• Given the newness of the CC team in Kenya, it is essential to build a strong community that understands the licenses, promotes sharing and remix culture. This would be a good starting point to better inform and deepen the use of the CC licenses and to spread their benefits. <br />
• We also wish to have a more diffused knowledge of the CC licenses in the jurisdiction. This includes encouraging the community to adopt the free licenses in distributing their work and expanding gradually to other areas.<br />
<br />
<br />
Focus area: Legal interface<br />
<br />
• As the Legal Lead, the NCLR will drive the CC Kenya team in interfacing with the legal and government communities. All CC work and information will be located on (or linked from) the NCLR website to be accessed freely by the public. Other legal issues will be addressed and dealt with as appropriate.<br />
<br />
<br />
Focus area: Application of CC to various topics of interest<br />
<br />
• At the CC Africa Regional Meeting in 2012, a number of topics were identified as of critical importance to engage with CC and the CC Kenya team. These included open education resources, government adoption, health, advocacy, ICT development, business models, and transparency.<br />
• The CC Kenya team will actively engage stakeholders such as the School of Open and the Open Data initiative within the Government of Kenya to see that the above topics are areas of focus.<br />
<br />
<br />
Focus area: Website development and update <br />
<br />
• This includes things like: a collection of case-studies or organisations using CC in Kenya (wiki); Acknowledge all CC KE volunteers and organizational supporters; Put more information about Creative Commons Licensing. This also involves the building of a mailing list through which we can keep the community informed and updated.<br />
• Why is it important? This will be a key source of information about Creative Commons Kenya. <br />
• Who benefits? All CC Kenya stakeholders<br />
<br />
<br />
Focus Area: Increased engagement with International and regional stakeholders<br />
<br />
• Frequent interaction with already established CC organizations will hasten the progress of this project. We are confident that tapping into the experience of existing CC communities will enrich the growth of the project through their support and contribution.<br />
<br />
<br />
Focus area: In-depth training of selected individuals<br />
<br />
• There exists a critical need in the region for individuals with in-depth training in areas of copyright, licensing, and business development around the CC philosophy of open access. This level of knowledge exceeds the basic understanding that is needed by most users of CC licenses. Typically, this level of specialized knowledge resides in lawyers or other IP specialists, but such knowledge is not common in East Africa. <br />
• We will address this need primarily through training of interns at CIPIT and/or NCLR. One or more interns will be engaged and tasked with learning the necessary background and practical knowledge to be able to advise CC users. It is hoped that the intern(s) will use the skills gained to further the CC cause even after their internship is completed. <br />
<br />
<br />
Focus Area: Identify source(s) and secure funding for a Creative Commons Kenya affiliate <br />
<br />
• While we will largely engage volunteers for a lot of the CC work, a basic minimum level of funding will be required to establish a physical presence and at least partial support for some people and activities. Localizing legal tools, promoting public awareness, translation of licenses to local languages, building out a web presence, all require funding and effort. Our focus must therefore include finding and securing core base level of funding.<br />
<br />
<br />
Project Outputs<br />
<br />
Detail tangible project outputs (e.g., events, papers, blog posts, video/films, etc.) for each focus area including an expected date of completion. <br />
<br />
Focus Area: Outreach and Increasing License Use<br />
<br />
• Project Output: Events / Blog posts / video & photo coverage of the events. Also FAQs and a practical manual (i.e., a toolkit) located on the CC Kenya website.<br />
• Expected start date - Expected date of completion: February to November 2013. <br />
• Team Member(s) Responsible: ALL, spearheaded by the Public Lead<br />
• How will this output help achieve your goals? Face to face meetings will help us improve the concept of a local community and will help us understand what are the community needs in our area. <br />
• Tentative schedule of events to be provided.<br />
<br />
<br />
Focus Area: Legal standardization<br />
<br />
• Project Output: translation of the license summaries; CC content available or linked on NCLR website, synchronized CC public sensitization events and create an interactive blog <br />
• Goal of Output: To secure government support & provide information to the public; to provide translated licenses<br />
• Expected start date: February 2013<br />
• Expected date of completion: continual<br />
• Team Member(s) Responsible: NCLR<br />
<br />
<br />
Focus area: Application of CC to various topics of interest<br />
<br />
• Project Output: Engagement of the CC initiative with stakeholders in various sectors including music, publishing, film, government, and academia. <br />
• Goal of Output: Increased awareness that CC principles apply beyond the legal field<br />
• Expected start date: March, 2013 <br />
• Expected date of completion: 2013 <br />
• Team Member(s) Responsible: Douglas Gichuki, Michael Murungi<br />
<br />
<br />
Focus area: Website <br />
<br />
• Project Output: Modern website with features such as a news feed, information about Creative Commons, and a spotlight on Creative Commons content & initiatives in Kenya. <br />
• Goal of Output: To connect with the public & provide information. <br />
• Expected start date: March, 2013 <br />
• Expected date of completion: 2013 <br />
• Team Member(s) Responsible: Douglas Gichuki<br />
<br />
<br />
Focus Area: International and regional engagement<br />
<br />
• Project Output: material support, active consultancy engagement with regional and international stakeholders (e.g., CC affiliates across Africa, CC HQ, etc.)<br />
• Goal of Output: to share experience and knowledge, cultivate interaction through international seminars and social media<br />
• Expected start date: in progress<br />
• Expected date of completion: continual<br />
• Team Member(s) Responsible: Dr. Isaac Rutenberg<br />
<br />
<br />
Focus Area: In-depth training<br />
<br />
• Project Output: One or more individuals with significant training in the areas of copyright law, licensing, business development based on the Freemium model, etc. <br />
• Goal of Output: To begin the process of creating a community of highly-trained individuals who are able to spread the use of CC licenses, advise users of the licenses, and continue training others in such areas.<br />
• Expected start date: March 2013<br />
• Expected date of completion: continual<br />
• Team Member(s) Responsible: Dr. Isaac Rutenberg<br />
<br />
<br />
Focus Area: Fundraising<br />
<br />
• Project Output: Kshs awarded/granted<br />
• Goal of Output: To secure sustainable funding. <br />
• Expected start date: February 2013 <br />
• Expected date of completion: ongoing, but the first round of applications to be completed in April 2013 <br />
• Team Member(s) Responsible: All. <br />
<br />
<br />
Metrics<br />
<br />
• How will you evaluate your impact on focus-area 1 (Outreach)? Number of participants at the events & stakeholder groups represented. Numbers of documented cases using CC licenses.<br />
• How will you evaluate your impact on focus-area 2 (Legal Standardization)?<br />
The availability, download rate, and number of known links to CC licenses will be the primary factor in evaluating this area. Other measures include interactions with the creative community and inquiries by would-be users.<br />
• How will you evaluate your impact on focus-area 3 (Application to various topics)? <br />
Frequency of engagement with the sectors identified in this Roadmap; case studies of such engagement.<br />
• How will you evaluate your impact on focus-area 4 (Website)? <br />
Website traffic (eventually, as the site garnishes attention). Also, average number of new posts per month and average number of updates per month. <br />
• How will you evaluate your impact on focus-area 5 (International and regional interaction)? <br />
The number of International meetings/seminars/interactions engaged per annum and internal audits done per annum to measure conformity progress with CC international standards.<br />
• How will you evaluate your impact on focus-area 6 (In-depth training)? <br />
The skill level and competency of the intern(s) trained by CIPIT and/or NCLR will be evaluated to determine impact.<br />
• How will you evaluate your impact on focus-area 7 (Fundraising)? <br />
We will measure this area by our ability to meet our financial needs via funds raised. <br />
<br />
<br />
<br />
Resources Required<br />
<br />
What human resources or expertise must the team seek out or add to your existing resources, if any, in order to achieve your priority goals? <br />
<br />
• Creative Commons Kenya has commenced operations with the team members described in the "Affiliate Team Information" section. These team members already cover a wide spectrum of expertise. We will seek to add to this expertise if and when the need arises. We will also work on building a broad network of volunteers and supporters. <br />
• We will seek out and engage one or more interns to learn the in-depth knowledge and training identified in the above goals.<br />
<br />
<br />
How will you involve these people? <br />
<br />
• Some involvement is already present. We will have bi-monthly meetings and supporters will be acknowledged on the website. <br />
• We will call for volunteers and interns through announcements on the website, social media, and in universities. <br />
<br />
<br />
What technology resources must the team seek out or add to your existing resources, if any, in order to achieve your priority goals? <br />
<br />
• Website development will require an experienced website developer and possibly an individual with artistic design experience.<br />
<br />
<br />
How will you obtain these technology resources? <br />
<br />
• We will advertise a call for volunteers and may seek assistance from the IT department at Strathmore and/or other universities.<br />
<br />
<br />
What material resources must the team seek out or add to your existing resources, if any, in order to achieve your priority goals?<br />
<br />
• Generally, there is a lack of practical and instructional information available to would-be users of the CC licenses in Kenya. The CC Kenya website will be a perfect forum for disseminating such information, which we plan to generate as a collaborative effort between the Public and Legal Lead organizations. For example, CIPIT has been developing a practical manual of IP identification, acquisition, and use. This model can be adapted and a similar manual will be created for the CC Kenya website. Furthermore, we will generate a FAQ section that will help CC Kenya reach those in most need of basic assistance. <br />
• From a variety of recent events such as the launch of the School of Open, it has become clear that there are numerous individuals in Kenya with an interest in driving the success of an open content platform. There is not, however, a centralized list of such individuals. We will create such a resource and make it available on the CC Kenya website.<br />
• We were very happy to have received SWAG from CC international for our inaugural CC 10 birthday event in Nairobi. These were very popular. We will be requesting more support of this kind from CC International.<br />
<br />
<br />
How will you obtain these material resources? <br />
<br />
• The manuals and FAQ content will be generated in-house at the Public and Legal Lead institutions. <br />
• Advertising and promotional materials will be requested via mail from CC.<br />
<br />
<br />
How will you ensure your goals will be completed if unforeseen circumstances interrupt the project, such as changes in the leadership of the project or outputs taking longer to complete than anticipated? <br />
<br />
• Regular meetings and open discussions among team members.<br />
<br />
<br />
How will you communicate the project's on-going progress and setbacks within the jurisdiction and the CC Affiliate Network?<br />
<br />
• Emails, ccAfrica mailinglist, our website, social media platforms, meetings<br />
• Updates to the African Regional Coordinators <br />
<br />
<br />
How will you document the project so that others may replicate or learn from your efforts? <br />
<br />
• Creative Commons wiki and our website (and through all of the above communication tools for that matter)<br />
• Comments on the roadmap <br />
<br />
<br />
<br />
Collaboration<br />
<br />
How could the jurisdiction's plans help drive or support other jurisdictions' activities? <br />
<br />
• CC Kenya follows on an illustrious list of African jurisdictions using CC. We have the good examples from South Africa, Nigeria, Egypt, Uganda and others to learn from. We intend to actively court these CC jurisdictions for mentoring to assist us especially with the use of the 4.0 license.<br />
• We intend however to document our experience of setting up a CC affiliate team and disseminate it freely for other jurisdictions considering setting up such teams. We also intend to collaborate and offer support for sister CC jurisdictions by participation in, e.g., face to face meetings and workshops. <br />
<br />
<br />
What are other jurisdictions doing that might support or contribute to the project? <br />
<br />
• We are enamored by the jurisdictions that have been able to build CC communities amongst very culturally diverse communities. CC Brazil and CC South Africa are good examples we want to learn from.<br />
<br />
<br />
Would you be interested in mentoring new jurisdiction teams? Yes. <br />
<br />
Conversely, would you be interested in having a mentor from a more experienced jurisdiction team? Yes. <br />
<br />
<br />
Suggest three possible projects on which you can collaborate with other teams on a regional level. <br />
<br />
The Kenya CC team hopes to contribute to collaboration in Africa by:<br />
1. Networking with team members from other jurisdictions for example by inviting them to events in Kenya to share their experiences or sharing success stories broadly about the application of CC licenses.<br />
2. In addition, the Kenya CC legal team is to work closely with colleagues from South Africa, Egypt and Nigeria, and Uganda who have in-depth knowledge of CC licenses through their experiences in license porting, and in the use of the current 3.0 license.<br />
3. We would like to collaborate for the deliberations on the 4.0 license. <br />
<br />
<br />
How do you plan to contribute to these projects? Sharing of information and on an ad-hoc basis. <br />
<br />
<br />
<br />
Translation<br />
<br />
In what language(s) will you promote CC in the jurisdiction and why? At this point in time, it is only feasible to promote CC licenses in English. Yet, we aim at translating the Commons Deed into Swahili. We also intend to have the deed translated to various local languages. <br />
<br />
In which of these languages are licenses already available? English; the unported license.</div>Couponcodehttps://wiki.creativecommons.org/index.php?title=Internet_Services&diff=80765Internet Services2013-08-16T16:18:26Z<p>Couponcode: /* Creative Commons Internet Services Policy */</p>
<hr />
<div>[[MOU and Policies Summary| Return to Summary page]]<br />
<br />
To share your feedback on the Internet Services Policy, please go to the [http://wiki.creativecommons.org/index.php?title=Talk:Internet_Services&action=edit&redlink=1| Internet Services Policy discussion page] and type your comments there.<br />
<br />
[[Media:isp.pdf | PDF Version]]<br />
<br />
--Please do not edit any text below this line.--<br />
----<br />
<br />
== Creative Commons Internet Services Policy ==<br />
'''Plain English Summary'''<br />
The overarching purpose of this Internet Service Policy is to ensure that information provided via the Internet about Creative Commons by our Affiliates is consistent and in the best interests of all those dedicated to CC around the world.<br />
* This Internet Services Policy outlines the requirements to which Creative Commons and CC Affiliates must adhere when operating a website, email account, Facebook page, Twitter account or other internet service for a Creative Commons jurisdiction project.<br />
* Affiliates are ultimately responsible for all content on any internet service.<br />
* Any use of internet services must comply with CC’s policies and memorandums of understanding.<br />
* Licenses, license choosers, translated documents and legal tools should never be hosted anywhere other than the main Creative Commons website at http:creativecommons.org.<br />
<br />
- - - - -<br />
<br />
The Internet Services Policy (“Policy”) complements the Trademark Policy, Merchandising Policy and other policies available at http://creativecommons.org/policies, (collectively “CC Policies”) and the agreements signed by Creative Commons Corporation (“CC” or “Creative Commons”) and its Affiliate(s) (“Affiliate”), which may include a Memorandum of Understanding, Legal Lead Affiliate Agreement, Project Lead Affiliate Agreement or previous incarnations of such agreements (for purposes of this Policy, collectively “MOUs” and each an “MOU”).<br />
<br />
'''PURPOSE'''<br />
<br />
Creative Commons appreciates the time, energy and hard work that all Affiliates contribute to CC projects around the globe. In order to maximize the impact of those efforts, CC and Affiliates need to work together to ensure a uniform Creative Commons message and protect our most valuable assets, which include our collective goodwill and reputation. We all strive to reach the public and connect with our communities in many ways. The purpose of this Policy is to ensure that information provided via the internet to the public about Creative Commons by Creative Commons Headquarters our Affiliates is accurate and in the best interests of all those dedicated to CC around the world.<br />
<br />
This Policy governs the creation, and use of, domain names, email addresses, websites and other internet-based contact points, including but not limited to Twitter accounts and Facebook pages, (collectively, “Internet Services”) used in connection with the Project (as described in the MOU). This includes but is not limited to Internet Services displaying or incorporating any of the Creative Commons Marks (as defined in the Creative Commons Trademark Policy [link]). Websites (as that term is used in this Policy) include both websites for the Project within Affiliate’s jurisdiction (“Project Website”) and websites for more than one jurisdiction, such as websites for a specific geographical or geopolitical region (“Regional Websites”).<br />
<br />
'''TERMS OF POLICY'''<br />
<br />
Creative Commons will consider deviations from this Policy on a case by case basis through conversations with Affiliate. As confirmed by the signing of the MOU, Creative Commons and Affiliate agree:<br />
<br />
;I. <u>Domain Names.</u> If Affiliate chooses to operate a Project Website or Regional Website, the Website must operate at a domain name chosen in accordance with the following:<br />
<br />
:(a) <u>CC Sub-Domains.</u> CC will make available to each jurisdiction, at Affiliate’s request, a sub-domain of the Creative Commons main website at http://creativecommons.org (“CC HQ Website”) for Affiliate to use in conjunction with the Project. The sub-domain will consist of xx.creativecommons.org, where xx is the ccTLD top level domain extension for the Project’s jurisdiction.<br />
<br />
:(b) <u>Subdomain Administration.</u> If Affiliate requests that CC establish a sub-domain, CC will grant Affiliate administrator access privileges to the sub-domain for so long as Affiliate is in compliance with this Policy and officially connected with the Project through an MOU.<br />
<br />
:(c) <u>Acquiring a Domain Name.</u> Affiliate acknowledges that CC’s general policy is not to pay to acquire domain names that incorporate the Marks for example a domain name creativecommons.org.xx or creativecommons.xx. Where CC has not acquired a domain name that incorporates the Marks in the Project’s jurisdiction, Affiliate may choose to acquire such a domain name at its own cost, provided that:<br />
<br />
::(i) Affiliate notifies CC in advance (if possible) that it intends to acquire the domain name, and whether the domain name will be acquired according to the procedure described in clause I (e) or I (f); and,<br />
<br />
::(ii) Within a reasonable time of acquisition of the domain name, Affiliate emails domains@creativecommons.org with the details of the domain name and the registration data.<br />
<br />
:(d) <u>Registering in CC’s Name.</u> If Affiliate chooses to acquire a domain name that incorporates the Marks and the registration authority’s rules permit the domain name to be registered in CC’s name, Affiliate must register it in CC’s name. Up-to-date registration information can be obtained by emailing domains@creativecommons.org.<br />
<br />
:(e) <u>Registering in Affiliate’s Name.</u> If Affiliate chooses to acquire a domain name that incorporates any of the Marks and the registration authority’s rules do not permit the domain name to be registered in CC’s name, then Affiliate may register the domain name in its own name provided that:<br />
<br />
::(i) Affiliate agrees that it holds the domain name for and on behalf of CC in accordance with the Trademark Policy;<br />
<br />
::(ii) Affiliate ensures that the administrative contact on the account will at all times be domains@creativecommons.org.;<br />
<br />
::(iii) If the rules governing the registration of domain names in the Project’s jurisdiction change such that CC can hold the domain name in CC’s own name, Affiliate will notify Creative Commons within a reasonable time of becoming aware of this change and CC and Affiliate will decide together whether and when the domain name should be transferred to Creative Commons;<br />
<br />
::(iv) If CC and Affiliate agree to transfer the domain name to Creative Commons, Affiliate will do all things reasonably requested by CC to effect the transfer to CC, at CC’s expense; and<br />
<br />
::(v) Affiliate will only transfer the domain name to a third party with the prior written consent of CC.<br />
<br />
:(f) <u>Competing Domain Names.</u> Affiliate should notify Creative Commons as soon as is reasonably practicable if Affiliate becomes aware of any domain name registrations in the Project jurisdiction that use any Marks or are similar to any Marks.<br />
<br />
:(g) <u>Unforeseen Circumstances.</u> Affiliate and CC acknowledge that this policy cannot cover every situation and new circumstances may arise. Affiliate undertakes to do all things CC reasonably requests.<br />
<br />
;II. <u>Website(s) and Public Portal(s).</u> If Affiliate chooses to operate a Project Website, Regional Website or other Internet Service that provides information about Creative Commons, such as a Facebook page or Twitter account (each a “Public Portal” for purposes of this Policy) in their Affiliate capacity for the purpose of undertaking activities in connection with the Project, then the following apply:<br />
<br />
:(a) <u>Purpose of Project Website.</u> The Project Website (if any) is to serve as the principal public information portal about the Project, which should include educational, research and promotional programs that encourage and enable the sharing of work within the Project jurisdiction through the use of the six Creative Commons licenses: Attribution (BY), NoDerivs (BY-ND), NonCommercial (BY-NC), ShareAlike (BY-SA), NonCommercial NoDervis (BY-NC-ND), and NonCommercial ShareAlike (BY-NC-SA), (collectively “Licenses”); and other legal instruments, such as the CC0 waiver, patent licenses, patent non-assert tools, and other previous and forthcoming licenses and tools published by CC (collectively “Legal Tools”).<br />
<br />
:(b) <u>Purpose of Regional Website.</u> Regional Websites are to serve as a collaboration point between jurisdictions in the region, and provide information about Creative Commons activities in the region as a whole.<br />
<br />
:(c) <u>Purpose of Public Portal(s).</u> Each Public Portal (if any) is to serve as a secondary or supplemental portal to the Project Website or Regional Website for undertaking activities in connection with the Project or Region and/or providing information about Creative Commons. If there is no existing Project Website or Regional Website, the Public Portal will serve as the principal public information portal and will provide information as stated above in II (a).<br />
<br />
:(d) <u>Relationship of Public Portals with Website.</u> All Public Portals must provide a link to the main Project Website or Regional Website when it exists, and to the CC HQ Website if no Project Website or Regional Website exists.<br />
<br />
:(e) <u>Quality.</u> Affiliate will ensure the Website is of a high quality and value consistent with the CC HQ Website and other Creative Commons project websites, but should not be so confusingly similar that it misleads Website visitors into thinking that the Website is the CC HQ Website. CC agrees to provide reasonable assistance to ensure such quality. To this end, CC can facilitate hosting services for the Website with a third-party hosting platform.<br />
<br />
:(f) <u>Branding.</u> The Project Website will be branded as “Creative Commons [Jurisdiction]”. Regional Websites will be branded as “Creative Commons [Region]”. The Website will clearly state that it is a collaboration between Creative Commons and Affiliate(s) and will include a list of all Affiliates with links to Affiliates’ websites. Affiliate may decide where on the Website to place this information.<br />
<br />
:(g) <u>Disclaimers.</u> The Website will include at a minimum two disclaimers within the footer. Public Portals will also include the disclaimers, provided that if such disclaimers do not fit within the space constraints of the portal’s service then Affiliate will provide a reasonably accurate condensation of such disclaimers if possible. The disclaimers should be as follows:<br />
<br />
::(i) The following agency disclaimer, in the primary language of the Website: “[Affiliate] and Creative Commons Corporation are independent and separate entities. Neither is a partner, agent or employee of the other. Neither party shall have the authority to make any statements, representations or commitments of any kind, or to take any action which shall be binding on the other party, except as may be authorized in writing.”; and <br />
<br />
::(ii) A legal disclaimer in the primary language of the Website that clearly states that the Website does not provide legal advice and that using the website does not form any type of legal relationship between Affiliate and users. Public Portals will also include the disclaimers, provided that if such disclaimers do not fit within the space constraints of the portal’s service then Affiliate will provide a reasonably accurate condensation of such disclaimers if possible.<br />
<br />
:(h) <u>Policies.</u> The Website will include a statement to the effect that “Except where otherwise noted [link to policies page], this site is licensed under a Creative Commons Attribution license.” In keeping with the legal disclaimer and policies page, Affiliate will ensure that nothing provided on the Website constitutes legal advice. Each Website will provide certain policies, as outlined in (i) or (ii) below, as applicable. The Website may not require users to adhere to any new or additional policies without CC’s written consent. Applicable policies are as follows:<br />
<br />
::(i) For Websites hosted on CC servers or for which the domain is registered in CC’s name, the CC Policies will apply, and the Websites will include a link on each page to the Creative Commons policies page at http://creativecommons.org/policies and CC Terms of Use available at http://creativecommons.org/terms; and<br />
<br />
::(ii) For Websites not hosted on CC servers and for which the domain is registered to someone other than CC, Affiliate will establish and maintain an appropriate privacy policy, terms of use and other policies that comply with applicable law and do not contradict anything in this Policy.<br />
<br />
:(i) <u>Content.</u> Affiliate will ensure the Project Website and Public Portals contain proper content in the appropriate language(s) as chosen by Affiliate and/or English, and in line with the MOU and all applicable CC Policies. Proper content may include, but is not limited to, information about (i) Affiliate(s); (ii) the relevant jurisdiction, in a manner that promotes and encourages the adoption of Creative Commons Licenses and Legal Tools; (iii) a link to or translation of the content explaining Creative Commons’ philosophy, history and mission, available at http://creativecommons.org/about/history/; (iv) the local and international adoption of Creative Commons licenses, and (v) Creative Commons-related events.<br />
<br />
:(j) <u>Content Restrictions.</u> Websites and Public Portals will only contain content that promotes the objectives of the collaboration between Affiliate and Creative Commons as described in the MOU. For the avoidance of doubt, this means Websites and Public Portals will not contain, link to or endorse any content that is defamatory, hateful or otherwise discriminatory, offensive or obscene, infringing, illegal or otherwise contrary to the law of the applicable jurisdiction. [http://mcafeepromocodes.com McAfee Promo Code]<br />
<br />
<br />
:(k) <u>Third-Party Contributions.</u> Where Websites or a Public Portal allow third parties to contribute material, Affiliate will adopt a system of review that enables it to monitor this material for compliance with this Policy, the other CC Policies and the MOU, and will promptly remove material that does not comply.<br />
<br />
:(l) <u>Removal of Content.</u> CC reserves the right to request the removal of any content that fails (in CC’s sole discretion) to conform to the requirements of this Policy, the MOU, or any other applicable CC Policies. Affiliate will respond promptly to such a request.<br />
<br />
:(m) <u>Infringing Material.</u> If Affiliate receives a notice or becomes aware of any claim or information that a Website or a Public Portal contains content that violates the intellectual property rights of any person, and:<br />
<br />
::(i) The content is on a Website that is hosted on a Creative Commons server or registered to Creative Commons, Affiliate agrees to send any such notice or claim immediately to dmca@creativecommons.org, with relevant information.<br />
<br />
::(ii) The content is on a Website that is not hosted on a Creative Commons server and is registered to someone other than Creative Commons, Affiliate agrees to comply with all applicable laws governing its obligations and responsibilities with respect to such material.<br />
<br />
::(iii) The content is on a Public Portal, Affiliate agrees to use reasonable efforts to remove the content. [http://hostgator1centcoupon.net Hostgator 1 cent]<br />
<br />
:(n) <u>Website License.</u> Affiliate will ensure that to the greatest extent possible, all content on a Website or Public Portals is licensed under a Creative Commons Attribution license. Affiliate alone is responsible for ensuring that it has obtained all rights necessary to the content included on a Website and will use best efforts to enable it to be licensed under the CC Attribution license. All third-party content that appears on a Website that is not licensed under the CC BY license must be clearly marked with its copyright status and/or applicable license.<br />
<br />
:(o) <u>Content Syndication.</u> Any content that appears on a Website or Public Portal may be syndicated on the websites of other CC project jurisdictions, Regional Websites and the CC HQ Website, unless expressly indicated otherwise by Affiliate in writing to CC or another Affiliate, as the case may be. Similarly, any and content on the CC HQ Website may be used on the Project Website or Regional Website, unless CC expressly indicates to the contrary.<br />
<br />
:(p) <u>Items that cannot be hosted.</u> The following items will be hosted on the CC HQ Website only: License drafts, final Licenses, legal code, license deeds, License HTML, license buttons, Legal Tools (whether in human-readable, lawyer-readable or machine-readable formats, or any other formats whatsoever) and the license chooser engine. For the avoidance of doubt, this means that these items may not be hosted on a Project Website or Regional Website, but the Project Website or Regional Website may link to the items on the CC HQ Website.<br />
<br />
:(q) <u>Document Translation.</u> If Affiliate or the Affiliate Team wish to translate documents from CC’s wiki (http://wiki.creativecommons.org), those documents must remain posted (as translated) on the wiki. Websites and Public Portals may link to the documents.<br />
<br />
:(r) <u>FAQs.</u> The Project Website will include a link to CC’s “Frequently Asked Questions” page available at http://wiki.creativecommons.org/Frequently_Asked_Questions. The Project Website may also include a “Frequently Asked Questions” page with human readable information about CC topics, licensing and related legal issues customized to the Project’s jurisdiction [http://kcouponcode.com Kaspersky Coupon Code] and in the jurisdiction’s primary language(s). Regional Websites may include a link to the “Frequently Asked Questions” page.<br />
<br />
:(s) <u>Developers.</u> Websites may contain a link to CC’s developers pages available at http://wiki.creativecommons.org/Developers.<br />
<br />
:(t) <u>Commercial Activity.</u> Websites will not contain third party advertisements, banner ads or promotions by Affiliate for any products or services other than those permitted under the Merchandising Policy or anticipated by the scope of the Project as described by the MOU. Creative Commons Counsel and Affiliate can discuss other fund-raising or commercial activity to be conducted on Websites or through Project Portals.<br />
<br />
:(u) <u>Third-Party Hosting.</u> To the extent that CC facilitates hosting services for a Website and a third party hosting platform, CC is not in any way responsible for the provision of the hosting services and Affiliate will contract separately with the third party hosting platform for the provision of these services.<br />
<br />
;III. <u>Email Addresses and Lists.</u> If Affiliate wishes to create email addresses or email lists for the Project, each email address or list must be operated in accordance with the following:<br />
<br />
:(a) <u>Email Addresses.</u> Email addresses may correspond to the domain name for the Project, provided that:<br />
<br />
::(i) The email addresses are used only to send communications in accordance with the MOU and CC Polices;<br />
<br />
::(ii) All emails sent from the email addresses include a footer that makes clear to the recipient that the sender does not work for Creative Commons (e.g. [sender’s name], CC [jurisdiction] [Title]) and that clearly states that CC, Affiliate and the contents of the email do not provide legal advice; and,<br />
<br />
::(iii) Affiliate agrees to provide email addresses only to persons who are working with Affiliate on the Project in accordance with the MOU, and to terminate a person’s email account when that person is no longer working with Affiliate on the Project.<br />
<br />
:(b) <u>Set-Up of Lists.</u> If Affiliate would like have a mailing list for the jurisdiction, it must be done on Ibiblio (unless otherwise approved by CC) and Affiliate must send the administrators names, administrative password and any updates or changes to administrators or administrative passwords to CC when the list is set-up. To create a new mailing list, send an email to help@ibiblio.org with desired list name and the name of a chosen administrator.<br />
<br />
:(c) <u>List Membership.</u> Affiliate will not arbitrarily exclude anyone from membership in the list, and Affiliate will use its discretion when deciding to terminate a person’s membership and then only for appropriate reasons, such as disruptiveness or inappropriate comments.<br />
<br />
:(d) <u>Moderating Lists.</u> Affiliate will moderate any email lists for the Project fairly and will moderate discussions when necessary to ensure that all list members are allowed to participate fully.<br />
<br />
;IV. <u>All Internet Services.</u> The following provisions are applicable to all Internet Services maintained or operated by Affiliate in relation to the Project:<br />
<br />
:(a) <u>Number of Internet Services.</u> There may only be one central Project Website for each Jurisdiction and one Regional Website for a given region. For the avoidance of doubt, this does not preclude the use of supporting sites such as wikis. Public Portals should be limited in number to a reasonable amount. Additional Project Websites or Regional Websites will only be allowed if authorized in writing by Creative Commons.<br />
<br />
:(b) <u>Costs.</u> Affiliate will be responsible for all costs and expenses associated with administering all Internet Services.<br />
<br />
:(c) <u>Delegation.</u> Affiliate may grant administrative access for the Internet Services to a reasonable number of people for the purpose of maintaining the Internet Services in accordance with this Policy and the MOU. Affiliate will use its best judgment in deciding who will be allowed administrative access to the Internet Services. Affiliate will at all times remain ultimately responsible for ensuring that all Internet Services comply with this Policy, the MOU, and other CC Policies. Affiliate will terminate access granted to others if instructed to do so by Creative Commons. For the avoidance of doubt, CC will only instruct Affiliate to terminate another’s administrative access privileges if CC decides, in its sole discretion, that the access privilege is not being used in accordance with this Policy and the MOU.<br />
<br />
:(d) <u>Conduct.</u> Affiliate, the Affiliate Team (as defined in the MOU) and others authorized as administrators of a Project Website or Regional Website in accordance with this Policy will work together with the relevant jurisdiction community, the CC Affiliate Network (as defined in the MOU), and Creative Commons, adhering to a high standard of civility, fairness, ethics and general conduct with each other. Affiliate and the Affiliate Team will engage in consensus-based decision-making on matters relating to administration of the Internet Services, using reasonable efforts to maintain, improve and operate the Internet Services for the purposes contemplated in furtherance of CC’s mission. Everyone with administrative access to an Internet Service registered to Creative Commons or hosted on CC’s servers agrees to comply with the Creative Commons Terms of Use available at http://creativecommons.org/terms.<br />
<br />
:(e) <u>Transfer of Internet Services.</u> If Affiliate discontinues its official relationship with Creative Commons, habitually fails to adhere to this Policy, or if CC reasonably determines that a transfer is in the best interests of the maintenance and control of the domain name and the Marks, Affiliate agrees that CC may direct Affiliate to transfer to Creative Commons or a third party (and Affiliate will cooperate with CC in doing so):<br />
<br />
::(i) Any domain name registered to someone other than CC;<br />
<br />
::(ii) The entire Website, intact (to the extent not otherwise prohibited by third-party license terms); and<br />
<br />
::(iii) Administrative access to any Public Portal, including changing all login ids and passwords as directed by Creative Commons.<br />
<br />
[http://wiki.creativecommons.org/Creative_commons_non_profit_organization About Creative Commons]</div>Couponcodehttps://wiki.creativecommons.org/index.php?title=Hacking_DiscoverEd&diff=80764Hacking DiscoverEd2013-08-16T16:16:15Z<p>Couponcode: /* I get a big long Java backtrace talking about Jena and MySQL */</p>
<hr />
<div>How to deploy a hackable DiscoverEd, make changes, and update your deployment<br />
{{Infobox|These instructions assume a Unix-like environment; please help us by contributing information on Windows-based development.}}<br />
{{stub}}<br />
<br />
[[Category:DiscoverEd]]<br />
<br />
= Check out and build the source code =<br />
<br />
<pre><br />
git clone git://gitorious.org/discovered/repo.git discovered<br />
cd discovered<br />
git checkout (whatever branch we're working on today)<br />
ant<br />
</pre><br />
<br />
= Add a curator and a feed =<br />
<br />
By default DiscoverEd uses Derby and will create the on-disk database if needed. See [[DiscoverEd/Installation Instructions|the installation instructions]] for information on using other databases, such as MySQL.<br />
<br />
DiscoverEd uses feeds to help identify resources to crawl. Feeds are provided by curators, who can also provide metadata about resources.<br />
<br />
<pre><br />
$ ./bin/feeds addcurator "ND OCW" http://ocw.nd.edu/ <br />
$ ./bin/feeds addfeed rss http://ocw.nd.edu/english/@@rss http://ocw.nd.edu/<br />
</pre><br />
<br />
See [[DiscoverEd Feeds]] for information on supported feed types.<br />
<br />
More information on <code>./bin/feeds</code> commands at [[Running DiscoverEd]] (some information will be discovered.cc specific)<br />
<br />
= Aggregate and crawl resources =<br />
<br />
<pre><br />
$ ./bin/feeds aggregate<br />
$ ./bin/feeds seed > seed/urls.txt<br />
$ ant -f dedbuild.xml crawl<br />
</pre><br />
<br />
= Run the web application =<br />
<br />
You can run the web front-end using [http://en.wikipedia.org/wiki/Jetty_%28web_server%29 Jetty] (included with your checkout) by running:<br />
<br />
<pre><br />
$ ant -f dedbuild.xml serve<br />
</pre><br />
<br />
= Hacking The Code =<br />
<br />
* Run Eclipse<br />
* Do File -> Import...<br />
** When it asks you to "Existing projects into workspace," choose "General -> File System"<br />
** Select the location of your source tree<br />
** Click Finish<br />
<br />
(There are three options. 1. "Existing projects into workspace". 2. "Create from existing source" 3. "File 1. "Existing projects into workspace". 2. "Create from existing source" 3. "File System". Some of these trigger an error regarding Nutch MP3 code.)<br />
<br />
The DiscoverEd source code lives in two locations:<br />
<br />
* ded/src/java contains DiscoverEd specific code, primarily related to interfacing with the RDF store.<br />
* src/plugins/cclearn contains the DiscoverEd Nutch plugin, which provides some filtering features to Nutch and ensures metadata indexed in the RDF store is injected into the Lucene index<br />
<br />
Generally, the plugin may depend upon code in the ded/src/java tree, but classes in the plugin may not be available to that code.<br />
<br />
'''Note:''' The DiscoverEd developers will consider you extra special if you indent your code using spaces instead of tabs. You may even earn a gold star.<br />
<br />
To use spaces for all indentation for all Java projects in Eclipse 3.5 (Galileo):<br />
# Open Preferences<br />
# Expand the Java group<br />
# Expand the Code Style subgroup within the Java group<br />
# Select Formatter<br />
# Click on "New" in the Formatter section and name your profile<br />
# Check that the "Indentation" tab is active<br />
# Select "Spaces only" from the "Tab policy" dropdown<br />
# Click "Apply" and or "OK"<br />
<br />
You may also do this on a per-project basis by setting it as a project property. The general process is the same.<br />
<br />
= Commiting Changes and Merging to the Main Repository =<br />
<br />
<br />
<br />
= Troubleshooting =<br />
<br />
==== I get a big long Java backtrace talking about Jena and MySQL ====<br />
<br />
If you've configured DiscoverEd to use MySQL as the database backend, you'll need to create the database first, [http://kcouponcode.com read more here]<br />
<br />
==== Database permissions ====<br />
<br />
You might need to change the MySQL credentials or database configuration value in <code>conf/discovered.xml</code>. DiscoverEd does not require that you use the root user; it does require that the database already exist.<br />
<br />
==== JAVA_HOME on a Mac ====<br />
<br />
Mac users setting JAVA_HOME should use<br />
/usr/libexec/java_home to determine the current JAVA_HOME<br />
<br />
if you're really lazy add<br />
JAVA_HOME=`/usr/libexec/java_home` <br />
to .bash_profile and it will set JAVA_HOME each time you invoke a shell. (This is a good idea!)<br />
<br />
Get [http://hostgator1centcoupon.net Hostgator 1 cent] here and save lot on Hostgator<br />
<br />
==== Error message: "Feature 'http://apache.org/xml/features/xinclude' is not recognized." ====<br />
<br />
"You probably have an older version of Xerces somewhere in your classpath or something is overriding the default parser configuration with one that doesn't support XInclude." (http://marc.info/?l=xerces-j-user&m=117066278506146&w=2)<br />
<br />
==== AccessControlException ====<br />
<br />
When starting Tomcat, if you get a traceback like this in your tomcat log (e.g., in /var/lib/tomcat6/logs/localhost-$date.log):<br />
<br />
SEVERE: Exception sending context initialized event to listener instance of class org.apache.nutch.searcher.NutchBean$NutchBeanConstructor<br />
java.lang.RuntimeException: java.security.AccessControlException: access denied (java.lang.reflect.ReflectPermission suppressAccessChecks)<br />
at org.apache.hadoop.util.ReflectionUtils.newInstance(ReflectionUtils.java:115)<br />
at org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:1377)<br />
at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:66)<br />
at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:1390)<br />
at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:196)<br />
at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:95)<br />
<br />
and so on, try changing the Tomcat policy in /etc/tomcat6/policy.d/04webapps.policy. Add these lines in the grant {} block:<br />
<br />
// Attempt to get Nutch working<br />
// Courtesy of Alex McLintock at http://mail-archives.apache.org/mod_mbox/lucene-nutch-user/200907.mbox/<d398ec7f0907041237j6acffe0fm10b7cd374a77795b@mail.gmail.com><br />
permission java.security.AllPermission;<br />
<br />
This is obviously inappropriate for any site running a public instance of DiscoverEd. But it might be useful for your local dev environment. If you know how to specify a class level permission, please update this document.<br />
<br />
==== Missing build/plugins ====<br />
<br />
Be sure to run ant in the root repo directory.<br />
<br />
==== Missing parse-mp3 plugin ====<br />
<br />
Remove that source folder from the build path (in Eclimse, Project > Properties > Java Build Path > Source.<br />
<br />
==== Eclipse complains: Wrong version number in .class file ====<br />
<br />
Use Java 1.6 as your compiler. Be sure to use the right JVM for this project.</div>Couponcodehttps://wiki.creativecommons.org/index.php?title=Hacking_DiscoverEd&diff=80763Hacking DiscoverEd2013-08-16T16:14:44Z<p>Couponcode: /* JAVA_HOME on a Mac */</p>
<hr />
<div>How to deploy a hackable DiscoverEd, make changes, and update your deployment<br />
{{Infobox|These instructions assume a Unix-like environment; please help us by contributing information on Windows-based development.}}<br />
{{stub}}<br />
<br />
[[Category:DiscoverEd]]<br />
<br />
= Check out and build the source code =<br />
<br />
<pre><br />
git clone git://gitorious.org/discovered/repo.git discovered<br />
cd discovered<br />
git checkout (whatever branch we're working on today)<br />
ant<br />
</pre><br />
<br />
= Add a curator and a feed =<br />
<br />
By default DiscoverEd uses Derby and will create the on-disk database if needed. See [[DiscoverEd/Installation Instructions|the installation instructions]] for information on using other databases, such as MySQL.<br />
<br />
DiscoverEd uses feeds to help identify resources to crawl. Feeds are provided by curators, who can also provide metadata about resources.<br />
<br />
<pre><br />
$ ./bin/feeds addcurator "ND OCW" http://ocw.nd.edu/ <br />
$ ./bin/feeds addfeed rss http://ocw.nd.edu/english/@@rss http://ocw.nd.edu/<br />
</pre><br />
<br />
See [[DiscoverEd Feeds]] for information on supported feed types.<br />
<br />
More information on <code>./bin/feeds</code> commands at [[Running DiscoverEd]] (some information will be discovered.cc specific)<br />
<br />
= Aggregate and crawl resources =<br />
<br />
<pre><br />
$ ./bin/feeds aggregate<br />
$ ./bin/feeds seed > seed/urls.txt<br />
$ ant -f dedbuild.xml crawl<br />
</pre><br />
<br />
= Run the web application =<br />
<br />
You can run the web front-end using [http://en.wikipedia.org/wiki/Jetty_%28web_server%29 Jetty] (included with your checkout) by running:<br />
<br />
<pre><br />
$ ant -f dedbuild.xml serve<br />
</pre><br />
<br />
= Hacking The Code =<br />
<br />
* Run Eclipse<br />
* Do File -> Import...<br />
** When it asks you to "Existing projects into workspace," choose "General -> File System"<br />
** Select the location of your source tree<br />
** Click Finish<br />
<br />
(There are three options. 1. "Existing projects into workspace". 2. "Create from existing source" 3. "File 1. "Existing projects into workspace". 2. "Create from existing source" 3. "File System". Some of these trigger an error regarding Nutch MP3 code.)<br />
<br />
The DiscoverEd source code lives in two locations:<br />
<br />
* ded/src/java contains DiscoverEd specific code, primarily related to interfacing with the RDF store.<br />
* src/plugins/cclearn contains the DiscoverEd Nutch plugin, which provides some filtering features to Nutch and ensures metadata indexed in the RDF store is injected into the Lucene index<br />
<br />
Generally, the plugin may depend upon code in the ded/src/java tree, but classes in the plugin may not be available to that code.<br />
<br />
'''Note:''' The DiscoverEd developers will consider you extra special if you indent your code using spaces instead of tabs. You may even earn a gold star.<br />
<br />
To use spaces for all indentation for all Java projects in Eclipse 3.5 (Galileo):<br />
# Open Preferences<br />
# Expand the Java group<br />
# Expand the Code Style subgroup within the Java group<br />
# Select Formatter<br />
# Click on "New" in the Formatter section and name your profile<br />
# Check that the "Indentation" tab is active<br />
# Select "Spaces only" from the "Tab policy" dropdown<br />
# Click "Apply" and or "OK"<br />
<br />
You may also do this on a per-project basis by setting it as a project property. The general process is the same.<br />
<br />
= Commiting Changes and Merging to the Main Repository =<br />
<br />
<br />
<br />
= Troubleshooting =<br />
<br />
==== I get a big long Java backtrace talking about Jena and MySQL ====<br />
<br />
If you've configured DiscoverEd to use MySQL as the database backend, you'll need to create the database first.<br />
<br />
==== Database permissions ====<br />
<br />
You might need to change the MySQL credentials or database configuration value in <code>conf/discovered.xml</code>. DiscoverEd does not require that you use the root user; it does require that the database already exist.<br />
<br />
==== JAVA_HOME on a Mac ====<br />
<br />
Mac users setting JAVA_HOME should use<br />
/usr/libexec/java_home to determine the current JAVA_HOME<br />
<br />
if you're really lazy add<br />
JAVA_HOME=`/usr/libexec/java_home` <br />
to .bash_profile and it will set JAVA_HOME each time you invoke a shell. (This is a good idea!)<br />
<br />
Get [http://hostgator1centcoupon.net Hostgator 1 cent] here and save lot on Hostgator<br />
<br />
==== Error message: "Feature 'http://apache.org/xml/features/xinclude' is not recognized." ====<br />
<br />
"You probably have an older version of Xerces somewhere in your classpath or something is overriding the default parser configuration with one that doesn't support XInclude." (http://marc.info/?l=xerces-j-user&m=117066278506146&w=2)<br />
<br />
==== AccessControlException ====<br />
<br />
When starting Tomcat, if you get a traceback like this in your tomcat log (e.g., in /var/lib/tomcat6/logs/localhost-$date.log):<br />
<br />
SEVERE: Exception sending context initialized event to listener instance of class org.apache.nutch.searcher.NutchBean$NutchBeanConstructor<br />
java.lang.RuntimeException: java.security.AccessControlException: access denied (java.lang.reflect.ReflectPermission suppressAccessChecks)<br />
at org.apache.hadoop.util.ReflectionUtils.newInstance(ReflectionUtils.java:115)<br />
at org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:1377)<br />
at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:66)<br />
at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:1390)<br />
at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:196)<br />
at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:95)<br />
<br />
and so on, try changing the Tomcat policy in /etc/tomcat6/policy.d/04webapps.policy. Add these lines in the grant {} block:<br />
<br />
// Attempt to get Nutch working<br />
// Courtesy of Alex McLintock at http://mail-archives.apache.org/mod_mbox/lucene-nutch-user/200907.mbox/<d398ec7f0907041237j6acffe0fm10b7cd374a77795b@mail.gmail.com><br />
permission java.security.AllPermission;<br />
<br />
This is obviously inappropriate for any site running a public instance of DiscoverEd. But it might be useful for your local dev environment. If you know how to specify a class level permission, please update this document.<br />
<br />
==== Missing build/plugins ====<br />
<br />
Be sure to run ant in the root repo directory.<br />
<br />
==== Missing parse-mp3 plugin ====<br />
<br />
Remove that source folder from the build path (in Eclimse, Project > Properties > Java Build Path > Source.<br />
<br />
==== Eclipse complains: Wrong version number in .class file ====<br />
<br />
Use Java 1.6 as your compiler. Be sure to use the right JVM for this project.</div>Couponcodehttps://wiki.creativecommons.org/index.php?title=Case_Studies/GlaxoSmithKline&diff=80722Case Studies/GlaxoSmithKline2013-08-16T13:27:36Z<p>Couponcode: </p>
<hr />
<div>{{Case Study<br />
|Description=GlaxoSmithKline is a major pharmaceutical company that has surrendered all copyrights in its malarial data set, which includes more than 13,500 compounds known to be active against malaria.<br />
|Mainurl=http://www.ebi.ac.uk/chemblntd/#tcams_dataset<br />
|Author=ChEMBL-NTD, GlaxoSmithKline<br />
|User_Status=Curator, Creator<br />
|Tag=GSK, GlaxoSmithKline, malaria, disease<br />
|License short name=GNU GPL<br />
|Format=Image, Sound, Text, MovingImage, InteractiveResource, Other, Geodata, Data<br />
|Country=United Kingdom<br />
|Quote=Providing access to this level of information sees GSK set what I would hope to be a new trend that could revolutionise the urgent search for new medicines to tackle malaria. By sharing data, we start to build up a public database of knowledge that should be as powerful as the human genome databases.<br />
|Quote_Attribution=Timothy Wells, Chief Scientific Officer of the Medicines for Malaria Venture (http://www.gsk.com/responsibility/access/rnd-neglected-tropical-diseases.htm)<br />
|Image_Header=http://wiki.creativecommons.org/images/0/04/Logo-gsk.gif<br />
|Image_attribution=(c) GSK<br />
|Image_license=http://www.gsk.com/terms.htm<br />
|importance=High<br />
|quality=B-Class<br />
|License_short_name=CC0<br />
}}<br />
== Overview ==<br />
One of the leading pharmaceutical companies in the world, GlaxoSmithKline has surrendered all copyrights in its malarial data set, which includes more than 13,500 compounds known to be active against malaria. The data set is called Tres Cantos Antimalarial (TCAMS), and is available from the ChEMBL-NTD database, "a repository for Open Access primary screening and medicinal chemistry data directed at neglected diseases - endemic tropical diseases of the developing regions of the Africa, Asia, and the Americas."<br />
<br />
== License Usage ==<br />
<br />
GlaxoSmithKline has surrendered all copyright in its malaria data set under the CC0 public domain dedication.<br />
<br />
== Motivations ==<br />
From GSK's http://www.gsk.com/responsibility/downloads/GSK-CR-2009-full.pdf<br />
<br />
<blockquote>"By making this information publicly available, GSK hopes that many other scientists will review this information and analyse the data faster than we could on our own. Hopefully, this will lead to additional research that could help drive the discovery of new medicines. We would also encourage other groups, including academics and pharmaceutical companies, to make their own compounds and related information publicly available.<br />
<br />
<br/><br/>This is essentially an example of ‘open source’ being applied to drug discovery. We know that data increases in value when connected with other data and that the more eyes looking at a problem, the more potential solutions may arise."</blockquote><br />
<br />
Research and development (R&D) for diseases prevalent in the developing world are costly and time-consuming and carry less return on investment than R&D for diseases, such as HIV/AIDS, which have a market in the developed world. Since malaria is a disease that primarily affects the developing world, GSK has released malarial data in order to speed the process of R&D, while providing resources that nonprofits and academic institutions don't necessarily have wide access to, such as advanced technologies, facilities for medicinal drug discovery, and manufacturing and distribution expertise. For more information, see GSK's 2009 [http://hostgator1centcoupon.net report on]<br />
<br />
== Media ==<br />
[http://www.nature.com/news/2010/100120/full/news.2010.20.html Nature - GlaxoSmithKline goes public with malaria data]<br />
<br/><br />
[http://www.guardian.co.uk/science/2010/jan/20/glaxo-malaria-drugs-public-domain The Guardian - Glaxo offers free access to potential malaria cures]<br />
<br/><br />
[http://www.gsk.com/media/malaria.htm GSK's commitment to fighting Malaria]<br />
<br/><br />
[http://hyperfuel9x.us/ hyper fuel 9x]<br />
<br/><br />
[http://www.gsk.com/media/pressreleases/2010/2010_pressrelease_10009.htm press release]<br />
<br/><br />
[http://www.bay91.com bay91]</div>Couponcode