List of plays and bindings to the name the Folger Shakespeare Library uses in their website, for use in and . The format of each entry is:
| Field | Description | ||
|---|---|---|---|
| scope=row | title | The play's title as it is commonly known. Probably not the full title as it appeared on the play's title page in any given edition, but the common name for it. Since this is the rule of thumb for Wikipedia article names too, this and the wikilink field could have been one if it wasn't for disambiguations and similar. You can think of the value of title as what comes after the horizontal pipe in a wikilink: | |
| scope=row | folgerid | The text string the Folger uses on their website for this play. It's a fairly straightforward play title → filesystem name type mapping, but it isn't consistent and therefore can't be automated. It also isn't really an id (as in identifier) in the strict sense, but it works kinda like one when you squint just right and the old version of the Folger website did have a real identifier for the plays (it just turned out to not be persistent). | |
| scope=row | wikilink | The page name on Wikipedia where the article about the play lives. This is the counterpart to the title field, and they could have been merged if it wasn't for disambiguations and such. You can think of the value of wikilink as what comes before the horizontal pipe in a wikilink: | |
| scope=row | keys | A list of names (keys) by which a user of can specify which play they mean. For most plays just giving the title would be good enough, but for several of the history plays it is incredibly tedious to keep repeating "Henry VI, Part 3" when there's an established shorthand like "3H6". Any number of names and aliases can be specified, although there must obviously be at minimum one; and too many aliases is a pain to both maintain and use. 2–3 per play is probably a good rule of thumb. |
All fields must be present and must contain a value. Additional fields can be safely added (they will just be ignored).
Apart from fixing errors that have crept in or future changes at the Folger, it is not anticipated that most editors will have a need to edit this configuration (it is not dynamic and it is nominally complete). And judging by previous experience it is very likely that changes to the Folger website will require a complete rewrite of the module anyway.