I am having two problems with xslt in dspace. One is related to the XMLUI and the other to the import script.
I recently set up an instance of dspace for a special collection that doesn't fit well into the dublin core schema. I created a unique metadata schema and altered the browse and sort indexes. I edited the messages.xml file accordingly and managed to get it running correctly last week. However, when I returned to the site this week, the UI is full of untranslated labels. For some reason, the UI is not processing the messages.xml file.
I don't know why it just stopped working. I had not touched anything related to dspace. The only thing I had done on the server was install python2.7 in parallel with the native python2.6. I checked the permissions on the file and checked the syntax within it. Everything appears in order. I tried rebuilding dspace, but the problem persists. I also cleared the Cocoon cache. Can anyone recommend another area to check?
There is a second problem with this instance. When I tried doing a batch import of items the script complained about the missing dublin_core.xml files for the items. But I am using the custom metadata file using the format (metadata_[scheme].xml), so it shouldn't need it. I added a dummy DC file just to see what would happen. The import script reads the dublin_core.xml file and complains about a premature end of file. If I add metadata using my custom scheme does the import script still require a dublin_core.xml file? What are some reasons that it complains about a premature end of file? I checked the file and it looks fine.
It's strange that both problems are related to reading xml files.
Digital Library Programmer Analyst
George Washington University