Issue Details (XML | Word | Printable)

Key: MBS-631
Type: Improvement Improvement
Status: Closed Closed
Resolution: Fixed
Priority: Normal Normal
Assignee: Oliver Charles
Reporter: Brian Schweitzer
Votes: 1
Watchers: 3

If you were logged in you would be able to see more operations.
MusicBrainz Server

Add support for deprecating a relationship

Created: 24/Mar/10 01:48 PM   Updated: 30/Sep/13 11:03 AM  Due: 16/Sep/13   Resolved: 30/Sep/13 11:03 AM
Component/s: Edit system, Schema Change
Affects Version/s: None
Fix Version/s: Schema change, 2013-10-14

Issue Links:

 Description  « Hide

We ran into this when the OLGA AR was removed a while back. There was no way on mason (nor afaik on NGS, yet) to disable an AR without just entirely removing it.

Esp with composition-data Recording ARs which really should be Work ARs, and need to be moved over manually, it would seem we'll have at least a few ARs which need some way to disable adding new ones, while still allowing existing ARs to be displayed, edited, or removed. The ability to flag an AR as "disabled; don't show this AR on the add page, or allow new ones of this type to be created" would therefore seem like something we'll find really useful to have in there.

Sort Order: Ascending order - Click to sort in descending order
Aurélien Mino added a comment - 24/Mar/10 03:51 PM

I hope that composition-data Recording ARs won't need manual move, with the branch I'm working to initialize works (

But this feature is still interesting to have. E.g. for disabling the creation of new 'part of set' ARs post NGS.

nikki added a comment - 06/May/12 02:19 AM

nikki added a comment - 06/May/12 02:24 AM

Note: I'm not sure if the code I just put on codereview is enough to consider this fixed.

Oliver Charles added a comment - 08/May/12 09:37 AM

I don't consider this fixed, but I'm going to add a new related ticket.

Ian McEwen added a comment - 19/May/13 04:33 AM

Note: remaining work here should be for moving the deprecation to the DB. See

Ian McEwen added a comment - 09/Jul/13 01:05 AM

we should really do this formally in the DB next schema change.