-
Notifications
You must be signed in to change notification settings - Fork 0
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
feat: Merge Software by ID #55
base: main
Are you sure you want to change the base?
Conversation
@@ -12,6 +12,7 @@ | |||
create_software_version_observation, | |||
create_special_statistics_observation, | |||
create_user_observation, | |||
merge_software_by_id, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do it see it correctly, that the merging is something that the user has to do manually?
Could you please shortly describe the workflow this feature would allow?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Correct. This is strictly a manual process.
On identification of a duplicate extension - such as Discord Notifications
with and without space, or Miraheze Magic
and <extensionname-mirahezemagic>
, both of which we've actually encountered in this project - this would allow us to merge the two records. We call the first record "base" and the second "additional", and pass in the baseId
and additionalId
.
All of the software version records collected from wikibases that referred to the additional software would be shifted over to the base software. Any tags collected from Mediawiki for the additional would also be shifted to the base (avoiding duplicates, of course).
No description provided.