To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.db.invOpen lugnet.db.inv in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 Database / Set Inventories / 288
    Another (semi-) standard field for inventories —Steve Bliss
   I couldn't find a definitive prior discussion to followup-to, so I'm posting this fresh. So far, the general standard set of fields for an inventory has been: Part Name Part Number (where available) Color Quantity I'd like to suggest another field (...) (25 years ago, 24-Feb-00, to lugnet.db.inv)
   
        Re: Another (semi-) standard field for inventories —Todd Lehman
     (...) A side note: The contents of any particular bag in a medium- to large-sized LEGO set can change over time on different production runs. I've seen it happen many times -- one copy of the set has, say, a 2x3 black brick in the same bag as a 2x4 (...) (25 years ago, 24-Feb-00, to lugnet.db.inv)
    
         Re: Another (semi-) standard field for inventories —Steve Bliss
     (...) Very interesting. I was wondering if bag-contents changed over time. But I could only think of one or two people who I was fairly certain would know the answer, and I wasn't sure they'd feel like sharing. So thanks for passing on that bit of (...) (25 years ago, 24-Feb-00, to lugnet.db.inv)
    
         Re: Another (semi-) standard field for inventories —Charles Eric McCarthy
     (...) Hmm. Who doesn't want to share? I'll share. The most recent set I noticed this phenomenon in was the 5978 Sphynx Secret Surprise. It was pretty annoying since a bag was missing from one of the sets I got. I wanted to know what pieces I was (...) (25 years ago, 27-Feb-00, to lugnet.db.inv)
    
         Re: Another (semi-) standard field for inventories —Mike Timm
     (...) Old post but hey why not :^) I recently bought a 4806 Axe Cart which is a small boxed castle set. It normally comes glued on all sides and flaps, this had been opened then resealed with a LEGO seal like they use on the larger boxes that have (...) (24 years ago, 21-Mar-01, to lugnet.db.inv)
   
        3033 1200-Piece Blue Bucket —Steve Bliss
   Here is an example of an inventory with the bags identified. It's tab-delimited, so the columns won't line up, unless you mess with your tab settings or import the data into a spreadsheet. Read Todd's message in this thread about bag-inventories (...) (25 years ago, 24-Feb-00, to lugnet.db.inv)
   
        Re: 3033 1200-Piece Blue Bucket —Larry Pieniazek
     (...) <snip> Lines up for me... (25 years ago, 24-Feb-00, to lugnet.db.inv)
    
         Re: 3033 1200-Piece Blue Bucket —Steve Bliss
     (...) Hey, cool! I didn't know the web-interface did that. Nifty. (if you don't get it, go to (URL) to see what we mean. So much for arguing over spaces or tabs in inventory posts. Steve (25 years ago, 25-Feb-00, to lugnet.db.inv)
   
        Re: 3033 1200-Piece Blue Bucket —John Cromer
   Steve, How do you identify the bags? Just make up the numbers in hex? I really don't understand how this helps sorters. I sort for the most part but I don't pay much attention to what comes from what bag. as evah, John C. (...) [ETC...] (25 years ago, 27-Feb-00, to lugnet.db.inv)
   
        Re: 3033 1200-Piece Blue Bucket —Steve Bliss
   (...) Actually, I had keyed "bag1", "bag2", etc. But I figured the "bag" prefix was redundant (at least in this case). If I was inventorying 8448, where there are several boxes, each with multiple bags, I'd use a notation like "box1.bag3", or (...) (25 years ago, 28-Feb-00, to lugnet.db.inv)
   
        Re: 3033 1200-Piece Blue Bucket —John Cromer
   Ok, for multiple sets I can see how it helps. I just hate to give up another field in that 80-character line. I guess I should just give up on the 80-character line.... John C. In lugnet.db.inv, Steve Bliss writes: [SNIP] (...) (25 years ago, 1-Mar-00, to lugnet.db.inv)
 

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR