Hi again Franck,
Sorry for the long delay, but I've finally gotten an initial response from one of our developers. Unfortunately, the advice is limited - without digging deeply into the specification and the code to analyze what's possible, there's not too much we can add (and this deeper digging is beyond what we can provide for basic user forum support). Here's what I got back:
We don't have a multi-culture export at the moment, so this could only be achieved by changing the Symfony culture before the DC or EAD plugin is called to write the XML. But the "sf_culture" param can't be sent in the OAI URLs because it's not recognized as a legal argument.
As a workaround, if you can save and reuse the session, you can change the sf_culture in a non OAI URL and subsequent requests using that session will return the records in that culture. You can test it by using the same browser, going to ".../index.php/?sf_culture=fr" and then to ".../index.php/;oai?verb=ListRecords&metadataPrefix=oai_dc".
I'd guess that having multi-culture DC and EAD export would be the ideal solutions but, if multiple `<oai_dc:dc>` elements per record metadata are allowed, we could get the available cultures for each record and repeat that section per culture, which would be easier than multi-culture exports.
This is pretty similar to what I was already saying. As for the last part, I'm not sure that including multiple <oai_dc:dc> elements per record in a ListRecords response would be a proper response - and for a harvester, these would likely be treated as separate records with the same identifier, causing issues (as this is a non-standard approach). For these same reasons, we would be unlikely to add such features to AtoM. However, if you want to dig into this possibility, you might consider making a post in the OAI-PMH user forum, here:
You might also consider investigating and modifying the AtoM API instead - since the API is our own specification, there's more leeway, and we could probably devise a way to return all available cultures for a single record in a response. There is also already support for a culture param. See: