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

Jump to navigation Jump to search
m
no edit summary
mNo edit summary
mNo edit summary
(3 intermediate revisions by the same user not shown)
Line 3: Line 3:


== 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 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"
{| 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 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]]
| [[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
|-
|-
| 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
| An instance or occurrence of data across fields or columns
|-
|-
Line 25: Line 25:
| 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 36:
::;Intro:
::;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).

Navigation menu