Agent and event: Further examples - Revision history

Dbalzer: /* The Event entity */

2011-06-21T12:24:20Z

‎The Event entity

Dbalzer: /* The Event entity */ xml links

2011-05-10T06:47:11Z

‎The Event entity: xml links

Dbalzer: /* The Event entity */

2011-04-05T08:44:52Z

‎The Event entity

Dbalzer: /* The Event entity */

2011-04-05T08:43:40Z

‎The Event entity

Dbalzer: /* The Event entity */

2011-04-05T08:26:13Z

‎The Event entity

Dbalzer: /* The Event entity */

2011-04-05T08:14:27Z

‎The Event entity

Dbalzer at 07:59, 5 April 2011

2011-04-05T07:59:43Z

Dbalzer: Created page with "''From the TC 372 Workshop Compendium'' ==The Agent entity== The Agent entity was deliberately left '''underspecified''' in EN 15907. This decision was made in order to fac..."

2011-04-05T07:31:29Z

Created page with "''From the TC 372 Workshop Compendium'' ==The Agent entity== The Agent entity was deliberately left '''underspecified''' in EN 15907. This decision was made in order to fac..."

New page

''From the [[TC 372 Workshop Compendium]]''

==The Agent entity==

The Agent entity was deliberately left '''underspecified''' in EN 15907. This decision was made in order to facilitate interoperability among filmographic information systems with different '''data models'''.

{| style="float: right; border: 1px solid #BBB; margin: .46em 0 0 .2em;"
|-
| valign="top" width="405px" |[[File:Agent-simple.png|400px]]<br />
<span style="font-size:8pt">
</span>

| valign="top" width="405px" |
Many bibliographic (and filmographic) database systems have used (and some are still using) a so-called '''flat file model'''. This is a model without many-to-many relationships (e.g. a person related to multiple works and a work related to multiple persons).

Data from flat-file systems typically has '''text fields''' filled '''with''' personal or corporate '''names''', where the field name (or MARC tag number) represents the relationship with the work.

Data from such systems can be translated straightforwardly into an EN 15907 data structure by using the Agent Name and Activity elements of an '''Agent Relationship'''
|}

@@ Line 109: / Line 109: @@
 {| height="20px" width="100%"
 |- style="text-align:center; "
-|<span style="color:#808080"> • Previous: [[Description levels: A worked example]] • Up: [[TC 372 Workshop Compendium|Contents]] •  Next: [[Common pitfalls in vocabulary selection]] • </span>
+|<span style="color:#808080"> • Previous: [[Description levels: A worked example]] • Up: [[TC 372 Workshop Compendium|Contents]] •  Next: [[Approaching the subject of a film work]] • </span>
 |-
 |}

@@ Line 67: / Line 67: @@
 This is a record about a '''decision event''' from the French ''commission de classification''. In addition to the decision event, it contains data about a '''publication event'''.
