id,summary,reporter,owner,description,type,status,priority,milestone,component,version,resolution,keywords,cc,drp_resources,i_links,o_links,remaining_time,sprint 10304,Bug: Original metadata is unquoted and not safe to parse,rleigh,,"Affects 4.4+ Original metadata can potentially contain both = symbols (in both key and value) and can also contain newlines. Currently, when retrieving the original metadata, for example with: {{{ test User-Comment[0] Test test test test Entry entry entry Test test test test }}} this would result in {{{ test User-Comment[0]=Test test test test Entry entry entry Test test test test }}} With the current server and gateway code, there is no quoting, so the second two lines will not be associated with the first. It would be better if the data provided by the server was properly quoted so that the data is unabiguous and parsing can be robust. This could include: - surrounding key and value with quotes ("") - allowing quotes inside keys and values with escaping (\"") - allowing escaping of escaping (\\) The server can encode keys and values using this simple scheme. And the client/gateway code can decode it before presenting it to the user. Keys and values are between unquoted quotes. And the escaping can be stripped from the separated keys and values. Regards, Roger",task,new,critical,Metadata,OmeroPy,4.4.9,,,jburel florian.leitner@… java@…,,,,,