Open stgraveyard opened 7 years ago
Ok... i see now when i have access to the new AL design that it is basically much like the old AL structure wise, and my suggestions is a big change. What is your opinion?
The detailed information for the game structure i suggest is pretty much based on Atarimanias since thats what i am used to. For example the structure of AM is allowing the ability to specify wich release that is STE compatible... in Dragon Ninjas case so does not the first release suppert STE but the later budget and compilations release do support STE... this goes for several other games also.
ATM so have i not been able to see how a game entry might look at the new AL, but i have been told they can be found here at github though, just have not found it yet and i will search after this post :)
I am very much for documenting as accurate and detailed information as possible for all official Atari ST game releases. My first experience with game preservation and documentation was the MAME project wich i helped by dumping roms and searching undumped arcade games, you could say the MAME team are my teachers :)
Correct @stefanjl, the game structure hasn't changed. And it is becoming clear to me that it has to be expanded and converted in the future. To be honest, I did not know what you explained about Dragon Ninja was possible. In the current AL DB structure, I guess the game 'Dragon Ninja' is tagges 'STe Enhanced'. Period. You tell me it is version dependent. That is very new for me.
@Brume-AL Are you reading this. I think we need to discuss about this after the first release. This will not be an easy job.
BTW @stefanjl, if you want to see the game structure, you need to check it in the manual, which you can download from the first tab here in github (technical analysis)
I see game compilations is missing at AL... so that needs to be added. I mean the abillity to see wich game compilations the game is part of... this is a feature that is currently missing at AM. And i am talking about commercial compilations and not compact disk menus ;)
And then the question how to split the different releases of games... lets take "Outrun" as an example. It had 3 full price releases.. one for USA and one for Spain and one for the rest of the world, and then at least 2 budget release "Kixx" and "KlassiX", and was part of several compilations... like "Power Pack" and "Giants".
Maarten do you have screenshot of the latest design of how a gamepage would look at the new AL so i can try to edit it a bit to find a acceptable design/presentation for a game entry with many releases?
Another thing is that i also have in mind that there will be many downloads for the games... almost like light version of SPS project but with sharing in mind and of course always supply RAW images of the disks like in SCPro and Kryoflux format. I don't mean we should do like SPS and provide IPF type of disk images... i want it more to be that AL is only supplying the actaul RAW data and then people can do whatever they want with them, this also means i would like multiple copies of the games as download... and by multiple copies i don't mean you copy the same disk many times but do copies from different original copies. This is kind of what SPS does already... they want multiple copies before releasing an IPF, and i think multiple copies is the way to go.
I am not a fan of SPS "non-sharing" mentality, and thats why i so far only support SCPro... i have no plans on buying a Kryoflux device.
Hello Stefan,
Yes, this is the design of the main game page : https://github.com/stgraveyard/AtariLegend/issues/149
We really need to think on how we can enhance/rewrite the DB structure for different releases. Currently we have a country table and a game is linked to different countries. This really is not enough by far. The layout of the page does not need to change, maybe only an extra tile which shows all the different versions that you can click on and than leads to another version of this page. Almost as if it is a totally new game entry in the table.
I could really use @stsilversurfer here. Mattias, if you have some time, can you help think about this a bit. It seems our DB structure is seriously lacking here, and just creating a completely new entry of the same game doesn't seem like a good solution to me. Seems like we need some sort of cross table, but the problem is that even though it is the same game, the different version of the same game is linked to other entries in all tables (screenshots, boxscans, publishers, developers ...). I wonder how we could solve this in a completely normalized way? I will be losing some sleep on this one!
Cheers, Maarten
Right, need to look at the diagram but to be honest it feels like I have thought about this but on the other hand I/we may have left it alone and pushed it towards the future.
The advantage of well normalized db design is that it is very easy to add more later without redesigning the entire structure.
If I remember correctly we solve this at the "download" level.
Every version/download/dump/whatever-you-want-to-call-it of a game gets a download entry that is tagged/labled accordingly, in the Outrun example that would be
@stgraveyard I see you renamed the "labels" tables to "options" tables, not that it matters but "options" doesn't really cover the scope of the feature.
Hello Mattias,
First of all, thanks for taking the time to help think about this. I agree with the normalize statement you made. However, I'm afraid in this case, we have seriously missed something and it won't be easy.
Regarding the donwloads structure, this doesn't make sense to me.
I think the downloads section is perfect, but not for this case. What Stefan is talking about are actual different version of a game. These versions are linked to all other tables. Let's take the OUTRUN example again :
Outrun
Each version depicted here has got its own publisher and developer (of course, most of the authors are the same, except for perhaps artwork designers). These versions all have their own set of screenshots, boxscans ... and so on ...
Now, I agree that underneath these different game versions, you can add downloads. Each of these versions can have an official download in whatever kind of filetype, can have a cracked version with or without intro, by 1 person or belonging to a crew (and menu disk).
Currently, If I understand correctly, at Atari Mania, these 'game versions' are actually a new game entity in the game DB. We could also solve it like that. Over at AM, once you link a publisher to a game, an entry in their game table is made (or something like that). I am just wondering if there isn't a better solution. It almost seems as if there should be a sub game table, which can divide an existing game into a version, once a publisher is linked to it.
Solving this with the download table doesn't make sense to me. Do you understand this, or am I completely coockoo here? The way our game structure is set up, regarding the different region and version releases ... to me, it seems like a mess, as it is all linked to one and the same game entry. It is not structured. You link all kinds of different boxscans to the game, together with the versions. But which boxscans or screenshot belongs to which region?
Adding duplicate entries to the game table is not a pretty thought... lets not do that.
I do think we should look at solving this (somehow) on the download level.
The only other sane way would be add another db layer between game and download, that would certainly shake things up a bit in complexity. :-) This layer, lets call it the "version" layer, would then be where we hook up all the pub_dev, boxscans and so on. How do we solve this for cracks, menu disks and other crazyness? I can imagine that some of the cracks and packs are probably so mangled that it would be very hard to say which specific version it came from. Could we just default them to the first known full price release?
I don't know... need to loose some sleep on this. ;-)
And to think I was laughed at for bringing up the game_aka as a potential problem... :-)
Well, if I laughed with the game_aka stuff, it must have been 15 years ago, cause I don't remember that. But if I did, my apologies ;-) The game_aka structure seems perfect to me but is a whole other beast. I do think we need another layer Mattias, but game_aka should be linked to the top layer (which is the game table).
From the top of my head (and from a more technical pov), I think we need to copy the game table and rename it to 'game_release' or something and add an extra game_release_id field (version doesn't seem correct as the version nr is stored in the download table :-) an official release can have different official downloads which differ in version nr). The 'game_release' is linked to most of the tables that are now linked to the game table. The game table itself will be linked to the game_release table.
Afterwards we can write a script or something to check which games currently have a link to different countries, which games have more than 1 boxscan ... And than add an extra entry in the game_release table linked to the same game table entry.
Something like that. Once the first version of AL is online, I will start with a new diagram of our game structure so we have a clear view of how big the impact will be. I was planning to do a complete overhaul of the game section in the CPANEL anyway, adding lots and lots of AJAX (just the way you like it).
@stefanjl We will fix this issue! ;-)
Alright so this is for after first release! Then we can think it through properly.
Just one question to @stefanjl: I don't get it. How do yo imagine the structure of game details page on the site? I mean, do we have to present all releases / boxes of the same game in a different page?
@Brume-AL YES, that is the idea. The main game page will have an extra tile, that will show other release and which leads to these releases. They will contain some tiles with the same info, others, like boxscan ... with other info. I do thing a clear seperation is necessary. I think currently, even though Atari Mania seem to have a better DB structure, it is not clear on that website as well.
Sorry, you asked Stefan, I just can't stop giving my opinion :-)
Brume i am not clear yet either how it should be done i am still trying to adjust my ideas to the current design of AL. But i have presented my ideas for seperation of releases and thats what we can discuss now and of course come up with examples how it could be done :)
And also to discuss what a different release really is.... a slightly different boxart maybe is enough for a seperate relaese? And if thats not a good idea how is that information best documented? (minor boxart difference i mean). Different software should of course be a different release... but then how do we find what software is different... i don't know for sure unless it is very obvious like differnt graphics and such since i am not a ST hacker... so this goes back to the differnt box art again and maybe the different boxart means the software is different also? For example there is two version of the box design (not art) for "Stunt Car Racer"... should they be different releases? this is what i want to discuss :)
i still don't know exactly how Stonsih menus is gonna be presented on the new AL, and i really want all pirate copies of a game to be a seperate release... "unofficial release" ;) Menus and single cracks, and those newer HD adaptions of ST games.
Stefan, wait wait wait. Keep in mind you have a "version/release" on a download level, and on a game level! That is a first thing.
A different game "release" (as the word release already means), would be a different publication of the same game, I would think. So if STUNT CAR RACER was released in europe with 2 different box scans, I guess these can both be added to the same entry. However, if there was an American release and a EU release with different box art, I think those would be 2 entries. Same for a budget release or other re-release.
Now when thinking of pirate copies. A pirate release done by team X, and one by team Y, that is something else. I agree we need to add all different hacked versions, but the question here would be, to which GAME RELEASE would these be linked? maybe to all of them?
Another thing, to me, a release is also something different to an official game version. for example, you have sensible soccer version 1.0 and you have version 1.1. These games are the same release. We can both upload them and link them to the same game entrie, but I would never make a different entry in the game table for these, I think.
This is just from the top of my head of course, but like you say, this needs to be thought through very good, we need to write the rules down and eventually stick with them.
Good to have a discussion about this :)
About Sensible Soccer so do i think that especially software differences should be seperated, and SS and SS1.1 do not only have different software they do also have different design on gamebox and the gamebox also has an extra sticker for the new version and the disks have different art/text, quite a lot if differences i think and how to seperate them in one entry in a good way? wich box/disk scans belong to wich download. If having SS and SS1.1 in the same entry could they have differnt tiles maybe?
About pirate copies... due to the nature of pirate games... they are hacked so they are all different and the question on wich game release they should be linked to so is my suggestion that all unoffical game releases is linked to all official game releases.
The main problem is to determinate when a version of a game deserves a different entry, and when it doesn't. I understand your point of view about Sensible Soccer, I have the same case with a French game named Enigme A Oxford (we hacked this poor game long time ago, but I've recently discovered Coktel edited a new version with a new box, real gfx, better interface, ...).
On the other side, there's also tons of examples where a different box and/or a different manual doesn't mean a different game. As an example, take a look at Gobliiins by Coktel Vision :
there's an European version, that includes a box and a manual in English, French, German and Italian. The game is in English, French, German and Italian. The game is also playable in English, French, German and Italian, but also in Spanish.
there's also an English version of the box, that includes a manual in English only. But the game is fully playable in English, French, German, Italian and Spanish. The three disks are exactly the same version as the European version (three disks have the same size, same intro, same graphics, etc.). It's exactly the same game, nothing has been changed.
Does this kind of case deserves a different page on the site? Won't it be confusing for the visitors? Also, does it mean we'll have to remake screenshoots?
Let me know. We really need to discuss about that :)
I agree the problem is to determin when releases should be seperate or not and thats why i wanted to know other peoples opinions :)
Even if USA releases of ST games could use different box/manual so might the software be identical, do they deserve a seperate entry more than the Gobliiins example... since both are releases for different regions and both have different boxes but software is identical... thats something to think about :)
If i would choose so should any release with any kind of difference get it's own entry... like different design on box, other box art, other text at the back of the box, the software is different... maybe even different design on disklabel/print would get it's own entry ;) The reason for this is that it is easy to document this way. But i know it is not the optimal way that each gets it's own entry. Maybe one way is to have sub entrys, the most important is to know to wich release each scan or download is connected to... and also author information, for example the boxart might be different for two releases that might share the same entry then we need to specify wich artwork is made by wich author. it is also up to the design of AL how to handle all info, for the desktop version would i think be quite easy to add more info but for the mobile version it might get messy... but i am no expert in mobile websurfing as i practically never use my phone for webstuff :)
Ok... maybe we need some more examples and use them as examples in discussion. So now we have: -Gobliiins -Stunt Car Racer -Sensible Soccer
And i would like to add: -Outrun -After the War -Skrull -Populous -Populous 2 -Outlands -Titus the Fox -Formula 1 Grand Prix
And also i think the ability to have multiple downloads from the same release is needed, for example SPS project require that (if i rememebr correctly) 5 dumps from 5 different copies of the same release before they consider that release/version of it "preserved"... and it is possible other projects also will have similar rules and thats why i want multiple downloads fro each release... the new AL will be RAW material for similar future project and there will be no (or less) questions about bad disk used for mastering or such... and also this way we might find unknown versions also. Actually i feel uneasy if we don't have multiple dumps for each release... it feels more futureproof if we do.
Here is two pictures showing the two boxes of Stunt Car Racer, the blue one to the left is the first release and the right one is the later release with the newer Micropose type of design of the box wich i think they started to use around 1990.... as yo usee the right one has lot's of ratings and review text on the box, i guess the game was so popular so they did a "reprint" (dont know what word to use) of it. The second pic show the back of the boxes and the content... the manual seems to be the same in both releases and so is the barcode, the disk of the right release looks identical to the first except for one thing and taht is a number is printed to the left of the disk "S2809" and i don't know what that would mean since i suspect the software is identical in these two releases.
I have some ideas.... but i have absolutley no idea how to make them suitable for mobile version?
Maarten... can screenshot and box scan be in the same tile?
or maybe like this... it has the tile with version selection.
Hey guys,
First some remarks :
@Brume-AL The gobliiins versions you are talking about, do they have the same publisher or not? If so, to me it would definitely be a new entry.
@stefanjl multiple downloads is absolutely no problem, even at the moment. How many you add and which version, that is for you guys to decide as I really am not up to date regarding filetypes and all that stuff.
As some extra info - This is our current GAME DOWNLOAD table structure :
If this is not clear for you, I would gladly go over it step by step. But in short ... all these tables are linked to the GAME_DOWNLOAD table, which by itself is linked to the GAME table containing the game entries. So in other words, more GAME_DOWNLOAD entries (with all of its extra tables) can be linked to the same GAME. You can find a description of all the tables here : http://dev.stonish.net/php/admin/administration/technical_doc.php#downloads
Now, to go back to our GAME structure. What about this.
We have the GAME table and the GAME_AKA table in the highest level (GAME_AKA contains the other names for the same game). These tables are used for the search engine of the website (as it is now). But, instead of linking all the sub tables to the GAME table directly (as it is now), we could add an extra layer called eg. GAME_VERSION. This would mean that 1 game could have different "versions" with its own data and info linked to it. BUT now hear this. The main problem is, when do we create a version of a game? That is a very good question. Perhaps a possible solution could be some kind of "GAME_LABEL" table, linked directly to the GAME_VERSION table (a bit like we have with the download structure and its DOWNLOAD_OPTIONS table). This GAME_LABLE table can contain all kinds of entries like eg "MAIN release, EU version, USA Version, RE-RELEASE, Budget, KIXX XL, REPACK ... any "label" we want.
So for example, let's take the game STUNT CAR RACER (and let's pretend this game is also called SUPER CRAZY STUNT MACHINE). When the user searches for STUNT CAR RACER, we get one entry in the list. When we click on this and go to the detail page, we enter the MAIN release (this is where the label table kicks in). But ofcourse, in the background in the code, we also search our GAME_VERSION table, we check if there are other versions and what LABEL they are linked to. If there are other versions, these are loaded in an extra tile, and the labels are used as a link in this tile. So in other words, every game has standard 1 version, the main release, which is loaded. But this way, we can add other versions just the way we like. So back to STUNT CAR RACER detail page, the main release is opened, the AKA name is displayed and there is an extra tile containing an extra version, a REPACK version (as displayed above). When we click on this REPACK link, a new game detail page is opened, with the data of this repack version, and in the GAME_VERSION tile of this REPACK version, we see a link to the MAIN RELEASE.
So this way of thinking gives us endless possibilities, yet everything is nicely structured, I think (at first sight). I could suggest to keep the LABEL version to a max of 20 different labels or something. And I would build a part in the CPANEL to add and edit labels of course (just like it is now in the download section).
And again, how many different downloads you add to the game versions is totally up to you.
This way we can always discuss with the team if a new game_version entry for a certain game needs to be created or not.
One problem I have is the following. Let's take Stunt car racer again as example. Lets say we make an extra GAME_VERSION entry (apart from the main release) for the repacked box. If the only difference is the game box, we still need to add all data entered for the main release, as well in the repacked release. I need to think how to avoid this. How to add existing data to a game version yes or no, else, we will have double or tripple or whatever the amount of work.
@stsilversurfer If you have some time this week, can you let me know what you think of this way of thinking? Am I missing something, is this normalized? Do you think this is over the top?
What do you all think?
@stefanjl don't worry about the layout. The propositions you make are indeed doable, but I don't see any problem with the mobile view when more data is entered. AL is based on tiles, and is very modular, We can easily add extra tiles, or remove existing ones or even only display certain tiles in certain occasions. So unless I am missing your point, I don't see an issue here ...
Cheers, Maarten
Maarten your "version" idea seems fine :) To make an extra GAME_VERSION maybe it is possible to get the option to duplicate the main release and then edit out or add the data that is differnt? And if you add info to a GAME_VERSION or main release then you get the option to add the same data to all other linked GAME_VERSIONs... that should work i think?
I have made another mock up picture on how it could look for viewers when they go to a game entry:
Remember it is a mockup and it is based on the Gods entry mockup by Maarten but i used "Stunt Car Racer" as GAME_LABEL and GAME_VERSION example :) I have sorted them by publisher in the tile as you see and the top version is the main release. The green square shows wich version you are seeing right now and in the mock up it is the main release, everything in this "Versions / Releases" tile is real info except for the "alt. box 1 / alt. software 1" version it is just and example how it could look if the "alt. box" version (wich is the repack version) would have a second version with different software... for example one double sided disk instead of two single sided disks.
I also added compilations in the "versions/releases" tile even if they are not to be linked to the main release in such way as the other release/versions in the tile, i just wanted all versions info to be as close as possible and the best way is to do it in the same tile... for quick overview of all different releases Stunt Car Racer was released in/part of.
Other stuff that could be added in this tile is if the game had "data disks" released for it or if a "demo version" was released of it.
Now to the question what is a "GAME_VERSION". If tehre is a software change then it should always be seperate GAME_VERSION. Minor game box differences should not be a new GAME_VERSION, none of the examples i listed above is minor though imo. The Gobliiins example should be a seperate GAME_VERSION imo, because of the totally different manual.
Sensible Soccer was a bit more difficult to figure out but i think they (version 1.1 and 1.2) should be considered sequels... different "GAME_LABEL" and not different "GAME_VERSION".
Was this ok? What are your opinions?
Also here are some games i am not sure if different releases of them should be seperate "GAME_LABEL" or just seperate "GAME_VERSION".
There is probably more games but i could only think of these two right now :)
In both case, we could say they are different games. Differences between Titus the Fox and Les Aventures de Moktar are important, so we can't say it's the same game. That's the same between both versions of Helter Skelter.
Same goes for Chrono Quest / Explora and Chrono Quest II / Explora II, for instance. (btw, we are working on a translation of Explora III in English ;) )
Yes Titus and Moktar is different enough to get it's own GAME_LABEL, i don't know much about Helter Skelter though to have an proper opinion.
Hmm... Chrono Quest and Explora is a borderliner i would say... ChronoQuest has new and additional music as well as new title screens... what else is different? This could go under GAME_VERSION i would say, Anyway This was a good example i think.
As i wondered earlier... is the "GAME_VERSION" and "GAME_LABEL" the way we will go now and was my screenshot ok?
Stefan, I think I'm missing something. I think we talk about different things.
Game_label table is used to explain what the Game_version is. In other words, if we create a version, it is linked to a label. eg. main version (=version 1 with label 'main version'), usa release (=version 2 with label 'USA release') ... Unless I am missing something here? game_label is only used as a solution for not knowing WHEN to use a a new game_version (which we had in the beginning)...
I also have doubts about the following you explain in your stunt car racer example :
...everything in this "Versions / Releases" tile is real info except for the "alt. box 1 / alt. software 1" version it is just and example how it could look if the "alt. box" version (wich is the repack version) would have a second version with different software... for example one double sided disk instead of two single sided disks.
Why not create 1 version for this with label 'repack version' and link 2 different downloads to this game_version (think about what I explained above with the download diagram!). You can add loads of info to a download as well.
We have to really think this through, and write this down (as we do now :-)...but you have to keep in mind that a new version of a game is something else than a download type of a game imp. We need to set up a good clear set of rules.
I will be working on the release of AL in the next week, but once it is all online, I will be back on this here. It is very important. Also, @stsilversurfer , I really really want your input on this matter ...
Cheers, Maarten
Yes i misunderstod you maarten. I was thinking gamelabel was the game entry and gameversion was "subentry" , and was what i based my screenshot mockup on. I will write more when i am home from work.
i make a new try tomorrow
since i misunderstod the Gamelabel and gameversion so did it become something else as you see on the mockup pic i did.... but now i think it could be working like that... the way to split up releases/versions/whatever in a non-confusing way for viewers.
pic again:
This is subentry style or what to call it to show what i mean.
Each of these will have unique, game info, boxscan (diskscan), screenshot and download.
Compilation is not part of this game entry since compilations are completely seperate products.
For example a game collector should be able to tell people what version they have in their collection... like "i have the altbox/altsoft Stunt Car Racer" and then they can link "games_detail.php?game_id=365_3"
Hello Stefan,
Do the altbox 1 have different box art, or do they both contain the same boxart? If so, it should be one entry with 2 downloads (with extra info linked to the download) imo.
Also, I have doubts about your compilation remark. I think it definitely should be mentioned in the box. I don't know yet how to store compilations in the DB. I think this also needs a separate structure linked to the game entries themselves (on a technical level I mean).
Maarten
I do like clean seperations and if the software is different and share screenshots from another version then the screenshots will be mixed from different version (in case there is a graphical difference at all of course), HOL does this mixing of all releases and versions and i personally think it is a mess... AL should be better :)
About compilations... i did not mean to remove them as links as seen in the first uncropped screenshot i posted, i just did not want them as subentry... like "games_detail.php?game_id=365_2"... they should have their own entry example "games_detail.php?game_id=4216". Compilations can be stored in the DB right now without problem... but the author list might get very long :)
Now i have been calling the seperation for "releases", "versions" and "downloads"... but in fact a better word would be "product variation"... thats what i want to document and as detailed as possible.
Different box variation = it's own "subentry" Different publisher = it's own "subentry" Different region = it's own "subentry" Different software... like SS or DS disks, updated revision, language, bugfix = it's own "subentry" Different software... that is more than title/loadingscreen = it's own entry (not subentry) example Titus the Fox. Probably Helter Skelter also.
Any pros and cons doing it this way? The only "con" i can think of is that this is a way that is time consuming... but we are not here to be lazy we are here to create the best ST game database ever :)
I don't know what is the best for pirate copies and hacks, i personally don't think we should try and identify from wich version a crack is made from and new hacks like Ppera's harddrive versions use several different versions of a game. Menu's have their own section at AL so more precise detail can be added there and not on the actual game entry (speaking commercial games now).
@stefanjl Have you checked the download section on the dev server already? (dev.stonish.net). In the download section, search for GODS :
When you have clicked on GODS in the list you see this :
I just have a feeling that you are creating too many subentries of games that could be solved with the download section. I just want to make sure you are aware of the functionalities in the download section.
Ofcourse, maybe I am wrong (probably I am), you are the software expert.
@stsilversurfer @Brume-AL We need your help in this one!
Also, I have doubts about your compilation remark. I think it definitely should be mentioned in the box. I don't know yet how to store compilations in the DB. I think this also needs a separate structure linked to the game entries themselves (on a technical level I mean).
We could solve that in the same technical way as we have solved game series. we just add download to the mix and it should be easily presentable.
I read this topic last night a couple of times but couldn't really get anywhere in terms of structuring it in a way that is technically sane and understandable.
So then I thought how about looking at it from the other end of the stick, lets say we have a download file that we want to tie into the database.
So lets say we have a file called stuntcar.stx that we want to tie to game_id 365, could we connect it directly to the game_id? Sure but all information we have then about the file is the game_id and from the game_id all we really can glean from that with certainty is the game name.
If we were to hook the file to the game_publisher table(this is where we connect the game_id with the companies) then we would get the publisher_id and the game_id. This is better but how would this work for PD games that don't really have a publisher?
Nevermind my previous ramblings.
I am looking at the current game download section and I like it, we basically have what we need but I think we need some tweaking.
[ ] We need the ability to select which publisher released this, the selection should be the publisher which are already linked to the game. If the same publisher released it several times it could be separated by the release years.
[ ] I think that the Tos details options should reflect which Tos versions are NOT compatible with the game. I mean the normal should be that the game is fully compatible with all tos versions, right?
[x] We need an option to choose "Unmodified Original". When this option is selected all options regarding crews, trainers, intros, menudisks and so on is automatically hidden and not valid for this file download.
We obviously need to add functionality to for adding release year to publisher for this to work.
As far as boxscans and artworks goes I think we can move that discussion to a separate thread.
If we need (I think so) to hook the scans to the publisher level or download level we should do that in the appropriate section.
So does this means (at least as i understand) that everything will be listed in one "page"... one game entry?
Yes that would be possible
Looking at your example here:
If I have a Pasti dump of Stunt Car Racer from Kixx I would upload that file and then select Unmoddified Original, Select Publisher Kixx.
And then do the same for each of the other file uploads.
Come to think about it, from a research point of view that would be quite good. The file would have to be added for the information to be added and then anyone can download the file and verify the information that is connected to the download, right?
I don't quite understand what you ment... i think you misunderstod the example pic i made... i made the pic to show differnt links to the subentrys i suggested... it is not download links.
But it is a good way to show all the versions/releases if downloads was shown as the pic i made.
The thing i wanted to say with the mock up pics i made is that i want to keep different releases/versions etc as seperate as possible but still connected... and thats why tried to use the word "product variation" instead, and each (game) subentry page has it's own boxscan, download, screenshot, author information etc. It would be like going into a game store and you pick the gamebox you want and the same way would i like the game subentry to be like... only that game you have from the game store is seen... boxscan from that copy, software from that copy and not mixed with other boxscans or downloads etc... that is my dream scenario in documenting ST games :)
Everything i have said is all based on how a game entry could be looking for the end user (viewer) and not much how it works in DB level. So what i want to know is how a entry will be presented on AL with all the needed seperation of releases, that is what i have been discussing mostly in this thread... when that is complete then we can work out what DB structure would suit most :)
Well strictly speaking I am talking mostly from a technical point of view, where I really want to avoid structural dead ends in the database. And I don't see any issues with what you are suggesting.
Worth pointing out also is that the cpanel is NOT made to be the front end of the project but rather a tool to insert/update data as efficiently as possible. Work flow efficiency is key and to have relevant information and tools on each page is important.
The frontpage is where we are going to present the content of the database. How we lay the data out can look very differently then how we insert/update the data into the database.
Now from this perspective I say that we some tweaking/expanding of the downloads we can indeed present the information like you suggest.
That being said, this is a mammoth undertaking both from a coding point of view but also from a data entry point of view.
From a coding point of view I would suggest we do incremental changes like adding release year to publisher, adding an autoinc game_publisher_id, hooking boxscans to downloads, hooking screenshots to downloads etc etc.
As a user browsing the frontend I don’t really know…. I like the way it is layed out now but it would be intriguing if I could drill further into a game and discovering more about a particular release!
Mattias, very very interesting take on the whole thing. But...
If I understand correctly, what you are suggesting is to move all the game data (pubs, devs, screenshots, boxscans) to the download level. I do understand this, but on a technical level, what would be the advantage of this compared to adding an extra layer below the game table (like I suggested a few weeks ago?). Aren't you suggesting to completely throw away our current way of thinking by starting from the actual download instead of starting from the main game?
Or would a combination of these things work. We have a game entry in the game table (and perhaps still some data linked to this game). Than we have a download or more downloads linked to this game entry and all data like pubs, devs, scans, screens, years, are linked to this download.
From a main website perspective, the game searching still uses the game table, but the game detail page loads the game table, the game download that is tagged with 'main release' (or something) and all its data, and an extra box with all other available downloads which the user can click to go to its detail page?
That is what you mean, right? That sounds bloody marvelous!!!!
@stefanjl do you understand this? Do you think this can cover all your needs? I think we need to figure out which data could still be considered game data (eg. genre, aka name...) but all other data would be linked to the actual download.
@stsilversurfer Correct me if I am wrong here. @Brume-AL Read this! ;-)
And an interesting question. Take Xenon 2 an think about what Mattias has written.
We have a Xenon 2 game entry. But there is also a fan made STe only Xenon 2. Will this fan made game get a separate game entry, or is this a download? I guess the last, right? If so, than this #277 should be linked to the download as well, and not to the game entry...
stgraveyard.. if i understand... i get better and better at understanding but not completely there yet :) If the game_label solves the problem i see with mixed info for all game releases versions then it is good.
and if it can be listed in a way that looks the screenshot i made then it is awesome :)
Do you have an example how a seperation will look on the website? for example for a European release and the USA release? will they have different links to them?
About Xenon 2 fan made for STE... and other hacks... the easy way would be to put it in the "expanded" Menu section. But... then there are some really awesome hacks that gets kind of lost (or hidden) if they are put in the menu section with all other cracks and hacks... i don't really know what would be best... should the best hacks get it's own game entry? If so... what is a "good" hack? A hacked titlescreen... NO.
Hello @Brume-AL , @stsilversurfer ,
For the past days I have been talking to Stefan Lindberg of Atari Mania. He seems like a very dedicated guy. He has been sharing info regarding the setup of the Atari Mania game section and I have learned a lot and it seems to me our game sections is missing some really crucial stuff regarding game versions. I will copy/past our complete conversation. This is a lot of info, please read it carefully when you have time. I think we do need to make some changes in the near future to the game structure, but this is something we should analyse and think about very deeply before continueing.
Here goes :
STEFAN wrote :
Hi,
you asked me to send an PM with my questions :) As you might know so am i already part of the Atarimania team and have been for 3-4 years now and i have asking for updates at the AM admin forums to more suit what need to be documented and how, but there is only one person that have access to actually update AM design/layout and he is practically not present at all and my discussions at the forums usually only gets replies from Marakatti and he can do nothing but saying he hope Franck will see the discussion and reply, and i do very rarely get any reply at all. This got me very worried when only one person controls a database and if he disapears so does the database (like Guardians of the Past) and in early 2015 i had the idea to get new ST database in works and i got my brother to promise me to program it (i have no programming skills) and then i started looking for people to be part of this new database and i noticed Brume had been posting lot's of posts here at Atari-forum about all ST original games he had and i thought it would be a good idea to contact him and ask if he would like to join me in starting a new ST database... but it turned out the new Atarilegen was just in early works and instead Brume asked me to join the new Atarilegend in early 2015, he welcomed me to AL team and said he would give me access to a private forum to propose my ideas. But i never heard from him again despite send a reminder PM. I know he is very busy and maybe he has to much to think of. And after taht so was i restrictive with adding info to AM database since i thought the new AL was about to be online soon and i did not want to add the info twice, but now i am adding lot's of stuff to AM and i once again get frustrated on how difficult it is to document all info i want. Some ideas i had is already part of the new AL... like having crack menus as download, thats a very good idea since crackers often got hold of early versions of games that might be difficult to get hold of today... for example the "Cisco Heat" thread i posted here at AF because i had seen the screenshot at the AM database was different from the one in the game i played, it turned out the screenshot for the AM Cisco Heat entry was from a cracked version and if i rememeber correctly so was it from a Pompey Pirate menu and i suspect they got hold of an review copy that they cracked, this is quite valuable information and the PP crack might be the only thing left of that early version of Cisco Heat.
other idea i have is to have screenshots with comments just like Moby Games have, and another much more controversial idea is to have screenshots with the border visible, to me the border is very much part of the Atari ST experience... most of the time it is of course black but several games use other colours, i suggested the border idea at AM admin forums and even said i myself would redo all sceenshots with border :) It was not an idea that got much understanding :) But if the screenshots always were at the same resolution then i proposed if the original screenshots were with border but the database system uatomatically cropped them to 320x200 and then let the user/viewer of the database to see the borderless or the full border version of the screenshot... i still think that is a very good idea... maybe a cookie stores the info if screenshots is to be seen with or without border. Anyway nowadays i always upload new screenshots with border to AM :) example: http://www.atarimania.com/game-atari-st-formula-1-grand-prix_9370.html
Ok, now more difficult things and this is more what i was asking in the forum post you replied to... how should the game releases/versions be presented? Will the releases and versions have their own entry so to speak like Atarimania? Or just mixed together like for example HOL (amiga) database? This is actually a strong plus for the AM database that it allows for that kind of seperation even if it needs to be updated for better flexibility. I always like the idea to have first a main entry for the game with mixed info from the various releases just like HOL... but then also have the ability to in detail check out the sub-entrys of the game like budget release, preview realease, compilaton release, different country release. This was something i wanted to discuss when the new AL was already in early stages but i suspect it is too late now... or? I know what i want when i am researching Atari ST games, how to find new software versions... releases with different packaging and such. I let you read this before writing more just so i know your standing in all this? Also i bet there is an limit on how text a PM can contain :wink:
Stefan Lindberg
Maarten replied :
Hello Stefan,
Thank you for your long pm. It shows clearly the frustration you, as a DB guy, have and this is a bit the reason why I started working on AL again and in the way I would like to move forward now.
I will try and answer everything as detailed as possible.
Exactly, the same goes for the story about Atari Legend. MugUk, Marcer, Champions and so many others have spent ours updating the DB, yet from 2008-2009 the project was abandonned because the devs (me) just didn't have the urge any more to work on it. So in that respect I do really understand Franck. Working on these projects takes a lot of time (I don't need to tell you this of course), I have been working for 2 years now on the new AL. That is why I want to open everything up. Create API's, downloadable database content, technical document regarding the public, release the complete source code ... just everything. This way, it becomes more something for the scene and if at one point in time I want to take a break, everything is there for every one. I am so happy that all the work that went into AL in the past, will now be used again, even if it isn't as complete as Atari Mania. But that would have never happened if I did start working on the project again and I don't like this way of thinking. Also, regarding Guardians of the past...These kind of projects can be revived again, if they use one central DB (example the new AL db). I want everything to be usable for everyone and vice versa!
All I can say, you are welcome to the team if you want. I am really looking for motivated people with new and good ideas. Regarding your DB idea, well, the AL database currently contains over 170 tables, all normalised and linked together. I'm making the project bigger and bigger. I still need to document it, but I'm doing it in such a way, using schema's and examples, that non technical people can understand it as well. I think you would be amazed. So in that perspective, I/WE are building what you wanted to make. But it is also the scene that needs to accept and embrace this project, because I can not do it all on my own. We currently have about 8 people in the team, but most of them are a bit in active and doing other stuff like the whole disk archiving. I'm currently doing all the coding on my own. That is why I want to release something in 1.5 months so the public can finally see what I am doing and I hope to create interest on all levels. Please continue working on AM, as this is the best game db around and I am not planning to do that work again. I'm still trying to figure out a solution to open all the data, but it is not in my power of course. Currently, I'm really busy for the release, but when it is done, I would gladly do a demo for you, ecplain the DB, explain the structure, welcome you to the team, explain the new forum so we can share ideas! Everything you want...
First things first. It is never to late Stefan! ;-) It is never too late to change the db if we can perfect its structure, all we need to do is convert the data. But that is always doable if we take our time, do a decent analysis and use our heads. No manual work is needed, we write scripts for all this stuff.
I am gonna try and answer your question to the best of my knowledge. In the beginning of this year, I did a new analysis together with Brume and ICS regarding the downloads structure of the new AL project. I've always been a gamer and I don't have the deeper knowledge of different downloads, cracks, hacks, menus ... like you, or Brume or Makaratti has, that is why it is important to talk, discuss and make analysis together.
Everything is very modular based on DB level and on project level. We have a game entry in the db. A game can have a different name, it can be an official release, it can be a budget release ... and so on and so on ... like at AM I suppose. However, we now have created a very elaborate downloads table structure, meaning a game can have all kinds of downloads versions. It can be an official download, a crack download by a single person (coming from a menu - and thus linked to the menu section and to the individuals section (crackers), a menu download ... Seriously, like I said it has been a few months now so I need to read my analysis again. But it is safe to say, the structure is already very deep, the options are fantastic (as Brume wants to build something amazing, with these kind of circular schema's on how valid the download is and stuff like that). When you see the structure and you have ideas, because everything has been modularly build, new tables can be added and linked to the download structure without problems. IT goes really really far. We also have a complete 'MENU' structure ready which is complete bonkers :-) as well as a scene structure for crack and hack teams and everything. For all of these structures, the control panel is ready! however, the actual site isn't yet and the tables are still empty. In a new fase, I will be thinking of ways to fill the db from Stonish, from the scene archiving team, from Fujiology ... In ways we will need as less efforts as possible ...
Regarding the screenshots, you are correct, you don't need to make these again. you can write code to make borders. I had this fun idea to give people the chance to make screenshots go in 'st low' with an interlace effect and in ST mono, stuff like that. but I have put this fun stuff aside as I don't have time, first things first and that is the basic site :-) Auto cropping is no problem as we already do this, I have writting a script for that.
If you have more questions, don't hesitate to contact me.
Cheers, Maarten
STEFAN replied :
Hi Maarten and thanks for your reply :)
First i think you misunderstod about screenshots with border, i always want to document as detailed as possible and having the borders as part of the screenshots made for AL is a way to document the game... many games use different colour for the borders and many other just use black and sometimes you get rasters in the border area...and i have an example of multicolour border with raster effect and thats Wrath of the Demon, check out the following link to see my video on youtube and you see the part of the game use the rasters: https://youtu.be/-1qTULa-g4A?t=24m54s
I did not mean borders should be added automatically by the DB system... they should be part of the screenshot from the beginning.
I do know people don't want to see borders in games or screenshots but i feel the urge to document that.. sorry :) Would you at leat have the option for border screenshots to be uploaded to the DB and then autocropped by the system to 300x200 and then two screenshots is stored in the DB and the viewer can select if border screenshots should be viewed or the borderless one. I think using Steem SSE option "border:large" would be useable and it saves the screenshots in 416x275 reolution.
And another thing that i actually suggested at AM and it was added by Franck is to use PNG, actually i think only PNG should be used for screenshots at AL... jpg add compression artifacts... gif is limited to only 256 colours... and also PNG is a free format :)
So much to discuss about even simple things like screenshots :)
More about the layout and game entry. At Atarimania so is the games seperated by publisher (and then again by country or distributor) and i guess it is the best way to use... i don't really have any other ideas how it should be made if not that way... this was one thing i always would have liked to discuss with other people how it should be done.
I use the AM and even HOL and moby games for research about different verisons of games and such. And now i come into screenshot subject again... something i want when research about games is that the screenshots specify wich version of the game they come from... once again see the Cisco Heat example i mentioned in the previous PM, the AM entry for Cisco Heat was not using screenshots from the actual dump that was downloadable from the entry... so in AM case so would it be very possible to have screenshots exclusiv from that specific entry (if downlaod is available) but most of the time so is the same screenshots used for all releases of the game (not talking about Cisco Heat in that case as it only had one official release)... and i think it is like that just so some entrys with no dump available would have no screenshots and then when a dump becomes available so is the screenshots not changed.
So for example a game is first released as full price in UK, France and Germany, this would be one entry on the DB and the are seperated later into sub-entrys (or what to call it... i am no DB coder) by country... in AM so do they have seperate pages when browsing, and when in this way i would like that each page showing the country version use screenshots from a dump that comes from the country release they show... like browsing the page with the german release shows screenshots taken from the german release dump and not the UK release even if the game is still in english for the german release... this is just so the actual entrys can be useful for research and documenting the history of Atari ST games in detail. the same game might get an budget release later on... lets say Kixx label and then of course that entry will have screenshots from a dump of the Kixx release and not the first fullprice, but of course if no dump is available then maybe a place holder pic from the fullprice release can be used instead of nothing.
Now i have been using screenshots a lots as a way to explain how i use databases but the stuff i said about screenshots go for dumps also... for example dumps of the UK release should not be used as download for the german release even if the game for both releases use english language and looks identical. This means contributing dumpers should be as detailed as possible when contributing games and alawys supply a photo of the games disk(s) and/or game box... much like i do when i post dumps here at AF's SCPro forum... see example:
Everyone these days have access to a digital camera (all mobile phones have it) so there is no excuse not to include it together with the dump.
I hope this was not too confusing... i am quite good at english but no expert in writing in it as it is a foreign language to me :)
And then there is how the pirate menus should be presented in the DB? how is it solved now? And all those HD patched games like from Atarizoll (ppera).
Stefan Lindberg
Maarten replied :
Hello Stefan,
It is clear to me that I could really use someone like you to help think about the db structures, too bad you weren't there 2 years ago. You do give me a headache for sure, because what you propose here goes really, really deep imo. But than again, I am no archivist or db guy, so ... read on ...
AL only uses png for screenshots. So, if I understand correctly, you are not only talking about a physical screenshot, but also about preserving all the info regarding the borders (which you think you could explain by use of screenshots) , right? So from a technical DB pov I need to ask the question (let's do this exercise as an example), the difference in borders, is this per game, or can a single game have different versions with different border styles? If the answer is NO, we could link 1 or more tables containing to the game main table, like a game_border table. This table contains all kinds of info regarding the border (the technical stuff you mention above) and this table could also be linked to the screenshot table, so you have the chance to add a screenshot with the special borders. That could be a very nice and modular solution. If a game has more border types by release or download, these tables could be linked to the download tables. You see, such an addtion to the existing tables structures is easy, as long as you made a well thought out structure (which I thought we already had - but after reading your email, I see we are lacking in some parts - read on).
Ok, first off, I would really like to discuss our complete game structure with you at one point in time. Our game structure has mostly stayed the same as AL1.0, and I think the game structure of AM might be better, I don't know. It is impossible to discuss about this in a pm, without the DB schema's but I do have some remarks and thoughts. When I look at AM for Cisco Heat, I see 1 entry. However, the game has different countries. Compare this to the way 'Secret of Monkey Island' is setup at AM, this has an entry for each country version. This doesn't seem uniform to me, as it seems in the AM DB, Secret of Monkey island is setup per country, while cisco heat isn't.
Now, over in the AL DB, we create a game, we link as many publishers and developers and authors to this game. We are also able to link a country and extra info to a publisher and developer. Example, Cisco heat can be released by image works as a main release in the USA, but it can also be released by Renegade as a budget title in the UK. The same goes for release year, extra info (like budget, main release...) can be linked to the year. However, the fact remains that all this info is mixed together and linked to 1 main game entry!!!! And I think the same is done over at AM, and that you guys "solve" this by adding a game more times in the DB with different info (which is an ok solution, but this could be made better on a db level - this is something I would definitely want to think about with your AFTER the first release, if you and others are interested).
HOWEVER, now for the interesting part. When you talk about your versions and screenshots of a game, you are always talking about it together with a DUMP of that game. So in other words, you want to add these screenshot types and other info to a download. This is another way of thinking about it. We over at AL have a very deep downloads structure. So a download is linked to a game. This download (or dump as you call it) can have its own language, its own county, its own type (is it official, a crack from a menu...). So you see, it is again a bit the same as the BORDER story above, at what level do you link this in the structure.
I absolutely have NO concerns regarding the border and dump story you are telling me here. These things are additional information and can be added to our existing structure in a very coherent way, which I would gladly provide (however, how we will get all the info (from AM???) or who will fill all the tables - That is another story!). What does concern me is what you have told regarding the different country versions! This is something that doesn't seem completely right at AL, nor at AM. I think this could be made better, because the way I see it now, at AM you have all this info regarding countries mixed together linked to one game, or you have multiple DB entries of the same game (like monkey island), which is also not 100% correct from a DB analysis perspective (as you create redundant data). Maybe I am wrong here as I can not see the DB structures of AM, but I think I am correct.
I would really like to copy our discussion to our AL dev forum so Bruno, MArcer, ICS and the others can read and share their opinion on this, so maybe I can do small conversions to the DB at game level to make it better. But more thought and analysis are needed.
1 concern remains Stefan. I am not a fan of doing a job twice. So in the end, I can build all this great stuff, my heart would break if we need to do all the work, that has been done over at AM again in a new DB structure of AL. The reason I want the DB to be open to everyone is just to avoid this kind of stuff. So this is something we also need to think about. You are saying you also use moby games for research. I know Moby is developing an API, which gives developers the oportunity to link to moby to fill their DB. This is what I will do in the future release, so no manual work is needed. I want to do this with other projects as well, to build the ultimate open source ST DB for the scene.
We need a guy like you on the dev board, and I think it would be good if you also learn a bit about DB structures so you can participate on a more technical level on the discussions. I can always learn you a bit by use of schematics I have made, it will be much clearer for you when you see these things...
If you have more remarks, or if I have misinterpreted some of your info again, let me know ... keep these questions coming ;-)
Cheers, Maarten
STEFAN Replied :
Hello Maarten :)
You are correct it is difficult to discuss
What you said about screenshots is exactly what i ment but i did not know how to explain it in a good way but your words are excellent when you said i would like to document the borders by using screenshots :) And i would like that screenshots should always be made and uploaded to the DB with borders as standard. I dont know if there is a game with differnt verison that use different border... but thats something that could be discovered if screenshots with borders are used.
About Cisco Heat and Monkey Island... First have in mind that all info at AM is not correct, it gets updated all the time :) I belive Cisco Heat was only released in english by the same publisher and thus gets one entry in the database while Monkey Island have specific version for other countries like France for example in wich the gamebox is is in french and manual in french and the game is in french.
I like how AM is structured... but it is not perfect and can get better but it is the best one available right now. AM is the best game DB on the internet for any system... HOL and Moby Games have no chance compared to it, the main reason i use HOL for research is because it lists compiliations in the entry so you know wich compilation the game was used in since most of the time so was the same compilation released for both Amiga and Atari ST... sadly so does not Atarimania list compilations in game entries, i have suggested it many years ago but Franck has not yet made an update to support it.
About "dumps"... i use the word "dump" becuase it is easier to write than the word "downlaod" :wink:
In AM DB so are a game first added with basic information and such but do not get an entry until you add an "publisher", lets take "Bad Duded vs Dragon Ninja" as an example... if you serach "Dragon Ninja" at AM you get 2 hits... one from publisher Imagine and one for the budget release Hit Squad. And in the Imagine entry so can you find scans of the Imagine gamebox and a downlaod that is from the Imagine release of the game and in the Hit Squad entry so can you find scans of the Hit Squad box and downloads of the game disk taht is from the Hit Squad release. And this is good way to seperate different releases and downloads... and if i get my wish fullfilled so should these two entries use screenshots taken from the download on each page.... like the Imagine entry use screenshots taken from the Imagine download and the Hit Squad use screenshots from the Hit Squad release. And of course the downlaods used in these entries must come from the particular release, and as i understand so are downloads clearly seperated in the new AL so that should not be a problem in case the new AL begin to use a similar structure as AM.
I was thinking if i should show you the interface we use at Atarimania when adding games and edit the database.. i mean the one Franck supplied to us moderators, do you think it is ok if i show it to you? screenshot of it or video.
Stefan Lindberg
MAARTEN replied :
Thank you for all this information. Just talking about this has given me food for thought, so to speak. I have learned a lot. At first sight, I really like the way AM is setup. You create a main game and it gets online when it is linked to a publisher. It seems very well thought out. I wonder how this looks on a DB level.
Stefan, I hope you don't mind, I want to share this conversation with the AL team, see what they think and how we could expand and make our game structure better. I really like the job we are doing, but it seems to me the way we handle different releases is not good.
This all being said, the main problem stays, as expected. I can put all this effort in building the ultimate Atari ST database (and I am happy I can expand from what we had), the fact of the matter is that I'm am doing work, that is already done. This is a bit stupid, but I don't know how else to solve it. I think there should be an open source Atari ST database! So I'm building it as part of the AL project.
I just wish that we were all working on the same project ...
Anyhow, I'm very interested in seeing the AM admin pages, but I don't want to look like I'm spying. I am all for complete transparancy, but of course, not everybody thinks the way I think. So if it is up to me, you can show me the AM backside, but I don't want anyone to get in trouble.
Like I said, you are also welcome to the AL team, to help think about db structures and ways to AUTOMATICALLY fill the database (we don't want to do manual work that has already been done in the past). And of course, you can stay on the AM team simultaniously.
For now, I still need to code. I just want to release some stuff soon so the work we have been doing in the past 2 years can finally be shared with the public.
Cheers, Maarten