IMSMA3 script changes 6.0 - Revision history

Alnaucler at 20:23, 26 November 2018

2018-11-26T20:23:42Z

← Older revision		Revision as of 22:23, 26 November 2018
Line 67:		Line 67:
	* CoordRefFormat		* CoordRefFormat
	* UserInputFormat		* UserInputFormat

			If you have UTM coordinates then you use GetWGS84Longitude for calculating the Longitude/Latitude values:<br/>
			Attribute.SetDouble("Longitude", Translate.GetWGS84Longitude("UTM42N", Cast.String(Row.GetAttribute("Xcoord")), Cast.String(Row.GetAttribute("Ycoord"))))<br/>
			Attribute.SetDouble("Latitude", Translate.GetWGS84Latitude("UTM42N", Cast.String(Row.GetAttribute("Xcoord")), Cast.String(Row.GetAttribute("Ycoord")))) <br/>

			{{Note \| There is no function that calculates Longitude and Latitude from a MGRS coordinates so that has to be done with e.g. ArcGIS before the import and needs to be part of the indata to the script. But if you have Longitude and Latitude then the MGRS may be calculated with:
			Attribute.SetString("UserEnteredMGRS", Pojo.GetUserEnteredCoord( Row.GetString("clnLandMarkLongitude"), Row.GetString("clnLandMarkLatitude"), Row.GetString("clnMapCoordinateSystemTC"))) }}

	===Key and Object Mapping===__NOEDITSECTION__		===Key and Object Mapping===__NOEDITSECTION__

Alnaucler: Alnaucler moved page Script changes 6.0 to IMSMA3 script changes 6.0 without leaving a redirect

2017-06-14T11:01:18Z

Alnaucler moved page Script changes 6.0 to IMSMA3 script changes 6.0 without leaving a redirect

← Older revision	Revision as of 13:01, 14 June 2017
(No difference)

Alnaucler at 05:54, 11 November 2016

2016-11-11T05:54:50Z

← Older revision		Revision as of 07:54, 11 November 2016
Line 77:		Line 77:

	===Mandatory information===__NOEDITSECTION__		===Mandatory information===__NOEDITSECTION__
	{{Note \| There is no changes in version 6.0 for these fields but there were a change in version 5.08.02 and many existing scripts are not yet updated. I would also recommend to double-check '''new''' scripts written by Novetta.}}		{{Note \| There is no changes in version 6.0 for these fields but there were a change in version 5.08.02 and many existing scripts are not yet updated. I would also recommend to double-check '''new''' scripts written by Novetta. ''Date of Information'' and ''Form ID'' are vital for the function of {{IMSMANG}} and should always be filled in.}}
	Verify that the following fields are set and correct in Pojo Fieldreport:		Verify that the following fields are set and correct in Pojo Fieldreport:
	* Date of Information (previously called Date of Report) -> DateOfReport		* Date of Information (previously called Date of Report) -> DateOfReport

Alnaucler at 13:55, 16 June 2016

2016-06-16T13:55:02Z

← Older revision		Revision as of 15:55, 16 June 2016
Line 15:		Line 15:
	===SQL syntax===__NOEDITSECTION__		===SQL syntax===__NOEDITSECTION__
	{{Note \| It is strongly recommended to copy all SQL statements to a SQL tool like PGadminIII or NaviCat and test them before running the script in {{IMSMANG}} 6.0}}		{{Note \| It is strongly recommended to copy all SQL statements to a SQL tool like PGadminIII or NaviCat and test them before running the script in {{IMSMANG}} 6.0}}
	Due to PostgreSQL is case sensitive you need to adapt SQL statements by adding " around column names that contains capital case and because of the " you also need to add \ (escape character).		Due to PostgreSQL is case sensitive you need to adapt SQL statements by adding " around column names that contains capital case and because of the " you also need to add \ (escape character).<br/>

	'''5.08.04 example'''		'''5.08.04 example'''
	<pre>		<pre>
