Database overview. As of version 0.19, Book items are broken out into Work and Edition.
(Standard Django and Wagtail tables omitted for simplicity.)
Footnote details (v0.21)¶
Version 0.21 adds djiffy for importing IIIF Manifests and Canvases, in order to link digitized versions of lending library cards with database footnotes.
Bibliography records now have an
optional foreign key to an associated
Footnote records now have an
optional foreign key to a
belongs to that manifest.
Book details (v0.19)¶
Work and edition details.
Database overview; standard Django and Wagtail tables omitted for simplicity.
Account Events (v0.18)¶
There are several types of events, related to a common, generic event (implemented with Django multitable inheritance). As of v0.18, all events can have an optional associated item and partially known dates, in order to allow documenting non-standard events from lending library cards.
Diagrams for v0.18 generated with davila.js.
Overview (v0.10) - Wagtail¶
Person detail (v0.6)¶
Account detail (v0.6)¶
Book detail (v0.6)¶
Database Overview (v0.3)¶
Person detail (v0.3)¶
Account detail (v0.3)¶
Book detail (v0.3)¶
Books Detail (0004)¶
Initial Schema Design (Version 004)¶
This does not include additional complexity of URLs for people records per 19 June 2017 project meeting.
Database updates and changes by version¶
Remove Mezzanine and add Wagtail dependencies.
Pagesmodule with CMS functionality.
Purchasenow has fields and flags for partial start and end dates.
PartialDateMixinnow contains fields and validation for partial dates, including date precision flags.
Personhas a new boolean flag to indicate if the entity is an organization
Borrowevent has date precision flags to track partially known dates for both start and end date, a status field to indicate if the item was returned, bought, or missing, and a relationship to
Itemfor the book borrowed.
Purchaseevent is still present in the database but not currently in use.
Address has been renamed to Location, and changed to allow Person and Account to have one or more Address, which is a Location with optional start/end dates.
Subscribe event has been renamed to Subscription; subscription type field has been converted from a Django choice field to the editable SubscriptionType.
Subscription duration has been converted from months and fraction of months to the actual days between start and end dates.
The overall architectures of the schema remains the same, but several fields were made less restrictive to accommodate variation in the Logbook data. These include:
Reimbursement price (now optional)
Options were provided for Subscribe sub_type fields, as well as for modification.