Bug #398
closederror in handling '&' in response to queries
0%
Description
There appears to be a problem in how Metacat handles entities like '&' in
responding to queries. If a data file name contains a '&' that gets encoded into
the triple linking the datafile to the datapackage. It get encoded as '&' in
the text, but when one looks at the response to an 'squery' the triple shows up as
"><subject>higgins.498</subject><relationship>isDataFileFor(96l</relationship><object>higgins.497</object></triple><triple><subject>higgins.498</subject><relationship>&</relationship><object>higgins.497</object></triple>"
actually, the relationship should have & after the "(961..."
Apparently, entities are not created when characters like '&' are pulled from
the database as the result of an 'squery'
Updated by Chad Berkley almost 23 years ago
fixed by adding a 'normalize' method to MetaCatUtil and calling that every time data is added to the triples in the resultset.