Line 24:		Line 23:
	<pre>		<pre>
	SELECT \"Loc_VillageGUID\", \"mMREID\" FROM loc_link_mre WHERE \"Loc_VillageGUID\" IS NOT NULL		SELECT \"Loc_VillageGUID\", \"mMREID\" FROM loc_link_mre WHERE \"Loc_VillageGUID\" IS NOT NULL
	</pre>		</pre> <br/>

	In PostgreSQL there are other reserved words than in MySQL. In your SQL tool you will see them marked with blue text. <br/>		In PostgreSQL there are other reserved words than in MySQL. In your SQL tool you will see them marked with blue text. <br/>
	[[Image:Reserved_word1.png\|800px\|center]]		[[Image:Reserved_word1.png\|800px\|center]]
Line 52:		Line 50:
	Attribute.SetBoolean("Active", Cast.Boolean("true"))		Attribute.SetBoolean("Active", Cast.Boolean("true"))
	</pre>		</pre>
			===Multi-select===__NOEDITSECTION__
			{{Note \| If any of the fields that are imported are multi-select then you need to verify that position in cdfvalue is set. Scripts run with 6.0 works better than 5.08.04, see ICR-114. If position is NOT set then the update query in [[Multi-select CDFs]] needs to be added as a ''Data.RunSQLStatement'' in Migration Cleanup or run in a SQL tool. }}
	===Geodata===__NOEDITSECTION__		===Geodata===__NOEDITSECTION__
	The column ''userenteredcoord'' has been split up in 3 columns		The column ''userenteredcoord'' has been split up in 3 columns
Line 68:		Line 68:
	* UserInputFormat		* UserInputFormat

			===Key and Object Mapping===__NOEDITSECTION__
			One parameter seems to be need to be changed '''from'''
			Object.SetKeyedObjectMapping(Row.GetString("clnGUID"), "Geopoint", Object.CreatePojo("Geopoint"))
			'''to '''
			Object.SetKeyedObjectMapping("", "GeopointDA", Object.CreatePojo("Geopoint"));

			{{Note \| The second parameter is a variable name and I find it easier to read the scripts if the variable have a slightly different name than the third parameter which is the pojo''.}}

	===Mandatory information===__NOEDITSECTION__		===Mandatory information===__NOEDITSECTION__
	{{Note \| There is no changes in version 6.0 for these fields but there were a change in version 5.08.02 and many existing scripts are not yet updated. I would also recommend to double-check '''new''' scripts written by Novetta.}}		{{Note \| There is no changes in version 6.0 for these fields but there were a change in version 5.08.02 and many existing scripts are not yet updated. I would also recommend to double-check '''new''' scripts written by Novetta.}}
Line 96:		Line 104:

	{{Note \| Other clean-up and value setting in Domain-MigrationCleanup.mtxt '''still''' needs to be done.}}		{{Note \| Other clean-up and value setting in Domain-MigrationCleanup.mtxt '''still''' needs to be done.}}
			===MRE details===__NOEDITSECTION__
	===~~Multi-select~~===__NOEDITSECTION__		The difference between other items and Education which is using the table ''mredetail'' is the double reconciliation. In version 6.0 the approach is as e.g. Hazdeviceversion with a loop using SQLSubQuery and Pojo.SetChildren + Pojo.PersistPojo after the loop. The link to the table ''fieldreport'' needs to be added in the end of the loop Attribute.SetObject("Fieldreport", Pojo.GetPojoByGuid("Fieldreport", Cast.String(Object.GetKeyedMapping("", "FieldReport"))));
	~~{{Note \| If any of~~ the ~~fields that are imported are multi-select then you need to verify that position in cdfvalue~~ is ~~set~~. ~~Scripts run with~~ 6.0 ~~works better than 5~~.08.~~04, see ICR-114~~. ~~If position is NOT set then~~ the ~~update query in [[Multi-select CDFs]] needs~~ to ~~be added as a~~ ''~~Data.RunSQLStatement~~'' in ~~Migration Cleanup or run in a SQL tool~~. }}

	{{NavBox Upgrade}}		{{NavBox Upgrade}}
	[[Category:NoPublic]]		[[Category:NoPublic]]
	[[Category:NAA]]		[[Category:NAA]]

