 | | Re: take a piece, leave a piece -- traveling box of LEGO
|
|
Boxtrot gets my vote. Julie (...) (27 years ago, 10-Jul-99, to lugnet.market.buy-sell-trade, lugnet.admin.general)
|
| |
 | | Re: take a piece, leave a piece -- traveling box of LEGO
|
|
I'm partial to .market.boxtrot it's in a box.. and it's trotting all over the place.. for some reason it just fits in my mind... my 2nd vote would be for travelmix... mailathon doesn't bring anything to mind.. mailswap and mailtrade just seem to (...) (27 years ago, 10-Jul-99, to lugnet.market.buy-sell-trade, lugnet.admin.general)
|
| |
 | | Re: take a piece, leave a piece -- traveling box of LEGO
|
|
I LOVE boxtrot. Let's get a group asap as the posts are spread all over... Forget the mail part as it's not a given that boxes will move via mail. Actually it's not a given that the pieces will move in boxes. So I vote for mixorama. or boxtrot, what (...) (27 years ago, 9-Jul-99, to lugnet.market.buy-sell-trade, lugnet.admin.general)
|
| |
 | | Re: take a piece, leave a piece -- traveling box of LEGO
|
|
(...) lol (...) .market.mix-o-rama (variation, just because I like the hyphenated look with orama :) (...) .market.trailmix (sounds copyrighted though..) .market.taplap (take a piece leave a piece) .market.piecemail .market.bricksalad (...) Maybe (...) (27 years ago, 9-Jul-99, to lugnet.market.buy-sell-trade, lugnet.admin.general)
|
| |
 | | Re: take a piece, leave a piece -- traveling box of LEGO
|
|
(...) Sure, I don't see why not -- if there's enthusiasm toward it and if a sensible name could be picked. It certainly belongs in the .market.* hierarchy as it's purely an aftermarket person(s)-to-person(s) trading thing. I'll toss out a few random (...) (27 years ago, 9-Jul-99, to lugnet.market.buy-sell-trade, lugnet.admin.general)
|
| |
 | | Re: Inventory format (was Re: 8250 Search Sub)
|
|
(...) My point was that it would be useful for people to be able to use the inventory data in as many different ways as possible. For a lot of people, using the data means opening a list in Excel. Non-techies need data in better formats than (...) (27 years ago, 8-Jul-99, to lugnet.admin.general, lugnet.db.inv)
|
| |
 | | (canceled)
|
|
|
| |
 | | Re: Newsgroup for this (was Re: The Bricktionary project)
|
|
(...) Right. Identification and reference and browsing and all that. Massively cross-referenced within itself and to/from set inventories, MOC's, and the marketplace. So it's really a sub-database of the larger database. The "Brictionary" part is (...) (27 years ago, 8-Jul-99, to lugnet.admin.database, lugnet.cad, lugnet.cad.dev, lugnet.db.inv, lugnet.general, lugnet.admin.general)
|
| |
 | | Re: Newsgroup for this (was Re: The Bricktionary project)
|
|
(...) Steve, I totally agree what is needed is a complete classification/taxonomy system so you can find a part. The naming component is useful and interesting but this project should be a parts database not just a name database. If the (...) (27 years ago, 8-Jul-99, to lugnet.admin.database, lugnet.cad, lugnet.cad.dev, lugnet.db.inv, lugnet.general, lugnet.admin.general)
|
| |
 | | Re: Newsgroup for this (was Re: The Bricktionary project)
|
|
(...) Sounds good. Right place in the hierarchy. (...) And it's not actually part names, but a parts identification database, right? Having standard/prefered names is good, but it's the pictures (and maybe schematics) that actually identify the (...) (27 years ago, 8-Jul-99, to lugnet.admin.database, lugnet.cad, lugnet.cad.dev, lugnet.db.inv, lugnet.general, lugnet.admin.general)
|