Subject:
|
Technica DB outline, rev
|
Newsgroups:
|
lugnet.publish
|
Date:
|
Sat, 11 Mar 2000 03:01:37 GMT
|
Viewed:
|
1220 times
|
| |
|
|
Here is the latest outline of a Lego set database. As I noted previously
I dont know RDB theory but I figure this is one way to learn:
A complete Lego set consistes of elements, instructions and the box (or other
packaging).
A set can be identified by one or more set numbers and one or more set names. A
set can be classified by Lego Theme/subtheme or by model type.
Name table
set_ID | set_no | set_name | default_name | iso2_code | name_date | name_source
set_no Lego set number
set_name Set name
iso2_code 2 letter code for the set name country
name_date date of the set name for a particular country
name_source source of the set name for a specific country
default_name yes/no
This table allows for multiple names and set numbers to be asspciated with a
single set.
ISO 3166 table
iso3_code | iso2_code | iso_name
iso2_code 2 letter ISO code
iso3_code 3 letter ISO code
iso_name ISO country name
Just an accessory table to have all of the country codes.
Set Classification table
set_ID | theme | subtheme | subtheme_2 | model_type | model_type_2 | pri_color
| sec_color
theme major theme
subtheme subtheme
subtheme_2 3rd level theme
model_type model classification
model_type_2 secondary model type
pri_color primary model color
sec_color secondary set colors
Integrates 2 separate common classification schemes: Lego Themes/Subthemes
and model type and color. So conceivably a search could return all of the blue
helicopters, e.g.
Set Information Table
set_ID | rel_date | dis_date | date_note | element_cnt | cnt_type | cnt_source
| element_note
rel_date earliest release date
dis_date discontinue date
date_note notes about release/discontinue date
element_cnt element count
cnt_type approximate/exact
cnt_source source of element count
minifig_cnt no of minifigs/action figs, etc
element_note notes about special elements
General set information. There is a provision for indicating the source of the
element count.
Instruction Book table
Set_ID | media_type | inst_pages | inst_size | isnt_note
media_type book, CD-ROM, etc
inst_pages Number of pages in instruction book
inst_size size of instruction book
inst_note notes about instruction book
This table allows for multiple instruction books or other media to be
associated with a given set. I am still trying to figure out if this really
needs to be a separate table.
This format will roughly allow me to organize all of the information that I
normally collect about my Technic sets. Is there other information I need to
include to make this more generally useful? Is there a better way to organize
this data (both conceptually and in terms of relational design)?
Thanks
|
|
1 Message in This Thread:
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
