[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Gathering package upstream meta-data in the UDD. (was: Re: more formally indicating the registration URL)

Le Tue, Jan 19, 2010 at 03:20:51PM +0100, Andreas Tille a écrit :
> On Tue, Jan 19, 2010 at 10:51:48PM +0900, Charles Plessy wrote:
> > 
> > CREATE TABLE "biblio" (package, key, value);
> > INSERT INTO "bib" VALUES('kalign','DOI','10.1093/nar/gkn1006');
> > INSERT INTO "bib" VALUES('seaview','DOI','10.1093/molbev/msp259');
> > INSERT INTO "bib" VALUES('ballview','DOI','10.1093/bioinformatics/bti818');
> > INSERT INTO "bib" VALUES('kalign','PMID','19103665');
> > INSERT INTO "bib" VALUES('seaview','PMID','19854763');
> > INSERT INTO "bib" VALUES('ballview','Reference-Year','2006');
> > INSERT INTO "bib" VALUES('kalign','Reference-Year','2009');
> > INSERT INTO "bib" VALUES('seaview','Reference-Year','2009');
> > 
> > Note that this is the first time I deal with Python code, so please be indulgent :)
> However, I wonder if we should use an additional table mentioning the
> keys we are actually using.  When I write database applications I just
> do this to make sure no invalid values will propagate into the database
> - but perhaps this is overkill here and consumes resources of the server
> for not much use.

Why not. Maybe other UDD developers can comment ?

I have applied to the collab-qa Alioth group. I will try to provide drafts for
the loading in UDD. But I never programmed in Python, so I do not expect it
will work out of the box. Hopefully, it will save you some typing.

Have a nice day,

Charles Plessy
Debian Med packaging team,
Tsurumi, Kanagawa, Japan

Reply to: