idolpx/csdb-ng

Project to rebuild CSDb from scratch.

CSDb-ng

Let's rebuild CSDb! It's due for some upgrades. Let's make it happen!

Open an issue for suggestions and requirements. Start a discussion to share any relevant information and ideas.

This will be the central shared repo for the project.

More to come soon.

Evolving Schema

csdb-ng's Issues

Don't expose DB id's to the outside world

Add a Guid to the scener/releases/etc etc so that can be used to retrieve a specific release/scener etc.
Also add created/modified/deleted columns for those kind of tables

Define exactly what is what

One major reoccuring problem with csdb is that there are no clear instructions about what the various things in the db actually are, what belongs where, what doesnt belong into the db at all etc pp. So everyone handles this according to their personal pet theories, resulting in endless discussion and drama. The only way to fix this is to have proper definitions written down which then everyone can refer to and follow.

IMHO this has to be done before even making a db scheme - because this is what tells you what your data actually IS.

Use Time Intervals rather than absolute dates

Describe the requirement
We need to be able to specify time intervals for example when a handle was used, changed, then reused again at a later date.
Or for when a member was part of a group, left, then rejoined etc.
Also need to be able to specify if it was an approximate time (around/before/after)
Open ended time frames would work by having a start date with no end date

UI for mobile devices

Is your feature request related to a problem? Please describe.
CSDb is not mobile friendly, I have to do a lot of scrolling, panning and zooming to be able to check out the latest information.

Describe the solution you'd like
When I visit CSDb on a moble device, I get the mobile version which lets me checkout the latest information (releases, forum posts, events etc.) and lets me search for specific items.

Describe alternatives you've considered
I use RSS feeds to stay up-to-date, but it is not searchable and does not allow me access to all content ever.

Additional context
I wouldn't mind having a read-only version with the core data in it, and use the site for editing stuff.

Groups can be member of another group

Very often a group was a member ("sub group") of another group. So not only sceners should be able to be member of a group, but also groups by itself

Two levels of classifying releases

There should be two levels of how a release is categorized. The first level should be a rather small and carefully selected set of fundamental types, eg:

game
demo
graphics
music
tool

each release should relate to exactly one of the above.

the second level should be "tags", and any release can releate to multiple ones, eg

crack
preview
reu
easyflash

etc. there can be many different of these

Add created/modified/deleted fields to each record type

Useful for syncing data

"scener/handle" and "person" must be seperate things

in csdb "scener" is a person, and a scener can have a handle (or more than one).

the fundamental problem with this is, that there are cases where a handle was used by more than one person and appeared as one "scener" (but not as a group of sceners). famous example was "the ministry", which was two people, who joined groups under the single handle "the ministry". the same two people also had their individual handles (Jayce and Marcus). see https://csdb.dk/scener/?id=7956

so it must be possible to:

• a scener ("person") can relate to one or more handles
• a handle can releate to one or more sceners ("persons)

Groups can be in a co-op

Groups can form co-ops for a period of time. Some famous examples are "Success + The Ruling Company" and "Ikari + Talent". Usually those co-ops are mentioned in trivia of the groups involved, or in the case of SCS*TRC a group is created (https://csdb.dk/group/?id=133), which is technically wrong, but that co-op lasted so long it became a group in its own right I think.

Co-ops can create releases and those releases should be linked to the co-op, not the individual groups, but when browsing releases of a member of a co-op, the releases linked to the co-op should also be listed. Listing the releases of a co-op should only list those done under the co-op label, not adding releases of the individual groups as well.

I have never been in a co-op myself, so perhaps some insights of sceners who have been in a co-op might be helpful to work out some details or get additional requirements.

different versions of the same release must be groupable

What the topic says. Currently in csdb every version gets a completely new entry. Instead, certain parts should be inherited from the first version