Model train database

[Martijn Meerts]

Been a while again, but I'm still working on this on and off. I've started and re-started a couple of times now, the system always started turning into spaghetti code, or used too many magic framework functions.. Either way, eventually I ended up with code that worked, but I had no idea why it worked ;)


I've started with a much lighter framework now, implemented some handy features, and have started the back-end. I bought a simple yet elegant design, which makes working on the whole thing much easier.

Now, if someone can invent a time machine, travel to the future, and see if I ever finish this thing, that'd be nice ;)

[Kumo]

Been a while again, but I'm still working on this on and off. I've started and re-started a couple of times now, the system always started turning into spaghetti code, or used too many magic framework functions.. Either way, eventually I ended up with code that worked, but I had no idea why it worked ;)


I've started with a much lighter framework now, implemented some handy features, and have started the back-end. I bought a simple yet elegant design, which makes working on the whole thing much easier.

Now, if someone can invent a time machine, travel to the future, and see if I ever finish this thing, that'd be nice ;)

Did you try contacting Trainspo?
Your both projects have many similarities and Trainspo's database must be quite huge now. They are really neat guys, I had some mail exchanges with them.

Anyway, I can't wait to see your project! :-)

[Martijn Meerts]

Haven't contacted them (yet) since they're more focussed on pictures of prototypes, whereas I'm more focussed on models and their specs :) I might contact them after I get my base system up, maybe I could use pictures from their site, and they use info from my site ;)

(to be honest, I'm a bit put off by their 'stats' page. I always dislike sites that try to show off with stats ;))

[Martijn Meerts]

Yes, I'm actually still working on this :)

Progress is slow, mainly because I really want to have multi-language UI and content support in there from the start. I've also kept getting stuck at the UI design, but I ended up finding a quite decent UI for sale for a couple of dollars. I bought that, altered the colors a bit, and basically started working from there. The UI will change over time based on feedback most likely, but as a basis to work from it's really nice for a database site I believe.

Attached a few pictures (don't mind the menu options or icons, they're not correct yet ;)):

1: Shows the autocomplete input field. This is really nice for searching the database for models/prototypes since it gives you immediate feedback. I'll have to see if this works well with large databases, but with proper indexing it should be fine. Also show the top part of the 'data sheet', with the main focus being a large-ish image.

2: Shows the lower half of the pages and the tabs to switch between various bits of info.

3: Shows the dashboard/personal page options and an example of a list of collections. The idea is that you can create multiple collections, for example per country or per scale. The public/private thing is so that you can set a collection to be visible for everyone (or available via RSS for example), or just personal. Not sure about the feature yet :)


Anyway, just some quick shots that show I am actually working on things, and that the project isn't entirely dead =)

[keitaro]

nice it does look good.

i'm sure the look is great but of course additional features and options would be added over time from feed back as you mentioned.

once it's in trial/beta I'd be happy to upload info on my models. Even "when" i get around to it pics on dcc installs.

[Martijn Meerts]

Might be a while before I have a version where people can add prototypes/models, but I do hope to put a version online at some point that at least allows people to register/login and play around a bit with the interface, and the wishlist/collection features.

