Difference between revisions of "Relationships with objects in other databases"

From filmstandards.org

 
(2 intermediate revisions by the same user not shown)
Line 40: Line 40:
  
 
In this case, we include a reference to a record from a '''performing rights organisation''' as an aid to users doing rights research.
 
In this case, we include a reference to a record from a '''performing rights organisation''' as an aid to users doing rights research.
 +
|}
 +
 +
{| style="float: right; border: 1px solid #BBB; margin: .46em 0 0 .2em;"
 +
|-
 +
| valign="top" width="405px" |[[File:Waxman-cimarron-sacem.png|400px]]<br />
 +
<span style="font-size:8pt">
 +
from: http://www.sacem.fr/oeuvres/oeuvre/rechercheOeuvre.do
 +
</span>
 +
 +
| valign="top" width="405px" |
 +
This is what we would get if our '''musical works record''' for the Cimarron title song had a '''link to the''' French '''SACEM database'''. SACEM is the French performing rights organisation collecting royalties for musicians and rights holders.
 +
|}
 +
 +
{| style="float: right; border: 1px solid #BBB; margin: .46em 0 0 .2em;"
 +
|-
 +
| valign="top" width="405px" |[[File:Waxman-cimarron-gema.png|400px]]<br />
 +
<span style="font-size:8pt">
 +
from: https://online.gema.de/werke/
 +
</span>
 +
 +
| valign="top" width="405px" |
 +
... and this is what a link to GEMA, the German performance rights organisation, would produce.
 +
 +
Note that authors, composers, arrangers, as well as publishers or '''agents are identified by an IPI''' (Interested Party Identifier) number. Adding this number to a person authory record can also facilitate rights research.
 +
|}
 +
 +
{| height="20px" width="100%"
 +
|- style="text-align:center; "
 +
|<span style="color:#808080"> • Previous: [[Relating artifacts with events]] • Up: [[TC 372 Workshop Compendium|Contents]] •  Next: [[In-house usage scenarios]] • </span>
 +
|-
 
|}
 
|}

Latest revision as of 07:56, 20 May 2011

From the TC 372 Workshop Compendium

Taking the internet seriously

Film works are not only of interest because of their immediate content, but also for creative works that have been used in, or derived from them.

Event-metadata.png

Taking the idea of events as connectors a bit further, we could envision a resource that allows us to uniquely identify events. Such a resource would resemble what librarians call an authority file.

Using a publicly available identifier for the Basel film festival would allow machines to find other resources referring to this event. This could be other films shown at the festival, posters like the one seen in the previous session, or any other materials such as press articles or photographs.

Cimarron-poster.jpg

From: http://en.wikipedia.org/wiki/File:Cimarron1960.jpg

Though this is yet another poster, we will now look at a different relationship.

For this film from 1960, MGM commissioned composer Franz Waxman with creating the music. Waxman, a German emigré also known under his former name Franz Wachsmann, composed the score as one of the last works before his death in 1967.

Cimarron-musicrel.png

Assuming that we have a resource type for musical works associated with our filmographic records, then we can use the music description to include further references.

In this case, we include a reference to a record from a performing rights organisation as an aid to users doing rights research.

Waxman-cimarron-sacem.png

from: http://www.sacem.fr/oeuvres/oeuvre/rechercheOeuvre.do

This is what we would get if our musical works record for the Cimarron title song had a link to the French SACEM database. SACEM is the French performing rights organisation collecting royalties for musicians and rights holders.

Waxman-cimarron-gema.png

from: https://online.gema.de/werke/

... and this is what a link to GEMA, the German performance rights organisation, would produce.

Note that authors, composers, arrangers, as well as publishers or agents are identified by an IPI (Interested Party Identifier) number. Adding this number to a person authory record can also facilitate rights research.

• Previous: Relating artifacts with events • Up: Contents • Next: In-house usage scenarios