Another minor issue in the JSON

[MikedaSpike]

First of all, create work ! I'm not a programmer, but try to make my work a bit easier with some code and it looks like your vpsdb.json can help with that :) I'm testing with the first json record from the list (table :"1-2-3..."), and noticed that the tableFiles_createdAt date and the tableFiles_updatedAt date are the same . Checking vpforums , the dates are different Or is tableFiles_createdAt not the submitted date ?

And do you adjust the time to hours (so no minutes ?)

Again : great work, and thanks for this. This will be a good addition to the community !

[Fraesh]

Hey ! So the time stamps are actually our own. createdAt is set on creation of the object, updated at when the version number is changed. The created at is set manually though sometimes when adding older tables. I use timestamps so it includes hours and minutes. Its still a bit weird though, dont really know what to make of it.

I needed some timestamps for internal processing of course, now people expect them to be the timestamps of the actual files on the other site. Of course we could copy those aswell but every property adds even more overhead for the moderators so gotta be carefull how much we actually wanna upkeep.

[MikedaSpike]

Gotcha ! thanks for your reply and totally understand your way for the timestamp. It was just my assumption that was incorrect. Maybe I compared it too much with Dux retro his sheet.

I have some questions (if you don't mind)

• Will the json file be change din the future ? (name changes ?)
• Will this only be for Visual Pinball, or you planning to add other systems as well ?
• Can I use the data for PinballX Database Manager ? it is a small program that can be used as a replacement of the original gamelist manager. I build that with a good friend of mine (Scutters) and think the data you provide can be used in our program.

Again, very good data. It is very fast and you go a lot of data in it

[Fraesh]

Np ask ahead :) The timestamps might change, well have to see a bit how itll turn out. depending on how many moderators we can gathers, the workload should decrease per person.

The file itself is the actual database btw. The site works in that with every update, a git commit is pushed triggering an intrgration action that updates the huge json file. so if you fetch from the github pages deployment, youre always up to date.

https://fraesh.github.io/vps-db/vpsdb.json

That is actually what i do for the VPS website :) I believe Dux also has data for FP and FX3 thall well add in the future, although upkeep is again not garanteed yet. Its a hell of a lot of work :/