We do regular batch uploads of electronic theses and dissertations, pulling both metadata another database. The metadata (especially the abstracts) often contains entity references when we get it. After we upgraded to 1.5, our content people started noticing that these references were not being translated in the item display -- that is, we see "<" where we'd prefer to see a less-than sign. They don't THINK this was happening before the upgrade, but we're not entirely sure.
Checking the html source, we found that the entities were be mangled by the translation of the ampersand into yet another entity; that is, in the source, the poor would-be less-than sign reads "&lt;". The entities are stored properly in the metadatavalues table; so, somewhere between there and the browder, dspace is promiscuously translating ampersands into entities. I understand that entities are allowed in metadata, buy haven't been able to find much information on the matter. Is anyone else having this problem? Are we just missing a config setting somewhere? Interestingly, when the metadata is edited, the references are translated into literals in the editing text boxes, and get saved back to the database in their pure forms; so just opening the item for editing and then saving it fixes the record. Thanks, Bill Bill Anderson Software Developer Digital Library Development Georgia Tech Library "The chance of bread falling with the buttered side down is directly proportional to the price of the carpet." ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
