Files with spaces in filenames not found when testing import

[Mesuva]

We've found that during a batch status check that it will fail to find (many) files that have been imported because of spaces in their name.

For example, we'll see the message:

Note that there is a space between Booklet and 1
Here's the file in source website:

That same filename is what the file is exported as.

When it's imported into the batch, in the v8 file manager it looks like this:

It appears to have imported the title correctly, but the stored filename no longer has the space in it. In v8 I'm pretty sure the sanitize function used on filenames before importing the files is what is responsible for replacing the spaces with underscores.

So then when it comes to the batch matching, it seems to be trying to match up the files via their filename and not the title, and therefore doesn't find file due to the replaced spaces with underscores.

Our workaround in our last import was to go back to the original export.xml file and do some find and replaces in that for the files that we knew existed but weren't matching. Then we imported that and they were found fine.

I'd suggest the fix would be to apply the same sanitize function to the filename that is imported from the migration xml file. I did look for a fix myself but simply couldn't find where this is done.