Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refine mapping of text classes #13

Open
cmil opened this issue May 29, 2022 · 2 comments
Open

Refine mapping of text classes #13

cmil opened this issue May 29, 2022 · 2 comments

Comments

@cmil
Copy link
Member

cmil commented May 29, 2022

The original EarlyPrint documents assign the following values in their ep:subgenre elements:

  • CO
  • closet drama
  • comedy
  • dialogue
  • entertainment
  • history play
  • interlude
  • masque
  • preface to a collection of plays
  • preface to a collection of plays
  • tragedy
  • tragicomedy

In 97fa5ed the mapping of "comedy", "tragedy" and "tragicomedy" to their respective Wikidata IDs has been implemented. We should decide if and how to map the remaining subgenres.

@cmil
Copy link
Member Author

cmil commented May 2, 2024

@lucagiovannini7, @peertrilcke The DraCor API currently supports the text classes "Comedy", "Tragedy", "Tragicomedy", "Satyr play" and "Libretto" via their respective Wikidata IDs (see https://github.com/dracor-org/dracor-api/blob/0fe102e735708e4f3cfe3e736d54b23a3a1a9514/modules/config.xqm#L77). Should we

  1. just ignore the EarlyPrint ep:subgenres that are not exactly match those text classes,
  2. somehow map the at least some of the ep:subgenres to our text classes, or
  3. add more text classes to the DraCor API to support more ep:subgenres?

This may also be relevant for dracor-org/dracor-schema#52.

@peertrilcke
Copy link
Member

I would prefer a combination of 1 and 2: We ignore the corpus-specific EP subgenres (1). In addition, @lucagiovannini7 could successively make a careful adaptation of the obvious EP subgenres to the subgenres used by DraCor so far (2)
I lack a systematic approach to (3). Here we should define an extended controlled vocabulary in perspective. In my opinion, however, this is a larger and different task.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants