Skip to content
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

ConceptMap for migrating from one version to another #19

Open
jpwiedekopf opened this issue Feb 21, 2022 · 1 comment · Fixed by #20
Open

ConceptMap for migrating from one version to another #19

jpwiedekopf opened this issue Feb 21, 2022 · 1 comment · Fixed by #20
Assignees
Labels
enhancement New feature or request

Comments

@jpwiedekopf
Copy link
Member

The information obtained by computing the difference graph, as well as the vicinity graph, can be used as the basis for a semi-automatic ConceptMap generation, so that data coded with one version can be migrated to the newer version.

This feature was suggested by @hannesUlrich

@jpwiedekopf jpwiedekopf self-assigned this Feb 21, 2022
@jpwiedekopf jpwiedekopf added this to the v1.2.0 milestone Feb 21, 2022
@jpwiedekopf jpwiedekopf added the enhancement New feature or request label Feb 25, 2022
@jpwiedekopf
Copy link
Member Author

Feedback from Cora has made me question the current implementation of ConceptMap. The use case for mapping in case of additions is extremely slim at best, and poses significant challenges for generating the auto-mapped concepts. Automapping should only be supported for deletions, while UI for adding arbitrary mappings should be mapped.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant