Overview of tables - eba-diary/Travelogues-db-conversion GitHub Wiki
The three main tables are publications
, travelers
, and contributions
. If you are simply editing publication or traveler information, you don't need to look at any tables other than these three.
Important: You will never need to manually assign the id
column of anything in these tables. They are automatically assigned.
publications
Each row in the publications
table represents a publication, usually a book. Every column can be NULL except for id
. Each have the following rows:
id
- An auto-assigned, unique ID numbertitle
- Publication titletravel_dates
- A human-readable string representing travel dates that the publication describes. The format mimics how travel dates appear in Kalfatovik.travel_year_min
- Can either be 3 or 4 digits long depending on if you know the precise year of the start of travel. Can also be NULL if you just don't know. For example, you could put1932
if you know travel started in 1932, or you could put193
if you know it started in the 1930s but not which year.travel_year_max
- Can only be 4 digits long. Can also be NULL if you just don't know. This is the last travel year of the publication.publisher
- Publisher of the publicationpublication_place
- Place of publicationpublication_date
- Date of publication. This column is text because one of the publications in Kalfatovik had a date range.publisher_misc
- Any miscellaneous or uncategorized publication infosummary
- Summary of the publicationurl
- Do not put anything here. Currently unassigned use. Carryover from when the DB was being converted from a spreadsheet. Will likely be used for TEI URLs when we figure out how that works.iiif
- URL of the IIIF manifest file that can be given to an IIIF reader to display images of book pages.ia_ident
- Internet Archive identifier of this publication. See IA docs for more info.
travelers
Each row in the travelers
table represents a person who contributed to a publication. Usually this is a traveler (because, you know, it's the Nile Travelogues Database), but they could be an editor or illustrator or whatever. Every column can be NULL except for id
.
id
- An auto-assigned, unique ID numbername
- Name of the travelernationality
- Nationality of the travelergender
- Gender of the traveler
contributions
Each row in the contributions
table represents a contribution to a publication. For example, if Alice and Bob co-authored "Introduction to Databases," there would be two contributions; one for each author. The only column that can be NULL is type
, so make sure both the publication and the traveler exist in their respective tables before creating a contribution row.
id
- Auto-assigned, unique ID numberpublication_id
- Theid
of the publication this contribution is for. The publication with that ID must exist in thepublications
table before you fill in this tablepublication_id
- Theid
of the traveler making the contribution. The traveler with that ID must exist in thetravelers
table before you fill in this tabletype
- The type of contributor this traveler is for the publication. Usually "Author", but can be "Illustrator" or anything else.
Other tables
publicationsfts
and travelersfts
and all tables that start with those names are FTS5 index tables. These are used to speed up searching. For more information, refer to the official FTS5 documentation. You will probably never need to modify these because triggers are set up to automatically update them when you make changes to the publications
or travelers
tables.