Difference between revisions of "Import descriptions and terms"

From ICA-AtoM
Jump to navigation Jump to search
 
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 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>
 
</div>
  
 
[[Category:User manual]]
 
[[Category:User manual]]

Latest revision as of 14:59, 16 October 2012

Please note that ICA-AtoM is no longer actively supported by Artefactual Systems.
Visit https://www.accesstomemory.org for information about AtoM, the currently supported version.

Main Page > User manual > Import/export > Import descriptions and terms

Select an XML fle to import
Select View Archival Description

ICA-AtoM provides an import functionality that can be used to import single archival descriptions, authority records, archival institutions and terms.

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)
  • EAC (authority records)
  • SKOS (hierarchical taxonomies)
  • CSV (comma separated values)


  1. In the main menu, hover your cursor over the "Import" menu and select "XML".
  2. Click Browse to select a file
  3. Click Import
  4. If the file is successfully uploaded, the page will show the elapsed time. If there are errors in the file, the page will display a message describing the errors. However, it should still be possible to edit and view the imported descriptions. You will need to review them carefully to determine whether the errors in the import file were serious enough to affect the display of the descriptions.
  5. Click the "View Archival Description" button in the button block to go to the view page of the highest level of description of the imported object(s) (i.e., the fonds description for an archival description or the top-level term in a hierarchical taxonomy). You will be able to view and edit this description and any child records just as you would if you had entered them in ICA-AtoM instead of importing them.

If you are importing large datasets please review the documentation on the Qubit-toolkit wiki: XML Import/Export. The first section discussed the use of command-line interface (CLI) as a tool for import.

You can also import SKOS files from the view page of a taxonomy term. Doing so will result in the highest level term in the SKOS file being imported as a child level of the term currently being viewed.

CSV import

ICA-AtoM Release 1.3 provides a CSV import functionality. A CSV file consists of a number of records (rows), that have identical fields, separated by commas. The CSV import function allows users to import data from a spreadsheet, or another database (as long as the export from the database is CSV format). To learn more about the CSV format see: Wiki CSV and scroll to the General functionality section to gain an introduction to CSV and relational databases.

For small data imports (CSV files with less than 1,000 rows) the CSV import located as a drop-down under the Import tab in the Main Menu can be used.

  1. In the main menu, hover your cursor over the "Import" menu and select "CSV"
  2. Click Browse to select a file
  3. Select the Type of information represented in the CSV file from the drop-down list (e.g., archival description, authority record, accessions or event)
  4. Click Import
  5. If the file is successfully uploaded, the page will show the elapsed time.If there are errors in the file, the page will display a message describing the errors.
  6. 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 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 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: 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.