<?xml version="1.0" encoding="utf-8" standalone="no"?>
<!DOCTYPE document PUBLIC "-//CNX//DTD CNXML 0.5//EN" "http://cnx.rice.edu/cnxml/0.5/DTD/cnxml_mathml.dtd">
<document xmlns="http://cnx.rice.edu/cnxml" xmlns:md="http://cnx.rice.edu/mdml/0.4" xmlns:bib="http://bibtexml.sf.net/" id="m10887">
  <name>Editing Modules</name>
  <metadata>
  <md:version>2.25</md:version>
  <md:created>2002/10/07</md:created>
  <md:revised>2006/04/28 14:15:48.063 GMT-5</md:revised>
  <md:authorlist>
      <md:author id="mhusband">
      <md:firstname>Mark</md:firstname>
      <md:othername>S.</md:othername>
      <md:surname>Husband</md:surname>
      <md:email>mhusband@rice.edu</md:email>
    </md:author>
      <md:author id="jago">
      <md:firstname>Adan</md:firstname>
      
      <md:surname>Galvan</md:surname>
      <md:email>jago@rice.edu</md:email>
    </md:author>
  </md:authorlist>

  <md:maintainerlist>
    <md:maintainer id="mhusband">
      <md:firstname>Mark</md:firstname>
      <md:othername>S.</md:othername>
      <md:surname>Husband</md:surname>
      <md:email>mhusband@rice.edu</md:email>
    </md:maintainer>
    <md:maintainer id="jago">
      <md:firstname>Adan</md:firstname>
      
      <md:surname>Galvan</md:surname>
      <md:email>jago@rice.edu</md:email>
    </md:maintainer>
  </md:maintainerlist>
  
  <md:keywordlist>
    <md:keyword>content</md:keyword>
    <md:keyword>editing</md:keyword>
    <md:keyword>metadata</md:keyword>
    <md:keyword>modules</md:keyword>
    <md:keyword>role</md:keyword>
  </md:keywordlist>

  <md:abstract>This module shows how to edit the contents of a module. This includes the text, files, and metadata of a module.</md:abstract>
