CaseStudy:Designing Memento databases:Photographic equipment: Difference between revisions

← Older edit

CaseStudy:Designing Memento databases:Photographic equipment (view source)

Revision as of 19:21, 13 August 2023

1,054 bytes removed , 13 August 2023

m

no edit summary

UnConnoisseur

Write, Bureaucrats, Administrators

4,332

edits

@@ 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 =
 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 ==
-Before we begin, let's ensure we have an agreed understanding of the terminology we'll use in this study. In Memento, our terminology values from other [[Glossary#DBMS]] disciplines, notably relational DBMSes (or RDBMSes). The following table shows the equivalencies:
+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"
 ! Memento !! Relational !! Definition
 |-
 | [[Glossary#Database|Database]] || Database
-| A generic term meaning the base of all interrelated data regarding a person or application or subject matter.
+| 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]]
 | 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
 |-
-| Field[[Glossary#Entry|Entry]] || [[Glossary#Record|Record]] (or row)
+| [[Glossary#Entry|Entry]] || [[Glossary#Record|Record]]<br/>(or [[Glossary#Row|row)]]
 | 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
 |}
+</big>
 ;Requirements (the need):
 :;Intro:
@@ Line 36: / Line 40: @@
 ::;Intro:
+[[Category: CaseStudy]]
-'''''The email'''''
-I have a LOT of camera equipment (Camera, Lens, Filters, tripods, bags, etc.). I want to be able to create records of all of this equipment for personal inventory as well as insurance purposes.
-So far, none of the prebuilt programs I have looked at covered all of the data that I wanted to track on a per item basis, so I decided to use this program, some research into existing templates and a lot of soul-searching to create my own me-friendly database. So far so good. I spent all day yesterday architecting  starting database. As will all programming, there will be further minor changes (new fields, verbiage tweaks, section grouping changes, etc.). That said, I am very happy with my initial go at this.
-So, in this bare bones example, I have a camera entry, a lens entry, and a filter entry.
-In real life, ALL three of these items are physically part of the same "group/unit", The Lens is attached to the camera body and the filter is attached to that particular lens.
-While I still want to keep each item as their own separate record, I also want to link these 3 records together to visually show this relationship. And at some point, i want this grouping be part of a larger grouping (in a camera bag with other items for example).