Change Details

The SMILES properties (canonican SMILES, isomeric SMILES, CXSMILES) values all have characters that need encoding before passed as $1 in the formatter URL. Currently this causes broken links out the CDK Depict. Now, I have seen (cannot remember which property) a similar problem where the statement value needs preprocessing before it links out. I like to set this up for the SMILES properties, but do not have entirely clear to how to start this effort (besides finding what property was doing something like what I think may be the solution). A simpler alternative is that the 'formatter URL' approach allowed encoding the statement value before pass as $1.

The Wikidata SMILES properties (canonican SMILES, isomeric SMILES, CXSMILES) values all have characters that need encoding before passed as $1 in the formatter URL. Currently this causes broken links out the CDK Depict. Now, I have seen (cannot remember which property) a similar problem where the statement value needs preprocessing before it links out. I like to set this up for the SMILES properties, but do not have entirely clear to how to start this effort (besides finding what property was doing something like what I think may be the solution). A simpler alternative is that the 'formatter URL' approach allowed encoding the statement value before pass as $1.

The Wikidata SMILES properties (canonican SMILES, isomeric SMILES, CXSMILES) values all have characters that need encoding before passed as $1 in the formatter URL. Currently this causes broken links out the CDK Depict. Now, I have seen (cannot remember which property) a similar problem where the statement value needs preprocessing before it links out. I like to set this up for the SMILES properties, but do not have entirely clear to how to start this effort (besides finding what property was doing something like what I think may be the solution). A simpler alternative is that the 'formatter URL' approach allowed encoding the statement value before pass as $1.