Write, Bureaucrats, Administrators
4,332
edits
CaseStudy:Designing Memento databases:Photographic equipment: Difference between revisions
CaseStudy:Designing Memento databases:Photographic equipment (view source)
Revision as of 19:21, 13 August 2023
, 13 August 2023no edit summary
mNo edit summary |
mNo edit summary |
||
| (3 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 35: | Line 39: | ||
:;Implementation: | :;Implementation: | ||
::;Intro: | ::;Intro: | ||
[[Category: CaseStudy]] | |||