Releases: LondonStageDB/data
Releases · LondonStageDB/data
v2.0
v2.0
Released October 9th, 2025.
A major release of the database that adds two new tables to serve XML files from the Text Creationship Partnership and incorporates corrections
to the Works and Author tables.
The corrections reflect a mixture of systematic and ad-hoc fixes to issues identified by LSDB researchers while incorporating TCP data; further correction of known issues is planned. Verify key details against primary source records whenever possible.
Enhancements
- Adds the TCP and WorksTCP tables to the database.
- Adds foreign key constraints linking TCP and WorksTCP tables to existing tables.
- Removes the unused WorksBak and AuthTemp tables.
- Updates the Author table with new Authors.
- Add birth and death dates for some authors.
- Adds newly identified Works to the Works table.
- Adds publication dates and known sources to some Works.
- Adds curated variant titles for some Works to WorksVariant to support better related work retrieval.
- Adds curated WorkIds for some Performances for better related work retrieval.
Bug fixes
- Consolidates duplicate Works and updates associated pointers in Authors, WorkAuthMaster,
WorksVariant, and Performances tables. - Corrects WorkIds for some Performances to reflect further research and verification.
- Enforces utf-8 encoding for all tables.
Documentation
- Adds a new data dictionary to the
docs/folder of this repository. - Updates
docs/schema.pngto reflect new table structure.
v1.1
Released April 4th, 2025.
The first release of the database after active development resumed in 2025. This revision incorporated minor changes that lay the foundation for future development work.
Bug fixes
- Corrects the TheatreCode of 13 events.
- Corrects the TheatreID of 7 events.
Enhancements
- Adds foreign key constraints between relational database tables.
- For example, it is no longer possible for Events to be held at a Theatre that does not exist in the Theatre table.
- These constraints will prevent the addition of values to one table that conflict with information in a corresponding table, a necessary safeguard as we expand the database.
v1.0
Created November 2022 for archiving in Zenodo.