CaseStudy:Designing Memento databases:Photographic equipment: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
mNo edit summary |
||
(4 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
{{Stamp|2023-08-12|5.0|2.0}} | |||
{{BannerMenu}} | |||
{{PageTitle|Case study<br/>A photographic database}} | |||
= Case Study: An initial photographic equipment database = | = Case Study: An initial photographic equipment database = | ||
In this study, we set out to create a barebones design & implementation of a database for a photographic equipment inventory for an amateur photographer or for a solo or very small professional photographic enterprise.<br/>Our idea is to design a barebones but extensible database that will initially consist of a single library and will be able to grow to support several interrelated, linked libraries. | In this study, we set out to create a barebones design & implementation of a database for a photographic equipment inventory for an amateur photographer or for a solo or very small professional photographic enterprise.<br/>Our idea is to design a barebones but extensible database that will initially consist of a single library and will be able to grow to support several interrelated, linked libraries. | ||
== Nomenclature == | == Nomenclature == | ||
Before we begin, let's ensure we have an agreed understanding of the terminology we'll use in this study. In Memento, our terminology | Before we begin, let's ensure we have an agreed understanding of the terminology we'll use in this study. In Memento, our terminology varies from other [[Glossary#DBMS|DBMS]] disciplines, notably ''relational'' DBMSes (or [[Glossary#RDBMS|RDBMSes]]). The following table shows the equivalencies between them:<big> | ||
{| class="wikitable" | {| class="wikitable" | ||
! Memento !! Relational !! Definition | ! Memento !! Relational !! Definition | ||
|- | |- | ||
| [[Glossary#Database|Database]] || Database | | [[Glossary#Database|Database]] || Database | ||
| A generic term meaning the base of all interrelated data regarding a person | | A generic term meaning the base of all interrelated data regarding a person's pursuit, an application, or a subject area. | ||
|- | |- | ||
| [[Glossary#Library|Library]] || [[Glossary#Table|Table]] | | [[Glossary#Library|Library]] || [[Glossary#Table|Table]] | ||
| Entries & fields or rows & columns of data | | Entries & fields or rows & columns of data | ||
|- | |- | ||
| [[Glossary#Field|Field]] || [[Glossary#Column|Column]] | | [[Glossary#Field|Field]] || Field (or [[Glossary#Column|Column]]) | ||
| A typed data item occupying a position within a library or table | | A typed data item occupying a position within a library or table | ||
|- | |- | ||
| | | [[Glossary#Entry|Entry]] || [[Glossary#Record|Record]]<br/>(or [[Glossary#Row|row)]] | ||
| An instance or occurrence of data across fields or columns | | An instance or occurrence of data across fields or columns | ||
|- | |- | ||
Line 25: | Line 29: | ||
| The means by which libraries or tables are related to each other | | The means by which libraries or tables are related to each other | ||
|} | |} | ||
</big> | |||
;Requirements (the need): | ;Requirements (the need): | ||
:;Intro: | :;Intro: | ||
Line 36: | Line 40: | ||
::;Intro: | ::;Intro: | ||
[[Category: CaseStudy]] | |||
Latest revision as of 19:21, 13 August 2023
« Page as of 2023-08-12, editions Mobile 5.0, Desktop 2.0 »
Wiki Home |
About Wiki | Memento |
Getting started Wiki | Memento |
Indexes Mobile | Desktop | Scripting |
Support Wiki | Memento |
Case study |
Case Study: An initial photographic equipment database
In this study, we set out to create a barebones design & implementation of a database for a photographic equipment inventory for an amateur photographer or for a solo or very small professional photographic enterprise.
Our idea is to design a barebones but extensible database that will initially consist of a single library and will be able to grow to support several interrelated, linked libraries.
Nomenclature
Before we begin, let's ensure we have an agreed understanding of the terminology we'll use in this study. In Memento, our terminology varies from other DBMS disciplines, notably relational DBMSes (or RDBMSes). The following table shows the equivalencies between them:
Memento | Relational | Definition |
---|---|---|
Database | Database | A generic term meaning the base of all interrelated data regarding a person's pursuit, an application, or a subject area. |
Library | Table | Entries & fields or rows & columns of data |
Field | Field (or Column) | A typed data item occupying a position within a library or table |
Entry | Record (or row) |
An instance or occurrence of data across fields or columns |
Entry name | Primary key | The field or ordered set of fields (Column or ordered set of columns) that identify an entry or record |
Link to entry | SQL | The means by which libraries or tables are related to each other |
- Requirements (the need)
-
- Intro
- Design considerations
- Initial camera/lens/filter&hood, flash, tripod, bag/strap
- Solution
-
- Intro
- Design
-
- Screenshots
- See the 5 email attachments
- Implementation
-
- Intro