Cast Lists #256

ingoboerner · 2024-06-14T04:21:25Z

ingoboerner
Jun 14, 2024
Maintainer

Maybe we should invest into making cast lists (element <castList>) more "useful" (for research), e.g. by linking the individual <castItem> to <person> in <particDesc>.

An example :

<castList>
        <head>Personen.</head>
        <castItem><role>Emilia Galotti.</role></castItem>
        <castGroup rend="braced">
          <castItem><role>Odoardo,</role></castItem>
          <castItem><role>Claudia Galotti,</role></castItem>
          <roleDesc>Eltern der Emilia.</roleDesc>
        </castGroup>
        <castItem><role>Hettore Gonzaga,</role>
          <roleDesc>Prinz von Guastalla.</roleDesc></castItem>
        <castItem><role>Marinelli,</role>
          <roleDesc>Kammerherr des Prinzen.</roleDesc></castItem>
        <castItem><role>Camillo Rota,</role>
          <roleDesc>einer von des Prinzen Räten.</roleDesc></castItem>
        <castItem><role>Conti,</role>
          <roleDesc>Maler.</roleDesc></castItem>
        <castItem><role>Graf Appiani.</role></castItem>
        <castItem><role>Gräfin Orsina.</role></castItem>
        <castItem><role>Angelo,</role> und <role>einige Bediente.</role></castItem>
      </castList>

and the corresponding which is used when creating/labelling/... the network:

<particDesc>
        <listPerson>
          <person xml:id="der_prinz" sex="MALE">
            <persName>Der Prinz</persName>
          </person>
          <person xml:id="der_kammerdiener" sex="MALE">
            <persName>Der Kammerdiener</persName>
          </person>
          <person xml:id="conti" sex="MALE">
            <persName>Conti</persName>
          </person>
          <person xml:id="marinelli" sex="MALE">
            <persName>Marinelli</persName>
          </person>
          <person xml:id="camillo_rota" sex="MALE">
            <persName>Camillo Rota</persName>
          </person>
          <person xml:id="claudia" sex="FEMALE">
            <persName>Claudia</persName>
          </person>
          <person xml:id="pirro" sex="MALE">
            <persName>Pirro</persName>
          </person>
          <person xml:id="odoardo" sex="MALE">
            <persName>Odoardo</persName>
          </person>
          <person xml:id="angelo" sex="MALE">
            <persName>Angelo</persName>
          </person>
          <person xml:id="emilia" sex="FEMALE">
            <persName>Emilia</persName>
          </person>
          <person xml:id="appiani" sex="MALE">
            <persName>Appiani</persName>
          </person>
          <person xml:id="battista" sex="MALE">
            <persName>Battista</persName>
          </person>
          <person xml:id="orsina" sex="FEMALE">
            <persName>Orsina</persName>
          </person>
          <listRelation type="personal">
            <relation name="parent_of" active="#odoardo #claudia" passive="#emilia"/>
            <relation name="associated_with" active="#marinelli" passive="#der_prinz"/>
            <relation name="associated_with" active="#camillo_rota" passive="#der_prinz"/>
          </listRelation>
        </listPerson>
      </particDesc>

Just some observation/guesses:

the order of the "items" is different. In the <particDesc> "Prinz" is listed as first character; he speaks first; --> <person>elements are ordered by order they speak on stage (is this true for all plays, we could check that automatically). In the castList though we have a different order (by rank, status, random, how the author wanted it to be presented). To look at this ordering alone would be interesting, I guess.
The name of a character in a <castItem> might be different to the "Ansetzungsform" in the ´´. The "names"/"labels" of the characters in the <person>elements might be based on the speaker labels <speaker> in the <text>, but also might be not... The would contain the "name" of a character as intended by the author. At the moment we can not connect that to the individual <speaker> labels. Looking at the "name" of a character in the <castList> and comparing it to each value in distinct-values(//speaker[@who eq '{character-id}']) could be interesting.
Additional information that might be included in the , even though it might be marked up, like "traits", "age", ... whatever is not extractable at the moment (I mean, via the API), because the .../characters endpoint to my understanding is only taking information from <person xml:id="{character-id}".
Not all speaking characters might be mentioned in the <castList> as <castItem>; not all characters in the might "speak" in the play and thus might not be included in the

What we could do for a start is linking <castItem> to the respective <person> element with @corresp or vice versa, e.g.

Use @corresp on the <castItem>

<person xml:id="emilia" sex="FEMALE">
            <persName>Emilia</persName>
</person>

<castItem @corresp="#emilia"><role>Emilia Galotti.</role></castItem>

introduce actual ids for the <castItem>:

<castItem xm:id="{prefix}_emilia"><role>Emilia Galotti.</role></castItem>

and then

<person xml:id="emilia" sex="FEMALE" corresp="#{prefix}_emilia">
            <persName>Emilia</persName>
</person>

Option 2 would involve two edit operations but all relevant information would be connected to the <person> element, whereas option 1 is the less intrusive variant (1 edit and we are ready to go).

There could be a third option using some kind of <relation> but this does not really seem necessary at the moment (could be when wanting to record the type of relation, e.g. unclear, ...?) But maybe not start with things like that.

The question remains how to add this information, e.g. @corresp as in option 1.

At the ExploreCor TS I talked to @cmil about maybe re-using his "who is" GUI to make the connections of <castItem> and <person>? So, we seem to already have some tool that could be re-used for this annotation task..

So, what do you think about it?

(It is also somehow connected to #255)

cmil · 2024-06-14T18:53:47Z

cmil
Jun 14, 2024
Maintainer

Two quick comments:

Technically we probably do not need to link castItems and persons in two directions, i.e. with both @xml:id and @corresp on both sides. What would be the use case for that 2. step of linking that requires @xml:ids on castItems?
The epdacor-whois is highly specialised on the epdracor-sources and would have to be heavily modified to work in a more general context. But it can certainly serve as a model for newly developed UI that could handle the easier use case of linking an already existing particDesc with castItems.

2 replies

ingoboerner Jun 17, 2024
Maintainer Author

ad 1. I was just listing some options of how to link them, and did not mean, that we need to use all of them together. I would go for @corresp on the <castItem> and use the <person>s @xml:id for a start, so the first option.

lehkost Jun 17, 2024
Maintainer

If we decide to link them, this would be my preferred option, too.

ingoboerner · 2025-09-05T13:48:07Z

ingoboerner
Sep 5, 2025
Maintainer Author

<listPerson>
<person xml:id="emilia">....</person>
</listPerson>

<castList>
<castItem corresp="#emilia">gsdfgfd</castItem>
</castList>

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Cast Lists #256

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Replies: 2 comments 2 replies

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Select a reply

Uh oh!

Cast Lists #256

Uh oh!

Uh oh!

ingoboerner Jun 14, 2024 Maintainer

Replies: 2 comments · 2 replies

Uh oh!

cmil Jun 14, 2024 Maintainer

Uh oh!

ingoboerner Jun 17, 2024 Maintainer Author

Uh oh!

lehkost Jun 17, 2024 Maintainer

Uh oh!

Uh oh!

ingoboerner Sep 5, 2025 Maintainer Author

ingoboerner
Jun 14, 2024
Maintainer

Replies: 2 comments 2 replies

cmil
Jun 14, 2024
Maintainer

ingoboerner Jun 17, 2024
Maintainer Author

lehkost Jun 17, 2024
Maintainer

ingoboerner
Sep 5, 2025
Maintainer Author