Importing Data - Revision history

Mike: /* Structure Map - CMAP Structure */

2015-11-17T15:55:43Z

‎Structure Map - CMAP Structure

Mike: /* Importing Chains */

2015-10-13T14:24:15Z

‎Importing Chains

Mike: /* Importing Chains */

2015-10-13T14:20:12Z

‎Importing Chains

Mike: /* Importing Chains */

2015-10-13T14:19:48Z

‎Importing Chains

Mike at 14:18, 13 October 2015

2015-10-13T14:18:41Z

Guy at 20:19, 4 December 2012

2012-12-04T20:19:34Z

Guy at 20:19, 4 December 2012

2012-12-04T20:19:18Z

Guy: /* Overview */

2012-04-16T18:31:06Z

‎Overview

Guy: /* Structure Map - CMAP Structure */

2010-09-21T20:38:54Z

‎Structure Map - CMAP Structure

Guy at 20:36, 21 September 2010

2010-09-21T20:36:11Z

@@ Line 76: / Line 76: @@
 *'''Class''' - The first question asks what type of import the tools should run on this data. These classes mirror (but do NOT match) the ARK dataclasses.
-*'''Raw Item Val''' - The next question aims to establish the location of the raw item val. This is a key concept in the import tools (see notes). This question aims to establish whether a join (to a secondary table) will be necessary to arrive at this information. in the simplest case, this information is in a column on the import table itself.
+*'''Raw Item Val''' - The next question aims to establish the location of the raw item val. This is a key concept in the import tools (see notes). This question aims to establish whether a join (to a secondary table) will be necessary to arrive at this information. in the simplest case, this information is in a column on the import table itself. The item values to import must be in the sql.
 *'''Site Code''' - The system provides three options for the site code to be used in the import of each field. The simplest option is just to use the fixed site code specified in the CMAP. The second option is to use a code specified in a column of this table which will permit data from multiple sites to be imported from this field. Thirdly there is an option to get a site code from a joined table.
@@ Line 83: / Line 83: @@
 *'''notset''' - This provides a way to specify records that should not be imported to the database. For example, you might use a keyword BLANK or SKIP in your source data as a way to prevent certain rows from being imported. Be aware that you should carefully check over the data to be imported in the extraction test.
 ====Keys====

@@ Line 155: / Line 155: @@
 Chains can be imported by using the link in the structure defining frame:
-If attributes are to be chained to this number then click [here].
+:If attributes are to be chained to this number then click <u>[here]</u>.
 Clicking that link will save the structure and flag it so that when it is imported the ids of the new datafrags will be inserted into a column in the import_ table named ''''%col%'''_itemval', where '''%col%''' is the name of the column to chain.
 [[category:administrator]]

@@ Line 157: / Line 157: @@
 If attributes are to be chained to this number then click [here].
-Clicking that link will save the structure and flag it so that when it is imported the ids of the new datafrags will be inserted into a column in the import_ table named ''''%col%'''_itemval', where '''%col%''' is the name of the column to chain
+Clicking that link will save the structure and flag it so that when it is imported the ids of the new datafrags will be inserted into a column in the import_ table named ''''%col%'''_itemval', where '''%col%''' is the name of the column to chain.
 [[category:administrator]]

@@ Line 157: / Line 157: @@
 If attributes are to be chained to this number then click [here].
-Clicking that link will save the structure and flag it so that when it is imported the ids of the new datafrags will be inserted into a column in the import_ table named '[b]%col%[/b]_itemval', where [b]%col%[b] is the name of the column to chain
+Clicking that link will save the structure and flag it so that when it is imported the ids of the new datafrags will be inserted into a column in the import_ table named ''''%col%'''_itemval', where '''%col%''' is the name of the column to chain
 [[category:administrator]]

← Older revision		Revision as of 14:18, 13 October 2015
Line 151:		Line 151:
	Bear in mind that in the case of Attributes of type B, the preview will most likely show a series of SQL statements indicating the additions to the look up table (and Aliases) that would be run.		Bear in mind that in the case of Attributes of type B, the preview will most likely show a series of SQL statements indicating the additions to the look up table (and Aliases) that would be run.

		+	===Importing Chains===
		+
		+	Chains can be imported by using the link in the structure defining frame:
		+
		+	If attributes are to be chained to this number then click [here].
		+
		+	Clicking that link will save the structure and flag it so that when it is imported the ids of the new datafrags will be inserted into a column in the import_ table named '[b]%col%[/b]_itemval', where [b]%col%[b] is the name of the column to chain

	[[category:administrator]]		[[category:administrator]]

← Older revision		Revision as of 20:19, 4 December 2012
Line 1:		Line 1:
−	As of the v1.0 release of ARK there is a set of data import tools within ARK. These tools speed up and improve the process of creating a concordance map between the source data and an ARK database. Never the less, using the tools will require a working knowledge of ARK's data structures. If you are unable to import your data or would like training in the ARK import tools, please contact [http://www.lparchaeology.com/cms/about-lp/contact L - P : Archaeology] who provide both training and custom ARK installations. ~~Test~~	+	As of the v1.0 release of ARK there is a set of data import tools within ARK. These tools speed up and improve the process of creating a concordance map between the source data and an ARK database. Never the less, using the tools will require a working knowledge of ARK's data structures. If you are unable to import your data or would like training in the ARK import tools, please contact [http://www.lparchaeology.com/cms/about-lp/contact L - P : Archaeology] who provide both training and custom ARK installations.

	==Overview==		==Overview==

@@ Line 3: / Line 3: @@
 ==Overview==
-The ARK import tools are designed to provide a means to import data from table based data. This can be either in the form of a series of tables from a relational database or from a spreadsheet. The tools map the fields int he data onto fields within the ARK data structure. Data can then be inspected before running an import.
+The ARK import tools are designed to provide a means to import data from table based data. This can be either in the form of a series of tables from a relational database or from a spreadsheet. The tools map the fields in the data onto fields within the ARK data structure. Data can then be inspected before running an import.
 The tools provide some join functionality and are intended to reduce the need for pre-processing of data where possible. Inevitably, there will be some need to pre-process data for import.

@@ Line 79: / Line 79: @@
 *'''Site Code''' - The system provides three options for the site code to be used in the import of each field. The simplest option is just to use the fixed site code specified in the CMAP. The second option is to use a code specified in a column of this table which will permit data from multiple sites to be imported from this field. Thirdly there is an option to get a site code from a joined table.
 ====Keys====
@@ Line 136: / Line 140: @@
 Specify the XMI itemkey and xmi itemval column for the XMI links.
 ===Extraction Tests and Execution===

← Older revision		Revision as of 20:36, 21 September 2010
Line 136:		Line 136:

	Specify the XMI itemkey and xmi itemval column for the XMI links.		Specify the XMI itemkey and xmi itemval column for the XMI links.
		+
		+
		+	===Extraction Tests and Execution===
		+
		+	Once you have registered a mapping into the database, this can be tested. The test will do a dry run on the import and show you a table of results that show the exact values to be added to the database for this extraction from the source db. It is vital that you very closely check this data to ensure that you have got your set up correct.
		+
		+	In addition, check for duplicates or otherwise mangled data.
		+
		+	Undoing an incorrectly specified import will require use of the phpMyAdmin tool and will require knowledge of SQL.
		+
		+	Bear in mind that in the case of Attributes of type B, the preview will most likely show a series of SQL statements indicating the additions to the look up table (and Aliases) that would be run.
		+

	[[category:administrator]]		[[category:administrator]]