Linking right shares

In the MWN standard, communicating a right share chain (e.g. a collection share based on an original publisher share based on a manuscript share) is possible by using the elements HasOriginalPublisherShare and IsFollowerInTitleOf in the RightShare composite. The principles and some examples can be found here.

This article describes typical use cases.

Use case 1: one writer, one publisher and one administrator

The figure below illustrates the situation in which a music publisher P2 is the original publisher of a musical work written by writer P1, and where an administrator P3 collects royalties for that musical work.

Both P2’s original publisher share S2 and P3’s collection share S3 need to point back to the manuscript share S1 controlled by writer P1. This is done in the IsFollowerInTitleOf element by setting both the BaseRightShare and the ManuscriptShare/BaseRightShare elements to point to S1.

UC1.png

Use case 2: one writer, one publisher and one administrator (alternative)

The figure below illustrates a variant of use case 1, in which the collection share S3 of the administrator P3 is not based on P1’s manuscript share, but on P2’s original publisher share.

In this case, the IsFollowerInTitleOf/BaseRightShare points to S2, but the ManuscriptShare/BaseRightShare element still points to S1.

UC2a.png

In addition, the HasOriginalPublisherShare/OriginalPublisherShare element should be set to point to S2 to express that S3 is linked to an original publisher share, which would otherwise not be visible without looking up the type of the right share S2 linked in the IsFollowerInTitleOf/BaseRightShare element.

UC2b.png

Use case 3: one writer, one original publisher, one licensing publisher and one administrator

The figure below illustrates a situation in which a licensing publisher P3 is involved between the original publisher P2 and the rights holder P4 of the collection share S4, which is then based on P3’s licensing share S3. In this case, the licensing share S3 is set up like the collection share in use case 2:

  • The ManuscriptShare/BaseRightShare element points to the manuscript share S1;

  • The IsFollowerInTitleOf/BaseRightShare; and

  • The HasOriginalPublisherShare/OriginalPublisherShare elements point to the original publisher share S2.

As the collection share S4 is now based on the licensing share S3, its IsFollowerInTitleOf/BaseRightShare element points to S3, while the HasOriginalPublisherShare/OriginalPublisherShare element still points to S2 and the ManuscriptShare/BaseRightShare element points to S1.

A specific example for this use case will be described in a separate article.

UC3.png

Use case 4: one writer, one publisher and two administrators

The figure below illustrates a situation in which two administrators P21 and P22 are involved, e.g. two administrators collecting royalties in different territories. Their collection shares S21 and S22 are set up exactly as described in use case 2.

UC4.png

Use case 5: one writer, two publishers and two administrators

The figure below illustrates a variant of use case 4, in which the collection shares S22 and S23 of the two administrators P22 and P23 are based on different original publisher shares S12 and S13, respectively. S22 and S23 therefore differ from each other with regard to the pointers in the IsFollowerInTitleOf/BaseRightShare and HasOriginalPublisherShare/OriginalPublisherShare elements.

UC5.png

Search