Refactor long method importDatabase() in OvidImporter

[merlinymy]

Is your suggestion for improvement related to a problem? Please describe.
The importDatabase() method in OvidImporter has grown into a long method that mixes multiple functionalities including record splitting, per-field parsing, regex handling for Source fields, and final cleanup. This makes it harder to understand, test, and maintain.

Describe the solution you'd like
I’d like to refactor importDatabase() by extracting several small private helper methods (parseSource(), parseField(), normalizeContributors(), and resolveEntryType()) while preserving all current behavior and public APIs. The goal is purely to improve readability and separation of concerns, not to change functionality.

Additional context
This refactoring proposal was discussed and approved on the JabRef Gitter channel.

Would you prefer helper methods like these to be annotated with @VisibleForTesting and have direct unit tests, or should testing rely solely on the existing integration-level coverage for OvidImporter? I understand there are different schools of thought on this and would like to follow JabRef’s convention.

[merlinymy]

I’d like to work on this issue

[subhramit]

/assign @merlinymy

[github-actions]

👋 Hey @merlinymy, 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.

For questions on JabRef functionality and the code base, you can consult the JabRef Guru or ask on our Gitter chat.

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! 🚀

[github-actions]

⏰ Assignment Reminder

Hi @merlinymy, this is a friendly reminder about your assignment to this issue.

Warning

This issue will be automatically unassigned in 11 days if there's no activity.

Remember that you can ask the JabRef Guru or DeepWiki about anything regarding JabRef.
Additionally, our contributing guide has hints on creating a pull request and a link to our Gitter chat.

How to keep your assignment

If you are working on it, you can prevent automatic unassignment by:

• Submitting a draft pull request with your progress within 11 days
• Asking for the 📌 Pinned label if you need more time

We appreciate your contribution and are here to help if needed!

[koppor]

Would you prefer helper methods like these to be annotated with @VisibleForTesting and have direct unit tests, or should testing rely solely on the existing integration-level coverage for OvidImporter? I understand there are different schools of thought on this and would like to follow JabRef’s convention.

The former is preferred by JabRef. As long as the tests test something "meaningful" 😅