In Progress : SLR : Improved study.yml format and terminology alignment so far

[faneeshh]

Closes #12642 (hopefully)

This is basically a continuation of the work done in #13844. I'm starting with the foundational schema changed for the improved SLR support and I'm currently just gonna focus on getting the infrastructure right before diving into the actual fetcher logic.

Progress so far in the 1st Commit :

Terminology Alignment : Renamed StudyDatabase to StudyCatalog across the model and logic to match the UI and align with the domain language used in the repository
Schema Versioning : Added the version field to the Study model to support SEMVER (v2.0) which I feel is necessary for the migration

I'm attaching this rough sketch of how the data flow changes between the legacy format and the v2 format. I'm planning on creating a Migrator and string to string integration tests to ensure we don't break existing user studies

Checklist

• I own the copyright of the code submitted and I license it under the MIT license
• I manually tested my changes in running JabRef (always required)
• [/] I added JUnit tests for changes (if applicable)
• [/] I added screenshots in the PR description (if change is visible to the user)
• [/] I added a screenshot in the PR description showing a library with a single entry with me as author and as title the issue number
• [/] I described the change in CHANGELOG.md in a way that can be understood by the average user (if change is visible to the user)
• I checked the user documentation for up to dateness and submitted a pull request to our user documentation repository

[faneeshh]

I've added the reason field directly into the StudyCatalog model. While it's not fully wired into the fxml yet in this specific commit I felt like having it in the data model would make sure that upcoming StudyYamlMigrator can handle the field mapping consistently from the start.

[github-actions]

Your pull request conflicts with the target branch.

Please merge with your code. For a step-by-step guide to resolve merge conflicts, see https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line.

[subhramit]

For submodule conflicts see https://devdocs.jabref.org/code-howtos/faq.html#submodules

[subhramit]

Refs #14170

[koppor]

I think, its OK for me to drop support for the old format. If anyone rasies their voice rearging this, we can work on this.

One reason for this: the current code does not keep datastructrures for the v1 format, it just updates to the new one.

[koppor]

Superficially, this PR should also include the other fixes outlined at #13844 (comment)

[testlens-app]

✅ All tests passed ✅

🏷️ Commit: 2573254
▶️ Tests: 10195 executed
⚪️ Checks: 49/49 completed

---

Learn more about TestLens at testlens.app.

[calixtus]

Whts the status here?

[faneeshh]

Whts the status here?

The Migrator is handling the v1 to v2 conversion automatically on read and the tests are passing as well. I do still have to extend StudyQuery to support catalogSpecific map for per-catalog native query overrides and also add the string to string tests that @koppor pointed out were missing from the original PR.

I had finals going on at college so didn't really get much time to work on it in a while. I can possibly work on it next week.