 | | Re: Add book to database? —Joshua Delahunty
|
| | | (...) when it releases later. I too struggled with how to put it into the LUGNET database. For my sets database, I used a fake number. Not having a number available makes the release tough. I've been through all the documentation looking for a good (...) (14 years ago, 12-Jul-10, to lugnet.admin.database)
|
| | | |
| | | | | Re: Add book to database? —Larry Pieniazek
|
| | | | (...) Have you considered using the ISBN? It's a lot of digits but it's a known quantity. One issue is that if there is a "second edition" I think it will get a different ISBN if the content is in any way different. But that's analogous to the (...) (14 years ago, 13-Jul-10, to lugnet.admin.database)
|
| | | | |
| | | | | | Re: Add book to database? —Joshua Delahunty
|
| | | | (...) <snip> (...) <snip> (...) <snip> Took me awhile to get around to this. I suspected that number would be FAR too large for a key in Todd's database, and it turns out I was probably right. The set number entry field stops echoing digits after (...) (14 years ago, 25-Jul-10, to lugnet.admin.database)
|
| | | | |
| | | | | | Re: Add book to database? —Larry Pieniazek
|
| | | | (...) Who me? :) Ya probably. But it is what it is. (...) Is there any rule that could be used to assign a number that fits the size limit but that is sure not to be a LEGO set number? All the set numbers in the DB are nnnn-1 or nnnn-2 (rarely) (...) (14 years ago, 26-Jul-10, to lugnet.admin.database)
|
| | | | |
