Israel Chauca wrote:
Hi!
> I would like to help with this, it's the least I can do ;)
Great. Welcome to the club. :)
>> Perfectly agree. Additionally, if there're other tags
>> available you could also include them. Usual tags that
>> might be available are:
>
> Throwing away info hurts, usually there is a point when
> you'll need it.
Hi, hi, did some db management recently? ;)
Anyway, the project has IMHO to work out a core of data and
a set of "we really want if we get it" and a set of
normalisations how to handle additional data. Normalisation
is crucial IMHO and it requires work, that has not to be
underestimated. I think e.g. for player names a close work
with Franz Nagl and the spell checking is required.
>> with some thoughts about how to build up the DB at all. E.g.
>> I do not know whether their tags are normalised well.
>> Besides player names also the "event" and "site" tags are
>> often a mess and one of the main inconveniences of my own
>> reference base. Mostly though pgns from a single site are in
>> one common style. Therefore if you e.g. decide to use TWIC
>> for the continous upgrade of the DB (probably a wise
>> decision) one could base the tagging conventions on TWIC,
>> then start adding tournaments and tag them accordingly.
>
>
> How good is the scid db format to work with multiple changes by
> multiple people?
AFAIK you can't concurrently access the DB at all.
> would it be better to use pgn in the middle editing?
Well, I'd suggest to split the stuff on some basis. Either
the sources to work through or the event layer or whatever.
Then you can use whatever format you want. It surely also
depends a bit on your version control mechanism. Tools like
cvs would surely prefer pgn instead of scids binary format
(simply as the diffs get smaller) on the other hand PGN is
huge and it could be that real versioning is not needed but
its more suitable to add e.g. a
[Version "20080722-1"]
or even
[CmailGameName "CentriScid-123456789"]
like tag. The latter ist IMHO worth severe consideration,
as it could serve as a persistend identifier for a game
within the DB. By this it gets "citable" ie. you can
uniquely refer to that game, even from outside. The tag name
is arbitrary, CmailGameName is just currently used in CC
already for exactly that purpose.
From a recent discussion with someone at ChessBase: it would
be a _VERY_ handy featrue if you can generate a diff between
CentriScid-2008 and CentriScid-2009 _easily_ without any
manual intervention. ChessBase can not do that! They told me
that, even internally(!), they could not produce a diff
between Mega2006 and Mega2007. The ability to upgrade my
current installed DB by a Diff to the actual version is IMHO
crucial. The user may add his own tags and propagating them
from one DB to the next without diffs is PITA.
--
Kind regards, / War is Peace.
| Freedom is Slavery.
Alexander Wagner | Ignorance is Strength.
|
| Theory : G. Orwell, "1984"
/ In practice: USA, since 2001
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Scid-users mailing list
Scid-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/scid-users
