Creating MINT Domains - Revision history

Alnaucler at 19:10, 20 February 2020

2020-02-20T19:10:32Z

← Older revision		Revision as of 21:10, 20 February 2020
Line 141:		Line 141:
	{{Note\|Note that a domain can only be deleted if no object in the Repository is depending on it, i.e. there is no [[Creating Ad Hoc Views in MINT\|Ad-Hoc View]] in the Repository that is based on this domain.}}		{{Note\|Note that a domain can only be deleted if no object in the Repository is depending on it, i.e. there is no [[Creating Ad Hoc Views in MINT\|Ad-Hoc View]] in the Repository that is based on this domain.}}

	{{NavBox ~~Business Intelligence~~}}		{{NavBox Hub}}
	[[Category:~~VIE~~]]		[[Category:NoPublic]]

Evinek at 12:53, 20 June 2017

2017-06-20T12:53:42Z

← Older revision		Revision as of 14:53, 20 June 2017
Line 1:		Line 1:
	{{TOC right}}		{{TOC right}}
	~~{{Under construction\| This page is under construction}}~~
	A '''Domain''' in MINT is a view on data from a data source, e.g. from an IMSMA staging area. It presents the data in a certain context and allows end-users to access that data in a comprehensive way. A domain can be compared to a ''view'' on the database - it in fact implements a view functionality within MINT. This means that instead of having a view object directly on the database, a domain is a metadata layer residing inside MINT.		A '''Domain''' in MINT is a view on data from a data source, e.g. from an IMSMA staging area. It presents the data in a certain context and allows end-users to access that data in a comprehensive way. A domain can be compared to a ''view'' on the database - it in fact implements a view functionality within MINT. This means that instead of having a view object directly on the database, a domain is a metadata layer residing inside MINT.

Evinek at 12:53, 20 June 2017

2017-06-20T12:53:18Z

← Older revision		Revision as of 14:53, 20 June 2017
Line 133:		Line 133:
	Then, click '''Edit with Domain Designer''' to open the domain in the designer and make any changes in one of the tabs described above.		Then, click '''Edit with Domain Designer''' to open the domain in the designer and make any changes in one of the tabs described above.
	{{Note\|When editing a domain in the Domain Designer, the view jumps to the '''Display''' tab. Click any other tab (Tables, Derived Tables, Joins, etc.) as required to make changes.}}		{{Note\|When editing a domain in the Domain Designer, the view jumps to the '''Display''' tab. Click any other tab (Tables, Derived Tables, Joins, etc.) as required to make changes.}}
			Make sure to click '''OK''' in the lower left corner, and then '''Submit''' on the following page in order to save the changes made to the domain.

			{{Note\|Some changes are not permitted. For example, if a field from a domain is used in an [[Creating Ad Hoc Views in MINT\|Ad-Hoc View]], then this field cannot be removed from the list of displayed field, because it would corrupt depending objects. Resulting error messages usually point to the exact issue.}}

	== Delete a domain ==__NOEDITSECTION__		== Delete a domain ==__NOEDITSECTION__
			To delete a domain, highlight the domain in the Repository and click '''Delete'''.
			[[File:MINT_delete_domain.png\|center]]
			{{Note\|Note that a domain can only be deleted if no object in the Repository is depending on it, i.e. there is no [[Creating Ad Hoc Views in MINT\|Ad-Hoc View]] in the Repository that is based on this domain.}}

	{{NavBox Business Intelligence}}		{{NavBox Business Intelligence}}
	[[Category:VIE]]		[[Category:VIE]]

Evinek at 12:47, 20 June 2017

2017-06-20T12:47:45Z

