diff options
Diffstat (limited to 'docs/_build/html/_sources/administration.txt')
| -rw-r--r-- | docs/_build/html/_sources/administration.txt | 129 |
1 files changed, 107 insertions, 22 deletions
diff --git a/docs/_build/html/_sources/administration.txt b/docs/_build/html/_sources/administration.txt index db7e078..2f8ddb5 100644 --- a/docs/_build/html/_sources/administration.txt +++ b/docs/_build/html/_sources/administration.txt @@ -60,7 +60,7 @@ Item list #. search items by word (not available for all type of items) #. this filter box permit to filter current entries with some criteria (not available for all type of items) -#. the header of the table is clickable. Click on an header sort the items by +#. the header of the table is cliquable. Click on an header sort the items by this header (ascending or descending). Multiple header sort is possible (the number on the right of the header explain the order of sorting). #. each item can be checked (for applying an action) or selected (by clicking on @@ -80,36 +80,121 @@ Item form item, they can be ordered by drag and drop. #. the form has to be validated by one of theses actions buttons. They are self-explanatory. -Creating news + +Status +****** + +*Status* is a property attached to each geographic item in Chimère. To +administrate efficiently Chimère you need to understand the mean of each status. + +- **Submited**: Status of a new item freshly proposed by an end user. This item + is not visible on the map. +- **Available**: Status of an item visible on the map. +- **Disabled**: Status of a discarded item. +- **Modified**: Status of an amendment proposed by an end-user. +- **Imported**: Status of a newly imported item. Import and export operations + need that all items with *imported* status are treated (validated, disabled + or deleted). + + +Managing news ------------- A news system is available. -All you have to to do is to click on the Add button near News. -For each news you have to provided a name and a content. The content can contain HTML tags. -The avaibility is set with a checkbox. +All you have to to do is to click on the **Add** button near News. +For each news you have to provided a name and a content. The content can contain +HTML tags. +The availability is set with a checkbox. Creating categories/subcategories --------------------------------- -Before adding categories you have to set some icons. Theses icons appears on the map and in the categories' box on the main map. -Be careful to resize correctly your icons. Indeed the icon will be presented at their real size on the map. -To add icons: the Add button near Icons. +Before adding categories you have to set some icons. Theses icons appears on the +map and in the categories' box on the main map. +Be careful to resize correctly your icons. Indeed the icon will be presented at +their real size on the map. +To add icons: the **Add** button near Icons. + +Categories are in fact only containers for subcategories. You'll have to provide +only a name and an order. +To add categories: the **Add** button near categories (quite clear now, isn't +it?) + +Fields of subcategories are: an associated category, a name, an icon, an order, +a color and an element type. +Theses fields are mainly quite self- explanatory. +The color is used to draw routes (if this subcategory contains routes). If it a +basic color it can be set with the English name (for instance: *red*, *blue*, +*yellow* or *purple*) otherwise you can put the HTML RVB code (for instance +*#9227c9*). +The element type is the type of element the subcategory can contain: POI, route +or both. + +Edition/moderation of items +--------------------------- -Categories are in fact only containers for subcategories. You'll have to provide only a name and an order. -To add categories: the Add button near categories (quite clear now, isn't it?) +The moderation step is quite simple. It works the same with POIs and routes. +The moderator can access to all POIs (or routes) by clicking on them on the +list. -Fields of subcategories are: an associated category, a name, an icon, an order, a color and an element type. -Theses fields are mainly quite self-explainatory. -The color is used to draw routes (if this subcategory contains routes). If it a basic color it can be set with the english name (for instance: "red", "blue", "yellow" or "purple") otherwise you can put the HTML RVB code (for instance "#9227c9"). -The element type is the type of element the subcategory can contain: POI, route or both. +A search field is available to search by name but the more interesting is to +filter POIs (or route) by state and by subcategory. -Moderation ----------- +There is a some actions available in the action list. -The moderation step is quite simple. It works the same with POIs and routes. -The moderator can access to all POIs (or routes) by clicking on the Modify button. -A search field is available to search by name but the more interesting is to filter POIs (or route) by state and by subcategory. -Then to modify an item you have to click on his name. -The submission can now freely modified. Compared to the main submission interface there is only on field add: the state field. To be publish in the main site the item must have the state: Available. -If an item is not revelant the Delete button permit to remove it. +- **Delete** to delete selected items. A confirmation step is displayed. +- **Validate** to set the status *Available* to selected items. +- **Disable** to set teh status *Disabled* to selected items. This is useful to + keep items you don't want to be exposed on the map. +- **Managed modified items** to manage the amendment made by end users on the + main site cf. to :ref:`managing-modified`. Modified item has to be treated + one by one. +- **Export to...** to export selected item to the selected format. + + +To modify an item, classically you have to click on his name. +Then you access to a form to freely modify the item. +In this form there is all data available to the end user form plus some extra +fields. The *Import fields* only make sense with data imported from an external +source or for data to be exported to OSM cf. to the :ref:`import section +<importing>` of this documentation. *Associated items fields* are read only +fields that list items associated to the current one (reference item of an +amendment, associated file of a route). + +Associated multimedia items are at the bottom of the form. You can freely add, +change items and change their order with drag and drop. + +Don't forget to validate your change with one of the **Save** buttons at the +bottom of the form (it is easily forgot when you change multimedia items). + +If an item is not relevant the **Delete** button permit to remove it. + +.. _managing-modified: + +Managing end user amendment +--------------------------- + +Amendment can be proposed on the main site by end-users. +In Chimère an amendment is a new item with the status *Modified* and with a link +to the reference item modified. + +.. Note:: + If you are logged as an administrator and make changes on the map with the + end user form there will be directly validated. + +A special form has been developed to facilitate the processing of theses +modified items. + +You can access to this special form with the action *Managed modified items*. + +.. image:: _static/chimere_admin_modified_management.png + +This form is a table with three columns. + +#. The first column display the information for the reference item. +#. The second column display the information proposed by the submitter. +#. The third column is a list of checkboxes. For each row checked, after the + validation, the value of the modified item will replace the value of the + reference item. +To reject all modification validate the form with no checkbox checked. |