Template Project: Difference between revisions

From Tygron Preview Support Wiki
Jump to navigation Jump to search
No edit summary
Line 6: Line 6:


==What is transferred to a new project==
==What is transferred to a new project==
In a template project, certain elements are transferred to a new project, created with the template.
These elements are the elements that are not spatial, thus the elements that are not linked to a location.
These are for example:
* [[Indicators]]
* [[Overlays]]
* [[Stakeholders]]
* [[Panels]] (the location of the panels must be set)
* New [[functions]]/changes in function values
* [[Globals]]
* [[Actions]]
* New/changed [[Upgrade types]]
* [[WFS]] connections in the [[Geo Data Wizard]]
Elements that are not transferred to a new project are for example:
* (Imported) [[Areas]]. The areas have a certain location in the template project. The new project is very likely on a new location and therefore the areas are not in that location and in the new project
* [[Measures]]. Measures are drawn on a certain location, this location is also not present in the new project anymore


==Default templates in the Tygron Engine==
==Default templates in the Tygron Engine==

Revision as of 09:53, 7 May 2018

Template:Learned

What is a template in the Tygron Engine

A template is a project that can be used to create a new project with. This new project can have a different location as the original template project, but has the same Indicators, Actions, Overlays settings etc. as the template project. This is very convenient in case a similar spatial issue is at hand on different locations and you want to create different projects for these locations. Also, this functionality enables the user to make elaborate predefined actions or custom indicators, which can then be easily transposed with a template to another area. This functionality saves a lot of time and makes preparing projects faster.

What is transferred to a new project

In a template project, certain elements are transferred to a new project, created with the template. These elements are the elements that are not spatial, thus the elements that are not linked to a location. These are for example:


Elements that are not transferred to a new project are for example:

  • (Imported) Areas. The areas have a certain location in the template project. The new project is very likely on a new location and therefore the areas are not in that location and in the new project
  • Measures. Measures are drawn on a certain location, this location is also not present in the new project anymore

Default templates in the Tygron Engine


There are multiple default templates available in the Tygron Engine, including Climategame. For more information about this specific template, see the page for the Climategame.

How to add your own template

Projects can easily be set as a template, to be used as base for next projects. Once a project has been set as template it is added to the list of available templates. Setting a project as a template can only be done by users with Domain Administrator rights. By default the template is not shared with other users within your domain. Please refer to the next paragraph about making templates available for the domain.
Setting a project as a template makes the project read only!


How to set a project as template:
  1. Log in with Domain Admin rights
  2. Select "Options"
  3. Select "Projects"
  4. Highlight project to be made a template
  5. Check box named "Template (project becomes read only)"

Sharing your template with other users in your domain

Q1-2016-TemplatePermissions2.jpg
When a project has been made a project template, the read and write permissions will change. This is to ensure that nobody accidentally edits the project template. No write permissions remain (project cannot be edited anymore) and only the creator can read the template by default. In order to change the read permissions, so that other users within the same domain can also use the template, the creator can change the permissions of the original project in the editor.


How to share the template with other users in your domain:
  1. Load in the editor the template project to be shared with the domain
  2. Select "File" when in main view
  3. Select "Permissions"
  4. Change the entry for "Other users in domain" to "Read"
  5. Save project