TO BE EDITED - DESCRIPTION OF THE CSV FILE
When creating the CSV ingest file, all items in the file must be the same item type. For example, all images should be ingested in one file, all PDFs in another, etc.
All files to be ingested into OMEKA must be less 500MB. If you have files that are over that value, they will have to be adjusted. Please see Marguerite Grant for information.
Import files should all be in an internet repository. These files should have a URL pointing to their location. A relative link (local drive letter and directory) will not work with the ingest. You must link directly to the file, for example, http://juno.uml.edu/mjgtest/gringots.jpg would work. Verify that your files are accessible by copying and pasting the URL into a web browser and opening the file. For information about where to stage your files for ingest, please see Marguerite Grant.
Data must be normalized before it is imported. The first row of your CSV file contains the column names and every row must have the same number of columns. The columns will correspond to the types of data described in this document. Every row represents a single item. You cannot have any blank rows.
Examine your text to see if it contains commas. If it does, enclose the commas in double quotes (“,”). Some spreadsheet programs automatically convert text within a cell to be surrounded by double quotes when they are saved in a CSV format. Excel is one of these programs. To check this, open your CSV file in a plain text editor (notepad) verify the way additional commas are handled.
Data in the CSV file should make sense outside of the local content. If a record is looked at in a standalone context, the information should still make sense. For example in a collection about the Civil War, each record should contain a reference to the Civil War. This will make the items and the collection easier to find.
The CSV file may be created in Excel and then saved as a CSV document.