Difference between revisions of "In-house usage scenarios"

From filmstandards.org

(Created page with "''From the TC 372 Workshop Compendium'' Why is it that most cinematheques collect various things in addition to moving images? {| style="float: right; border: 1px solid #BB...")
 
Line 5: Line 5:
 
{| style="float: right; border: 1px solid #BBB; margin: .46em 0 0 .2em;"
 
{| style="float: right; border: 1px solid #BBB; margin: .46em 0 0 .2em;"
 
|-  
 
|-  
| valign="top" width="405px" |[[File:Event-metadata.png|400px]]<br />  
+
| valign="top" width="405px" |[[File:Krimskrams.jpg|400px]]<br />  
 
<span style="font-size:8pt">
 
<span style="font-size:8pt">
 
</span>
 
</span>

Revision as of 14:38, 20 May 2011

From the TC 372 Workshop Compendium

Why is it that most cinematheques collect various things in addition to moving images?

Krimskrams.jpg

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.

• Previous: Relationships with objects in other databases • Up: Contents • Next: ....