I am having no luck in attaching disk files to
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
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
It is my understanding that that
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 ,
I also assume that
After I index an such an object into
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
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
Any thoughts leading to a solution would be appreciated immensely.