Romm alreday has functionality for exporting platform metadata to a ES-DE gamelist.xml file, available currently only via API enpoint POST gamelist/export?platform_ids=. This is very useful for future proofing library scans and avoiding slow scrapers, as the file can be scanned back by Romm, but lacks a way to be triggered by the user other than an API call.
My proposal is to add an option, for example in config.yaml, to automatically trigger the export upon a successful library scan. It is very fast compared to scan itself, and would allow to keep all exports up to date, for people that want it, without cluttering the UI.
Romm alreday has functionality for exporting platform metadata to a ES-DE
gamelist.xmlfile, available currently only via API enpointPOST gamelist/export?platform_ids=. This is very useful for future proofing library scans and avoiding slow scrapers, as the file can be scanned back by Romm, but lacks a way to be triggered by the user other than an API call.My proposal is to add an option, for example in
config.yaml, to automatically trigger the export upon a successful library scan. It is very fast compared to scan itself, and would allow to keep all exports up to date, for people that want it, without cluttering the UI.