------------ Builder_Item ------------ .. php:class:: Builder_Item Package: :doc:`Record\\Builder ` Build an item. .. php:const:: IS_PUBLIC .. php:attr:: _recordClass .. php:attr:: _settableProperties .. php:attr:: _elementTexts .. php:attr:: _fileMetadata .. php:method:: setElementTexts(array $elementTexts) Set the element texts for the item. :param array $elementTexts: .. php:method:: setFileMetadata(array $fileMetadata) Set the file metadata for the item. :param array $fileMetadata: .. php:method:: setRecordMetadata(array $metadata) Overrides setRecordMetadata() to allow setting the item type by name instead of ID. :param array $metadata: :returns: void .. php:method:: _addElementTexts() Add element texts to a record. .. php:method:: _replaceElementTexts() Replace all the element texts for existing element texts. .. php:method:: _addTags() Add tags to an item (must exist in database). .. php:method:: addFiles(string|Omeka_File_Ingest_AbstractIngest $transferStrategy, string|array $files, $options = Array) Add files to an item.
  • 'Url|Filesystem' => string|array If a string is given, this representsthe source identifier of a single file (the URL representing the file, orthe absolute file path, respectively). If an array is given, it assumesthat each entry in the array must be either an array or a string. If itan array, there are several default keys that may be present:
  • :param string|Omeka_File_Ingest_AbstractIngest $transferStrategy: This can either be one of the following strings denoting built-in transfer methods: 'Upload', 'Filesystem', 'Url' Or it could be an implemented Omeka_File_Ingest_AbstractIngest class. :param string|array $files: This can be a single string, an array of strings, or an array of arrays, depending on the parameters that are needed by the underlying strategy. Expected parameters for the built in strategies are as follows: .. raw:: html