Database Type: MariaDB - 10.3.23-MariaDB-1:10.3.23+maria~focal
|Table / View||Children||Parents||Columns||Rows||Type||Comments|
This table is used to aggregate artefacts into groups. An artefact group consists of a name (see artefact_group_name) and a list of members (see artefact_group_member). It is up to the user to determine what an artefact group is meant to do functionally. Typically we assume that when one member of a group is transformed, all members of the group will also be transformed accordingly. The responsibility for such operations, however, lies downstream from the database (i.e., there are no database triggers involved with artefact groups).
This table stores basic information about the gross metrics of a manuscript. The user is able to specify an x/y-origin point for the start of the manuscript along with its proposed height and width in millimeters. The coordinate system begins top left, positive values increase while moving downward on the y-axis and while moving rightward on the x-axis. The PPI is currently fixed ad 1215 PPI to facilitate comparison of GIS data between manuscripts. All images should be scaled to this resolution before creating artefacts and ROIs that are placed upon the virtual manuscript.
This table contains the mapping information to correlate images of the same object via linear affine transformations. The mapping may only invlove a portion of either image as defined in the region_on_imageX columns.
The manuscript is an abstract placeholder that is given metadata via the manuscript_data table. This allows multiple editions of the same manuscript to be created, regardless of the naming scheme used. A manuscript will contain one or more text fragments (manuscript_to_text_fragment)
This table holds the polygon describing the region of the artefact in the coordinate system of its image. The image must first be scaled to the PPI defined in manuscript_metrics (1215 PPI by default).
Contains the bounding box and position metrics of a scribal font. Only used to calculate ROIs not yet set by the user.
This table holds a list of unique tokens that are sent to the user in order to confirm certain operations in the database. These tokens are intended to expire and a scheduled event in the database clears out all entries that are over 2 days old.
Each edition has one or more edition editors, which are the individual users working on that edition. Each edition editor has individual access rights that are specified here.
Gives a stream of fragments in a scroll in the right order
This table allows editors to attach commentary to a specific attribute of a sign interpretation.
Description of a reconstructed manuscript or combination.
Hierarchical list which defines parallel_types
This table stores the relationship between artefacts which make up a stack, meaning that they represent parallel layers in a stack. This could be:
The tables allow the creation of a sequence of artefacts: A = recto of layer 1 -> B = verso of layer 1 -> C = recto of recto of layer 2 -> D = verso of layer 2 … (where -> represents a record with the left as artefact_A and the right term as artefact_B)
A special case is marked by shared. We could, e.g., have A as verso and B as recto and additionally a subregion of B as shared to A.
Creates a pair of parallel_groups
This table links lines of an edition to a specific text fragment.
This table enables a connection to be made between parallel words in two different manuscripts.
ROI’s are linked to artefacts. To get the location of the ROI in the coordinate system of the “virtual manuscript, one must first apply the roi_position and then the position of the linked artefact. This can by done via the UDF nested_geom_transform.
Temporary table to link image catalog info with edition info until the SQE_image table is fully populated. Once that table is populated this one will become redundant. This was autogenerated from IAA data.
Created by Martin 17/03/29
This table defines an image. It contains referencing data to access the image via iiif servers, it also stores metadata relating to the image itself, such as sizing, resolution, image color range, etc. It also maintains a link to the institutional referencing system, and the referencing of the editio princeps (as provided by the imaging institution).
The text_fragment is an abstract placeholder that can be named via text_fragment_data, subsumed in a manuscript (manuscript_to_text_fragment), and joined with the lines that contitute it (text_fragment_to_line).
Contains a font file to be used for reconstructed text or overlays
This table joins with the main_action table to record all mutation actions taken regarding each edition.
This table links sign_interpretations to the words they are part of. This creates a bridge from the SQE data to the words stored in the QWB database.
This table stores the data for a request for a user to become an editor of an edition. It contains details about the permissions associated with the request.
Custom CSS to be applied to and attribute when it is visualized in an HTML context.
This table stores data pertaining to an artefact group, specifically its name.
A collection of coherent signs from a stream.
This is a temporary table to curate matches between the image catalog system and the SQE text fragments in a manuscript. It should eventually be deprecated in favor of matches inferred by spatial overlap on the virtual scroll of a the placement of a ROI linked to text transcription and an artefact linked to an image.
Connexts a parallel_group_pair with a parallel type
This table creates a connection between the references in the QWB database and the textual references within the SQE text system.
This table contains the IAA data for the editio princeps reference for all of their images.
This is an abstract placeholder allowing a multiplicity of interpretations to be related to each other by linking to the same sign_id.
This table stores attributes that can be used to describe a sign_interpretation. They are used in conjunction with a string value in the attribute_value, and any related numeric value can be added in the numeric_value column of the sign_interpretation_attribute table.
Linking of abstract signs to a line.
This stores metadata about the artefact.
This table is part of the temporary and preliminary catalog info matching system. There are three possibilities here: 1. confirmed = 0 and user_id IS NULL (the match has neither been confirmed nor rejected); 2. confirmed = 0 and user_id IS NOT NULL (the user with user_id has rejected the match); 3. confirmed = 1 and user_id IS NOT NULL (the user with user_id has confirmed the match as valid). The pairing confirmed = 1 and user_id IS NOT NULL is an invalid combination.
Table recording mutation actions (it can be used for infinite undo). This table stores the state of the action (rewound or not), the date of the change, and the edition that the action is associated with. The table single_action links to the entries here and describes the table in which the action occurred, the id of the entry in that table that was involved, and the nature of the action (creating a connection between that entry and the edition of the main_action, or deleting the connection between that entry and the edition of the main_action).
URL’s for the iiif image servers providing our images.
Links an entry in the text_fragment table to a reconstructed manuscript.
Provides a unique identifier for groups of sign_stream_sections representing parallel chunks of text
This table defines the properties of a unified grouping of text containing one or more lines.
Metadata pertaining to the description of a line of transcribed text.
The referencing system of the institution providing the images.
The line is an abstract placeholder which can receive definition via the line_data table. It must be nested in a text fragment (text_fragment_to_line) and will contain signs (line_to_sign)
This table provides the anchor for a complete scholarly edition of a manuscript. It also maintains the locked and public status of the edition.
This table describes the interpretation of signs in an edition. Currently this includes both characters, spaces, and formatting marks, it could perhaps also include other elements that one might want to define as a sign.
Every virtual manuscript is made up from artefacts. The artefact is a polygon region of an image which the editor deems to constitute a coherent piece of material (different editors may come to different conclusions on what makes up an artefact). This may correspond to what the editors of an editio princeps have designated a “fragment”, but often may not, since the columns and fragments in those publications are often made up of joins of various types. Joined fragments should not, as a rule, be defined as a single artefact within the SQE system. Rather, each component of a join should be a separate artefact, and those artefacts can then be positioned properly with each other via the artefact_position table.
Defines a font found in the scrolls. It connects to a font file and is referred by glyph info
The artefact status is a user definable placeholder to store information about how state of work on defining the artefact.
The specific string value associated with an attribute to describe some aspect of a sign_interpretation.
This table stores the data of all registered users,
The email is the unique identifier for each user (i.d., the username).
This table links a sign_interpretation to the ROI or ROIs it describes.
This table holds the polygon describing the ROI in its own coordinate system. The roi_position table situates the polygon in the coordinate system of the artefact.
Provides n:m connection between qwb words and sections of the sign stream.
This table stores user-definable work status messages that can be applied to various data tables. They are used to indicate the current status of editor curation for the data entry.
This table links sign_interpretations to the attributes that further describe the sign’s interpretation.
Contains kerning of glyph of a scribal font. Only used to calculated the position of signs not yet positioned by the user
This table holds data pertaining to nonlinear transforms between a set of two images. It stores a list of points in one image and the corresponding points in another image.
This table provides ordering data for the transcriptions. It provides a DAG linking sign_interpretations to each other.
This table holds the abstract IDs for the artefact group. An artefact group consists of a name (see artefact_group_name) and a list of members (see artefact_group_member). It is up to the user to determine what an artefact group is meant to do functionally. Typically we assume that when one member of a group is transformed, all members of the group will also be transformed accordingly. The responsibility for such operations, however, lies downstream from the database (i.e., there are no database triggers involved with artefact groups).