I am having no luck in attaching disk files to Fez records with the ‘File Upload’ facility, when creating image records from scratch (manually).


Moreover, it appears that no matter what type of record document type I create, and with any file mime type, I always receive the following error (logged to error_handler.log), whenever I attempt to attach a file by uploading:


Error when calling addDatastream :org.xml.sax.SAXException: Bad types (boolean -> class java.lang.String)



I have noticed nothing so far in the fez-users mailing-list threads that refers to any similar issues that others have experienced with respect to attaching files.  On the other hand, I have no problem adding URL links to records.  Also, I have been successful in using the batch upload facility (although I limited my test to a batch of four image files just to test).


My plan is to create an image collection of tiff files, with the intent of using Fez to create the customary ‘presmd’ and the thumbnail-, preview-, Web-, and archival streams associated with each attached image file.  It is necessary that I create manual records, for each collection record which is associated with two or more images, because some images serve as different datastreams or views (using the default Fedora disseminator for image/tiff) of the same object under a single title.  For this reason, aggregating the images (in quantities of two to five) within a single record is preferable to using the batch ingest facility for all except images singularly representing record content.  This also reflects a degree of augmented usability for the persons creating the content, as it would permit generating a single metadata record for two or more attached files, and to change only the descriptions of the individual files themselves.


Alternatively, I have tried generating a ‘multi-datastream” record within the Fedora admin utility and indexing it into Fez, which, for each original Fedora datastream, appears to generate the preservation metadata along with the various image byte streams, and then seems to assign these to appear as “attached files” under the new Fez record.


However, I have had only partial success with that procedure, because all metadata on the fedora record appears “lost” during the process—that is, no metadata (except perhaps title) show up in the respective fields of the Fez record object (I have this problem with ALL the Fedora demo objects, except for the image labels, indexed into Fez).  Also, in following the Fez-Wiki tutorial for creating an image collection, I assume that only one choice can be configured, when initially creating the collection or when editing (updating) the configuration for the collection to handle standard image files in my case:


     Image Version MODS 1.0


In the admin panel for managing XSD displays for XSD OAI DC, I see the displays for ‘Image MODS DC Display’ and ‘Image OAI DC Display’, but I do not know how to use the latter display, or whether of not that is what is needed, although the Fedora demos and my “homemade” Fedora objects contain a fully filled oai_dc:dc element.  Again, I assume that nothing needs to be changed, according to the tutorial.


When I indexed the new Fedora test object into Fez, a number of additional observations were made.  I ascertained the existence of each Fez-created tiff stream, and Fez seems to have directed Fedora to create these as ‘rosenwald_09670968+DS2+DS2.0 ‘, ‘rosenwald_09670968+DS2+DS2.0’, etc. (I tested them in an image viewer.)  On the record view and edit pages, Fez refers to these in the generated hyperlinks by the name DS1, DS2, etc. (from the DS label attribute values in the initial Fedora object).





It is my understanding that that Fez would substitute the Web stream (named as ‘rosenwald_09670968+web_DS1.jpg+web_DS1.jpg.0’, etc.) in the popup window, in place of the tiff image named above, when a user clicks on the first hyperlink to the right of each thumbnail.  Instead, in my case, Fez serves them as tiff images, when any user clicks on one of these hyperlinks immediately to the right of the thumbnails.


When logged in as administrator, the circular ‘disk’ icon appears with each linked stream (immediately left of the preservation metadata icon).  Each ‘disk’ is linked to a stream referred to as ‘archival_DS1’, ‘archival_DS2’, etc., in my case ,

For example:





I also assume that Fez would present the archival, or the original full tiff resource (in this case), only to the logged in administrator, by default, when the gold ‘disk’ icon is clicked.


After I index an such an object into Fez, for some reason, the link to the archival (the full tiff) datastream gets broken somehow, such that, when the administrator clicks on the ‘disk’ icon to retrieve the archival image, the resulting page contains only the response:


 An error has occurred in the Fedora Access Subsystem.



Again, I thought that the archival stream (tiff in my case) would be served, when the administrator clicks this ‘disk’ icon.  This problem does not seem to occur, when I use the batch ingest facility for individual image files (the expected behavior results).


Finally, and as mentioned initially, I cannot even attach files manually to records created with the batch utility itself, so that leaves me with no capability of associating more than one image file, even with a record previously created with the batch utility.  This also means that I would have to destroy a given record and re-create it, if any change in the single attached file is necessary.


As yet I have no reason to believe that Fez and Fedora are not configured correctly to communicate with each other and that one or more services are not available.  I am running Fez 1.3 rc3, with Fedora 2.1.1, PHP 5.2.0, MySQL 5.0.26 on Apache 2.24 on Windows XP SP2.  All sanity-checks were OK, and as stated or implied earlier, all ‘presmd’ and all thumb-, web-, preview-, and archive versions of the originals get generated and stored.


As an aside, does all content get stored as “managed” (Fedora type-M), as opposed as “external” or as “redirect”?  I noticed that I have only been successful in indexing in Fez a manually created Fedora object, the content of which is type M.


Any thoughts leading to a solution would be appreciated immensely.



Frederick Smith