# Extra backslashes in MARC fields after OpenRefine TSV export

**URL:** https://forum.openrefine.org/t/extra-backslashes-in-marc-fields-after-openrefine-tsv-export/2748
**Category:** Running OpenRefine
**Created:** [March 12, 2026, 9:26am UTC](https://forum.openrefine.org/t/extra-backslashes-in-marc-fields-after-openrefine-tsv-export/2748 "2026-03-12T09:26:05Z")
**Posts on this page:** 1
**Showing post:** 1

<div class="post-metadata">

### Author: ![Shivani\_Thakur](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.openrefine.org/shivani_thakur/32/1834_2.png) [@Shivani\_Thakur](https://forum.openrefine.org/u/Shivani_Thakur)
#### Post date: [March 12, 2026, 9:26am UTC](https://forum.openrefine.org/t/extra-backslashes-in-marc-fields-after-openrefine-tsv-export/2748/1 "2026-03-12T09:26:06Z")

</div>

I’m working with MARCEdit and OpenRefine and running into an issue with backslashes.

Here’s my workflow:

1. I export MARC data from MARCEdit in JSON format using the “Export for OpenRefine” option.

2. I upload that JSON file into OpenRefine, clean the data, and then export it as a TSV.

3. I re‑import the TSV back into MARCEdit using the “Import from OpenRefine” option.

The problem: after re‑import, every backslash in the MARC fields is doubled. For example, the correct 020 field should look like:

=020 \\$a9789351611066

But after import it becomes:

=020 \\\\$a9789351611066

Has anyone else encountered this? Is there a way to configure OpenRefine’s TSV export (or MARCEdit’s import)?

I am using OpenRefine version 3.10.0

And my colleague is using version 3.5.1, and in that, we are not getting any error like this.

---

_[View the full topic](https://forum.openrefine.org/t/extra-backslashes-in-marc-fields-after-openrefine-tsv-export/2748)._