Changeset 566


Ignore:
Timestamp:
08/09/09 01:43:29 (5 years ago)
Author:
tom
Message:

updating documentation and educommons.com links

Location:
enpraxis.educommons/trunk/enpraxis/educommons
Files:
32 edited

Legend:

Unmodified
Added
Removed
  • enpraxis.educommons/trunk/enpraxis/educommons/CHANGES.txt

    r8 r566  
     1======================== 
     2Changes in version 3.2.1 
     3======================== 
     4Installers 
     5   Simplified installation have been added, including buildout scripts and Windows installers. 
     6Expanded IMS Import 
     7   eduCommons can now import from IMS Common Cartridge, IMS Content Package, MIT course downloads, Blackboard IMS, WebCT Vista, WebCT 6.1/7.0, and Moodle Backups. 
     8Improved IMS Export 
     9   eduCommons can now export to IMS Common Cartridge, IMS Content Package, and IMS Package for Moodle. 
     10WordPress Import/Export 
     11   Support has been added to import pages from a WordPress site as well as export eduCommons content directly to WordPress pages. 
     12Static Site 
     13   It is now possible to publish an entire eduCommons site to static HTML. 
     14Expanded RSS 
     15   Additional RSS have been added to create an RSS feed of most recent items. 
     16OIA-pmh and Improved Metadata 
     17   Support has been added for additional metadata in rdf/rss views as well as OAI/pmh. 
     18OpenSearch Support 
     19   Support has been added for OpenSearch, including the Firefox OpenSearch widget which allows a search of a specific eduCommons site directly from the browser's search window. 
     20 
    121======================== 
    222Changes in version 3.1.0 
  • enpraxis.educommons/trunk/enpraxis/educommons/IMSContentPackaging.txt

    r522 r566  
    1 IMS Content Packaging and eduCommons 3.2.1 
     1IMS Content Packaging and eduCommons 3.2.1-rc2 
    22================================================ 
    33 
    44This document details how to write IMS Content packages that are compatible with 
    5 eduCommons 3.2.1.  
     5eduCommons 3.2.1-rc2.  
    66 
    77eduCommons uses version 1.2 of the IMS Content Packaging Specification. XML Schemas 
  • enpraxis.educommons/trunk/enpraxis/educommons/INSTALL.txt

    r522 r566  
    11================================== 
    2 Installing eduCommons 3.2.1 
     2Installing eduCommons 3.2.1-rc2 
    33================================== 
    44 
    5 Download the eduCommons 3.2.1 release, available at: 
     5Download the eduCommons 3.2.1-rc2 release, available at: 
    66 
    77:: 
  • enpraxis.educommons/trunk/enpraxis/educommons/LOCALIZATION.txt

    r522 r566  
    1818 
    1919======================================== 
    20 Localization with eduCommons 3.2.1 
     20Localization with eduCommons 3.2.1-rc2 
    2121======================================== 
    2222 
     
    3737less time consuming because most of the translation work has already been done in Plone. 
    3838 
    39 There are about 400 strings needed for a translation of eduCommons (compared to about 1600 strings  
     39There are about 470 strings needed for a translation of eduCommons (compared to about 1600 strings  
    4040for a Plone translation). Some of these are sentences or paragraphs, but the major part are one or  
    4141two words. These strings are scattered around in Plone, for example in page templates. Other items  
    4242to translate are widget labels, and workflow states. All those strings are collected in master  
    43 files. Currently eduCommons contains six .pot files. Each language requires its own .po files that 
     43files. These are called .pot files. Each language requires its own .po files that 
    4444corresponds to the strings or message ids declared in the .pot files. The .pot is the blueprint for 
    4545the .po files. 
     
    8282    this translation compared to not getting one at all :) 
    8383     
    84     4. Here is a link to the most recent translation files available for eduCommons (plone.po and  
    85     eduCommons.po). Remember, unless there is already an existing translation available, you need  
    86     to grab the .pot files. 
    87   
    88         http://cosl.usu.edu/svndev/eduCommons3/trunk/i18n/ 
    89          
    90         Here are links to the latest translations for each of the eduCommons products on the Plone  
    91         Collective site (these links may change, so check back for the most accurate information):  
    92  
    93         http://svn.plone.org/svn/collective/ZipFileTransport/branches/cosl-plone3/i18n/  
    94  
    95         http://svn.plone.org/svn/collective/IMSTransport/branches/cosl-plone3/i18n/  
    96  
    97         http://svn.plone.org/svn/collective/ContentLicensing/branches/cosl-plone3/i18n/ 
    98  
    99         http://svn.plone.org/svn/collective/PloneBookmarklets/branches/plone3/i18n/ 
     84    4. Each product in eduCommons has .po files located in the locales directory. We have combined 
     85    all these files in a single location of ease of translation. It can be accessed here: 
     86    http://educommons.com/localization/localization-files.zip 
     87    If you wish to translate a language for which we do not currently have translation files,  
     88    please contact us at info [at] educommons [dot] com. 
    10089     
    10190     
     
    139128    ${number} TRANSLATION. 
    140129 
    141     9. Keep translating (but take breaks, this isn't done in one sitting - it's repetetive (but  
     130    9. Keep translating (but take breaks, this isn't done in one sitting - it's repetitive (but  
    142131    rewarding) work. After you have translated all of plone.pot, you should start on eduCommons.pot.  
    143132    Don't worry, you have already completed the biggest part. 
     
    154143    works, you can get an account with Plone (Here's how to request write access to the Collective.) 
    155144    and maintain the files in SVN yourself (see next section). If not, no problem, just e-mail your 
    156     translation to us at eduCommons [at] cosl [dot] usu [dot] edu, and we will add it for you and put it into the 
     145    translation to us at info [at] educommons [dot] com, and we will add it for you and put it into the 
    157146    eduCommons distribution in the next release. We will also add you to our our `eduCommons 
    158     Localization Team page. <./educommons-localization-team>`__ 
     147    Localization Team page, here: http://educommons.com/documentation/how-to/educommons-localization-team 
    159148     
    160149    13. Please check on your translations periodically to keep them updated as new versions are  
    161     released. A quick find for "" will reveal any new or missing stings that need to be translated. 
     150    released. A quick search for "" will reveal any new or missing stings that need to be translated. 
    162151     
    163152    14. If you have other questions or about contributing a translation to eduCommons please contact 
    164     us at educommons [at] cosl [dot] usu [dot] edu. Thank you for you help! 
     153    us at info [at] educommons [dot] com. Thank you for you help! 
    165154 
  • enpraxis.educommons/trunk/enpraxis/educommons/MIGRATION.txt

    r522 r566  
    11=================================== 
    2 Migrating to eduCommons 3.2.1 
     2Migrating to eduCommons 3.2.1-rc2 
    33=================================== 
    44 
     
    1313 
    1414 
    15 Migration of eduCommons 3.1.1-final to 3.2.1 
     15Migration of eduCommons 3.1.1-final to 3.2.1-rc2 
    1616-------------------------------------------------- 
    1717 
    18 The migration eduCommons from version 3.1.1-final to version 3.2.1 
     18The migration eduCommons from version 3.1.1-final to version 3.2.1-rc2 
    1919includes the following: 
    2020 
    21211. Pre-migration of Data.fs in version 3.1.1-final 
    2222 
    23 2. Movement of Data.fs file to a new 3.2.1 instance 
     232. Movement of Data.fs file to a new 3.2.1-rc2 instance 
    2424 
    25 3. Migration to the eduCommons 3.2.1 instance 
     253. Migration to the eduCommons 3.2.1-rc2 instance 
    2626 
    27 4. Export/Import of eduCommons site to a new 3.2.1 instance 
     274. Export/Import of eduCommons site to a new 3.2.1-rc2 instance 
    2828 
    29295. Final steps 
     
    7070 
    7171 
    72 Movement of Data.fs file to a new 3.2.1 instance 
     72Movement of Data.fs file to a new 3.2.1-rc2 instance 
    7373------------------------------------------------------ 
    7474 
    7575For this step, you will move the Data.fs file from the old instance to 
    76 the new instance. First of all, install an eduCommons-3.2.1 
     76the new instance. First of all, install an eduCommons-3.2.1-rc2 
    7777instance using the installations instructions found in [new instance home]/eduCommons/docs/. Stop both sites. Then 
    7878copy the Data.fs file from the var directory of the old site to the 
     
    8383 
    8484 
    85 Migration to eduCommons 3.2.1 instance 
     85Migration to eduCommons 3.2.1-rc2 instance 
    8686------------------------------------------------ 
    87 eduCommons 3.2.1 uses the portal_setup tool to perform the necessary upgrade from 3.1.1 to 3.2.1. Due to the fact that eduCommons and it's dependencies were moved to python eggs, we must start with a new eduCommons site. The migration script will then copy and past content and relevant settings to the new installation: 
     87eduCommons 3.2.1-rc2 uses the portal_setup tool to perform the necessary upgrade from 3.1.1 to 3.2.1-rc2. Due to the fact that eduCommons and it's dependencies were moved to python eggs, we must start with a new eduCommons site. The migration script will then copy and past content and relevant settings to the new installation: 
    8888 
    89891. Navigate to the root of your ZMI instance and create a new eduCommons site called eduCommons321 
    90 2. Open your new 3.2.1 eduCommons site in the ZMI. (click educommons Setup, then click Zope Management Interface.) 
     902. Open your new 3.2.1-rc2 eduCommons site in the ZMI. (click educommons Setup, then click Zope Management Interface.) 
    91913. Navigate to portal_setup 
    92924. Press the 'Upgrades' tab 
     
    9696 
    9797 
    98 Export/Import of eduCommons site to a new 3.2.1 instance 
     98Export/Import of eduCommons site to a new 3.2.1-rc2 instance 
    9999-------------------------------------------------------------- 
    100100 
     
    102102 
    1031031. Navigate to the root of your ZMI instance 
    104 2. Select the checkbox next to your new 3.2.1 eduCommons site 
     1042. Select the checkbox next to your new 3.2.1-rc2 eduCommons site 
    1051053. Press Import/Export 
    1061064. If your production environment is on the same server as your migration environment, choose 'Save file to server', else 
  • enpraxis.educommons/trunk/enpraxis/educommons/SETUP.txt

    r522 r566  
    7878The *Site Title* and *Site Description* fields should contain values that were initially set during the installation process. If you want to change these fields, you can do so here. The *Site Title* field is referred to throughout the site. It is important to remember that eduCommons will only change the portal title on a page when a template is applied. If you change this setting here, it will be necessary to also change it throughout the site, or to reapply templates that refer to it. 
    7979 
    80 eduCommons provides a number of settings that can be used with your site. The *Site 'From" Name* and *Site 'From' Address* are already discussed in the section titled `Mail Settings`_.  
    81  
    8280*JavaScript for web statistics support* is an area for enabling web statistics support from external providers (for e.g. Google Analytics). Paste the code snippets provided. It will be included in the rendered HTML as entered near the end of the page. 
    8381 
    84 The *Default Language* setting is discussed in the next section. 
    8582 
    8683Setting the Default Language for your Site 
     
    141138There are other options that are available if you find yourself needing extra functionality. The `development site`_ for eduCommons can be used to check to see if your bug is being or has been fixed, or to see what features have been scheduled for development on the `roadmap`_. There are also `forums`_ where you can post issues and get responses from the development team and/or other eduCommons users. 
    142139 
    143 .. _development site: http://cosl.usu.edu/trac 
    144 .. _roadmap: http://cosl.usu.edu/trac/roadmap 
    145 .. _forums: http://cosl.usu.edu/forums 
     140.. _development site: http://educommons.com/dev 
     141.. _roadmap: http://educommons.com/dev/roadmap 
     142.. _forums: http://educommons.com/support-forums 
    146143 
    147144eduCommons depends on community support, and participation in the user community/development process is both appreciated and welcome. 
    148145 
    149 For additional documentation, including updates to these setup instructions, please visit: http://cosl.usu.edu/projects/educommons/documentation, specifically http://cosl.usu.edu/projects/educommons/documentation/how-to 
     146For additional documentation, including updates to these setup instructions, please visit: http://educommons.com/documentation 
  • enpraxis.educommons/trunk/enpraxis/educommons/SeleniumRCTests.txt

    r522 r566  
    11========================================= 
    2 eduCommons 3.2.1 SeleniumRC Testing 
     2eduCommons 3.2.1-rc2 SeleniumRC Testing 
    33========================================= 
    44 
     
    5353 Role      Username   Password   
    5454 ====     =========   ========= 
    55  admin      admin       admin 
     55 admin/manager admin  test1234 
    5656 producer  producer   producer 
    5757 reviewer  reviewer  reviewer 
    58  qa          qa          qa        
     58 qa        quality   quality        
    5959 publisher publisher publisher 
    60  viewer    viewer   viewer   
     60 viewer    viewer    viewer   
    6161 =======  =========   ========= 
    6262 
  • enpraxis.educommons/trunk/enpraxis/educommons/browser/templates/faq_view.pt

    r564 r566  
    708708cluster and a content staging cluster.</p> 
    709709 
    710 <p>For more information on eduCommons, please contact The Center for Open and Sustainable Learning (<a href="http://cosl.usu.edu/">http://cosl.usu.edu/</a>).</p> 
     710<p>For more information on eduCommons, please visit <a href="http://educommons.com">http://educommons.com</a>.</p> 
    711711 
    712712<p><a href="#TOP">Top</a></p> 
  • enpraxis.educommons/trunk/enpraxis/educommons/docs/CHANGES.html

    r520 r566  
    1212 
    1313 
     14<div class="section" id="changes-in-version-3-2-1"> 
     15<h1>Changes in version 3.2.1</h1> 
     16<dl class="docutils"> 
     17<dt>Installers</dt> 
     18<dd>Simplified installation have been added, including buildout scripts and Windows installers.</dd> 
     19<dt>Expanded IMS Import</dt> 
     20<dd>eduCommons can now import from IMS Common Cartridge, IMS Content Package, MIT course downloads, Blackboard IMS, WebCT Vista, WebCT 6.1/7.0, and Moodle Backups.</dd> 
     21<dt>Improved IMS Export</dt> 
     22<dd>eduCommons can now export to IMS Common Cartridge, IMS Content Package, and IMS Package for Moodle.</dd> 
     23<dt>WordPress Import/Export</dt> 
     24<dd>Support has been added to import pages from a WordPress site as well as export eduCommons content directly to WordPress pages.</dd> 
     25<dt>Static Site</dt> 
     26<dd>It is now possible to publish an entire eduCommons site to static HTML.</dd> 
     27<dt>Expanded RSS</dt> 
     28<dd>Additional RSS have been added to create an RSS feed of most recent items.</dd> 
     29<dt>OIA-pmh and Improved Metadata</dt> 
     30<dd>Support has been added for additional metadata in rdf/rss views as well as OAI/pmh.</dd> 
     31<dt>OpenSearch Support</dt> 
     32<dd>Support has been added for OpenSearch, including the Firefox OpenSearch widget which allows a search of a specific eduCommons site directly from the browser's search window.</dd> 
     33</dl> 
     34</div> 
    1435<div class="section" id="changes-in-version-3-1-0"> 
    1536<h1>Changes in version 3.1.0</h1> 
     
    253274<hr class="footer" /> 
    254275<a class="reference external" href="CHANGES.txt">View document source</a>. 
    255 Generated on: 2009-08-06 16:49 UTC. 
     276Generated on: 2009-08-09 07:41 UTC. 
    256277Generated by <a class="reference external" href="http://docutils.sourceforge.net/">Docutils</a> from <a class="reference external" href="http://docutils.sourceforge.net/rst.html">reStructuredText</a> source. 
    257278 
  • enpraxis.educommons/trunk/enpraxis/educommons/docs/IMSContentPackaging.html

    r520 r566  
    1212 
    1313 
    14 <div class="section" id="ims-content-packaging-and-educommons-3-2-1"> 
    15 <h1>IMS Content Packaging and eduCommons 3.2.1</h1> 
     14<div class="section" id="ims-content-packaging-and-educommons-3-2-1-rc2"> 
     15<h1>IMS Content Packaging and eduCommons 3.2.1-rc2</h1> 
    1616<p>This document details how to write IMS Content packages that are compatible with 
    17 eduCommons 3.2.1.</p> 
     17eduCommons 3.2.1-rc2.</p> 
    1818<p>eduCommons uses version 1.2 of the IMS Content Packaging Specification. XML Schemas 
    1919for the specification can be found at <a class="reference external" href="http://imsglobal.org/xsd/imscp_v1p2.xsd">http://imsglobal.org/xsd/imscp_v1p2.xsd</a> and 
     
    475475<hr class="footer" /> 
    476476<a class="reference external" href="IMSContentPackaging.txt">View document source</a>. 
    477 Generated on: 2009-08-06 16:49 UTC. 
     477Generated on: 2009-08-09 07:41 UTC. 
    478478Generated by <a class="reference external" href="http://docutils.sourceforge.net/">Docutils</a> from <a class="reference external" href="http://docutils.sourceforge.net/rst.html">reStructuredText</a> source. 
    479479 
  • enpraxis.educommons/trunk/enpraxis/educommons/docs/INSTALL.html

    r520 r566  
    55<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 
    66<meta name="generator" content="Docutils 0.5: http://docutils.sourceforge.net/" /> 
    7 <title>Installing eduCommons 3.2.1</title> 
     7<title>Installing eduCommons 3.2.1-rc2</title> 
    88<link rel="stylesheet" href="./default.css" type="text/css" /> 
    99</head> 
    1010<body> 
    11 <div class="document" id="installing-educommons-3-2-1"> 
    12 <h1 class="title">Installing eduCommons 3.2.1</h1> 
     11<div class="document" id="installing-educommons-3-2-1-rc2"> 
     12<h1 class="title">Installing eduCommons 3.2.1-rc2</h1> 
    1313 
    14 <p>Download the eduCommons 3.2.1 release, available at:</p> 
     14<p>Download the eduCommons 3.2.1-rc2 release, available at:</p> 
    1515<pre class="literal-block"> 
    1616http://sourceforge.net/projects/educommons/files/educommons/eduCommons-3.2.1-final/educommons.buildout-3.2.1-final.tar.gz/download 
     
    112112<hr class="footer" /> 
    113113<a class="reference external" href="INSTALL.txt">View document source</a>. 
    114 Generated on: 2009-08-06 16:49 UTC. 
     114Generated on: 2009-08-09 07:41 UTC. 
    115115Generated by <a class="reference external" href="http://docutils.sourceforge.net/">Docutils</a> from <a class="reference external" href="http://docutils.sourceforge.net/rst.html">reStructuredText</a> source. 
    116116 
  • enpraxis.educommons/trunk/enpraxis/educommons/docs/LOCALIZATION.html

    r520 r566  
    2525setting from neutral to the appropriate setting for your instance.</p> 
    2626</div> 
    27 <div class="section" id="localization-with-educommons-3-2-1"> 
    28 <h1>Localization with eduCommons 3.2.1</h1> 
     27<div class="section" id="localization-with-educommons-3-2-1-rc2"> 
     28<h1>Localization with eduCommons 3.2.1-rc2</h1> 
    2929<div class="section" id="overview"> 
    3030<h2>Overview</h2> 
     
    4141translation work, but follows the same process as Plone. Adding an eduCommons translation is much 
    4242less time consuming because most of the translation work has already been done in Plone.</p> 
    43 <p>There are about 400 strings needed for a translation of eduCommons (compared to about 1600 strings 
     43<p>There are about 470 strings needed for a translation of eduCommons (compared to about 1600 strings 
    4444for a Plone translation). Some of these are sentences or paragraphs, but the major part are one or 
    4545two words. These strings are scattered around in Plone, for example in page templates. Other items 
    4646to translate are widget labels, and workflow states. All those strings are collected in master 
    47 files. Currently eduCommons contains six .pot files. Each language requires its own .po files that 
     47files. These are called .pot files. Each language requires its own .po files that 
    4848corresponds to the strings or message ids declared in the .pot files. The .pot is the blueprint for 
    4949the .po files.</p> 
     
    8181language you understand is Italian, and you want to provide a Chinese translation, we prefer 
    8282this translation compared to not getting one at all :)</p> 
    83 <p>4. Here is a link to the most recent translation files available for eduCommons (plone.po and 
    84 eduCommons.po). Remember, unless there is already an existing translation available, you need 
    85 to grab the .pot files.</p> 
    86 <blockquote> 
    87 <p><a class="reference external" href="http://cosl.usu.edu/svndev/eduCommons3/trunk/i18n/">http://cosl.usu.edu/svndev/eduCommons3/trunk/i18n/</a></p> 
    88 <p>Here are links to the latest translations for each of the eduCommons products on the Plone 
    89 Collective site (these links may change, so check back for the most accurate information):</p> 
    90 <p><a class="reference external" href="http://svn.plone.org/svn/collective/ZipFileTransport/branches/cosl-plone3/i18n/">http://svn.plone.org/svn/collective/ZipFileTransport/branches/cosl-plone3/i18n/</a></p> 
    91 <p><a class="reference external" href="http://svn.plone.org/svn/collective/IMSTransport/branches/cosl-plone3/i18n/">http://svn.plone.org/svn/collective/IMSTransport/branches/cosl-plone3/i18n/</a></p> 
    92 <p><a class="reference external" href="http://svn.plone.org/svn/collective/ContentLicensing/branches/cosl-plone3/i18n/">http://svn.plone.org/svn/collective/ContentLicensing/branches/cosl-plone3/i18n/</a></p> 
    93 <p><a class="reference external" href="http://svn.plone.org/svn/collective/PloneBookmarklets/branches/plone3/i18n/">http://svn.plone.org/svn/collective/PloneBookmarklets/branches/plone3/i18n/</a></p> 
    94 </blockquote> 
     83<p>4. Each product in eduCommons has .po files located in the locales directory. We have combined 
     84all these files in a single location of ease of translation. It can be accessed here: 
     85<a class="reference external" href="http://educommons.com/localization/localization-files.zip">http://educommons.com/localization/localization-files.zip</a> 
     86If you wish to translate a language for which we do not currently have translation files, 
     87please contact us at info [at] educommons [dot] com.</p> 
    9588<p>5. Open poEdit or your editor of choice and load the first of the master files. In poEdit 
    9689select File --&gt; Open (for existing .po translation files) or File --&gt; New catalog from POT file. 
     
    129122criteria.&quot; The code in the first part should be left as it is, so the translation will look like this: 
    130123${number} TRANSLATION.</p> 
    131 <p>9. Keep translating (but take breaks, this isn't done in one sitting - it's repetetive (but 
     124<p>9. Keep translating (but take breaks, this isn't done in one sitting - it's repetitive (but 
    132125rewarding) work. After you have translated all of plone.pot, you should start on eduCommons.pot. 
    133126Don't worry, you have already completed the biggest part.</p> 
     
    141134works, you can get an account with Plone (Here's how to request write access to the Collective.) 
    142135and maintain the files in SVN yourself (see next section). If not, no problem, just e-mail your 
    143 translation to us at eduCommons [at] cosl [dot] usu [dot] edu, and we will add it for you and put it into the 
    144 eduCommons distribution in the next release. We will also add you to our our <a class="reference external" href="./educommons-localization-team">eduCommons 
    145 Localization Team page.</a></p> 
     136translation to us at info [at] educommons [dot] com, and we will add it for you and put it into the 
     137eduCommons distribution in the next release. We will also add you to our our <a href="#id1"><span class="problematic" id="id2">`</span></a>eduCommons 
     138Localization Team page, here: <a class="reference external" href="http://educommons.com/documentation/how-to/educommons-localization-team">http://educommons.com/documentation/how-to/educommons-localization-team</a></p> 
     139<div class="system-message" id="id1"> 
     140<p class="system-message-title">System Message: WARNING/2 (<tt class="docutils">../LOCALIZATION.txt</tt>, line 142); <em><a href="#id2">backlink</a></em></p> 
     141Inline interpreted text or phrase reference start-string without end-string.</div> 
    146142<p>13. Please check on your translations periodically to keep them updated as new versions are 
    147 released. A quick find for &quot;&quot; will reveal any new or missing stings that need to be translated.</p> 
     143released. A quick search for &quot;&quot; will reveal any new or missing stings that need to be translated.</p> 
    148144<p>14. If you have other questions or about contributing a translation to eduCommons please contact 
    149 us at educommons [at] cosl [dot] usu [dot] edu. Thank you for you help!</p> 
     145us at info [at] educommons [dot] com. Thank you for you help!</p> 
    150146</blockquote> 
    151147</div> 
     
    155151<hr class="footer" /> 
    156152<a class="reference external" href="LOCALIZATION.txt">View document source</a>. 
    157 Generated on: 2009-08-06 16:49 UTC. 
     153Generated on: 2009-08-09 07:41 UTC. 
    158154Generated by <a class="reference external" href="http://docutils.sourceforge.net/">Docutils</a> from <a class="reference external" href="http://docutils.sourceforge.net/rst.html">reStructuredText</a> source. 
    159155 
  • enpraxis.educommons/trunk/enpraxis/educommons/docs/MIGRATION.html

    r520 r566  
    55<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 
    66<meta name="generator" content="Docutils 0.5: http://docutils.sourceforge.net/" /> 
    7 <title>Migrating to eduCommons 3.2.1</title> 
     7<title>Migrating to eduCommons 3.2.1-rc2</title> 
    88<link rel="stylesheet" href="./default.css" type="text/css" /> 
    99</head> 
    1010<body> 
    11 <div class="document" id="migrating-to-educommons-3-2-1"> 
    12 <h1 class="title">Migrating to eduCommons 3.2.1</h1> 
     11<div class="document" id="migrating-to-educommons-3-2-1-rc2"> 
     12<h1 class="title">Migrating to eduCommons 3.2.1-rc2</h1> 
    1313 
    1414<div class="section" id="preparation"> 
     
    2020</ol> 
    2121</div> 
    22 <div class="section" id="migration-of-educommons-3-1-1-final-to-3-2-1"> 
    23 <h1>Migration of eduCommons 3.1.1-final to 3.2.1</h1> 
    24 <p>The migration eduCommons from version 3.1.1-final to version 3.2.1 
     22<div class="section" id="migration-of-educommons-3-1-1-final-to-3-2-1-rc2"> 
     23<h1>Migration of eduCommons 3.1.1-final to 3.2.1-rc2</h1> 
     24<p>The migration eduCommons from version 3.1.1-final to version 3.2.1-rc2 
    2525includes the following:</p> 
    2626<ol class="arabic simple"> 
    2727<li>Pre-migration of Data.fs in version 3.1.1-final</li> 
    28 <li>Movement of Data.fs file to a new 3.2.1 instance</li> 
    29 <li>Migration to the eduCommons 3.2.1 instance</li> 
    30 <li>Export/Import of eduCommons site to a new 3.2.1 instance</li> 
     28<li>Movement of Data.fs file to a new 3.2.1-rc2 instance</li> 
     29<li>Migration to the eduCommons 3.2.1-rc2 instance</li> 
     30<li>Export/Import of eduCommons site to a new 3.2.1-rc2 instance</li> 
    3131<li>Final steps</li> 
    3232</ol> 
     
    6565</ol> 
    6666</div> 
    67 <div class="section" id="movement-of-data-fs-file-to-a-new-3-2-1-instance"> 
    68 <h1>Movement of Data.fs file to a new 3.2.1 instance</h1> 
     67<div class="section" id="movement-of-data-fs-file-to-a-new-3-2-1-rc2-instance"> 
     68<h1>Movement of Data.fs file to a new 3.2.1-rc2 instance</h1> 
    6969<p>For this step, you will move the Data.fs file from the old instance to 
    70 the new instance. First of all, install an eduCommons-3.2.1 
     70the new instance. First of all, install an eduCommons-3.2.1-rc2 
    7171instance using the installations instructions found in [new instance home]/eduCommons/docs/. Stop both sites. Then 
    7272copy the Data.fs file from the var directory of the old site to the 
     
    7676</pre> 
    7777</div> 
    78 <div class="section" id="migration-to-educommons-3-2-1-instance"> 
    79 <h1>Migration to eduCommons 3.2.1 instance</h1> 
    80 <p>eduCommons 3.2.1 uses the portal_setup tool to perform the necessary upgrade from 3.1.1 to 3.2.1. Due to the fact that eduCommons and it's dependencies were moved to python eggs, we must start with a new eduCommons site. The migration script will then copy and past content and relevant settings to the new installation:</p> 
     78<div class="section" id="migration-to-educommons-3-2-1-rc2-instance"> 
     79<h1>Migration to eduCommons 3.2.1-rc2 instance</h1> 
     80<p>eduCommons 3.2.1-rc2 uses the portal_setup tool to perform the necessary upgrade from 3.1.1 to 3.2.1-rc2. Due to the fact that eduCommons and it's dependencies were moved to python eggs, we must start with a new eduCommons site. The migration script will then copy and past content and relevant settings to the new installation:</p> 
    8181<ol class="arabic simple"> 
    8282<li>Navigate to the root of your ZMI instance and create a new eduCommons site called eduCommons321</li> 
    83 <li>Open your new 3.2.1 eduCommons site in the ZMI. (click educommons Setup, then click Zope Management Interface.)</li> 
     83<li>Open your new 3.2.1-rc2 eduCommons site in the ZMI. (click educommons Setup, then click Zope Management Interface.)</li> 
    8484<li>Navigate to portal_setup</li> 
    8585<li>Press the 'Upgrades' tab</li> 
     
    8989</ol> 
    9090</div> 
    91 <div class="section" id="export-import-of-educommons-site-to-a-new-3-2-1-instance"> 
    92 <h1>Export/Import of eduCommons site to a new 3.2.1 instance</h1> 
     91<div class="section" id="export-import-of-educommons-site-to-a-new-3-2-1-rc2-instance"> 
     92<h1>Export/Import of eduCommons site to a new 3.2.1-rc2 instance</h1> 
    9393<p>You are now ready to transfer your migrated instance to the production environment.</p> 
    9494<ol class="arabic simple"> 
    9595<li>Navigate to the root of your ZMI instance</li> 
    96 <li>Select the checkbox next to your new 3.2.1 eduCommons site</li> 
     96<li>Select the checkbox next to your new 3.2.1-rc2 eduCommons site</li> 
    9797<li>Press Import/Export</li> 
    9898<li>If your production environment is on the same server as your migration environment, choose 'Save file to server', else 
     
    113113<hr class="footer" /> 
    114114<a class="reference external" href="MIGRATION.txt">View document source</a>. 
    115 Generated on: 2009-08-06 16:49 UTC. 
     115Generated on: 2009-08-09 07:41 UTC. 
    116116Generated by <a class="reference external" href="http://docutils.sourceforge.net/">Docutils</a> from <a class="reference external" href="http://docutils.sourceforge.net/rst.html">reStructuredText</a> source. 
    117117 
  • enpraxis.educommons/trunk/enpraxis/educommons/docs/MIGRATIONS_OLD.html

    r520 r566  
    223223<hr class="footer" /> 
    224224<a class="reference external" href="MIGRATIONS_OLD.txt">View document source</a>. 
    225 Generated on: 2009-08-06 16:49 UTC. 
     225Generated on: 2009-08-09 07:41 UTC. 
    226226Generated by <a class="reference external" href="http://docutils.sourceforge.net/">Docutils</a> from <a class="reference external" href="http://docutils.sourceforge.net/rst.html">reStructuredText</a> source. 
    227227 
  • enpraxis.educommons/trunk/enpraxis/educommons/docs/PORTLETS.html

    r520 r566  
    158158<hr class="footer" /> 
    159159<a class="reference external" href="PORTLETS.txt">View document source</a>. 
    160 Generated on: 2009-08-06 16:49 UTC. 
     160Generated on: 2009-08-09 07:41 UTC. 
    161161Generated by <a class="reference external" href="http://docutils.sourceforge.net/">Docutils</a> from <a class="reference external" href="http://docutils.sourceforge.net/rst.html">reStructuredText</a> source. 
    162162 
  • enpraxis.educommons/trunk/enpraxis/educommons/docs/SETUP.html

    r520 r566  
    6060<h1>Site Settings</h1> 
    6161<p>The <em>Site Title</em> and <em>Site Description</em> fields should contain values that were initially set during the installation process. If you want to change these fields, you can do so here. The <em>Site Title</em> field is referred to throughout the site. It is important to remember that eduCommons will only change the portal title on a page when a template is applied. If you change this setting here, it will be necessary to also change it throughout the site, or to reapply templates that refer to it.</p> 
    62 <p>eduCommons provides a number of settings that can be used with your site. The <em>Site 'From&quot; Name</em> and <em>Site 'From' Address</em> are already discussed in the section titled <a class="reference internal" href="#mail-settings">Mail Settings</a>.</p> 
    6362<p><em>JavaScript for web statistics support</em> is an area for enabling web statistics support from external providers (for e.g. Google Analytics). Paste the code snippets provided. It will be included in the rendered HTML as entered near the end of the page.</p> 
    64 <p>The <em>Default Language</em> setting is discussed in the next section.</p> 
    6563</div> 
    6664<div class="section" id="setting-the-default-language-for-your-site"> 
     
    10098<h1>Other Customizations</h1> 
    10199<p>If you have a need for further customizations in your eduCommons site, it is possible to change things at a number of levels. This flexibility comes at a cost. The more a site is customized, the harder it is to upgrade when new versions become available. It is important to consider carefully the cost of additional functionality before you make any decisions on customizations.</p> 
    102 <p>There are other options that are available if you find yourself needing extra functionality. The <a class="reference external" href="http://cosl.usu.edu/trac">development site</a> for eduCommons can be used to check to see if your bug is being or has been fixed, or to see what features have been scheduled for development on the <a class="reference external" href="http://cosl.usu.edu/trac/roadmap">roadmap</a>. There are also <a class="reference external" href="http://cosl.usu.edu/forums">forums</a> where you can post issues and get responses from the development team and/or other eduCommons users.</p> 
     100<p>There are other options that are available if you find yourself needing extra functionality. The <a class="reference external" href="http://educommons.com/dev">development site</a> for eduCommons can be used to check to see if your bug is being or has been fixed, or to see what features have been scheduled for development on the <a class="reference external" href="http://educommons.com/dev/roadmap">roadmap</a>. There are also <a class="reference external" href="http://educommons.com/support-forums">forums</a> where you can post issues and get responses from the development team and/or other eduCommons users.</p> 
    103101<p>eduCommons depends on community support, and participation in the user community/development process is both appreciated and welcome.</p> 
    104 <p>For additional documentation, including updates to these setup instructions, please visit: <a class="reference external" href="http://cosl.usu.edu/projects/educommons/documentation">http://cosl.usu.edu/projects/educommons/documentation</a>, specifically <a class="reference external" href="http://cosl.usu.edu/projects/educommons/documentation/how-to">http://cosl.usu.edu/projects/educommons/documentation/how-to</a></p> 
     102<p>For additional documentation, including updates to these setup instructions, please visit: <a class="reference external" href="http://educommons.com/documentation">http://educommons.com/documentation</a></p> 
    105103</div> 
    106104</div> 
     
    108106<hr class="footer" /> 
    109107<a class="reference external" href="SETUP.txt">View document source</a>. 
    110 Generated on: 2009-08-06 16:49 UTC. 
     108Generated on: 2009-08-09 07:41 UTC. 
    111109Generated by <a class="reference external" href="http://docutils.sourceforge.net/">Docutils</a> from <a class="reference external" href="http://docutils.sourceforge.net/rst.html">reStructuredText</a> source. 
    112110 
  • enpraxis.educommons/trunk/enpraxis/educommons/docs/SeleniumRCTests.html

    r520 r566  
    55<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 
    66<meta name="generator" content="Docutils 0.5: http://docutils.sourceforge.net/" /> 
    7 <title>eduCommons 3.2.1 SeleniumRC Testing</title> 
     7<title>eduCommons 3.2.1-rc2 SeleniumRC Testing</title> 
    88<meta name="author" content="Santiago Suarez Ordoñez &lt;santiycr &#64; gmail..com&gt;" /> 
    99<meta name="copyright" content="This document has been placed in the public domain." /> 
     
    1111</head> 
    1212<body> 
    13 <div class="document" id="educommons-3-2-1-seleniumrc-testing"> 
    14 <h1 class="title">eduCommons 3.2.1 SeleniumRC Testing</h1> 
     13<div class="document" id="educommons-3-2-1-rc2-seleniumrc-testing"> 
     14<h1 class="title">eduCommons 3.2.1-rc2 SeleniumRC Testing</h1> 
    1515<table class="docinfo" frame="void" rules="none"> 
    1616<col class="docinfo-name" /> 
     
    9090Role      Username   Password 
    9191====     =========   ========= 
    92 admin      admin       admin 
     92admin/manager admin  test1234 
    9393producer  producer   producer 
    9494reviewer  reviewer  reviewer 
    95 qa          qa          qa 
     95qa        quality   quality 
    9696publisher publisher publisher 
    97 viewer    viewer   viewer 
     97viewer    viewer    viewer 
    9898=======  =========   ========= 
    9999</pre> 
     
    295295<hr class="footer" /> 
    296296<a class="reference external" href="SeleniumRCTests.txt">View document source</a>. 
    297 Generated on: 2009-08-06 16:49 UTC. 
     297Generated on: 2009-08-09 07:41 UTC. 
    298298Generated by <a class="reference external" href="http://docutils.sourceforge.net/">Docutils</a> from <a class="reference external" href="http://docutils.sourceforge.net/rst.html">reStructuredText</a> source. 
    299299 
  • enpraxis.educommons/trunk/enpraxis/educommons/docs/src/CHANGES.txt

    r8 r566  
     1======================== 
     2Changes in version 3.2.1 
     3======================== 
     4Installers 
     5   Simplified installation have been added, including buildout scripts and Windows installers. 
     6Expanded IMS Import 
     7   eduCommons can now import from IMS Common Cartridge, IMS Content Package, MIT course downloads, Blackboard IMS, WebCT Vista, WebCT 6.1/7.0, and Moodle Backups. 
     8Improved IMS Export 
     9   eduCommons can now export to IMS Common Cartridge, IMS Content Package, and IMS Package for Moodle. 
     10WordPress Import/Export 
     11   Support has been added to import pages from a WordPress site as well as export eduCommons content directly to WordPress pages. 
     12Static Site 
     13   It is now possible to publish an entire eduCommons site to static HTML. 
     14Expanded RSS 
     15   Additional RSS have been added to create an RSS feed of most recent items. 
     16OIA-pmh and Improved Metadata 
     17   Support has been added for additional metadata in rdf/rss views as well as OAI/pmh. 
     18OpenSearch Support 
     19   Support has been added for OpenSearch, including the Firefox OpenSearch widget which allows a search of a specific eduCommons site directly from the browser's search window. 
     20 
    121======================== 
    222Changes in version 3.1.0 
  • enpraxis.educommons/trunk/enpraxis/educommons/docs/src/LOCALIZATION.txt

    r8 r566  
    3737less time consuming because most of the translation work has already been done in Plone. 
    3838 
    39 There are about 400 strings needed for a translation of eduCommons (compared to about 1600 strings  
     39There are about 470 strings needed for a translation of eduCommons (compared to about 1600 strings  
    4040for a Plone translation). Some of these are sentences or paragraphs, but the major part are one or  
    4141two words. These strings are scattered around in Plone, for example in page templates. Other items  
    4242to translate are widget labels, and workflow states. All those strings are collected in master  
    43 files. Currently eduCommons contains six .pot files. Each language requires its own .po files that 
     43files. These are called .pot files. Each language requires its own .po files that 
    4444corresponds to the strings or message ids declared in the .pot files. The .pot is the blueprint for 
    4545the .po files. 
     
    8282    this translation compared to not getting one at all :) 
    8383     
    84     4. Here is a link to the most recent translation files available for eduCommons (plone.po and  
    85     eduCommons.po). Remember, unless there is already an existing translation available, you need  
    86     to grab the .pot files. 
    87   
    88         http://cosl.usu.edu/svndev/eduCommons3/trunk/i18n/ 
    89          
    90         Here are links to the latest translations for each of the eduCommons products on the Plone  
    91         Collective site (these links may change, so check back for the most accurate information):  
    92  
    93         http://svn.plone.org/svn/collective/ZipFileTransport/branches/cosl-plone3/i18n/  
    94  
    95         http://svn.plone.org/svn/collective/IMSTransport/branches/cosl-plone3/i18n/  
    96  
    97         http://svn.plone.org/svn/collective/ContentLicensing/branches/cosl-plone3/i18n/ 
    98  
    99         http://svn.plone.org/svn/collective/PloneBookmarklets/branches/plone3/i18n/ 
     84    4. Each product in eduCommons has .po files located in the locales directory. We have combined 
     85    all these files in a single location of ease of translation. It can be accessed here: 
     86    http://educommons.com/localization/localization-files.zip 
     87    If you wish to translate a language for which we do not currently have translation files,  
     88    please contact us at info [at] educommons [dot] com. 
    10089     
    10190     
     
    139128    ${number} TRANSLATION. 
    140129 
    141     9. Keep translating (but take breaks, this isn't done in one sitting - it's repetetive (but  
     130    9. Keep translating (but take breaks, this isn't done in one sitting - it's repetitive (but  
    142131    rewarding) work. After you have translated all of plone.pot, you should start on eduCommons.pot.  
    143132    Don't worry, you have already completed the biggest part. 
     
    154143    works, you can get an account with Plone (Here's how to request write access to the Collective.) 
    155144    and maintain the files in SVN yourself (see next section). If not, no problem, just e-mail your 
    156     translation to us at eduCommons [at] cosl [dot] usu [dot] edu, and we will add it for you and put it into the 
     145    translation to us at info [at] educommons [dot] com, and we will add it for you and put it into the 
    157146    eduCommons distribution in the next release. We will also add you to our our `eduCommons 
    158     Localization Team page. <./educommons-localization-team>`__ 
     147    Localization Team page, here: http://educommons.com/documentation/how-to/educommons-localization-team 
    159148     
    160149    13. Please check on your translations periodically to keep them updated as new versions are  
    161     released. A quick find for "" will reveal any new or missing stings that need to be translated. 
     150    released. A quick search for "" will reveal any new or missing stings that need to be translated. 
    162151     
    163152    14. If you have other questions or about contributing a translation to eduCommons please contact 
    164     us at educommons [at] cosl [dot] usu [dot] edu. Thank you for you help! 
     153    us at info [at] educommons [dot] com. Thank you for you help! 
    165154 
  • enpraxis.educommons/trunk/enpraxis/educommons/docs/src/SETUP.txt

    r8 r566  
    7878The *Site Title* and *Site Description* fields should contain values that were initially set during the installation process. If you want to change these fields, you can do so here. The *Site Title* field is referred to throughout the site. It is important to remember that eduCommons will only change the portal title on a page when a template is applied. If you change this setting here, it will be necessary to also change it throughout the site, or to reapply templates that refer to it. 
    7979 
    80 eduCommons provides a number of settings that can be used with your site. The *Site 'From" Name* and *Site 'From' Address* are already discussed in the section titled `Mail Settings`_.  
    81  
    8280*JavaScript for web statistics support* is an area for enabling web statistics support from external providers (for e.g. Google Analytics). Paste the code snippets provided. It will be included in the rendered HTML as entered near the end of the page. 
    8381 
    84 The *Default Language* setting is discussed in the next section. 
    8582 
    8683Setting the Default Language for your Site 
     
    141138There are other options that are available if you find yourself needing extra functionality. The `development site`_ for eduCommons can be used to check to see if your bug is being or has been fixed, or to see what features have been scheduled for development on the `roadmap`_. There are also `forums`_ where you can post issues and get responses from the development team and/or other eduCommons users. 
    142139 
    143 .. _development site: http://cosl.usu.edu/trac 
    144 .. _roadmap: http://cosl.usu.edu/trac/roadmap 
    145 .. _forums: http://cosl.usu.edu/forums 
     140.. _development site: http://educommons.com/dev 
     141.. _roadmap: http://educommons.com/dev/roadmap 
     142.. _forums: http://educommons.com/support-forums 
    146143 
    147144eduCommons depends on community support, and participation in the user community/development process is both appreciated and welcome. 
    148145 
    149 For additional documentation, including updates to these setup instructions, please visit: http://cosl.usu.edu/projects/educommons/documentation, specifically http://cosl.usu.edu/projects/educommons/documentation/how-to 
     146For additional documentation, including updates to these setup instructions, please visit: http://educommons.com/documentation 
  • enpraxis.educommons/trunk/enpraxis/educommons/docs/src/SeleniumRCTests.txt

    r8 r566  
    5353 Role      Username   Password   
    5454 ====     =========   ========= 
    55  admin      admin       admin 
     55 admin/manager admin  test1234 
    5656 producer  producer   producer 
    5757 reviewer  reviewer  reviewer 
    58  qa          qa          qa        
     58 qa        quality   quality        
    5959 publisher publisher publisher 
    60  viewer    viewer   viewer   
     60 viewer    viewer    viewer   
    6161 =======  =========   ========= 
    6262 
  • enpraxis.educommons/trunk/enpraxis/educommons/tests/seleniumtests/QA.py

    r512 r566  
    4040        sel = self.selenium 
    4141        sel.open("/eduCommons/logged_out") 
    42         sel.type("__ac_name", "qa") 
    43         sel.type("__ac_password", "asdfasdf") 
     42        sel.type("__ac_name", "quality") 
     43        sel.type("__ac_password", "quality") 
    4444        sel.click("submit") 
    4545        sel.wait_for_page_to_load("30000") 
     
    8080        sel.click("link=Log out") 
    8181        sel.wait_for_page_to_load("30000") 
    82         sel.type("__ac_name", "qa") 
    83         sel.type("__ac_password", "asdfasdf") 
     82        sel.type("__ac_name", "quality") 
     83        sel.type("__ac_password", "quality") 
    8484        sel.click("submit") 
    8585        sel.wait_for_page_to_load("30000") 
     
    9696        sel = self.selenium 
    9797        sel.open("/eduCommons/logged_out") 
    98         sel.type("__ac_name", "qa") 
    99         sel.type("__ac_password", "asdfasdf") 
     98        sel.type("__ac_name", "quality") 
     99        sel.type("__ac_password", "quality") 
    100100        sel.click("submit") 
    101101        sel.wait_for_page_to_load("30000") 
  • enpraxis.educommons/trunk/enpraxis/educommons/tests/seleniumtests/__init__.py

    r557 r566  
    11#import addNewSite 
    2 #import addNewUsersAll 
     2import addNewUsersAll 
    33import accountsLogin 
    44import createDivision 
  • enpraxis.educommons/trunk/enpraxis/educommons/tests/seleniumtests/accountsLogin.py

    r512 r566  
    3333    def test_admin_account(self): 
    3434        sel = self.selenium 
    35         sel.login("admin","admin") 
     35        sel.login("admin","test1234") 
    3636        self.failUnless(sel.is_element_present('//a[@id="user-name"]/span[text()="admin"]')) 
    3737        self.assertEqual("admin (Administrator)",sel.get_text('//li[a[@id="user-name"]]')) 
  • enpraxis.educommons/trunk/enpraxis/educommons/tests/seleniumtests/addNewUsersAll.py

    r512 r566  
    8787        sel.wait_for_page_to_load("30000") 
    8888        sel.type("fullname", "john doe") 
    89         sel.type("username", "qa") 
     89        sel.type("username", "quality") 
    9090        sel.type("email", "test@test.com") 
    9191        sel.type("password", "asdfasdf") 
Note: See TracChangeset for help on using the changeset viewer.