Skip to content

MCR-3479 Harmonize and modernize MCRClassificationMappingEventHandler implementations #2596

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 7 commits into
base: main
Choose a base branch
from

Conversation

toKrause
Copy link
Contributor

@toKrause toKrause force-pushed the issues/MCR-3479_Harmonize-and-modernize-MCRClassificationMappingEventHandler-implementations branch 3 times, most recently from 555c0b9 to 84b4e63 Compare July 28, 2025 23:17
@toKrause toKrause force-pushed the issues/MCR-3479_Harmonize-and-modernize-MCRClassificationMappingEventHandler-implementations branch from 84b4e63 to 5e0b111 Compare July 29, 2025 07:55
@sebhofmann
Copy link
Member

#2467 already handles this

@toKrause
Copy link
Contributor Author

In #2467 there is still copious amounts of code duplication and some behavioral inconsistencies in MCRDefaultClassificationMapper and MCRMODSClassificationMapper (that certainly should be addressed in a separate PR)

@sebhofmann
Copy link
Member

Yes, but classification mapping is not done in EventHandlers anymore, since the Information/Metadata they create, can always be derived from existing metadata.
It would be better to clean up the duplicate Code when my branch is merged.

@toKrause toKrause marked this pull request as draft July 29, 2025 09:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants