More option for "clean up" "renaming".

[jiucenglou]

Is your suggestion for improvement related to a problem? Please describe.

For an entry, a whatever-named PDF paper file is linked by automatic download.
The "clean up" "renaming" can rename that linked PDF paper file to predefined pattern, which is normally very welcome.
Later on, an image file that corresponds to Fig 6 of that PDF paper is downloaded and manually named to "pattern-fig6.jpg".
Or, a molecule corresponds to Fig 8 of that PDF paper is prepared and manually named to "pattern-fig8.xyz".
Then, the "auto link" can link that image file, and also that molecule file if xyz is manually added to "external file types", to the entry.
Now, the problem is when the "clean up" "renaming" is called upon again: that image file will be renamed to "pattern.jpg", and that molecule file will be named to "pattern.xyz".
I would like them to stay with the "-fig6" and the "-fig8" postfixes.

Describe the solution you'd like
A clear and concise description of what you want to happen.

I would like them to stay with the "-fig6" and the "-fig8" postfixes.
More option for "clean up" "renaming" could help.

1. For example, option to limit that to linked PDF files.
   After all, manuscript PDF is generally the first to be linked.
   This way, no additional txt, image, xyz, pdb files will be renamed.
   Additional files are generally manually prepared afterwards.
   For them to be "auto link"able, they have to be manually renamed anyway.

Additional context
Add any other context or screenshots about the feature request here.

[laky241]

/assign-me

[github-actions]

👋 Hey @laky241, thank you for your interest in this issue! 🎉

We're excited to have you on board. Start by exploring our Contributing guidelines, and don't forget to check out our workspace setup guidelines to get started smoothly.

In case you encounter failing tests during development, please check our developer FAQs!

Having any questions or issues? Feel free to ask here on GitHub. Need help setting up your local workspace? Join the conversation on JabRef's Gitter chat. And don't hesitate to open a (draft) pull request early on to show the direction it is heading towards. This way, you will receive valuable feedback.

Happy coding! 🚀

⏳ Please note, you will be automatically unassigned if the issue isn't closed within 90 days (by 18 April 2025). A maintainer can also add the "📌 Pinned"" label to prevent automatic unassignment.

[koppor]

This is a good issue to learn test-driven development.

At least, tests have to written for to reflect the issue. Edge cases need to be tested. There will be at least 10 different test cases IMHO. Single file, multipe files, with dash, with multiple dashes, dashes matching the generated filename, dashes not matching the generated filename, files following a pattern but not the configured one etc.