User:Jesus2099/Merge Into Oldest MBID: Difference between revisions
(draft from https://musicbrainz.org/edit/37406035) |
(This page is a personal point of view. This is NOT an official MB Guideline.) |
||
| (6 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
'''This page is a personal point of view. This is NOT an official MB Guideline.''' |
|||
== MERGE INTO OLDEST [[MBID]] == |
== MERGE INTO OLDEST [[MBID]] == |
||
| Line 4: | Line 6: | ||
=== Why keeping oldest MBID? === |
=== Why keeping oldest MBID? === |
||
It’s about the third party stuff (web sites, files, user scripts) that might have been more numerous to store the older MBID. |
|||
Some of those will loose some functionality (like not being able to display related info it it looks for the new MBID in its database but they were more likely to have stored it with the older MBID). |
|||
* Keep most [[FlickrMachineTag]] working OK |
* Keep most [[FlickrMachineTag]] working OK |
||
* Keep most COLLECTION HIGHLIGHTER working OK |
* Keep most [//duckduckgo.com/?q=%22mb.+collection+highlighter%22 COLLECTION HIGHLIGHTER] working OK |
||
=== How to spot oldest MBID? === |
=== How to spot oldest MBID? === |
||
The lowest row ID indicates the oldest MBID. |
The lowest row ID indicates the oldest MBID. |
||
You can see this row ID when you hover your mouse over the '''Merge''' link in the entity sidebar, it’s the end of the URL. |
|||
[//duckduckgo.com/?q=%22mb.+merge+helpor+2%22 '''MERGE HELPOR 2'''], a user script of mine, allows to easily identify oldest MBID and target it on entity merge page. |
|||
---- |
|||
== PROBLEM EXAMPLES == |
|||
=== [//duckduckgo.com/?q=%22mb.+collection+highlighter%22 COLLECTION HIGHLIGHTER] === |
|||
[//musicbrainz.org/edit/41240735 Edit #41240735 - Merge recordings] |
|||
* [[recording:16d2e14a-2418-4a36-b0d0-3b592d827b84|Polovtsian Dances (Prince Igor) (Beginning)]] ([//musicbrainz.org/search/edits?order=asc&conditions.0.operator=%3D&conditions.0.field=recording&conditions.0.name=11,136,141&conditions.0.args.0=11136141 11,136,141]) is more recent (so it’s good that it’s not the target) but is highlighted by my COLLECTION HIGHLIGHTER |
|||
* [[recording:6c2b3dd3-1d65-4948-b979-b210a4bbd233|Danses Polovtsiennes "Le Prince Igor"]] ([//musicbrainz.org/search/edits?order=asc&conditions.0.operator=%3D&conditions.0.field=recording&conditions.0.name=1,590,412&conditions.0.args.0=1590412 1,590,412]) is more ancient so it’s good that it is the merge target. |
|||
As the source is more recent, there are less chances that its MBID has been used by some stuff than the MBID. |
|||
The MBID of target has been public for a long time already. |
|||
Once the merge pass, both URL will lead to same merged recordings but [[recording:16d2e14a-2418-4a36-b0d0-3b592d827b84]] will only be a shortcut to [[recording:6c2b3dd3-1d65-4948-b979-b210a4bbd233]] and a normal browse can never show it and it will appear as a missing track in the COLLECTION HIGHLIGHTER. |
|||
=== [[FlickrMachineTag|flickr machine tag]] problem example === |
|||
If an artist having associated MBID machine tag photos in flickr is merged into another one, a user script displaying those on the artist page will never be able to show them any more. |
|||
So this is important to target the MBID that has been public the longest, still the smaller row ID. |
|||
Latest revision as of 21:28, 4 January 2020
This page is a personal point of view. This is NOT an official MB Guideline.
MERGE INTO OLDEST MBID
Each entity has a primary public MBID and several secondary hidden MBID.
Why keeping oldest MBID?
It’s about the third party stuff (web sites, files, user scripts) that might have been more numerous to store the older MBID. Some of those will loose some functionality (like not being able to display related info it it looks for the new MBID in its database but they were more likely to have stored it with the older MBID).
- Keep most FlickrMachineTag working OK
- Keep most COLLECTION HIGHLIGHTER working OK
How to spot oldest MBID?
The lowest row ID indicates the oldest MBID.
You can see this row ID when you hover your mouse over the Merge link in the entity sidebar, it’s the end of the URL.
MERGE HELPOR 2, a user script of mine, allows to easily identify oldest MBID and target it on entity merge page.
PROBLEM EXAMPLES
COLLECTION HIGHLIGHTER
Edit #41240735 - Merge recordings
- Polovtsian Dances (Prince Igor) (Beginning) (11,136,141) is more recent (so it’s good that it’s not the target) but is highlighted by my COLLECTION HIGHLIGHTER
- Danses Polovtsiennes "Le Prince Igor" (1,590,412) is more ancient so it’s good that it is the merge target.
As the source is more recent, there are less chances that its MBID has been used by some stuff than the MBID. The MBID of target has been public for a long time already.
Once the merge pass, both URL will lead to same merged recordings but recording:16d2e14a-2418-4a36-b0d0-3b592d827b84 will only be a shortcut to recording:6c2b3dd3-1d65-4948-b979-b210a4bbd233 and a normal browse can never show it and it will appear as a missing track in the COLLECTION HIGHLIGHTER.
flickr machine tag problem example
If an artist having associated MBID machine tag photos in flickr is merged into another one, a user script displaying those on the artist page will never be able to show them any more. So this is important to target the MBID that has been public the longest, still the smaller row ID.
