Issue Details (XML | Word | Printable)

Key: STYLE-97
Type: Task Task
Status: Reopened Reopened
Priority: Normal Normal
Assignee: Unassigned
Reporter: Alex Mauer
Votes: 5
Watchers: 4
Available Workflow Actions

RFC Sent
Operations

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

Move "medley" to an attribute of "performance of"

Created: 21/Feb/12 10:45 PM   Updated: 10/Sep/12 12:49 PM  Due: 29/Feb/12
Component/s: Relationships
Affects Version/s: None
Fix Version/s: None

Issue Links:
Relates
 


 Description  « Hide

"medley" should be an attribute of the "performance of" relationship instead of its own relationship. There is no way currently to relate a "live medley" performance, other than creating two separate ARs.

http://wiki.musicbrainz.org/User:Hawke/Proposal/Performance-medley

Once this attribute is created, all "medley of" relationships should be migrated to the new attribute. The wording should remain "medley of", "live medley of", etc. instead of "medley performance of", if possible.



Sort Order: Ascending order - Click to sort in descending order
nikki added a comment - 22/Feb/12 05:30 AM

Héctor Arroyo added a comment - 22/Feb/12 10:46 AM

I agree. In fact I was thinking about suggesting this myself.

<off-topic>Are we finally moving the style proposals to jira instead of the mailing list?</off-topic>


Nicolás Tamargo added a comment - 22/Feb/12 05:59 PM

[OT] No, but we're going to use it to track them. See http://musicbrainz.org/doc/Proposals


patate12 added a comment - 17/Jun/12 11:25 AM

Nicolás+OT+nikki+Héctor: It would be so much more efficient to have it all here as a whole, rather than needlessly splitting discussions, source of noise, mistakes and time lost.
ML could be used at the maximum, only to warn some people on new tickets for the ones who would feel doing so.


Philip Jägenstedt added a comment - 01/Aug/12 08:48 PM

RFC v2 at http://lists.musicbrainz.org/pipermail/musicbrainz-style/2012-July/016281.html

If that passes, http://wiki.musicbrainz.org/Medley_Relationship_Type should be deprecated so that no new such relationships can be added.


Héctor Arroyo added a comment - 10/Sep/12 12:36 PM - edited

Are there plans to implement this proposal? Deprecating the medley AR and convert the existing instances to an attribute of the performance AR with a bot at a later time sounds good to me

Could we send a RFV for this now, so we can prevent new "medley AR" from being created and the new attribute added?

It looks like there are only 65 "medley of" recording<->work ARs (!!), so manually fixing them doesn't seem like a big deal:

SELECT * FROM `link`WHERE link_type=244;
/* 0 rows affected, 65 rows found. Duration for 1 query: 0,078 sec. */