The Metadata Editor's XSLT convert "&" to "&": XML's escaped version of the ampersand. However, to render the search results, we pass the metadata.xml file through two XSLT parsers: the first one will convert "&" back to "&" and the second one will throw an error since just the "&" is not allowed in valid XML.
I don't have the valid permissions to modify the files on nknportal.nkn.uidaho.edu, where the search result rendering XSLT's still are. So I can't try to fix the issue. I think using "disable-output-escaping" or getting rid of the current "disable-output-escaping" statement might work, but I am unable to try without proper permissions.
The Metadata Editor's XSLT convert "&" to "&": XML's escaped version of the ampersand. However, to render the search results, we pass the metadata.xml file through two XSLT parsers: the first one will convert "&" back to "&" and the second one will throw an error since just the "&" is not allowed in valid XML.
I don't have the valid permissions to modify the files on nknportal.nkn.uidaho.edu, where the search result rendering XSLT's still are. So I can't try to fix the issue. I think using "disable-output-escaping" or getting rid of the current "disable-output-escaping" statement might work, but I am unable to try without proper permissions.