-The manifestation described in this record clearly differs from the first one added to our description of the work. [http://filmstandards.org/demo/xml/vitelloni_06_v.html Here is] a view of our record transformed from the [http://filmstandards.org/demo/xml/vitelloni_06.xml XML representation].
+The manifestation described in this record clearly differs from the first one added to our description of the work. [http://filmstandards.org/demo/xml/001/vitelloni_06_v.html Here is] a view of our record transformed from the [http://filmstandards.org/demo/xml/001/vitelloni_06.xml XML representation].
 |}
@@ Line 92: / Line 92: @@
 This is a possible way of '''encoding the outdoor filming locations''' found on the previous slide. We combine them in a '''single event''' as long as no precise dates of individual shootings are known.
-A transformed representation in the context of our description of ''I Vitelloni'' [http://filmstandards.org/demo/xml/vitelloni_07_v.html is here].
+A transformed representation in the context of our description of ''I Vitelloni'' [http://filmstandards.org/demo/xml/001/vitelloni_07_v.html is here].
 |}

@@ Line 102: / Line 102: @@
 | valign="top" width="405px" |
-Eventually, someone may have discovered the '''precise filming location''' for certain shots on the beach of Ostia.
+Eventually, someone may discover the '''precise filming location''' for certain shots on the beach of Ostia.
 In this case we could '''single out''' the Ostia production event, supplement it with geographical coordinates, and thus enable a map-based view of filming locations.

← Older revision		Revision as of 08:26, 5 April 2011
Line 68:		Line 68:

	The manifestation described in this record clearly differs from the first one added to our description of the work. [http://filmstandards.org/demo/xml/vitelloni_06_v.html Here is] a view of our record transformed from the [http://filmstandards.org/demo/xml/vitelloni_06.xml XML representation].		The manifestation described in this record clearly differs from the first one added to our description of the work. [http://filmstandards.org/demo/xml/vitelloni_06_v.html Here is] a view of our record transformed from the [http://filmstandards.org/demo/xml/vitelloni_06.xml XML representation].
		+	\|}
		+
		+	{\| style="float: right; border: 1px solid #BBB; margin: .46em 0 0 .2em;"
		+	\|-
		+	\| valign="top" width="405px" \|[[File:Vitelloni-prod-locations.jpg\|400px]]<br />
		+	<span style="font-size:8pt">
		+	Frame from: I Vitelloni (1953)
		+	</span>
		+
		+	\| valign="top" width="405px" \|
		+	Here we have some hints for a '''production event''', which may actually be treated as '''two or more''' production events.
		+
		+	Assuming that we have a vocabulary for production event types, we may choose to define a single event for the four '''filming locations''' and use ''outdoor shooting'' as the type name.
	\|}		\|}

← Older revision		Revision as of 08:14, 5 April 2011
Line 56:		Line 56:
	==The Event entity==		==The Event entity==

−	The Event entity in EN 15907 is in fact a class of six event types that can occur in the lifecycle of a cinematographic work.	+	The Event entity in EN 15907 is in fact a class of [[Events in the lifecycle of an audiovisual creation\|six event types]] that can occur in the lifecycle of a cinematographic work.
		+
		+	{\| style="float: right; border: 1px solid #BBB; margin: .46em 0 0 .2em;"
		+	\|-
		+	\| valign="top" width="405px" \|[[File:Event-decision.png\|400px]]<br />
		+	<span style="font-size:8pt">
		+	</span>
		+
		+	\| valign="top" width="405px" \|
		+	This is a record about a '''decision event''' from the French ''commission de classification''. In addition to the decision event, it contains data about a '''publication event'''.
		+
		+	The manifestation described in this record clearly differs from the first one added to our description of the work. [http://filmstandards.org/demo/xml/vitelloni_06_v.html Here is] a view of our record transformed from the [http://filmstandards.org/demo/xml/vitelloni_06.xml XML representation].
		+	\|}

← Older revision		Revision as of 08:43, 5 April 2011
Line 81:		Line 81:

	Assuming that we have a vocabulary for production event types, we may choose to define a single event for the four '''filming locations''' and use ''outdoor shooting'' as the type name.		Assuming that we have a vocabulary for production event types, we may choose to define a single event for the four '''filming locations''' and use ''outdoor shooting'' as the type name.
		+	\|}
		+
		+	{\| style="float: right; border: 1px solid #BBB; margin: .46em 0 0 .2em;"
		+	\|-
		+	\| valign="top" width="405px" \|[[File:Event-prod-xml.png\|400px]]<br />
		+	<span style="font-size:8pt">
		+	</span>
		+
		+	\| valign="top" width="405px" \|
		+	This is a possible way of '''encoding the outdoor filming locations''' found on the previous slide. We combine them in a '''single event''' as long as no precise dates of individual shootings are known.
		+
		+	A transformed representation in the context of our description of ''I Vitelloni'' [http://filmstandards.org/demo/xml/vitelloni_07_v.html is here].
		+	\|}
		+
		+	{\| style="float: right; border: 1px solid #BBB; margin: .46em 0 0 .2em;"
		+	\|-
		+	\| valign="top" width="405px" \|[[File:Ostia-2.jpg\|400px]]<br />
		+	<span style="font-size:8pt">
		+	</span>
		+
		+	\| valign="top" width="405px" \|
		+	Eventually, someone may have discovered the '''precise filming location''' for certain shots on the beach of Ostia.
		+
		+	In this case we could '''single out''' the Ostia production event, supplement it with geographical coordinates, and thus enable a map-based view of filming locations.
		+	\|}
		+
		+	{\| height="20px" width="100%"
		+	\|- style="text-align:center; "
		+	\|<span style="color:#808080"> • Previous: [[Description levels: A worked example]] • Up: [[TC 372 Workshop Compendium\|Contents]] • Next: [[Common pitfalls in vocabulary selection]] • </span>
		+	\|-
	\|}		\|}

← Older revision		Revision as of 07:59, 5 April 2011
Line 18:		Line 18:
	Data from such systems can be translated straightforwardly into an EN 15907 data structure by using the Agent Name and Activity elements of an '''Agent Relationship'''		Data from such systems can be translated straightforwardly into an EN 15907 data structure by using the Agent Name and Activity elements of an '''Agent Relationship'''
	\|}		\|}
		+
		+	{\| style="float: right; border: 1px solid #BBB; margin: .46em 0 0 .2em;"
		+	\|-
		+	\| valign="top" width="405px" \|[[File:Agent-include-1.png\|400px]]<br />
		+	<span style="font-size:8pt">
		+	</span>
		+
		+	\| valign="top" width="405px" \|
		+	The second method of handling an Agent Reference is to '''include descriptive data''' about the agent, encoded in a suitable format.
		+
		+	Evidently, this requires a '''relational data model''' in which data about agents (e.g. persons) is separated from film-related information, and joined via a many-to-many relationship.
		+
		+	Using this method, Agent descriptions can be '''transferred alongside''' with filmographic data. The drawback of this solution is that the person record may have to be transferred multiple times.
		+	\|}
		+
		+	{\| style="float: right; border: 1px solid #BBB; margin: .46em 0 0 .2em;"
		+	\|-
		+	\| valign="top" width="405px" \|[[File:Agent-ref-3.png\|400px]]<br />
		+	<span style="font-size:8pt">
		+	From: http://viaf.org/
		+	</span>
		+
		+	\| valign="top" width="405px" \|
		+	The third method of handling an Agent Reference is to '''include a reference''' to a network resource with information describing the agent.
		+
		+	In this example, the reference points to a VIAF (virtual authority file) record obtained from the Istituto Centrale per il Catalogo Unico (ICCU).
		+
		+	EN 15907 permits '''any combination of agent references'''. Thus, if a database has references to external authority files for the more famous people and only names for the less famous, then both types can be used in a single data exchange.
		+	\|}
		+
		+	{\| height="20px" width="100%"
		+	\|- style="text-align:center; "
		+	\|<span style="color:#808080"> • • • </span>
		+	\|-
		+	\|}
		+
		+	==The Event entity==
		+
		+	The Event entity in EN 15907 is in fact a class of six event types that can occur in the lifecycle of a cinematographic work.