Log inRegister an accountBrowse CSDbHelp & documentationFacts & StatisticsThe forumsAvailable RSS-feeds on CSDbSupport CSDb Commodore 64 Scene Database
You are not logged in - nap
CSDb User Forums


Forums > CSDb Feedback > Suggestion: New release type "C64 Import"
2013-09-14 00:16
bepp

Registered: Jun 2010
Posts: 268
Suggestion: New release type "C64 Import"

Rough started a discussion a couple of years ago (see Adding the cracker group to import/trainer version), pin pointing a problem where a crack may be credited repeatedly for a group - due to the many imports that may exist.

Some attempts have been made to differentiate cracks from import by suffixing the entry with "[import]" - an approach that might not be appealing to all.

Discussions suggest that original crack group (pun intended) be credited only on *their* release, while imports only be credited to importing group, leaving a link to the original release.

My biggest concern is to be able to (quickly) identify and differentiate cracks from import, when checking for existence of a certain release for example. Although this can be partly solved by suffixing the name, I'm not sure it's the right approach. Cleaning up the credits list would partly solve the problem, but I still wouldn't be able to clearly see a difference between crack and import.

So I'm suggesting that we add a new release type. Let's call it "C64 Crack Import" or just "C64 Import" for short. It would be a fairly easy task to just "re-categorize" any imports stumbled upon, and to some extent it could probably be batch-made with an SQL query (Perff?).

It is often talked about that the DB is not designed to handle certain new features (tags for instance), while adding a new release type would make no harm to performance. Also, from a DB design perspective, it would make more sense since you can then do filtered searches where imports and cracks are differentiated. Also in release lists, it would be possible to see the difference.


...


Having import as a release type, it would furthermore be possible to have an option in listings to "Hide imports"... the result of which of course would depend on the quality of the entries, but it *would* be possible. Think future. =)
2013-09-14 15:44
chatGPZ

Registered: Dec 2001
Posts: 11523
we have worked out something that will (also) cover this - its all a matter of perff actually finding some time to implement it - see here
2013-09-14 16:06
bepp

Registered: Jun 2010
Posts: 268
While all that looks wonderful, I can appreciate the effort required to implement it. Introducing a new release type is done very quickly and it would be a good complement to the other suggestions. It would allow us to start using it right away, while Perff gets to work on the more thorough solution.
2013-09-14 16:14
chatGPZ

Registered: Dec 2001
Posts: 11523
and it piles more stuff on top that needs to be removed again and then somehow migrated to the new scheme - i'd rather see this done properly right away.
2013-09-14 17:50
The Shadow

Registered: Oct 2007
Posts: 304
I suggest adding one distinction to this release type: Imported Crack

This makes it apparent that the release type started out as a crack and was imported.
2013-09-14 19:11
Mason

Registered: Dec 2001
Posts: 467
Also it would be nice if the imports was splitted in legal imports and not
2013-09-15 08:46
bepp

Registered: Jun 2010
Posts: 268
@The Shadow: Yes, Imported Crack would prolly be a better name.

@Groepaz: I've reviewed your suggestion again and if I understand it correctly, it would still have the release type of crack, with a "flag" property saying whether it is an import etc.

I'm a bit curious to know how this is intended to be presented in search results and release lists? At the end of the day I want to be able to distinguish cracks from imports in an easy way. It's all fine with this new meta data when looking at a specific entry, but when you have a list of entries, how would you present it (to be able to distinguish it)?
2013-09-15 10:14
bugjam

Registered: Apr 2003
Posts: 2720
I would prefer only "import", which would also cover the (few) imported/fixed demos.
2013-09-15 12:34
chatGPZ

Registered: Dec 2001
Posts: 11523
bepp: how it is presented is secondary for the time being - and i am sure perff can easily add whatever filtering is required once its implemented.
2013-09-15 17:43
Moloch

Registered: Jan 2002
Posts: 2972
Quoting bugjam
I would prefer only "import", which would also cover the (few) imported/fixed demos.

Yeah and the imported tools
2013-09-15 17:57
chatGPZ

Registered: Dec 2001
Posts: 11523
thats exactly why we want to make it a general flag and not add a releasetype for it :)
 
... 34 posts hidden. Click here to view all posts....
 
Previous - 1 | 2 | 3 | 4 | 5 - Next
RefreshSubscribe to this thread:

You need to be logged in to post in the forum.

Search the forum:
Search   for   in  
All times are CET.
Search CSDb
Advanced
Users Online
Pac
Solo Kazuki
Mythus/Delysid
Scooby/G★P/Light
megasoftargentina
Guests online: 177
Top Demos
1 Next Level  (9.7)
2 13:37  (9.7)
3 Codeboys & Endians  (9.7)
4 Mojo  (9.6)
5 Coma Light 13  (9.6)
6 Edge of Disgrace  (9.6)
7 Signal Carnival  (9.6)
8 Wonderland XIV  (9.5)
9 Uncensored  (9.5)
10 Comaland 100%  (9.5)
Top onefile Demos
1 Nine  (9.7)
2 Layers  (9.6)
3 Cubic Dream  (9.6)
4 Party Elk 2  (9.6)
5 Copper Booze  (9.5)
6 Scan and Spin  (9.5)
7 Onscreen 5k  (9.5)
8 Grey  (9.5)
9 Dawnfall V1.1  (9.5)
10 Rainbow Connection  (9.5)
Top Groups
1 Artline Designs  (9.3)
2 Booze Design  (9.3)
3 Oxyron  (9.3)
4 Performers  (9.3)
5 Censor Design  (9.3)
Top Webmasters
1 Slaygon  (9.7)
2 Perff  (9.6)
3 Sabbi  (9.5)
4 Morpheus  (9.4)
5 CreaMD  (9.1)

Home - Disclaimer
Copyright © No Name 2001-2025
Page generated in: 0.083 sec.