← Older revision		Revision as of 14:47, 20 June 2017
Line 95:		Line 95:
	The choice of the method depends on the requirements, the urgency, timeline, etc. It is important to be consistent though and document where each manipulation is implemented.}}		The choice of the method depends on the requirements, the urgency, timeline, etc. It is important to be consistent though and document where each manipulation is implemented.}}
	[[File:MINT_domain_designer_calculated_fields.png\|center\|900px]]		[[File:MINT_domain_designer_calculated_fields.png\|center\|900px]]
	{{Note\|~~A list~~ of ~~useful expressions to copy~~-~~and~~-~~paste will be posted~~ here.}}		{{Note\|The reference of the language used for defining calculated fields can be found [http://community.jaspersoft.com/documentation/jasperreports-server-user-guide/domel-syntax here].}}

	Once all required calculated fields are defined, click on the next tab, '''Pre-Filters'''.		Once all required calculated fields are defined, click on the next tab, '''Pre-Filters'''.
Line 125:		Line 125:

	Finally, after having organised and renamed the attributes, click '''OK''' in the lower left corner, and then '''Submit''' on the following page in order to save the domain.		Finally, after having organised and renamed the attributes, click '''OK''' in the lower left corner, and then '''Submit''' on the following page in order to save the domain.

			{{Note\|When defining a complex domain and/or making many changes that require some time, it is recommended to save/submit the domain design from time to time, to avoid losing changes due to e.g. a timeout or connection issue.}}

	== Edit a domain ==__NOEDITSECTION__		== Edit a domain ==__NOEDITSECTION__
			To edit an existing domain, highlight the domain in the Repository and click '''Edit'''.
			[[File:MINT_edit_domain.png\|center]]
			Then, click '''Edit with Domain Designer''' to open the domain in the designer and make any changes in one of the tabs described above.
			{{Note\|When editing a domain in the Domain Designer, the view jumps to the '''Display''' tab. Click any other tab (Tables, Derived Tables, Joins, etc.) as required to make changes.}}

	== Delete a domain ==__NOEDITSECTION__		== Delete a domain ==__NOEDITSECTION__

Evinek at 12:27, 20 June 2017

2017-06-20T12:27:36Z

← Older revision		Revision as of 14:27, 20 June 2017
Line 1:		Line 1:
	{{TOC right}}		{{TOC right}}
	{{Under construction\| This page is under construction}}		{{Under construction\| This page is under construction}}
	A '''Domain''' in MINT is a view on data from a data source, e.g. in an IMSMA staging area. It presents the data in a certain context and allows end-users to access that data in a comprehensive way. A domain can be compared to a ''view'' on the database - it in fact implements a view functionality within MINT. This means that instead of having a view object directly on the database, a domain is a metadata layer residing inside MINT.		A '''Domain''' in MINT is a view on data from a data source, e.g. from an IMSMA staging area. It presents the data in a certain context and allows end-users to access that data in a comprehensive way. A domain can be compared to a ''view'' on the database - it in fact implements a view functionality within MINT. This means that instead of having a view object directly on the database, a domain is a metadata layer residing inside MINT.

	Usually, different types of data (e.g. data on accidents, data on activities, etc.) are presented in different domains, unless these different types need to be put in context and presented in a single report.		Usually, different types of data (e.g. data on accidents, data on activities, etc.) are presented in different domains, unless these different types need to be put in context and presented in a single report.

Evinek at 12:27, 20 June 2017

2017-06-20T12:27:17Z

← Older revision		Revision as of 14:27, 20 June 2017
Line 1:		Line 1:
	{{TOC right}}		{{TOC right}}
	{{Under construction\| This page is under construction}}		{{Under construction\| This page is under construction}}
	A '''Domain''' in MINT is a view on data ~~residing in~~ a data source, e.g. in an IMSMA staging area. It presents the data in a certain context and allows end-users to access that data in a comprehensive way. A domain can be compared to a ''view'' on the database - it in fact implements a view functionality within MINT. This means that instead of having a view object directly on the database, a domain is a metadata layer residing inside MINT.		A '''Domain''' in MINT is a view on data from a data source, e.g. in an IMSMA staging area. It presents the data in a certain context and allows end-users to access that data in a comprehensive way. A domain can be compared to a ''view'' on the database - it in fact implements a view functionality within MINT. This means that instead of having a view object directly on the database, a domain is a metadata layer residing inside MINT.

	Usually, different types of data (e.g. data on accidents, data on activities, etc.) are presented in different domains, unless these different types need to be put in context and presented in a single report.		Usually, different types of data (e.g. data on accidents, data on activities, etc.) are presented in different domains, unless these different types need to be put in context and presented in a single report.

Alnaucler at 19:00, 29 September 2015

2015-09-29T19:00:05Z

← Older revision		Revision as of 21:00, 29 September 2015
Line 32:		Line 32:
	[[File:MINT_domain_select_schema.png\|center]]		[[File:MINT_domain_select_schema.png\|center]]

	On a PostgreSQL database (such as an [[IMSMA Staging Area]]), the actual data always resides in the schema called '''public'''. Therefore, the '''public''' schema always has to be selected in this step, no other one. Select '''public''' and click '''OK'''. For other database systems, the schema names might be different though. Please get in touch with your [[Management ~~Consulting~~ Team\|GICHD IM advisor]] in case of doubt.		On a PostgreSQL database (such as an [[IMSMA Staging Area]]), the actual data always resides in the schema called '''public'''. Therefore, the '''public''' schema always has to be selected in this step, no other one. Select '''public''' and click '''OK'''. For other database systems, the schema names might be different though. Please get in touch with your [[Information Management Team\|GICHD IM advisor]] in case of doubt.

	The Domain Designer now opens on its first tab called '''Tables'''. The sections of the designer are the following.		The Domain Designer now opens on its first tab called '''Tables'''. The sections of the designer are the following.

Alnaucler at 09:16, 6 November 2014

2014-11-06T09:16:04Z

← Older revision		Revision as of 11:16, 6 November 2014
Line 32:		Line 32:
	[[File:MINT_domain_select_schema.png\|center]]		[[File:MINT_domain_select_schema.png\|center]]

	On a PostgreSQL database (such as an [[IMSMA Staging Area]]), the actual data always resides in the schema called '''public'''. Therefore, the '''public''' schema always has to be selected in this step, no other one. Select '''public''' and click '''OK'''. For other database systems, the schema names might be different though. Please get in touch with your [[Management Consulting Team\|GICHD IM ~~focal point~~]] in case of doubt.		On a PostgreSQL database (such as an [[IMSMA Staging Area]]), the actual data always resides in the schema called '''public'''. Therefore, the '''public''' schema always has to be selected in this step, no other one. Select '''public''' and click '''OK'''. For other database systems, the schema names might be different though. Please get in touch with your [[Management Consulting Team\|GICHD IM advisor]] in case of doubt.

	The Domain Designer now opens on its first tab called '''Tables'''. The sections of the designer are the following.		The Domain Designer now opens on its first tab called '''Tables'''. The sections of the designer are the following.

Evinek at 06:36, 14 October 2014

2014-10-14T06:36:42Z

← Older revision		Revision as of 08:36, 14 October 2014
Line 120:		Line 120:
	<li>Finally, each attribute can be renamed by editing its properties.		<li>Finally, each attribute can be renamed by editing its properties.
	[[File:MINT_domain_designer_display_edit_properties.png\|center]]		[[File:MINT_domain_designer_display_edit_properties.png\|center]]
	{{Note\|It is recommended to change the '''Label''' only and keep the original attribute name as the '''ID'''.</li>		{{Note\|It is recommended to change the '''Label''' only and keep the original attribute name as the '''ID'''.}}</li>
	</ol>		</ol>
	[[File:MINT_domain_designer_display.png\|center\|900px]]		[[File:MINT_domain_designer_display.png\|center\|900px]]

			Finally, after having organised and renamed the attributes, click '''OK''' in the lower left corner, and then '''Submit''' on the following page in order to save the domain.

	== Edit a domain ==__NOEDITSECTION__		== Edit a domain ==__NOEDITSECTION__

Evinek at 06:35, 14 October 2014

2014-10-14T06:35:13Z

← Older revision		Revision as of 08:35, 14 October 2014
Line 109:		Line 109:
	=== Display ===__NOEDITSECTION__		=== Display ===__NOEDITSECTION__
	Finally, this last tab lets administrators organise and name the attributes to be presented to the users who will make ad-hoc views and reports based on domains. This is an important step that should be done carefully, since it is about giving meaningful names and labels to each attribute. {{Note\|The names of the attributes of the staging area might not always be meaningful, end-user names. For example, ''sourcereliabilityenum'' is the name of an attribute - display it as ''Source reliability'' will be much clearer for an end-user.}}		Finally, this last tab lets administrators organise and name the attributes to be presented to the users who will make ad-hoc views and reports based on domains. This is an important step that should be done carefully, since it is about giving meaningful names and labels to each attribute. {{Note\|The names of the attributes of the staging area might not always be meaningful, end-user names. For example, ''sourcereliabilityenum'' is the name of an attribute - display it as ''Source reliability'' will be much clearer for an end-user.}}

			On the '''Display''' page, the left-hand pane contains all selected tables and derived tables, each with all their attributes. In order to build up an organisation and select useful attributes, the below steps can be followed:
			<ol>
			<li>
			Think about how the attributes should be grouped together, in a folder-like manner. In a MINT domain, a ''folder'' is called a ''set''. For example, in the example followed through this page, attributes from accidents and from devices causing the accidents are exposed. One possibility would thus be to group the core accident attributes in a folder, and organise the device-related attributes in a sub-set.
			Use the '''Add Set''' button to add a new set. If an existing set is highlighted, then the new set will be created as a sub-set.
			[[File:MINT_domain_designer_display_detail.png\|center]]</li>
			<li>From the available attributes in the left-hand pane, select those that should be exposed to the user, and assign them to the set they logically belong to. While the tables can contain a lot of attributes, only a few might be really used and have values. It is thus recommended to only display those attributes that make sense to analyse in a specific context. Use the '''Add to sets''' and '''Add to selected set''' buttons to assign attributes to a set.
			[[File:MINT_domain_designer_display_add_to_sets.png\|center]]</li>
			<li>Finally, each attribute can be renamed by editing its properties.
			[[File:MINT_domain_designer_display_edit_properties.png\|center]]
			{{Note\|It is recommended to change the '''Label''' only and keep the original attribute name as the '''ID'''.</li>
			</ol>
	[[File:MINT_domain_designer_display.png\|center\|900px]]		[[File:MINT_domain_designer_display.png\|center\|900px]]
	~~[[File:MINT_domain_designer_display_detail.png\|center]]~~

	== Edit a domain ==__NOEDITSECTION__		== Edit a domain ==__NOEDITSECTION__