Database Revisions

In addition to website restructuring, there have been a number of minor database changes behind the scenes. In order to lay the foundation for future development work, the LSDB team has added constraints to codify the relationship between database tables. In the process of adding these constraints, we identified transcription problems where events were listed without the correct theater code. We revealed thirteen events with incorrect metadata about the theaters they were performed at, which should now be correctly identified in database searches. From a user perspective, these will result in small changes to performance entries, such as the example seen below.

A screenshot of an event before database changes. No theater is listed under the entry.
A screenshot of the same performance after database changes. This performance now contains theatre information.
The top image depicts a performance entry before the database changes, in which no theatre is listed for the event. The bottom image depicts the same event, which now includes information on the theatre. Click here to  view the entry on the website.
Six more events are now listed as having been performed for the Royal Court, as their theater information has been correctly identified.

Screenshot of search for Whitehall or St. James with 203 results.

Screenshot of search for Whitehall or St. James with 209 results.
The search for Whitehall or St.James now produces 209 results, rather than 203. This is a result of 6 additional entries being edited to include the correct theater.

These minor changes were designed to set up a pipeline for larger developments that were in the works. These developments are now being threatened by cuts to our NEH funding. For those who are interested in reading more about these database structural changes, please visit our GitHub repository.

Leave a Reply

Your email address will not be published. Required fields are marked *