Package: File\Ingest

class Omeka_File_Ingest_AbstractIngest

An abstract class that handles ingesting files into Omeka and database.

Specific responsibilities handled by this class: - Parsing/validating arbitrary inputs that somehow identify the files to be ingested. - Iterating through the parsed file information, validating, and transferring each file to Omeka. - Inserting a new record into the files table that corresponds to the transferred file’s metadata. - Returning a collection of the records associated with the ingested files.

Typical usage is via the factory() method:

<code> $ingest = Omeka_File_Ingest_AbstractIngest::factory(‘Url’, $item); $fileRecords = $ingest->ingest(’’); </code>

property _item

protected Item

property _options

protected array

Set of arbitrary options to use when ingesting files.

property mimeType


The current validated file MIME type.

setItem(Item $item)

Set the item to use as a target when ingesting files.

factory($adapterName, $item, $options = array())

Factory to retrieve Omeka_File_Ingest_* instances.

  • $adapterName (string) – Ingest adapter.
  • $item (Item) –
  • $options (array) –



Retrieve the original filename of the file.

  • $fileInfo (array) –


_transferFile($fileInfo, $originalFilename)

Transfer the file to Omeka.

To indicate validation errors, Omeka_File_Ingest_InvalidException can be thrown at any time. To indicate other types of non-recoverable errors related to file ingest, throw Omeka_File_Ingest_Exception.

  • $fileInfo (array) –
  • $originalFilename (string) –

string Real path to the transferred file.


Ingest classes receive arbitrary information. This method needs to parse that information into an iterable array so that multiple files can be ingested from a single identifier.

Example use case is Omeka_File_Ingest_Upload.

  • $files (mixed) –



Set options for ingesting files.

  • $options (array) – Available options include: - ‘ignore_invalid_files’: boolean false by default. Determine whether or not to throw exceptions when a file is not valid. This can be based on a number of factors: whether or not the original identifier is valid (i.e. a valid URL), whether or not the file itself is valid (i.e. invalid file extension), or whether the basic algorithm for ingesting the file fails (i.e., files cannot be transferred because the files/ directory is not writeable). This option is primarily useful for skipping known invalid files when ingesting large data sets.

Ingest based on arbitrary file identifier info.

If this is an array that has a ‘metadata’ key, that should be an array representing element text metadata to assign to the file. See ActsAsElementText::addElementTextsByArray() for more details.

  • $fileInfo (mixed) – An arbitrary input (array, string, object, etc.) that corresponds to one or more files to be ingested into Omeka.

array Ingested file records.


Determine whether or not to ignore file ingest errors. Based on ‘ignore_invalid_files’, which is false by default.

_logException(Exception $e)

Log any exceptions that are thrown as a result of attempting to ingest invalid files.

These are logged as warnings because they are being ignored by the script, so they don’t actually kill the file ingest process.

  • $e (Exception) –
_createFile($newFilePath, $oldFilename, $elementMetadata = array())

Insert a File record corresponding to an ingested file and its metadata.

  • $newFilePath (string) – Path to the file within Omeka.
  • $oldFilename (string) – The original filename for the file. This will usually be displayed to the end user.
  • $elementMetadata (array) – See ActsAsElementText::addElementTextsByArray() for more information about the format of this array.



Retrieve the destination path for the file to be transferred.

This will generate an archival filename in order to prevent naming conflicts between ingested files.

This should be used as necessary by Omeka_File_Ingest_AbstractIngest implementations in order to determine where to transfer any given file.

  • $fromFilename (string) – The filename from which to derive the archival filename.


addValidator(Zend_Validate_Interface $validator)

Add Zend Framework file validators.

Emulates the way Zend Framework adds validators.

  • $validator (Zend_Validate_Interface) –


_validateFile($filePath, $fileInfo)

Validate a file that has been transferred to Omeka.

Implementations of Omeka_File_Ingest_AbstractIngest should use this to validate the uploaded file based on user-defined security criteria.

Important: $fileInfo may need to contain the following keys in order to work with particular Zend_Validate_File_* validation classes:

  • ‘name’: string filename (for Zend_Validate_File_Extension) If ZF is

unable to determine the file extension when validating, it will check the ‘name’ attribute instead. Current use cases involve saving the file to a temporary location before transferring to Omeka. Most temporary files do not maintain the original file extension. - ‘type’: string MIME type (for Zend_Validate_File_MimeType) If ZF is unable to determine the mime type from the transferred file. Unless the server running Omeka has a mime_magic file or has installed the FileInfo extension, this will be necessary.

  • $filePath (string) – Absolute path to the file. The file should be local and readable, which is required by most (if not all) of the Zend_Validate_File_* classes.
  • $fileInfo (array) – Set of file info that describes a given file being ingested.

bool True if valid, otherwise throws an exception.