</metadata>
  <content>

    <section id="modulesummary">
      <name>What is a Module?</name>
      
      <para id="modulessummarypara">
	A module is the basic building block of a Connexions course. You can 
	think of it as a folder that contains the text, image, and CNXML files that 
	address a single topic or a specific aspect of a topic. The author of a 
	module determines the size of the module. Each module should contain enough 
	information to be able to stand alone, if necessary. To a student viewing 
	a course, a module is simply a web page of information on a specific topic. 
	Modules allow students to follow the information path in a course arranged 
	by their instructor or to branch off and discover their own path. To an 
	instructor putting a course together, having different topics in different 
	modules allows for easy selection and arrangement of the information. When 
	building a course, an instructor can include existing modules from other 
	courses or other academic disciplines that are important to the presentation 
	of the course subject.
      </para>

      	
      <para id="interfacemodules">
        An example of the contents of a new module are shown in <cnxn target="modulefiles"/>, 
        which displays the "Files" tab of the "Manage Files" screen.
      </para>

	<figure id="modulefiles"><media type="image/png" src="modulesfilesx.png"/>
	<caption>"Files" tab of a new module that contains only the index.cnxml file.</caption>
	    </figure>
    </section>


    <section id="statussec">
      <name>The Module Status Sidebar</name>
        <para id="statuspara">
       	    The  <cnxn target="statasboxfig">"Module Status"</cnxn> sidebar contains 
       	    important status information about the module and several links to useful 
       	    tasks for the module editor. This sidebar appears to the right of the 
       	    module contents and contains the following items:
	    <list id="statuslist">
	      <item><cnxn document="m10885" target="contentstatuslist">State</cnxn> - 
	      the current status of the module</item> 
	      <item>Last action - the last action performed on the module, 
	      who performed it, and when</item>		
	      <item>Actions - for new modules this item displays links to the Connexions 
	      pages for <cnxn target="submitmodule">publishing</cnxn> modules to the 
	      Content Commons and <cnxn target="discardmodule">discarding</cnxn> the 
	      current operations on the module. When editing an existing module, this 
	      item also displays links for <cnxn document="m11817">suggesting edits</cnxn> 
	      to original authors and creating a <cnxn document="m11804">derived copy</cnxn> 
	      of an existing module, </item>
	      <item>View - for new modules this item displays links to display the 
	      <cnxn target="onlinepreview">on-line</cnxn> version of the module, the 
	      <cnxn target="previewprint">print</cnxn> version, and the 
	      <cnxn target="onlinecodesource">CNXML source</cnxn>. When editing an 
	      existing module, this item also displays a summary of the 
	      <cnxn target="viewchanges">differences</cnxn> between the version 
	      of the module in your work area and the last published version</item>
	    </list>
         </para>
	  <figure id="statasboxfig">
	    <media type="image/png" src="statusboxnewmodule.png"/>
	    <caption>The "Module Status" sidebar for a new module.</caption>
	  </figure>
    </section>
      

    <section id="modules">
      <name>Editing Modules</name>
      <para id="editmodulespara1">
	Once you have <cnxn document="m10885" target="creatingmodules">created</cnxn> 
	a new module in or <cnxn document="m10885" target="addingexistingmodules">added</cnxn> 
	an existing module to your work area, you will need to edit the module to 
	add content, files, and images. These operations are performed with the links 
	and buttons on the "Manage Files" screen or the "Module Status" sidebar. The 
	recommended sequence to perform these operations in is described in this module 
	and appears in the following list:
      
	    <list id="sequecncelist" type="enumerated">
	      <item>Edit the <cnxn target="edittext">CNXML</cnxn> file.</item>
	      <item><cnxn target="createfileimage">Add</cnxn> any other files that you 
	      want to associate with the module.</item>
	      <item>Edit the <cnxn target="editmetadata">metadata</cnxn> to enter the 
	      appropriate search keywords and the module title.</item>
	      <item>Edit the module <cnxn target="editroles">roles</cnxn>.</item>
	      <item>Add <cnxn target="editlinks">links</cnxn> to the module.</item>
	      <item><cnxn target="previewmodule">Preview</cnxn> the module in both print 
	      and on-line versions.</item>
	      <item><cnxn target="submitmodule">Publish</cnxn> the module.</item>
	    </list>
	    
	    Each of these operations of module editing will be discussed in the 
	    following paragraphs.
      </para>
    </section>


    <section id="edittext">
      <name>Editing the CNXML File</name>
	<para id="edittextpara">
	    The "Edit" tab for the module displays the contents of the "index.cnxml" 
            file. This file contains the text that appears in the module, plus the 
            CNXML instructions to include any image, sound, or other media files 
            that appear in the module. The default content display and edit is with 
            the Edit-In-Place editor. Alternatively, you can display and edit the 
            content with the Full Source editor by clicking <code>Switch to Editing 
            Full Source</code>. From this tab you can perform the following actions 
            on the file:

	    <list id="editoptions">
	      <item><cnxn target="importsec" strength="9">Import content
              into the index.cnxml file</cnxn></item>
	      <item><cnxn target="exportsec" strength="9">Export the index.cnxml
              file to an external XML editor</cnxn></item>
	      <item><cnxn target="editinplacesec" strength="9">Edit the index.cnxml
              file with the Edit-In-Place editor</cnxn></item>
	      <item><cnxn target="editfullsrcsec" strength="9">Edit the index.cnxml
              file with the Full Source editor</cnxn></item>
              <item><cnxn target="exteditsec" strength="9">Edit the index.cnxml 
              file with an External Text Editor</cnxn></item>
            </list>

	</para>
	  
	  <figure id="editmodule"><media type="image/png" src="EditTabEIPx.png"/>
	    <caption>The "Edit" tab displaying contents of the "index.cnxml" file 
	    in the Edit-In-Place editor mode.</caption>
	  </figure>


    <section id="importsec">
      <name>Import Content into the "index.cnxml" File</name>
        <para id="importcontentpara1">
	    To import content into the "index.cnxml" file, use the following steps:

	  <list id="importlist1" type="enumerated">
	    <item>Select the format of file you want to import from the drop-down
	    list next to the <code>Import</code> button. The valid formats are:
	    <link src="http://cnx.rice.edu/help/UsingMSWord">Microsoft Word</link>, 
	    OpenOffice Writer, <cnxn document="m11160">XMLSpy/Authentic</cnxn>, 
	    and Plain XML.</item>
	    <item>Click <code>Import</code>. A screen displays with a text box
	    for the pathname of the file you want to import.</item>
	    <item>Type the pathname of the file in the text box or use 
	    <code>Browse</code> to display the name of the pathname in the text 
	    box.</item>
	    <item>Click <code>Import</code>. The content of the file you
	    specified is copied into the "index.cnxml" file in your module.
	    <note type="warning">When you click <code>Import</code> in the last 
	    step, the contents of the "index.cnxml" file are overwritten 
	    by the contents of the imported file.</note></item>
	  </list>
	</para>
      </section>	
	

    <section id="exportsec">	
      <name>Export the "index.cnxml" File to an External XML Editor</name>
        <para id="exportpara1">
	    You can export the "index.cnxml" file so that you can edit it with a 
	    software package that is specifically designed to edit XML files.
	    The "index.cnxml" file must be altered to allow the XML editor to read 
	    it. And once you have completed your edits, the file must be altered again 
	    to remove the changes for editor readability. The Connexions Export and 
	    Import functions automatically add and remove the changes for editor 
	    readability. Currently, the only XML editor format supported by 
	    Connexions is the format used by the 
	    <link src="http://www.altova.com">Altova</link> <term>xmlspy</term>® 
	    editor or the Altova <term>authentic</term>® editor.
        </para>

        <para id="exportpara2">
	    To export the "index.cnxml" file to be edited with an XML editor, 
	    use the following steps:
	    
	  <list id="importexportlist1" type="enumerated">
	    <item>Select the format of the file you want to export from the 
	    drop-down list next to the <code>Export</code> button. The valid formats
	    are: <cnxn document="m11160">XMLSpy/Authentic</cnxn>, and Plain XML.
	    </item>
	    <item>Click <code>Export</code>. A dialog box displays asking if you
	    want to open the file or save it to a disk.</item>
	    <item>Specify that you want to save the file to a disk.</item>
	    <item>Specify the pathname of where you want to save the file.</item>
	    <item>Launch your XML editor and edit the file.</item>
	  </list>
	</para>
	    
        <para id="exportpara3">
	    To import the "index.cnxml" file back into Connexions, use the 
	    instructions for <cnxn target="importsec">Import Content from Outside 
	    Connexions</cnxn> mentioned earlier in this module.
        </para>
    </section>


    <section id="editinplacesec">
      <name>Edit the index.cnxml file with the Edit-In-Place Editor</name>
	<para id="eippara1">
	   The Edit-In-Place editor is the default editor on the "Edit" tab. 
	   You can insert new text and media objects into a module or modify 
	   the existing contents of a module with this editor. You do not 
	   have to be familiar with the CMXML tags to use Edit-In-Place. It 
           inserts the appropriate CNXML tags for you when you insert a new
           item in the file. In addition, it has a help text feature that 
           describes the CNXML tags for the items you insert or edit with it. 
          
	 </para>
	 
     <section id="eipnewmodulesec">
       <name>Inserting Content in an Empty Module</name>
	 <para id="eippara2">
	   To insert text and media objects into a new module that contains
	   no content, use the following steps:
	   
	   <list id="eiplist1" type="enumerated">
	     <item>Click in the gray box that says "Click To Insert Text" 
	     in the Edit-In-Place editor. 
	  <figure id="eipnewmodulefig">
	    <media type="image/png" src="EIPnewmodule.png"/>
	    <caption>The "Click To Insert Text" text box in the 
	    Edit-In-Place editor.</caption>
	  </figure>
	      The gray box is replaced by a blue editing box.</item>
	     <item>Type the text you want to add in the blue editing box that 
	     says "Insert Module Text Here".	     
	  <figure id="eipinsertmodulefig">
	    <media type="image/png" src="EIPinsertmoduletext.png"/>
	    <caption>The "Insert Module Text Here" editing box in the 
	    Edit-In-Place editor.</caption>
	  </figure>
	     </item>
	     <item>Click <code>Save</code> to save the text you typed. 
	     The blue editing box is replaced by a gray box that displays 
	     your entry.</item>
	   </list>  
	 </para>
       </section>
       
       
       <section id="eipeditmodulesec">
         <name>Editing Existing Content with Edit-In-Place</name>
	   <para id="eipeditpara1">
	     To edit the content of a module, use the following steps:
	     
	     <list id="eiplist2" type="enumerated">
	       <item>Display the module you want to edit with Edit-In-Place.
	       </item>
	       <item>Scroll down to display the gray text box that contains 
	       the item you want to edit.</item>
               <item>Click in the text box. The gray box is replaced by a 
	       blue editing box that displays the text of the item.	       
	     <figure id="eipeditmodulefig">
	       <media type="image/png" src="EIPeditcontent.png"/>
	       <caption>The blue text box in the Edit-In-Place editor.</caption>
	     </figure>
               </item>
	       <item>Make the necessary changes to the item.</item>
	       <item>Click <code>Save</code> to save the entry or click 
	       <code>Cancel</code> to clear the entry in the blue editing 
	       box.</item>
               <item>Repeat steps 2 through 5 for any item you want to edit.
               </item>	       	  
	     </list>  	 
	     <note>In the gray text boxes mathematical equations are 
	     displayed as they appear in the module. In the blue editing box 
	     mathematical equations are displayed in the MathML markup language. 
	     Edit equations by making changes to the MathML.</note>
	   </para>  
       </section>
	       
	     
       <section id="eipadditemsec">
         <name>Adding Content Items with Edit-In-Place</name>
	   <para id="eipadditempara1">
	     You can add new content items to a module with Edit-In-Place.
	     The types of items you can add are: paragraphs, enumerated lists,
	     bulleted lists, equations, exercises, figures, code blocks, notes,
	     and examples. Edit-In-Place places the opening and closing CNXML 
	     tags around the item and it generates a unique item ID for each 
	     item you add. To add new items, use the following steps:
	     
	     <list id="eipadditemlist" type="enumerated">
	       <item>Display the module you want to edit with Edit-In-Place.
	       </item>
	       <item>Scroll down to display the location in the module in
	       which you want to insert the content item. You can insert 
	       the new item above or below and existing item by using the
	       <code>Add Here</code> button above or below the existing item
	       </item>
	       <item>Select the type of item you want to enter from the 
	       drop-down list next to the <code>Add Here</code> button. 
	       The default is "Paragraph". These items are described in the 
	       help text, which can be accessed by selecting "Other Elements" 
	       from the drop-down list.</item> 
	       <item>Click <code>Add Here</code>. An empty blue editing box 
               displays for the item you selected. You can display help text 
               for the item you selected by clicking <code>Help editing xxx</code> 
	       in the upper right corner of the blue box, where xxx is the
               CNXML tag for the item you selected.</item>
	       <item>Type the text that is appropriate for the type of item 
	       in the blue editing box.</item> 
	       <item>Click <code>Save</code> to save the entry or click 
	       <code>Cancel</code> to clear the entry in the blue editing box.</item>
	       <item>Repeat steps 2 through 6 for each new content item 
	       you want to add to the module.</item>
	     </list>
	   </para>
   </section>
   </section>


   <section id="editfullsrcsec">
      <name>Edit the "index.cnxml" File with the Full Source Editor</name>
	<para id="editonlinepara">
	    You can edit the content and CNXML tags in the "index.cnxml" file 
	    within Connexions with the Full Source editor. This method of editing 
	    is recommended for quick changes only. This is a simple text editor 
	    and it does not have the advanced functions (for example, spell 
	    checking and text searching) that are available with commercially
	    available text editors. To edit the file with the Full Source 
	    editor, use the following steps:
	    
	  <list id="editingonlinelist" type="enumerated">
	    <item>Click <code>Switch to Editing Full Source</code> on the "Edit" 
	    tab. The contents of the "index.cnxml" file are displayed in the 
	    Full Source editor mode. 	    
	  <figure id="fullsourceeditmode"><media type="image/png" src="FullSourceEditorx.png"/>
	    <caption>The "Edit" tab displaying the contents of the "index.cnxml"
	    file in the Full Source editor mode.</caption>
	  </figure>
	    </item>
            <item>Scroll down to display the location in the module in
	       which you want to edit.</item>
	    <item>Click in the text window and begin editing.</item>
	    <item>Click <code>Save</code> to save to save your changes.</item>
	  </list>
	</para>
	
	
        <para id="modules11">
	    As you edit the "index.cnxml" file, click <code>Save</code> at any 
	    point to save your changes. The page reloads and validates your CNXML
	    markups every time you save your changes. If there are no CNXML tag 
	    errors, your markup is valid and "Saved" appears in an information box 
	    at the top of the tab. If there are errors in your CNXML markup, they 
	    are listed above the file content.  
        </para>
        
        <note>Saving and publishing are two different operations. When you save
        your editing changes in the Full Source editor, your changes are saved 
        in your work area; they are not entered into the Connexions repository. 
        Your module must be published to be entered into the repository and be 
        accessible by visitors to Connexions. For information about publishing, 
        see the topic <cnxn target="submitmodule">Publishing the Module</cnxn> 
        later in this module.</note> 


    <section id="validatesec1">
      <name>Validating Your Work in the Full Source Editor</name>
            <para id="validatepara1">
	      Any "index.cnxml" file that you publish in the Connexions repository 
	      must be a valid CNXML document. This means that the file must be 
	      well formed and contain no CNXML errors. If it does contain errors, 
	      a <cnxn target="validatefig">description of each error</cnxn> 
	      appears when you click <code>Save</code>. Your changes are not 
	      saved until the errors are corrected. 

	</para>
	    <figure id="validatefig"><media type="image/png" src="validateerrorx.png"/>
	      <caption>Example of validation errors in the Full Source editor</caption>
	    </figure>
	    
	<para id="validatepara2">
	      A description of the errors appears in the information box that 
	      appears above the content.
	    <note type="warning">
	      You cannot publish the module in Connexions until all the CNXML errors 
	      are corrected and the "index.cnxml" file is validated.
	    </note>
	</para>    
	  
    </section>
    </section>
    
    
    <section id="exteditsec">
      <name>Edit the index.cnxml File with an External Text Editor</name>
	<para id="externalpara">
	    Another method of editing the "index.cnxml" file is with an external
	    text editor that is not specifically designed to be an XML editor.
	    Note that when you view the module on the "Files" tab a small pencil 
	    icon appears to the right of the "index.cnxml" filename. Click on 
	    this icon to launch an editing session of the "index.cnxml" file in 
	    an external text editor. This editing method does the downloading and 
	    uploading of the "index.cnxml" file for you, but it is only a text 
	    editor. You must manually enter all the CNXML tags. If you are not 
	    familiar with CNXML, this method is slow and awkward. It also 
	    requires that you or your system administrator set up the external 
	    editor as the default editor for files of type <term>.cnxml</term> 
	    before you can use it. In addition, you or your system administrator 
	    must install the Zope ExternalEditor client in a Windows environment 
	    and the Zope EditManager in a Macintosh environment. 
	</para>
    </section>
    </section>


    <section id="createfileimage">
      <name>Adding Associated Files to a Module</name>
	<para id="createfilepasra">
	    In addition to the "index.cnxml" file, a module can contain other files, 
	    such as images, files, and CNXML documents that are associated with the 
	    module. You can add these files from the "Files" tab. The image and file
	    must exist before you add them to the module. You can create the CNXML 
	    document during the addition process. When you add these items, you 
	    create an instance of the item in Connexions. 
	</para>
	
    <section id="filenamerestrictions">
      <name>File Guidelines</name>
        <para id="filenamepara1">
            Before you add an associated file to a module, please note the 
            following guidelines for files and filenames: 
            <list id="filenamelist1"><item>The size of a file must be smaller than 10 MB.</item>
              <item>The first character in a filename cannot be a digit. For
              example, a file named "1965mustangphoto.gif" would result in an 
              error. <cnxn document="m10885" target="renamingfilesec">Renaming</cnxn> 
              the file to "photo1965mustang.gif" prevents the error.</item>
              <item>A filename cannot contain an embedded blank space. For 
              example, the file named "eiffel tower.png" would cause an error. 
              <cnxn document="m10885" target="renamingfilesec">Renaming</cnxn> the 
              file to "eiffel_tower.png" or "eiffeltower.png" prevents the error.</item>
              <item>Use only alphanumeric, "." (dot), "-" (hyphen), and "_" 
              (underscore) characters in a filename. </item>
              <item><cnxn document="m12660">Multimedia files</cnxn> must have a 
              recognized MIME (Multipurpose Internet Mail Extension) type.</item>
            </list>  
        </para>
    </section>
    
    <section id="createfileimage2">
      <name>Adding an Image to a Module</name>	
      <para id="addimagepara1">
	    To add an image to a module, use the following steps:
	    
	    <list type="enumerated" id="addimagelist1">
	      <item>Click the down arrow in the text box next to <code>Add New 
	      Item</code>. A drop-down list of valid item types appears.</item>
	      <item>Select "Image" from the drop-down list and click <code>Add 
	      New Item</code>. The "Edit Image" tab displays.</item>
	      <item>Click <code>Browse</code>. The "File Upload" dialog box displays.
	      </item>
	      <item>Locate the appropriate image file and click on its filename.
	      </item>
	      <item>Click <code>Open</code>. The image filename appears in the 
	      text box next to <code>Browse</code>.</item>
	      <item>Click <code>Save</code> to upload the image file into 
	      Connexions. A confirmation message and a preview of the image 
	      display.</item>
	    </list>
	</para>  
    </section>


    <section id="createfileimage3">
      <name>Adding a File to a Module</name>	
	<para id="addfilepara1">
	    To add a file to a module, use the following steps:
	    
	    <list type="enumerated" id="addfilelist1">
	      <item>Click the down arrow in the text box next to <code>Add New 
	      Item</code>. A drop-down list of valid item types appears.</item>
	      <item>Select "File" from the drop-down list and click <code>Add 
	      New Item</code>. The "Edit File" tab displays.</item>
	      <item>Click <code>Browse</code>. The "File Upload" dialog box displays.
	      </item>
	      <item>Locate the appropriate file and click on its filename.</item>
	      <item>Click <code>Open</code>. The filename appears in the text box 
	      next to <code>Browse</code>.</item>
	      <item>Click <code>Save</code> to upload the file into Connexions. 
	      A confirmation message and information about the file display.
	      </item>
	    </list>
	</para>
    </section>


    <section id="createfileimage4">
      <name>Adding a CNXML Document to a Module</name>	
	<para id="addcnxmldocpara1">
	    To add a CNXML document to a module, use the following steps:
	    
	    <list type="enumerated" id="addcnxmldoclist1">
	      <item>Click the down arrow in the text box next to <code>Add New 
	      Item</code>. A drop-down list of valid item types appears.</item>
	      <item>Select "CNXML Document" from the drop-down list and click 
	      <code>Add New Item</code>. The "Edit CNXML File" tab displays.</item>
	      <item>Enter the contents for the CNXML file by either typing the 
	      text into the "Edit Directly" box, uploading a file, or importing a 
	      file.</item>
	      <item>Click <code>Save</code>. A confirmation message and information 
	      about the CNXML file display.</item>
	    </list>
	  </para>
    </section>


    <section id="createfileimage5">
      <name>Renaming, Cutting, Copying, and Removing Items in a Module</name>	
        <para id="addcnxmldocpara2">
	  You can rename, cut, copy, or remove any item that you add to a 
	  module. These operations are done at the module level in the same 
	  way as they are done at the work area level. See <cnxn document="m10885" target="removingfiles">Removing Items from a Work Area</cnxn>, 
	  <cnxn document="m10885" target="renamingfilesec">Renaming Items in 
	  a Work Area</cnxn>, and <cnxn document="m10885" target="cuttingcoying">
          Cutting or Copying Items in a Work Area</cnxn>, for a description of 
          how to do these operations in work areas.
	  </para>
	  <note type="note">
	  You should not rename, cut, copy, or paste the "index.cnxml" file.
	  </note>
    </section>
  </section>


    <section id="editmetadata">
      <name>Editing Metadata</name>
        <para id="editmetadatapara">
	    To enable users to search the Connexions Content Commons for a module, 
	    Connexions must have some information on the module. It is <emphasis>very 
	    important</emphasis> that you insert <cnxn target="metadatafig">metadata</cnxn> 
	    into the module. 
        </para>
        
          <figure id="metadatafig"><media type="image/png" src="MetadataTab180.png"/>
	    <caption>Example "Metadata" tab with entries for name, keywords, and abstract.
	    </caption>
	  </figure>
	  
        <para id="metadatapara2">
            To insert metadata, use the following steps:
            
          <list id="metadatalist1" type="enumerated">
            <item>Click the "Metadata" tab to display it.</item>
            <item>Type the name you want to give the module in the "Name" field. 
            This name will appear wherever the module title appears in Connexions.
            </item>
            <item>Type the topic related terms that a user may use in a search 
            for the module in the "Keywords" field. Enter each term on a separate
            line.</item>
            <item>Type a brief description of the module topic in the "Abstract" 
            field. Do not repeat the title of the module in the abstract. The 
            abstract displays under the title in the module and restating the 
            module title in the abstract would be redundant.</item>
            <item>Click <code>Save</code>. A message that the metadata was updated
            displays and the name of the module replaces "New Module" in the screen 
            title.</item>
	    </list>
        </para>
    </section>


    <section id="editroles">
      <name>Editing Module Roles</name>
        <para id="rolespara">As creator of a module, by default you hold all three 
	    <link src="http://cnx.rice.edu/help/reference/roles/document_view">roles</link>: author, maintainer, and copyright holder.
<list id="rolelist1" type="bulleted"><item><term>Authors</term> receive credit for writing the material. The author is the person who is responsible for the creation of the work, but may or may not be the person who actually enters the work into the Connexions. Any module work must have at least one person with an author role before it can be published in Connexions.</item>
<item><term>Maintainers</term> are able to edit and publish successive versions of a module. Most authors will serve as maintainers for their materials, but some may choose not to. Authors may appoint additional maintainers to assist them in updating the materials. </item>
<item><term>Copyright Holders</term> have the legal right to license the materials. In most cases, the copyright holder is the same person as the author, but this may not be the case in institutions where faculty and employees are required to sign over copyright to the institution. In this case the institution serves as copyright holder and the individual retains the author and/or maintainer roles.</item>
</list>
You can grant one or more roles to other Connexions account holders who you want to collaborate with you on the module. The "Roles" tab has a search feature for locating these people. The current collaborators on the module are listed by role under the heading "Current Roles" on the <cnxn target="rolesfig">"Roles"</cnxn> tab. You can change the roles assigned to these people by selecting or deselecting the check boxes in the "Authors", "Maintainers", or "Copyright Holders" columns under the heading "Change Roles". The following paragraphs describe how to grant or update roles.</para>

	  <figure id="rolesfig"><media type="image/png" src="RoleTab180.png"/>
	    <caption>Example "Roles" tab.</caption>
	  </figure>


    <para id="element-856">When you grant or update roles for a collaborator in a module in a workgroup, these changes do not take affect until that person accepts the role change and you publish the module. The prospective collaborator must accept the role because Connexions provides its account holders with the ability to accept or reject a role in another person's module. If there are any pending roles (roles not yet accepted or rejected) for a module, Connexions will not let you publish that module. Once the collaborator accepts the role or updated role, you must publish the module for Connexions to recognize the collaborator. Connexions looks to the information in a published module to see who is an author, maintainer, or copyright holder for the module.  
<note type="note">All pending role additions or changes must be accepted or rejected by the prospective authors, maintainers, and copyright holders before you can publish a module in Connexions. And you must publish a module with the new roles before Connexions will recognize the new roles.</note></para>

<section id="editroles2">
<name>Granting Roles to Someone Outside of Your Workgroup</name>
<para id="addingroles"><name/>
To grant one or more <link src="http://cnx.rice.edu/help/reference/roles/document_view">roles</link> in a module to a Connexions account holder outside of the current workgroup, use the following steps:	    <list id="editroleslist1" type="enumerated"><item>Click the "Roles" tab to display it.</item>
	     <item>Type the first or last name of the person you want to grant a role to in the text
	     box next to <code>Search</code>.</item>
	     <item>Click <code>Search</code>. The Connexions accounts are searched 
	     and any Connexions accounts that match the search string are displayed.</item>
	     <item>Select the check boxes for the appropriate roles next to the name of the person you want to add and click <code>Add People</code>. The name of the new collaborator appears with the names of authors, maintainers, and copyright holders under the "Current Roles" heading and in the table under the "Change Roles" heading. In both places, the new collaborator is noted as a role change that is pending acceptance.</item>  
	     <item>Look at the table under the "Change Roles" heading and verify that the check boxes in the "Author", "Maintainer", or "Copyright Holder" columns are checked for the roles you want to grant to the new collaborator. If necessary, you can click the check boxes to change which roles will be granted.</item>
	     <item>Click <code>Submit Changes</code>. The next time the new collaborator logs into Connexions, he or she will be notified of a pending role request. Connexions will not apply the roles to the new collaborator until he or she accepts the role request.</item>
	  </list>
	</para>
</section>

<section id="workgrproles1">
<name>Granting Roles to a Member of Your Workgroup</name>
<para id="element-78">To grant one or more 
	    <link src="http://cnx.rice.edu/help/reference/roles/document_view">roles</link> in a module to a member of your current workgroup, use the following steps:
	    
	   <list id="workgrouplist1" type="enumerated"><item>Click the "Roles" tab to display it.</item>
	     <item>Click the "Select from members of your current workgroup" link. A table that lists all the members of the current workgroup appears under the link.</item>
	     <item>Locate the name of the person or persons in the table that you want to grant roles to and click the check boxes in the Authors, Maintainers, and Copyright Holders columns to select the roles for that person.</item>
	     <item>Click <code>Add People</code>. The name of the newly added collaborator appears with the names of authors, maintainers, and copyright holders under the "Current Roles" heading and in the table under the "Change Roles" heading. In both places, the new collaborator is noted as a role change that is pending acceptance. </item>  
	  </list>
A notification of a pending role request will display to the collaborator upon his or her next login to Connexions. Connexions will not apply the roles to the new collaborator until he or she accepts the role request.</para>
</section>

<section id="changeroleorder1">
<name>Changing the Order of Appearance for Author Names</name>
<para id="element-77">To change the order in which the authors' names will appear on the module, use the following steps:
	    
<list id="authororderlist1" type="enumerated"><item>Click the "Roles" tab to display it.</item>
<item>Verify that all users who should have an author role on the module are listed in the "Change Roles" table. Select or deselect the check boxes in the "Adjust Roles" columns to make any necessary additions or changes to the module roles.</item>
<item>Click <code>Submit Changes</code> to save the role changes. The next step will erase any role changes that you have not saved with the <code>Submit Changes</code> button.</item> 
<item>Click the up or down arrows in the "Order" column to move an author up or down in the order of appearance in the module. The single arrows move the name up or down one place. The double arrows move the name to the top or bottom of the list.</item>
</list>
To have an author's name appear first in the module, his or her name must be at the top of the "Change Roles" table. The second name from the top of the table will appear as the second name in the list of authors, and so on.</para>
</section>

<section id="changeroles1">
<name>Changing Role Assignments</name>
<para id="element-417">To change the <link src="http://cnx.rice.edu/help/reference/roles/document_view">roles</link> in a module that were previously granted to a user, use the following steps:
<list id="changerolelist1" type="enumerated"><item>Click the "Roles" tab to display it.</item>
<item>Locate the name of the person or persons in the "Change Roles" table of which you want to change roles.</item>
<item>Click on a check box that contains a check mark to remove the check mark and to remove that role from the person. Click on an empty check box to make a check mark appear and to grant that role to the person.</item>
<item>Click <code>Submit Changes</code>. The "Change Roles" table is updated to show the role changes and to note the role changes that are pending acceptance.</item>
</list>
A notification of a pending role change request will display to the collaborator upon his or her next login to Connexions. Connexions will not apply the roles to the new collaborator until he or she accepts the role request.</para>	
</section>

    <section id="removerole1">
      <name>Removing a Collaborator</name>
<para id="removepara1">To remove a collaborator from a module, use the following steps:

<list id="removerolelist1" type="enumerated"><item>Click the "Roles" tab to display it.</item>
<item>Locate the name of the person or persons in the "Change Roles" table of which you want to remove.</item>
<item>Click on the check box in the "Remove User" column for the collaborator you want to remove.</item>
<item>Click <code>Submit Changes</code>. The "Change Roles" table is updated with the removed collaborator not appearing on the list of users with roles.</item>
</list>
A notification of a pending role request will display to the collaborator upon his or her next login to Connexions. Connexions will not remove the collaborator until he or she accepts the role removal request.</para>
</section>
</section>

    <section id="pending">
      <name>Viewing and Processing Pending Role Requests</name>
	
	<para id="pendingpara">
	  Connexions makes it easy to collaborate on educational materials. One way 
	  to do this is to share authorship or maintenance of a module or course.  
	  If another author has granted you a role in their module or course so that 
	  you can collaborate with them, the <cnxn target="collabbox">"Pending"</cnxn> 
	  sidebar will appear in the upper right corner of your Connexions pages.
	</para>

	<figure id="collabbox">
	  <media type="image/png" src="collaborationbox.png"/>
	  <caption>"Pending" sidebar with one role request.</caption>
	</figure>
	
	<para id="pendingpara2">Click the <emphasis>Role Request</emphasis> link to display the 
	  <cnxn target="collab2">"Collaboration Requests"</cnxn> screen. From this 
	  screen you can view and act upon: 
	  
	  <list id="things">
	    <item><cnxn target="requestsawaitingsect">Requests awaiting your approval</cnxn></item>
	    <item><cnxn target="requestsyouhavemadesect">Requests you have made awaiting others' acceptance</cnxn></item>
	    <item><cnxn target="requestscompletedsect">Completed requests</cnxn></item>
	  </list>
	</para>

	<figure id="collab2"><media type="image/png" src="collabrequests180.png"/>
	  <caption>"Collaboration Requests" screen showing one request awaiting 
	  your approval and one awaiting another author's approval.</caption>
	</figure>

	
      <section id="requestsawaitingsect">
	<name>Requests Awaiting Your Approval</name>

	<para id="requestsawaiting">If another Connexions author grants you a role on their module or course
	  as an author, maintainer, and/or copyright holder, an entry appears under 
	  the 'Requests Awaiting Your Approval' section of the "Collaboration Requests" 
	  screen. To accept the request select the check box in the table for the 
	  request you wish to accept and click <code>Accept</code>.
	</para>
	
	<para id="requestawaiting2">To reject the request, select the check box in the table for the request 
	  you wish to reject, and click <code>Reject</code>.
	  
	<note type="note">
	  If you have been requested to be added to a module or course as a copyright 
	  holder, you must select the check box indicating that you agree to the 
	  license which has been selected for that module before you can accept the
	  request. A link to the license is provided in the "License" column of the 
	  table.
	</note>
	</para>
      </section>


      <section id="requestsyouhavemadesect">	
        <name>Requests You Have Made</name>

	<para id="requestsyouhavemade">
	  If you have requested that someone be added to one of your modules 
	  or courses as an author, maintainer, and/or copyright holder, an 
	  entry appears under the "Requests You Have Made" section of the 
	  "Collaboration Requests" screen until the other author acts on it. 
	  You can cancel pending requests from here.
	</para>
       </section>	
       
	
       <section id="requestscompletedsect">
	 <name>Completed Requests</name>

	 <para id="requestscompleted">
	   Any requests you have made that were accepted or rejected are 
	   listed in the "Requests You Have Made -- Completed" section of 
	   the "Collaboration Requests" screen. When you no longer need 
	   to keep the record, you can delete it.
	</para>
	
      </section>
    </section>

 	
    <section id="editlinks">
      <name>Adding Links to a Module</name>
        <para id="editlinkspara">
	  To add or edit links that are associated with a module, click on the 
	  "Links" tab on the editing interface. The 
	  <cnxn target="editlinksfig">"Edit Links"</cnxn> screen displays. 
        </para>
        
	  <figure id="editlinksfig"><media type="image/png" src="editlinksx.png"/>
	    <caption>The "Links" tab.</caption>
	  </figure>

        <para id="editlinkspara2">
	    From the "Links" tab you can:

	    <list id="editlinkslist">
	      <item><cnxn target="addlinksect">Add new links</cnxn></item>
	      <item><cnxn target="editlinksect">Edit existing links</cnxn></item>
	      <item><cnxn target="deletelinksect">Delete a link</cnxn></item>
	    </list>
	    These links are viewable in the "links" tab that displays with each 
	    module. The links appear under their specified category type, for 
	    example, the supplemental links are listed under the "Supplemental" 
	    heading.
	</para>
	    

     <section id="addlinksect">
        <name>Adding New Links</name>
        <para id="editlinkspara3">
	    To add a new link to a module, use the following steps:
	    
	    <list id="addlinklist1" type="enumerated">
	      <item>Type the label for the link in the "Link Name" field (required). 
	      </item>
	      <item>Identify the target of the link by typing in a module ID in 
	      the "Module ID" field or typing a URL in the "Link URL" field. You can  
	      optionally specify a version if you entered a module ID.</item>
	      <item>Click on the down arrow next to the "Link Type" field and
	      select the type of link from the drop-down list. </item>
	      <item>Click on the down arrow next to the "Link Strength" field and
	      select a number from the drop-down list for the strength of the link. 
	      5 is the strongest link.</item>
	      <item>Click <code>Add</code> to add the link.</item>
	    </list>
	</para>
      </section>
      
      
      <section id="editlinksect">
        <name>Editing Existing Links</name>
	  <para id="editlinkspara3a">
	    If the module already contains links, they will appear in the top half
	    of the screen. To edit an existing link, use the following steps:
	    
	  <list id="editlinklist1" type="enumerated">
	    <item>Update the contents of the "Name" field to change the label of the 
	    link. </item>
	    <item>Update the contents of the "URL" field to change the URL of the 
	    link.</item>
            <item>Click on the down arrow next to the "Link Type" field and
	    select another type of link from the drop-down list. </item>
	    <item>Click on the down arrow next to the "Link Strength" field and
	    select another number from the drop-down list for the strength of the 
	    link. 5 is the strongest link.</item>
	    <item>Click <code>Update Links</code> to make your changes.</item>
	  </list>
        </para>
      </section>
      

      <section id="deletelinksect">
        <name>Deleting a Link</name>
	<para id="deletelinkspara1">
	    To delete an existing link, select the checkbox in the "Delete" column 
	    in the list of existing links. Then click <code>Update Links</code> 
	    to delete the link.
	</para>
    </section>
    </section>


    <section id="previewmodule">
      <name>Previewing the Module</name>
	<para id="previewpara">
	  After editing the module, you should preview the module to verify that it 
	  appears as you want it to appear. You can view modules from the "Preview"
	  tab in the following ways:

	  <list id="previewlist">
	    <item><cnxn target="onlinepreview" strength="9">Preview the module 
	    on-line</cnxn></item>
	    <item><cnxn target="previewprint" strength="9">Preview the module 
	    in a print version (PDF file)</cnxn></item>
	    <item><cnxn target="viewchanges">View the change summary</cnxn></item>
	    <item><cnxn target="onlinecodesource">View the markup source for 
	    the module</cnxn></item>
	  </list></para>

    <section id="onlinepreview">
      <name>Previewing Modules On-Line</name>
	<para id="onlinepreviewpara">
	    To view a module on-line, use the following steps:
	    
	  <list id="onlinepreviewlist1" type="enumerated">
	    <item>Click on the "Preview" tab. The "Preview" screen displays. 
	    </item>
	    <item>Click the <emphasis>Online Preview</emphasis> link. This 
	    displays an on-line version of the module that is similar to the 
	    on-line display of the published module. The difference between
	    the preview and the published versions is that the preview does not
	    contain the links and tabs at the beginning and the links at the end
	    of the module. Review the module content and verify that it appears  
	    as you intended it to display.</item>
	    <item>Use your browser's "Back" function to return to the "Preview" screen.
	    </item>
	  </list>  
	</para>
    </section>
    
    
    <section id="previewprint">
      <name>Previewing a Print Version of the Module</name>
        <para id="previewprintpara">
	    The print version of a module is formatted differently than the on-line 
	    version. This difference is necessary because of the differences in the
	    on-line and printed media. To view a print version of the module, use
	    the following steps:
	    
	  <list id="printpreviewlist1" type="enumerated">
	    <item>Click on the "Preview" tab. The "Preview" screen displays. </item>
	    <item>Click the <emphasis>Print Preview</emphasis> link. 
	    An "Opening index.pdf" dialog box appears.</item>
	    <item>Verify that the option to open the file with a PDF viewing 
	    application is selected and click <code>OK</code>. The print version 
	    of the module displays.</item>
	    <item>Review the module display and verify that text and figures display as 
	    you intended them to display. </item>
	    <item>You can print this PDF file using your PDF viewer's file/print
	    option.</item>
	    <item>Close the PDF viewing application. </item>
	  </list>  
	</para>
	
    </section>
    
    
     <section id="viewchanges">
	<name>Viewing Change Summary</name>
	  <para id="changespara1">
	    When editing an existing module, you can view a summary of the 
	    differences between the last published version of the module and
	    the version you are currently editing. Click the <emphasis>Changes</emphasis>
	    link to view the <cnxn target="changesummaryfig">change summary</cnxn>. 
	    This option is useful when you checked out a module some time ago and 
	    do not remember what changes you made to it. 
	  </para>
	  
	   <figure id="changesummaryfig"><media type="image/png" src="ChangeSummary2.png"/>
	     <caption>The "Changes to" summary.</caption>
	   </figure>
	   
	  <para id="changespara2">
	    The "Change To" summary lists changes to the module, including role 
	    assignments and the names of any files that were changed, files that were 
	    added, and files that were removed. Click on a file name to display 
	    a brief description of the changes.
	  </para>
	   

    </section>
    
    
    <section id="onlinecodesource">
      <name>Previewing the code source</name>
	<para id="onlinecodesourcepara">
	    Occasionally it may be convenient to view the markup source for 
	    a module. To view the source of the module, click the 
	    <emphasis>Source</emphasis> link under the "View" heading in the "Module 
	    Status" sidebar. The most recent markup source that has been saved 
	    displays.  
	  <note type="note">
	  This feature is useful when you are trying to find a markup error.
	  </note>
	</para>
    </section>
    
    
    </section>

    
    <section id="discardmodule">
      <name>Discarding Your Changes</name>
	<para id="discardpara">
	  The situation may arise in which you wish to return a module that you
	  are editing back to its original state: the state in which it was 
	  before you began editing it. To do this, click the 
	  <emphasis>Discard</emphasis> link under the "Actions" heading in the 
	  "Module Status" sidebar. The module will revert back to the state it 
	  was in when you checked it out.
	<note type="note">
	  If the module is new and has never been published, you will lose all 
	  the content you entered and the module will be blank.
	</note>
      </para>
    </section>


    <section id="submitmodule">
      <name>Publishing the Module</name>
 	<para id="submittext">
	  To make your module or your changes to an existing module viewable by 
	  anyone on the Internet, you must publish the module in Connexions. To
	  publish a module, use the following steps:
	  
	  <list id="submitmodulelist1" type="enumerated">
	    <item>Click on the "Publish" tab. The <cnxn target="publishfig">"Publish 
	    Module"</cnxn> screen displays. This screen contains a list of reminders 
	    for you to check before you publish the module.</item>
	    <item>Type a brief description of your work on the module in the 
	    "Description of Changes" text box.</item>
	    <item>Click <code>Publish</code>. Your work on the module is 
	    entered into the Connexions Content Commons. Once in the Content
	    Commons, anyone with Internet access can view the module.</item>
	  </list>
	</para>
	
	<figure id="publishfig"><media type="image/png" src="publishx.png"/>
	  <caption>The "Publish" tab.</caption>
	</figure>

	<para id="submittext2">
	  A new module would not necessarily have editing changes, so in the 
	  "Description of Changes" text box you might enter a comment like, 
	  "Created a new module".
	</para>

	<note type="note">
	The act of publishing a module is different from clicking on the 
	<code>Save</code> button in an editing session. When you save your changes,
	only you and the people who have access to your workgoup can see your changes. When you 
	publish a module, the entire world can view your work on the Internet. 
	</note>
	
    </section>


  </content>
</document>
