Standardize file rename

[thekiefs]

Is your feature request related to a problem?

I find many DATs have terrible naming standards. I want to rename some of these according to recognized standards which would make it easier to read and parse/search. Some small examples:

Air-Sea Battle ~ Target Fun (Japan, USA) (En)
Air-Sea Battle (1977)(Atari - Sears)(NTSC)[aka Target Fun (Anti-Aircraft)][CX2602, 6-99802, 49-75102]
Battlezone (1983-05-12)(Atari)(JP-US)(proto)

For instance, for country renaming, I'd like to use ISO 3166 and rename (Japan, USA) to (JP, US), and ensure (JP-US) is changed to (JP, US).

Describe the solution you'd like

I understand this change has a ton of variables and preferences which I think modeling it similar to how MusicBrainz Picard handles this will lead to something extensible.

Additional context

No response

[emmercm]

A primary goal of Igir is to treat DATs as the source of truth, trusting that their information is complete and accurate. This is a monumental task for groups that maintain DATs, so it's a task that I leave to them.

Replaceable symbols could work, and Igir already has some, but they currently can't manipulate the game or ROM names. But I'm also not sure that I could ever provide all the desired replaceable symbols a person may want, knowing there are diverse personal preferences. For example, you might like uppercase alpha-2 codes, but maybe I want lowercase alpha-3 codes, and someone else wants title-cased full names. The same argument can be made for ISO 639 languages.

My current thought is: I think you'd be better served by a DAT manipulation tool, but I'm not sure one exists to fit your needs. SabreTools has a lot of options, but I don't think it has field find-and-replace. If you're only using Logiqx XML DATs, then maybe some relatively straightforward Python (or similarly concise language) might do the trick.

[thekiefs]

Thanks. If Igir isn't building into the DAT manipulation space, then I totally get how this wouldn't fit neatly within scope. I just thought that with some SabreTools overlap like DAT Parsing and renaming, identifying ROMs, structuring directories, and dir2dats--which blurs the lines even more--this might be a good use-case.

Re: your point on symbols, totally agree it's hard to provide all standards from day 1. I do think there are some more basic ones like 2-letter (ISO 639-1): en, fr, ee that are probably more common than the 3 letters. And ideally, it's built in a way that can just accept the standards directly rather than having to customize for each ISO standard.

Tbh I've found that Igir is the best thing out there for its CLI-first approach, ease of use, and portability and I'd rather not have to learn another application or change my workflow. SabreTools also doesn't work cleanly in my docker-first environment. Surprised that the release groups don't use Igir more to manage their workflows 😉