Jump to navigation
Jump to search
← Older edit
Newer edit →
Revision as of 05:40, 30 April 2021
1,762 bytes added
05:40, 30 April 2021
no edit summary
== Notes ==
== Notes ==
=== Photographic equipment case study ===
;Nomenclature:[[Glossary#Library]], [[Glossary#Entry]], [[Glossary#Entry name]], & [[Glossary#Link to entry]] vs [[Glossary#Table]], [[Glossary#Record]] (or row), [[Glossary#Primary key]], & [[Glossary#SQL]]
;Requirements (the need):
:;Design considerations:Initial camera/lens/filter&hood, flash, tripod, bag/strap
::;Screenshots: See the 5 email attachments
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).
Retrieved from "