 | | Lego classification system
|
|
Here is an outline of the first levels of the classification system I'm implementing. It's derived from Auczilla categories to some degree, but I limited the number of categories to nine. Each category can have 9 sub-categories, with a further 9 (...) (25 years ago, 11-Feb-00, to lugnet.db.brictionary)
|
| |
| | Re: Online LEGO Inventory Database
|
|
Steve Bliss wrote in message ... (...) with (...) and (...) Here is the current scema. I have decided to concentrate on the parts section, and themn move onto creating a set inventory section (which I think will be the easy part)... Total of 6 (...) (25 years ago, 10-Feb-00, to lugnet.db.brictionary)
|
| |
| | Re: Online LEGO Inventory Database
|
|
Steve Bliss wrote in message ... (...) with (...) and (...) It will be a relational database, and I tend to remove all hard codings possible. I will be designing the schema later today, and posting it for everyone to rip apart =) --Eric (25 years ago, 10-Feb-00, to lugnet.db.brictionary)
|
| |
| | Re: Online LEGO Inventory Database
|
|
(...) Having a good list of properties at the start is a good idea, but don't hard-code specific properties into the schema. It's just a many-to-many relation between parts and properties. Assuming a relational approach. Steve (25 years ago, 10-Feb-00, to lugnet.db.brictionary)
|
| |
| | Re: Online LEGO Inventory Database
|
|
(...) have (...) I'd thought about this earlier, but forgot to mention it. (...) based (...) Once (...) avoid (...) Yeah, I agree. One of the other threads had come to the same conclusion and are curently trying to decide exactly which properties (...) (25 years ago, 10-Feb-00, to lugnet.db.brictionary)
|
| |
| | Gryphon Bricks (Mac) -> LDraw database
|
|
I've put together a few pages with an inventory of the Gryphon Bricks parts, and attempted to cross-reference them with LDraw pieces from Steve Bliss' site. Take a look at: (URL) is a first pass: there are some mistakes here and there, and quite a (...) (25 years ago, 9-Feb-00, to lugnet.cad, lugnet.db.brictionary)
|
| |
| | Re: Online LEGO Inventory Database
|
|
(...) Yep. (...) Oh, and each description should probably be tagged with a source. That way, when we change the description of some part in LDraw, the cross-reference database can be updated. (...) Yep. A better approach may be modeling a set of (...) (25 years ago, 9-Feb-00, to lugnet.db.brictionary)
|
| |
| | Re: Online LEGO Inventory Database
|
|
(...) collate. (...) Yep. The difficulty is in matching up the descriptions from the various sources (e.g. which LDraw part is this Technica part?). Sometimes it's easy, somethimes it's not. (...) Yep. (...) part (...) a (...) and (...) That's the (...) (25 years ago, 9-Feb-00, to lugnet.db.brictionary, lugnet.db.inv)
|
| |
| | Re: What words describe the Lego elements?
|
|
(...) went in and updated the description parameters to include a count of holes in the piece. So if you see the page before I've updated the page with a new image, just pretend there's a hole-count category, OK? Thanks again. Billb. (25 years ago, 9-Feb-00, to lugnet.db.brictionary)
|
| |
| | Re: What words describe the Lego elements?
|
|
(...) From the discussion so far, I can tell that some of us may be confusing a classification system with being able to identify a Lego element. In the perfect database, the inquiry about a piece would not need to know *anything* about how the data (...) (25 years ago, 9-Feb-00, to lugnet.db.brictionary)
|
