<?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.19</md:version>
  <md:created>2002/10/07</md:created>
  <md:revised>2004/08/14 14:41:27.090 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="modulefiles.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 "Files" tab for the module displays a list of all the files associated 
	    with the module. The file containing the text of the module that is marked up 
	    with CNXML is named "index.cnxml". To edit this file click on the file name. 
	    The <cnxn target="editmodule">"Edit CNXML File: index.cnxml"</cnxn> screen 
	    displays. From this screen you can perform the following actions on the file:

	    <list id="editoptions">
	      <item><cnxn target="importexport" strength="9">Export to an XML 
	      Editor</cnxn></item>
	      <item><cnxn target="external" strength="9">Export to an External 
	      Text Editor</cnxn></item>
	      <item><cnxn target="downloadupload" strength="9">Download to a Specific
	      Location for Editing</cnxn></item>
	      <item><cnxn target="editingonline" strength="9">Edit Text in 
	      Connexions</cnxn></item>
	    </list>

	    You can also <cnxn target="importexport">import/export</cnxn> other file 
	    types, and preview the module using appropriate tabs.
	</para>
	  
	  <figure id="editmodule">
	    <media type="image/png" src="editmodule.png"/>
	    <caption>The "Edit CNXML File: index.cnxml" tab.</caption>
	  </figure>


    <section id="importexport">
      <name>Import/Export to an XML Editor</name>
        <para id="importexport1">
	    The preferred method of editing your file is with a software package that 
	    is specifically designed for editing XML files. To do this, the index.cnxml 
	    file must be altered so that your XML editor can read it. Then the file 
	    is exported from Connexions to the editor. Once you have completed your 
	    edits, the file imported back into Connexions and the changes for editor 
	    readability are removed. Using the import and export functions on the 
	    module <cnxn target="importexportfig">"Import/Export"</cnxn> tab automatically 
	    adds and removes 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>

	  <figure id="importexportfig">
	    <media type="image/png" src="importexport.png"/>
	    <caption>The module "Import/Export" tab.</caption>
	  </figure>

        <para id="importexportpara2">
	    To export the "index.cnxml" file to be edited with your XML editor, 
	    use the following steps:
	    
	  <list id="importexportlist1" type="enumerated">
	    <item>Click the <emphasis>import/export</emphasis> link on the "Files" tab
	    to the right of the "index.cnxml" file entry in the module contents. The 
	    "Import/Export" tab displays.</item>
	    <item>Click <code>Export</code>. A dialog box displays for opening 
	    the "index.cnxml" file.</item>
	    <item>Specify that you want to save the file to a disk.</item>
	    <item>Specify the filename and location of the file to be saved.</item>
	    <item>Launch your XML editor and edit the file.</item>
	  </list>
	</para>
	    
        <para id="importexportpara3">
	    To import the "index.cnxml" file back into Connexions, use the following 
	    steps:
	    
	  <list id="importexportlist2" type="enumerated">
	    <item>Click the <emphasis>import/export</emphasis> link on the "Files" tab
	    to the right of the "index.cnxml" file entry in the module contents. The 
	    "Import/Export" tab displays.</item>
	    <item>Click <code>Browse</code>. Locate the "index.cnxml" file you edited
	    with your XML editor and click on the filename.</item>
	    <item>Click <code>Import</code>. The edited file is imported back into 
	    the Connexions module.
	    </item>
	  </list>
        </para>
    </section>


    <section id="external">
      <name>External Text Editor</name>
	<para id="externalpara">
	    Another method of editing the "index.cnxml" file is with an external
	    text editor which is not specifically designed to be an XML editor.
	    Note that when you view the module 
	    <cnxn target="modulefiles">contents</cnxn> 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 markups for CNXML. 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 id="downloadupload">
      <name>Downloading/Uploading Module Text</name>
	<para id="downloadpara">
	   You can download the contents of the "index.cnxml" file to a location of 
	   your choosing and then edit it with a text editor. To download the file,
	   use the following steps:
	   
          <list id="downloadlist1" type="enumerated">
	    <item>Click the <emphasis>Download a copy</emphasis> link on the "Edit" 
	    tab. A dialog box displays for opening the "index.cnxml" file.</item>
	    <item>Specify that you want to save the file to a disk.</item>
	    <item>Specify the filename and location of the file to be saved.</item>
	    <item>Launch your text editor and edit the file.</item>
	  </list>
	</para>
	    
        <para id="downloadpara2">
	    To upload the "index.cnxml" file back into Connexions, use the following 
	    steps:
	    
	  <list id="downloadlist2" type="enumerated">
	    <item>Click the <emphasis>Browse</emphasis> link on the "Edit" tab. 
	    The "File Upload" dialog box displays.</item>
	    <item>Locate the "index.cnxml" file you edited with your text editor and 
	    click on the filename.</item>
	    <item>Click <code>Open</code>.</item>
	    <item>Click <code>Upload File</code>. The edited file is uploaded into the 
	    Connexions module.
	    </item>
	  </list>
          <note type="note">
            Once you have downloaded the "index.cnxml" file, you can use any editor 
            you choose to edit it. For information on writing and editing CNXML, see 
            <cnxn document="m9000">The Basic CNXML</cnxn>.
	  </note>
	</para>
    </section>


    <section id="editingonline">
      <name>Editing index.cnxml directly</name>
	<para id="editonlinepara">
	    You can edit the "index.cnxml" file directly on the web within the 
	    Connexions editing interface. To edit the file directly, use the 
	    following steps:
	    
	  <list id="editingonlinelist" type="enumerated">
	    <item>Click on the "index.cnxml" filename in the module 
	    <cnxn target="modulefiles">contents</cnxn> display. The "The Edit CNXML 
	    File: index.cnxml tab" displays.</item>
	    <item>Click in the text window and begin editing.</item>
	    <item>Click <code>Save</code> when you have finished your edits to save 
	    your changes.</item>
	  </list>
	</para>
	
	<para id="editonlinepara2">
	  This method of editing the "index.cnxml" file is recommended for quick
	  changes only. This editor does not have the advanced functions that 
	  come with many text editors. 
	</para>


    <section id="saving">
      <name>Saving Your Work</name>
        <para id="modules11">
	      As you edit the "index.cnxml" file in Connexions, click <code>Save</code> 
	      at any point to save your changes to the file. When you want to check 
	      your CNXML markup, select the "Validate during save" check box and click
	      <code>Save</code>. The page reloads and any errors in your markup are 
	      listed at the top of the page.  If there are no errors, your markup 
	      is valid and the words "File OK" appear next to the "Validation 
	      results" heading.
        </para>


            <para id="validatepara">
	      Any "index.cnxml" file that enters the 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 the errors</cnxn> 
	      appears in a pink box when you save the file.

	      <note type="warning">You cannot publish the module in Connexions until 
	      all the markup errors have been fixed and the "index.cnxml" file has 
	      been validated.
	      </note>
	</para>
	    <figure id="validatefig">
	      <media type="image/png" src="validateerror.png"/>
	      <caption>Example of validation errors</caption>
	    </figure>
    </section>
    </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="editmetadata.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. You can grant one or more roles  
	    to other Connexions account holders who you want to be associated with 
	    the module. The table on the bottom the <cnxn target="rolesfig">"Roles"</cnxn> 
	    tab displays the names of the users and their current roles. A checked box in 
	    the "Author", "Maintainer", or "Copyright Holder" column indicates that person 
	    was granted that role or roles. 
        </para>

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


    <section id="editroles2">
      <name>Granting Roles to Other Users</name>
	 <para id="addingroles"><name/>
	    To grant one or more module 
	    <link src="http://cnx.rice.edu/help/reference/roles/document_view">roles</link> 
	    to a user, use the following steps:
	    
	   <list id="editroleslist1" type="enumerated">
             <item>Click the "Roles" tab to display it.</item>
	     <item>Type the name of the user 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 users that match the search string are displayed.</item>
	     <item>Select the checkbox next to the desired user name and click 
	     <code>Add People</code>. A "Roles Pending Approval" table displays 
	     under the "Roles" table.</item>  
	     <item>Verify that the checkboxes in the "Author", "Maintainer", 
	     or "Copyright Holder" columns are checked for the roles you want to 
	     grant to that user. By default all the checkboxes are selected.</item>
	     <item>If desired, de-select the checkboxes for the roles you do not 
	     want to grant, and click <code>Update Roles</code>.</item>
	     <item>A request to accept the role will display to the user upon 
	     his or her next login to Connexions.</item>
	  </list>
	</para>
	  
	<para id="collaboration">
	    When granting or updating another user's roles, the change does not
	    take affect until the other user has accepted the role change. Once the 
	    user has approved the change, their new roles are reflected in the "Roles"
	    table. See <cnxn target="requestsawaiting">approving role requests</cnxn> 
	    for information about approving requests.
	    <note type="note">
	    All pending role changes must be accepted or rejected before a module can 
	    be published.
	    </note>
	 </para>
    </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: 
	  
	  <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="collaborationrequests.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 checkbox 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 checkbox 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 checkbox 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>

	
    <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="editlinks.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="changesummary.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="publish.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 your collaborating authors can see your changes. When you 
	publish a module, the entire world can view your work on the Internet. 
	</note>
	
    </section>


  </content>
</document>