Alnaucler at 13:16, 16 June 2016

2016-06-16T13:16:25Z

← Older revision		Revision as of 15:16, 16 June 2016
Line 97:		Line 97:
	{{Note \| Other clean-up and value setting in Domain-MigrationCleanup.mtxt '''still''' needs to be done.}}		{{Note \| Other clean-up and value setting in Domain-MigrationCleanup.mtxt '''still''' needs to be done.}}

	===~~Verify~~===__NOEDITSECTION__		===Multi-select===__NOEDITSECTION__
	{{Note \| If any of the fields that are imported are multi-select then you need to verify that position in cdfvalue is set. Scripts run with 6.0 works better than 5.08.04, see ICR-114. If position is NOT set then the update query in [[Multi-select CDFs]] needs to be added as a ''Data.RunSQLStatement'' in Migration Cleanup or run in a SQL tool. }}		{{Note \| If any of the fields that are imported are multi-select then you need to verify that position in cdfvalue is set. Scripts run with 6.0 works better than 5.08.04, see ICR-114. If position is NOT set then the update query in [[Multi-select CDFs]] needs to be added as a ''Data.RunSQLStatement'' in Migration Cleanup or run in a SQL tool. }}

Alnaucler at 04:00, 2 May 2016

2016-05-02T04:00:20Z

← Older revision		Revision as of 06:00, 2 May 2016
Line 87:		Line 87:

	===Location===__NOEDITSECTION__		===Location===__NOEDITSECTION__
	In 5.x the Location migration was done in very special way which required post processing with migration scripts running SQL stored functions ~~(020_add_new_location_reconciliation_info.sql)~~. This did not work well with PostgreSQL and therefore Location scripts (a.k.a. CityCentric-Domain-GazetteerCity-Location.mtxt) should be re-written for 6.0~~. migrated is changed~~.		In 5.x the Location migration was done in very special way which required post processing with migration scripts running SQL stored functions. This did not work well with PostgreSQL and therefore Location scripts (a.k.a. CityCentric-Domain-GazetteerCity-Location.mtxt) should be re-written for 6.0.

	{{Note \| Other clean-up and value setting in Domain-MigrationCleanup.mtxt still needs to be done.}}		If your script contains Target.Set("Pojo", '''"Location"''') then you need to adapt it to 6.0 version and you do not need to:
			* call ''020_add_new_location_reconciliation_info.sql''
			* execute Data.RunSQLStatement("update location set isactive = true ") and
			* execute Data.RunSQLStatement("update locationinfoversion set manual = false")
			in the script ''Domain-MigrationCleanup.mtxt''.

			{{Note \| Other clean-up and value setting in Domain-MigrationCleanup.mtxt '''still''' needs to be done.}}

	===Verify===__NOEDITSECTION__		===Verify===__NOEDITSECTION__

Alnaucler at 20:49, 5 August 2015

2015-08-05T20:49:40Z

← Older revision		Revision as of 22:49, 5 August 2015
Line 84:		Line 84:
	* Data Entry Date		* Data Entry Date
	* Submitted Date		* Submitted Date
	see [[Data Entry Form Table]] which fields to use.		see [[Data Entry Form Table]] which fields to use because the field names are confusing.

	===~~Workarounds~~===__NOEDITSECTION__		===Location===__NOEDITSECTION__
	{{~~Warning~~ \| ICR-114~~: The~~ update query in [[Multi-select CDFs]] needs to be added as a ''Data.RunSQLStatement'' ~~if any of the fields that are imported are multi-select~~. }}		In 5.x the Location migration was done in very special way which required post processing with migration scripts running SQL stored functions (020_add_new_location_reconciliation_info.sql). This did not work well with PostgreSQL and therefore Location scripts (a.k.a. CityCentric-Domain-GazetteerCity-Location.mtxt) should be re-written for 6.0. migrated is changed.

			{{Note \| Other clean-up and value setting in Domain-MigrationCleanup.mtxt still needs to be done.}}

			===Verify===__NOEDITSECTION__
			{{Note \| If any of the fields that are imported are multi-select then you need to verify that position in cdfvalue is set. Scripts run with 6.0 works better than 5.08.04, see ICR-114. If position is NOT set then the update query in [[Multi-select CDFs]] needs to be added as a ''Data.RunSQLStatement'' in Migration Cleanup or run in a SQL tool. }}

	{{NavBox Upgrade}}		{{NavBox Upgrade}}
	[[Category:NoPublic]]		[[Category:NoPublic]]
	[[Category:NAA]]		[[Category:NAA]]

