What to do when an album name officially changes?

Tags: #<Tag:0x00007fd2a4bcebd8> #<Tag:0x00007fd2a4bceb10> #<Tag:0x00007fd2a4bce8e0>

Not sure how to resolve this situation, as it’s the first I’ve seen, but also know it’s not unheard of. Would love some guidance on how to edit this without messing anything up.

An artist seems to have officially changed the name of an album, retroactively. The release in question: https://musicbrainz.org/release/7c5a2f6b-f4c1-4a84-b018-36aa6f4b00d7

The official listing, and seemingly only official place to get said release: https://photay.bandcamp.com/album/1st

Discogs has updated their listing from original title “Photay” to new title “1st”: https://www.discogs.com/release/6105599

Now, I would assume it would be okay to just change the title of the release to match the new title, and add a note in the Annotation field about the original title. However, I understand that sometimes the distinction between Release, Release Group and things like that can complicate matters. Would love some input from my fellow editors.

1 Like

It’s not an option I personally use much, but you can give releases aliases. So one option would be to change the name to the new name and add the old one as an alias that’s no longer in use.

It’s probably too late to find out if the artwork changed too. If the artwork did change, I would make a separate release with a different name in the same release group. This album has been out for a while, but I don’t know when the change was made. There may be a lot of people with outdated tags. I’m a bit on the fence whether that would be enough for a separate release.

Whatever you do, it is probably a good idea to add an annotation with information about the release title change. Things get lost in edit histories, and not everybody always checks them anyway.

2 Likes

perhaps this is the old man in me talking…

Release names don’t change.
There can be a new release (re-release, 2nd edition, anniversary edition, etc). But once it is out there, it is out there,

6 Likes

That argument would make sense for physical releases. On Bandcamp, though, it’s less clear.

1 Like

First, rename the release group to “Photay / 1st”. This is a convention we can use when an album has been released under more than one title. (Here’s an example.)

Don’t rename the original 2012 release. As @justcheckingitout pointed out, it was known only as Photay for eight years. All references to it are by that name. In 2012, Photay had no album called 1st.

Instead, treat the retitle as a reissue: Create a new release, and set the release date to the date of the retitling. (You can omit the day and even the month if you don’t have a reliable source for those).

I think 1st is a suitable search-hint alias for the original 2012 release, since the current Bandcamp page is ambiguous. I say this because the original Bandcamp URL redirects to the retitled page, but the retitled page has the old release date. That’s confusing for listeners, but we can help by doing our part.

2 Likes

This makes it sound like a combination of 2 releases, though. I would rename the release group to the current name, like we do with artists. Plus the alias and maybe a disambig

2 Likes

Also add lots of notes to the annotation about this name change. Details of this unusual history.

I agree with people above - this is a “reissue” with a new name, but in same Release Group. It existed for 8 years with the original name.

1 Like

This is perfectly put - we can track these kinds of (very interesting) changes even if it is a digital release.

Edit: according to the wayback machine the cover was the same

Edit 2: The way that the Wayback machine stops tracking the first url (/photay) at the end of March 2017, and then picks up the second url (/1st) at the same time, might be a quite precise indication of when it changed?
https://web.archive.org/web/changes/https://photay.bandcamp.com/album/photay
compared to
https://web.archive.org/web/changes/https://photay.bandcamp.com/album/1st

1 Like