Getting Along with Relational Databases
Both relational databases (RDBs) and XML have strengths and weaknesses as data storage and modeling systems. Most researchers working with historical and literary data in the humanities would argue for the superiority of XML, since it allows unlimited nesting, linking, and complexity. Relational dat...
Saved in:
| Main Author: | |
|---|---|
| Format: | Article |
| Language: | deu |
| Published: |
Text Encoding Initiative Consortium
2022-02-01
|
| Series: | Journal of the Text Encoding Initiative |
| Subjects: | |
| Online Access: | https://journals.openedition.org/jtei/3874 |
| Tags: |
Add Tag
No Tags, Be the first to tag this record!
|
| _version_ | 1832578471083114496 |
|---|---|
| author | Martin Holmes |
| author_facet | Martin Holmes |
| author_sort | Martin Holmes |
| collection | DOAJ |
| description | Both relational databases (RDBs) and XML have strengths and weaknesses as data storage and modeling systems. Most researchers working with historical and literary data in the humanities would argue for the superiority of XML, since it allows unlimited nesting, linking, and complexity. Relational database proponents claim superior querying and processing speed, although recent advances in XML languages and tools have eroded that advantage. Nevertheless, RDBs remain popular and are widely used, particularly in the early stages of projects where resources and metadata are being collected, and projects may end up with both an RDB and an XML document collection. Programmers must then integrate these distinct forms of data when building project outputs. This article discusses the Digital Victorian Periodical Poetry (DVPP) project, where metadata on about 15,000 poems from nineteenth-century periodicals is captured in a MySQL database, and periodically exported to create a TEI file for each poem. Many of the poems are then transcribed and encoded. The canonical source of metadata is the RDB, while the canonical source of textual data is the TEI file. Metadata in the TEI files must be periodically updated from the RDB, without disturbing the textual encoding. Changes to the RDB data may result in changes to the id and filename of the related TEI file, so any existing TEI data is migrated to a new file, and the Subversion repository must be appropriately updated. All of this is done with XSLT and Ant. |
| format | Article |
| id | doaj-art-093479488a4e486cbd8d5568352a3435 |
| institution | Kabale University |
| issn | 2162-5603 |
| language | deu |
| publishDate | 2022-02-01 |
| publisher | Text Encoding Initiative Consortium |
| record_format | Article |
| series | Journal of the Text Encoding Initiative |
| spelling | doaj-art-093479488a4e486cbd8d5568352a34352025-01-30T13:56:39ZdeuText Encoding Initiative ConsortiumJournal of the Text Encoding Initiative2162-56032022-02-011410.4000/jtei.3874Getting Along with Relational DatabasesMartin HolmesBoth relational databases (RDBs) and XML have strengths and weaknesses as data storage and modeling systems. Most researchers working with historical and literary data in the humanities would argue for the superiority of XML, since it allows unlimited nesting, linking, and complexity. Relational database proponents claim superior querying and processing speed, although recent advances in XML languages and tools have eroded that advantage. Nevertheless, RDBs remain popular and are widely used, particularly in the early stages of projects where resources and metadata are being collected, and projects may end up with both an RDB and an XML document collection. Programmers must then integrate these distinct forms of data when building project outputs. This article discusses the Digital Victorian Periodical Poetry (DVPP) project, where metadata on about 15,000 poems from nineteenth-century periodicals is captured in a MySQL database, and periodically exported to create a TEI file for each poem. Many of the poems are then transcribed and encoded. The canonical source of metadata is the RDB, while the canonical source of textual data is the TEI file. Metadata in the TEI files must be periodically updated from the RDB, without disturbing the textual encoding. Changes to the RDB data may result in changes to the id and filename of the related TEI file, so any existing TEI data is migrated to a new file, and the Subversion repository must be appropriately updated. All of this is done with XSLT and Ant.https://journals.openedition.org/jtei/3874TEI and non-XML technologiesTEI and beyond: interactionsinterchangeintegrations and interoperabilityTEI environments and infrastructures |
| spellingShingle | Martin Holmes Getting Along with Relational Databases Journal of the Text Encoding Initiative TEI and non-XML technologies TEI and beyond: interactions interchange integrations and interoperability TEI environments and infrastructures |
| title | Getting Along with Relational Databases |
| title_full | Getting Along with Relational Databases |
| title_fullStr | Getting Along with Relational Databases |
| title_full_unstemmed | Getting Along with Relational Databases |
| title_short | Getting Along with Relational Databases |
| title_sort | getting along with relational databases |
| topic | TEI and non-XML technologies TEI and beyond: interactions interchange integrations and interoperability TEI environments and infrastructures |
| url | https://journals.openedition.org/jtei/3874 |
| work_keys_str_mv | AT martinholmes gettingalongwithrelationaldatabases |