To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.admin.databaseOpen lugnet.admin.database in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 Administrative / Database / 2722
2721  |  2723
Subject: 
Re: Getting my set list from Peeron to Lugnet
Newsgroups: 
lugnet.admin.database
Date: 
Thu, 11 Sep 2008 18:44:18 GMT
Viewed: 
1455 times
  
In lugnet.admin.database, Warren Nagel wrote:
Thank you for your reply, I guess I always thought it would be easy to go back
and forth with the information so I didn't pay that much attention that I was
updating Peeron and not Lugnet. I like your idea for Lugnet to automatically
refresh but I'm not holding my breath. I worry that all of the lego sites
aren't that stable so the more places I can keep that information the better.

Yeah, I'm not sure how quickly something like that could be done. It's enough of
a bite-sized chunk of work that I could see implementing it, although I
personally seem to have had my SSH key removed from the LUGNET server, so I'll
have to send Rene or Jerry a new one so I can log in again.

As for stability, it's probably a good idea to keep the information in a few
places, certainly. But I wouldn't worry about LUGNET or Peeron going away-- at
least not soon. In terms of sites, I think LUGNET's probably the longest-lived
major Lego site? It's been around for ALMOST 10 years (it'll be 10 years in
another 17 days!). BrickShelf was renamed from "kl.net" in September 1999, but
I'm not sure how long it was around before that (probably about a year?).
Similarly, Peeron's been around for a long time, too, although they started
hosting inventories around November 8th, 2000?

There's also BrickSet (been around since roughly Dec 1999), which ~sorta~ does
collection data, but they only allow you to enter a "yes/no" if you own a set--
not a quantity (unless they've changed it on me recently). But that's another
candidate that's pretty reliable.

Anyway, Personally, I'd recommend you do an export of your setlist from LUGNET
or Peeron every time after you've finished updating it. Not only will you have a
backup copy on your computer (in case there IS some sort of disaster with data
loss for both sites), but you'll also have information on how your collection's
grown. I've kept different versions of my own collection file starting around
October 2001, so it's occasionally handy to gauge things like how I've been
spending and how my collection's been growing.

DaveE



Message is in Reply To:
  Re: Getting my set list from Peeron to Lugnet
 
(...) Thank you for your reply, I guess I always thought it would be easy to go back and forth with the information so I didn't pay that much attention that I was updating Peeron and not Lugnet. I like your idea for Lugnet to automatically refresh (...) (16 years ago, 11-Sep-08, to lugnet.admin.database)

9 Messages in This Thread:




Entire Thread on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact
    
Active threads in Database

 
LUGNET Guide updates (Sun 29 Sep 2024)
9 hours ago
Custom Search

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