Note the default xmlns, and the un-bound prefix mods:..)
... but there's no reason to parse and reparse the document in the first place, when we can just munge the parsed data to match what we expect.
This wasn't a problem with the previous version of mods_display because we just stripped all the XML namespaces... it's also not clear that it's an actual problem with our production data because it all seems to use MODS as the default namespace, but better safe than sorry.
The string concatenation approach doesn't play nice with documents with a non-default prefix (resulting in MODs documents like:
Note the default xmlns, and the un-bound prefix
mods:
..)... but there's no reason to parse and reparse the document in the first place, when we can just munge the parsed data to match what we expect.
This wasn't a problem with the previous version of mods_display because we just stripped all the XML namespaces... it's also not clear that it's an actual problem with our production data because it all seems to use MODS as the default namespace, but better safe than sorry.