Re: [mb-users] Recording>Work>Work chain

Nicolás Tamargo de Eguren <[email protected]> Sun, 31 Aug 2014 22:45:42 +0300
Newsgroups gmane.comp.audio.musicbrainz.user
Message-ID <CAHSHD+WGQ2aQpTEr6bW6ovud4a0vmT2gJNQ5MTX0BnP6QFWADg@mail.gmail.com>
--===============2004178107==
Content-Type: multipart/alternative; boundary=20cf30266980b9ef8b0501f221ad

--20cf30266980b9ef8b0501f221ad
Content-Type: text/plain; charset=UTF-8

Just add the lyricist to the final work. He did write the lyrics after all
even if he didn't know at the time ;)
On 31 Aug 2014 22:43, "Robert Bihlmeyer" <[email protected]> wrote:

> Hi,
>
> if I enter a recording A of a song B that takes its lyrics from a poem
> C, I create recording A, works B (type song) and C (type poem). C points
> to an artist as its writer/lyricist, B points to a composer and to
> is-based-on C. A is-a-recording-of B.
>
> Viewing a medium containing the recording A, I am nicely shown the
> composer but not the lyricist. In other words, the chain is chased one
> level, but not two. I'd really like the poem's author to be show. She
> would be, if she had directly collaborated with the composer...
>
> A workaround would be to duplicate the lyricist relation in work B, but
> duplication and relationship clusters are frowned upon.
>
> These are other examples of a similar is-based-on relation:
>
> * Using the music of a song with different lyrics (derivative's lyricist
> should *replace* base's)
> * Using the music of a song with additional/translated lyrics
> (derivative's lyricist should be *added* to base's)
>
> Any thoughts?
>
> Robbe
>
> _______________________________________________
> MusicBrainz-users mailing list
> [email protected]
> http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-users
>

--20cf30266980b9ef8b0501f221ad
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr">Just add the lyricist to the final work. He did write the ly=
rics after all even if he didn&#39;t know at the time ;)</p>
<div class=3D"gmail_quote">On 31 Aug 2014 22:43, &quot;Robert Bihlmeyer&quo=
t; &lt;<a href=3D"mailto:[email protected]">[email protected]</a>&gt; w=
rote:<br type=3D"attribution"><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
<br>
if I enter a recording A of a song B that takes its lyrics from a poem<br>
C, I create recording A, works B (type song) and C (type poem). C points<br=
>
to an artist as its writer/lyricist, B points to a composer and to<br>
is-based-on C. A is-a-recording-of B.<br>
<br>
Viewing a medium containing the recording A, I am nicely shown the<br>
composer but not the lyricist. In other words, the chain is chased one<br>
level, but not two. I&#39;d really like the poem&#39;s author to be show. S=
he<br>
would be, if she had directly collaborated with the composer...<br>
<br>
A workaround would be to duplicate the lyricist relation in work B, but<br>
duplication and relationship clusters are frowned upon.<br>
<br>
These are other examples of a similar is-based-on relation:<br>
<br>
* Using the music of a song with different lyrics (derivative&#39;s lyricis=
t<br>
should *replace* base&#39;s)<br>
* Using the music of a song with additional/translated lyrics<br>
(derivative&#39;s lyricist should be *added* to base&#39;s)<br>
<br>
Any thoughts?<br>
<br>
Robbe<br>
<br>
_______________________________________________<br>
MusicBrainz-users mailing list<br>
<a href=3D"mailto:[email protected]">MusicBrainz-user=
[email protected]</a><br>
<a href=3D"http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-users"=
 target=3D"_blank">http://lists.musicbrainz.org/mailman/listinfo/musicbrain=
z-users</a><br>
</blockquote></div>

--20cf30266980b9ef8b0501f221ad--


--===============2004178107==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
MusicBrainz-users mailing list
[email protected]
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-users
--===============2004178107==--