@ruebot Noted. Great investigating, @adam-vessey! :-) Thanks to both of you for your help.

I sent a [message to the Djatoka development list](https://sourceforge.net/p/djatoka/mailman/message/32092843/ "[djatoka-devel] OpenURLResponse not returning true JSON: Windows paths are misinterpreted "). That said, I just noticed that the last time someone posted there was **June 2012** -- and neither of those people ever received a response. Add to that the fact the [last official release of Adore-Djatoka](https://sourceforge.net/project/showfiles.php?group_id=236706 "Djatoka Files") was **June 2009** and it makes me a bit nervous as to whether anyone there is still available to help -- especially since this JSON problem (and the Windows-incompatibility it introduced) was [first reported in 2010](https://sourceforge.net/p/djatoka/mailman/message/26642839/ "[djatoka-devel] Metadata: Bad JSON + Number of levels 5 while it should have been 7!"). It seems development and support of this software has ceased for several years.

This leaves few alternatives to fixing the problem other than creating an Islandora patch. With this in mind, I've made another attempt at finding a workable solution (*NOTE:* It just passed Travis CI).

I agree that my previous search-and-replace was too broad. I've updated my jQuery so that it only targets the "imagefile" path. It checks to see whether backslashes exist. Only then does it replace the backslashes -- and only in the "imagefile" path. The rest of the string is left alone. In this way, only Windows installations should have this search-and-replace performed. Outside of Windows, I can't imagine a valid reason to have backslashes in a file path -- or an escaped character.

I hear your concern about what would happen if Djatoka ever addressed the bug on their end. However, I don't believe it would adversely affect my code, since it already assumes that a valid JSON object is being passed to it. Beyond that, there hasn't been a new release in 5 years; so if a new version of Adore-Djatoka was posted, I imagine the Islandora team would do a lot of testing before endorsing it to ensure that larger incompatibilities weren't getting introduced.