Alnaucler at 21:03, 2 August 2015

2015-08-02T21:03:42Z

← Older revision		Revision as of 23:03, 2 August 2015
Line 58:		Line 58:
	* user_entered_mgrs		* user_entered_mgrs

	Search for ''UserEnteredCoord'' and replace the 5.08.04 syntax with (the row should end with a , or ;) : <br/>		Search for ''UserEnteredCoord'' and replace the 5.08.04 syntax with (the row should end with a , or ; depending on the row is inside an IF statement or not) <br/>
	Attribute.SetString("UserEnteredX", Row.GetString("Longitude")) <br/>		Attribute.SetString("UserEnteredX", Row.GetString("Longitude")) <br/>
	Attribute.SetString("UserEnteredY", Row.GetString("Latitude")) <br/>		Attribute.SetString("UserEnteredY", Row.GetString("Latitude")) <br/>

Alnaucler at 14:46, 21 January 2015

2015-01-21T14:46:21Z

← Older revision		Revision as of 16:46, 21 January 2015
Line 87:		Line 87:

	===Workarounds===__NOEDITSECTION__		===Workarounds===__NOEDITSECTION__
	# ICR-114: The update query in [[Multi-select CDFs]] needs to be added as a ''Data.RunSQLStatement'' if any of the fields that are imported are multi-select.		{{Warning \| ICR-114: The update query in [[Multi-select CDFs]] needs to be added as a ''Data.RunSQLStatement'' if any of the fields that are imported are multi-select. }}

	~~===Limitations===__NOEDITSECTION__~~
	~~Unfortunately there are no change in the following limitations of logic in scripts:~~
	* greater than (>)
	* less than (<)
	* LIKE (e.g. Eriks* or Eriks%)
	~~do not work because it is not included in the Java scripts.~~

	{{NavBox Upgrade}}		{{NavBox Upgrade}}
	[[Category:NoPublic]]		[[Category:NoPublic]]
	[[Category:NAA]]		[[Category:NAA]]

Alnaucler at 11:11, 21 January 2015

2015-01-21T11:11:13Z

← Older revision		Revision as of 13:11, 21 January 2015
Line 69:		Line 69:

	===Mandatory information===__NOEDITSECTION__		===Mandatory information===__NOEDITSECTION__
	Verify that the following fields are set and correct:		{{Note \| There is no changes in version 6.0 for these fields but there were a change in version 5.08.02 and many existing scripts are not yet updated. I would also recommend to double-check '''new''' scripts written by Novetta.}}
			Verify that the following fields are set and correct in Pojo Fieldreport:
	* Date of Information (previously called Date of Report) -> DateOfReport		* Date of Information (previously called Date of Report) -> DateOfReport
	* Data entry form ID -> LocalId ~~in Pojo Fieldreport~~		* Data entry form ID -> LocalId
	* Approved Date -> ReportVerifiedDate		* Approved Date -> ReportVerifiedDate
	* Approver -> VerifiedBy		* Approver -> VerifiedBy
	* Item ID ~~e.g. Victim ID~~ -> -> ~~LocalId in Pojo Victim~~
			Verify that the following fields are set and correct in Pojo Xxxinfoversion
			* Item ID -> LocalId
			* Type of item -> Type
			* Status of item -> Status

	If you have dates that you would like to use as		If you have dates that you would like to use as