Import descriptions and terms - Revision history

Jessica: /* CSV import */

2012-10-16T20:59:38Z

CSV import

Jessica: /* CSV import */

2012-10-16T20:59:12Z

CSV import

Jessica: /* CSV import */

2012-10-16T20:58:15Z

CSV import

Jessica: /* CSV import */

2012-10-16T20:50:54Z

CSV import

Jessica at 23:05, 5 September 2012

2012-09-05T23:05:26Z

Jessica at 22:41, 30 August 2012

2012-08-30T22:41:02Z

Jessica at 22:40, 30 August 2012

2012-08-30T22:40:33Z

Jessica at 22:39, 30 August 2012

2012-08-30T22:39:34Z

Jessica at 23:49, 29 August 2012

2012-08-29T23:49:34Z

Jessica: /* CSV import */

2012-08-29T23:06:59Z

CSV import

@@ Line 51: / Line 51: @@
 If you are importing datasets and you want them to be compatible with ICA-AtoM standards (i.e., ISAD(G) and RAD), you will want to review the first few sections on CSV Import, specifically the section titled "Column Mapping", which provides archival description csv templates. See, the Qubit-toolkit wiki [https://www.qubit-toolkit.org/wiki/CSV_import here].
-If you are importing large datasets, then you will need to execute these actions using Command-Line Interface (CLI), follow the instructions found on the Qubit-toolkit wiki [https://www.qubit-toolkit.org/wiki/CSV_import here, it is the same wiki page as above. This is necessary because PHP execution limits restrict the number of records you can import using a web interface, see: [https://www.qubit-toolkit.org/wiki/PHP_script_execution_limits PHP execution limits]. We are currently working on a geo-scheduling feature for AtoM Release 2.0, which will allow these large import jobs to be run in the background.
+If you are importing large datasets, then you will need to execute these actions using Command-Line Interface (CLI), follow the instructions found on the Qubit-toolkit wiki [https://www.qubit-toolkit.org/wiki/CSV_import here], it is the same wiki page as above. This is necessary because PHP execution limits restrict the number of records you can import using a web interface, see: [https://www.qubit-toolkit.org/wiki/PHP_script_execution_limits PHP execution limits]. We are currently working on a geo-scheduling feature for AtoM Release 2.0, which will allow these large import jobs to be run in the background.
 </div>
 [[Category:User manual]]

@@ Line 49: / Line 49: @@
 # Use the browse buttons to locate your imported data (e.g., browse archival descriptions if you imported an archival description).
-If you are importing datasets and you want them to be compatible with ICA-AtoM standards (i.e., ISAD(G) and RAD), you will want to review the first few sections on CSV Import, specifically the section titled "Column Mapping", which provides archival description csv templates. See, the Qubit-toolkit wiki [https://www.qubit-toolkit.org/wiki/CSV_import here], it is the same page as above.
+If you are importing datasets and you want them to be compatible with ICA-AtoM standards (i.e., ISAD(G) and RAD), you will want to review the first few sections on CSV Import, specifically the section titled "Column Mapping", which provides archival description csv templates. See, the Qubit-toolkit wiki [https://www.qubit-toolkit.org/wiki/CSV_import here].
-If you are importing large datasets, then you will need to execute these actions using Command-Line Interface (CLI), follow the instructions found on the Qubit-toolkit wiki [https://www.qubit-toolkit.org/wiki/XML_import/export here]. This is necessary because PHP execution limits restrict the number of records you can import using a web interface, see: [https://www.qubit-toolkit.org/wiki/PHP_script_execution_limits PHP execution limits]. We are currently working on a geo-scheduling feature for AtoM Release 2.0, which will allow these large import jobs to be run in the background.
+If you are importing large datasets, then you will need to execute these actions using Command-Line Interface (CLI), follow the instructions found on the Qubit-toolkit wiki [https://www.qubit-toolkit.org/wiki/CSV_import here, it is the same wiki page as above. This is necessary because PHP execution limits restrict the number of records you can import using a web interface, see: [https://www.qubit-toolkit.org/wiki/PHP_script_execution_limits PHP execution limits]. We are currently working on a geo-scheduling feature for AtoM Release 2.0, which will allow these large import jobs to be run in the background.
 </div>
 [[Category:User manual]]

@@ Line 49: / Line 49: @@
 # Use the browse buttons to locate your imported data (e.g., browse archival descriptions if you imported an archival description).
-If you are importing datasets and you want them to be compatible with ICA-AtoM standards (i.e., ISAD(G) and RAD), you will want to review the first few sections on CSV Import, specifically the section titled "Column Mapping", which provides archival description csv templates. See, the Qubit-toolkit wiki [https://www.qubit-toolkit.org/wiki/CSV_import here].
+If you are importing datasets and you want them to be compatible with ICA-AtoM standards (i.e., ISAD(G) and RAD), you will want to review the first few sections on CSV Import, specifically the section titled "Column Mapping", which provides archival description csv templates. See, the Qubit-toolkit wiki [https://www.qubit-toolkit.org/wiki/CSV_import here], it is the same page as above.
 If you are importing large datasets, then you will need to execute these actions using Command-Line Interface (CLI), follow the instructions found on the Qubit-toolkit wiki [https://www.qubit-toolkit.org/wiki/XML_import/export here]. This is necessary because PHP execution limits restrict the number of records you can import using a web interface, see: [https://www.qubit-toolkit.org/wiki/PHP_script_execution_limits PHP execution limits]. We are currently working on a geo-scheduling feature for AtoM Release 2.0, which will allow these large import jobs to be run in the background.

@@ Line 51: / Line 51: @@
 If you are importing datasets and you want them to be compatible with ICA-AtoM standards (i.e., ISAD(G) and RAD), you will want to review the first few sections on CSV Import, specifically the section titled "Column Mapping", which provides archival description csv templates. See, the Qubit-toolkit wiki [https://www.qubit-toolkit.org/wiki/CSV_import here].
-If you are importing large datasets, then you will need to execute these actions using Command-Line Interface (CLI), follow the instructions found on the Qubit-toolkit wiki [https://www.qubit-toolkit.org/wiki/CSV here]. This is necessary because PHP execution limits restrict the number of records you can import using a web interface, see: [https://www.qubit-toolkit.org/wiki/PHP_script_execution_limits PHP execution limits]. We are currently working on a geo-scheduling feature for AtoM Release 2.0, which will allow these large import jobs to be run in the background.
+If you are importing large datasets, then you will need to execute these actions using Command-Line Interface (CLI), follow the instructions found on the Qubit-toolkit wiki [https://www.qubit-toolkit.org/wiki/XML_import/export here]. This is necessary because PHP execution limits restrict the number of records you can import using a web interface, see: [https://www.qubit-toolkit.org/wiki/PHP_script_execution_limits PHP execution limits]. We are currently working on a geo-scheduling feature for AtoM Release 2.0, which will allow these large import jobs to be run in the background.
 </div>
 [[Category:User manual]]

@@ Line 6: / Line 6: @@
 ICA-AtoM provides an import functionality that can be used to import single [[Glossary#Archival description|archival descriptions]], [[Glossary#Authority record|authority records]], [[Glossary#Archival institution|archival institutions]] and [[Glossary#Term|terms]].
-The following filetypes can be imported:
+The following file types can be imported:
 * EAD (hierarchical archival descriptions and associated authority records, archival institution descriptions and taxonomy terms)
 * Dublin Core XML, MODS XML (archival descriptions and associated taxonomy terms)

@@ Line 23: / Line 23: @@
 </div>
-If you are importing large datasets please review the documentation on the Qubit-toolkit wiki: [https://www.qubit-toolkit.org/wiki/XML_import/export XML Import/Export]. The first section discussed the use of command-line interface (CLI) as a tool for import/export.
+If you are importing large datasets please review the documentation on the Qubit-toolkit wiki: [https://www.qubit-toolkit.org/wiki/XML_import/export XML Import/Export]. The first section discussed the use of command-line interface (CLI) as a tool for import.
 <div class="note">

@@ Line 22: / Line 22: @@
 <div class="clearfix">
 </div>
 <div class="note">

@@ Line 32: / Line 32: @@
 </div>
 </div>
 == CSV import ==
@@ Line 49: / Line 51: @@
 If you are importing large datasets, then you will need to execute these actions using Command-Line Interface (CLI), follow the instructions found on the Qubit-toolkit wiki [https://www.qubit-toolkit.org/wiki/CSV here]. This is necessary because PHP execution limits restrict the number of records you can import using a web interface, see: [https://www.qubit-toolkit.org/wiki/PHP_script_execution_limits PHP execution limits]. We are currently working on a geo-scheduling feature for AtoM Release 2.0, which will allow these large import jobs to be run in the background.
 [[Category:User manual]]