<< Chapter < Page | Chapter >> Page > |
To remove a module or subcollection from the collection, hover your mouse over the item. At the right, there will be a link reading "Remove from collection". In the example, let's say you've decided not to include the module titled Module from Word Document : A pop-up appears confirming that you want to remove the module. Behind the pop-up, the module marked for deletion is highlighted in pink with its title crossed out:
Modules that are published in the Content Repository display the titles given to them by their authors. If these titles are not appropriate for themodule when it appears in the context of your collection (e.g., it may contain numbering), you can provide an alternate title for the module. The module displays youralternate title when it is accessed from within your collection. The module displays its original title whenever it is accessedfrom outside of your collection.
In our example, let's rename "Creating a Module in Minutes" to "Creating a Connexions Module" in order to match the similarly titled module in Part II of the collection. Hover over the module's title and click on the "Edit title/version" link that appears to the right: A pop-up appears. In the text field under "Alternate Title", type the title with which you want to override the module's title. Click "Save". If you want to undo the override, simply return to the pop-up, erase the text from the "Alternate Title" text field, and click "Save" again. The module's title will revert to its original one.
When a module is updated or edited, Connexions saves the previousversion of the module in history and uses the latest version of the module for viewing. Each new version of a module is given its ownversion number. You can either have your collection always use the latest version of the module, or you can pinpoint a specific version to be used.
In the example, let's say that version 1.2 of one of the modules we include was a complete reformatting of that module's content, and that the new format no longer makes sense in the context of your collection. Hover over the module's title and click on the "Edit title/version" link that appears to the right: A pop-up appears. In the "Set Version" area, select version 1.1 from the dropdown. Click "Save".
Links allow the viewer to display related information or examples that are not part of the collection with the click of a mouse. Linksmay be defined by the module's author, but they may also be added or redefined/overridden/removed for that module by the collection's author. Any changes you make in the collection composer to a module's links only display when viewing the module from within your collection.
In the example, let's say that you felt strongly that the introductory module really needed a link to the Connexions home page. To add this link, hover your mouse over the module's title. Click the link at right reading "Edit featured links": A pop-up appears, and it includes a form where we can enter the new link's information. (If this module's author had already included links in the module, the form would have been hidden behind a link reading "Create a new link".) Enter some text for the link, select which type of link it is, the link's strength (how strongly related the link is to the content) and either a URL or the ID of another collection. Click "Add New Link". The link will then be added to a table. From there, you can edit the link, remove it, or add another one. When you are finished, click the "Done" button. Now the links will be present on the module when viewed from inside your collection.
You can edit an existing collection with the Collection Composer in the same way you create a new collection. You can edit onlycollections for which you have a maintainer role. To use the Collection Composer on an existing collection, first make sure you are logged in, then you can:
Notification Switch
Would you like to follow the 'Connexions tutorial for vef fellows' conversation and receive update notifications?