Adding prototype/model info is one of the more important things, so I really want to implement that right. Since a lot of prototype/model data will be global, there needs to be some moderation system (so that spam bots don't starting adding items with tons of commercials etc.) The system will also need to be able to find similar items to minimize duplicates. For example, when someone tries to add a C-57, it should notice there's already a C57 in the database, and notify the user of that.

Anyway, once I get to the point where it's possible to play around with the UI a bit, I'll put a test version online. That might take a while though, since I'm really only working on it about an hour a day, on the train to and from work =)

[JR500 のぞみ]

Oh how could i have missed this? This is a great idea! I was gonna ask where can we keep track of our collections online until...

Can i share an irrelevent but useful collection site experience?

When i was very into Lego, we had this site called http://www.brickset.com/mySets/

Basically, it's a database containing all the sets from years long gone till now, which users can create an account and then start ticking off which set they have. Recently, it even goes to the extend of calculating each piece count for each set so you will have a total number of bricks of your collection!

Sounds very intensive to build up the database, and also require a web space to hold the data?

Sorry if this is irrelevent, just thought could share my set monitoring site when i was into Lego...

P.s. MArtijn: Your site looks beautiful! Great work! Let me knwo if i can help on this project, with my limited train knowledge though...

[Webskipper]

It is a plus to have the info available offline.

I used to keep a copy on iWork server, now it's on iDisk and iCloud.

Decoder pro has a nice database that will keep pictures on your model.

We have this software at the clubhouse so at some point I will import my DecoderPro database.

I plan on using a label maker with 6mm tape to tape the address to the motor car belly. No more squinting.

[Martijn Meerts]

N500, it's always nice to look at other collection sites and get an idea of how they do things. Of course, Lego is a bit of a different beast than model trains, but still :)

Building up the database won't be that much of an issue, just need a few people to help get started with some initial models. The main database will actually be built up by the users for the most part. For example, say I have a C62 in my collection. I want to add that on the site, but it's not in the database yet, so to add it, I supply the basic information. Once I've added it, the next time someone wants to add a C62 to their collection, the C62 is already in the main database, so then it's just a matter of clicking an 'add to collection' button. Of course, there'll also be personal info someone can add for each model (maintenance log and things like that.)

I have a domain registered already, and running a VPS on that. It's a good sized VPS for a very decent price, but I'll have to see how things go with regards to disk space and bandwidth usage. The VPS is real easy to upgrade when needed. I'm hoping to keep the site free to use and possibly just accept donations.


Skip, the idea is to (eventually) add the ability to export your database to excel, pages, pdf, csv, xml, json and whatnot. An import script for decoder pro databases is also something I'm looking at. I'm also planning an OS X and iOS app that can create a local copy of your personal database (or maybe the entire database, we'll see :))

[Webskipper]

My Library is an app that lets you use your iPhone to scan barcodes to enter new items.

There's no wrong way to do this just whatever works for you.

In case of theft, fire or water damage, you want a copy elsewhere.

[Martijn Meerts]

A barcode scanner isn't a problem really, but there still needs to be an underlying database to get the actual product the barcode belongs to, and I'm fairly certain there's no (english-language) global database that has a lot of info on non-english-speaking-country prototype and model trains :)

(I'm actually already generating QR-codes for each prototype/model/rss feed/personal page/etc, so you could print those and paste them on the bottom of a train, then use the iOS app to scan the QR-code, and immediately get all the info. The prints would need to be high quality though)

[Martijn Meerts]

I'm running into a couple of issues again.. Easily solved issues, but still, I'd like some feedback :)

The problem I'm sort of stuck with at the moment, is scale/gauge .. Take for example N-scale. The general idea is that N-scale is 1:160, however, there's also 1:148 (UK) and 1:150 (Japan). I could make a drop down list, and list all 3 N-scale options, but Japan has both 1:150 and 1:160...

I would like the exact scale listed in the database, so that eventually it would be possible to compare the model to the prototype, and see if it was scaled down well.

An option would be to ask for both scale and gauge, with scale being a number input field, so people can just type 150, 160, 87, 220 etc, and gauge could be a drop down. The problem with that, if someone does a search for N-gauge, they'll also get narrow gauge H0 items that happen to run on standard N-gauge track =)

[CaptOblivious]

I'm running into a couple of issues again.. Easily solved issues, but still, I'd like some feedback :)

The problem I'm sort of stuck with at the moment, is scale/gauge .. Take for example N-scale. The general idea is that N-scale is 1:160, however, there's also 1:148 (UK) and 1:150 (Japan). I could make a drop down list, and list all 3 N-scale options, but Japan has both 1:150 and 1:160...

I would like the exact scale listed in the database, so that eventually it would be possible to compare the model to the prototype, and see if it was scaled down well.

An option would be to ask for both scale and gauge, with scale being a number input field, so people can just type 150, 160, 87, 220 etc, and gauge could be a drop down. The problem with that, if someone does a search for N-gauge, they'll also get narrow gauge H0 items that happen to run on standard N-gauge track =)

You could add a colloquial designator to aid in searching:
Scale: 1:150
Track Gauge: 9mm
Gauge name: "N"

[Martijn Meerts]

That'd mean asking for scale and gauge when adding new models. I've been leaning towards that direction anyway, and I'm already working on some sort of smart list system like the smart playlists in iTunes and such.

[CaptOblivious]

That'd mean asking for scale and gauge when adding new models. I've been leaning towards that direction anyway, and I'm already working on some sort of smart list system like the smart playlists in iTunes and such.

Probably worth doing. I'm thinking now of Kato's earlier D51 releases, that were in, what, 1:140? Anyway, I know there's some variation in scales in the Japanese market, and some variation in gauge (do we have anyone on the forum that re-gauges their 1:150 Japanese models to run on Z-gauge track?), and no standard nomenclature for some of the combinations (like there is for "HOn30". But "NnJ"—which combination is that?)

[Martijn Meerts]

Customized models will likely need to get some sort of special category, but as far as I know, the gauge is reasonably standardized.. For example 'N-gauge' will always be 9mm track, regardless of which version of 'N-scale' is used.