Hi both,
First, Mathieu if you're still following this thread, I apologize that no one ever responded! I did reproduce the problem you describe at the time, and filed the following ticket so we can track it and hopefully fix it in a future release:
It seems I forgot to respond back on this thread!
Sasa, we'd like to see a fix for this included in a future release as well. As you may know, we depend on our community for support in prioritizing bug fixes and new features. While Artefactual commits time with every release to addressing as many bugs as we can, we also need to prioritize and fix the worst issues with the time we can invest. For other bugs and new features, our business model (in which we make all of AtoM and its related resources freely available under open licenses) means we rely on support either via code contributions (such as a pull request with a fix), or else development sponsorship (so we can prioritize fixing the issue for the next release). You can read more about how we maintain and develop AtoM here:
If this is a priority for your institution and you might like to sponsor a fix, feel free to contact me off-list and our team can prepare an estimate for you. Otherwise, we will try to address it in a future release, though we can make no promises as to if and when that will happen. Right now we are focused on finalizing the 2.6 release, and this issue is unfortunately not currently slated to be addressed in the upcoming release.
Regards,