Discussions on LEGO
Start a New Discussion
-
-
the name field in a lego element is not unique, the element id is. unfortunately this database system autofills based on the name field, which is a pain as there are many bricks (different colours) with the same name. that means you have to create a new item entry for each name even though it is the same - ie.
brick 2x4 design id 3001 element id 300101 colour white
brick 2x4 design id 3001 element id 300121 colour red
is there a way to get it to use the element id as the index, not the name?
it would save allot of time in data entry
-
Perhaps the name of the lego element could be the element id, and the disambiguating information could be the brick style (e.g. 2 x 4), design id and color?
-
Sorry, I've still been trying to figure out the best way to model this, but you're right. How about this:
- The name property on Element Design should be the style description (i.e. brick 2x4)
- The Design ID property should be the design id (i.e. 3001)
- The name property on Element should be the Element ID (i.e. 300101)
- The Element ID property should be scrapped.
-
-
-
Ooh, Lego! This is very cool. Is there anything we can help you out with?
-
Just been knocking ideas around, really. The only real problem I'm having is modeling the LEGO Part type (which might be changed to LEGO Element). and naming each part. Ideally, I'd want to incorporate the data from LUGNET, but since I've just started, I haven't really explored that possibility. Any input on these types is welcome.
-
Well the theme and set stuff looks great. You could probably add some properties on set for its date of release, etc. I would dearly love to get this set up, populated, and maybe promote it into the commons.
-
