Re: [Gusdev-gusdev] BibliographicReference

[Arnaud K. <ax...@sa...>]

Hi Angel

some comments:

Could it be possible to add the following fields:
    * abstract,
    * pubmed_id,
    * medline_id,
    * is_curated,
    * the list of keywords, in a separate table, ReferenceKeyword.

Also, we would like to store each author in a separate entry instead of 
a unique column.

Besides, to facilitate the queries, it would be better to have a many to 
many relationships between BibliographicReference and the two tables, 
ReferenceKeyword and Author.

cheers
Arnaud

Angel Pizarro wrote:

>I want to add a table BibliographicReference to GUS30 SRes, in addition to
>the Reference table, or at least revamp the Reference table by adding the
>missing columns that are in BibRef (attached below).
>
>The reasoning is that the Reference table is a hold-over from parsing
>genbank records for this type of info. Thus the position column refers to
>the positional information from genbank features. Also we have the old
>'remark' column from Jian Wang's days of schema design. Here is the schema
>def for BibRef:
>
>CREATE TABLE SRes.BibliographicReference (
>	BIBLIOGRAPHIC_REFERENCE_ID NUMBER(10) NOT NULL,
>	TITLE VARCHAR2 ( 100 ) NOT NULL,
>	AUTHORS VARCHAR2 ( 100 ) NOT NULL,
>	PUBLICATION VARCHAR2 ( 100 ),
>	EDITOR VARCHAR2 ( 100 ),
>	YEAR NUMBER(5),
>	VOLUME VARCHAR2 ( 100 ),
>	ISSUE VARCHAR2 ( 100 ),
>	PAGES VARCHAR2 ( 100 ),
>	URI VARCHAR2 ( 100 ),
>	MODIFICATION_DATE DATE NOT NULL,
>	USER_READ NUMBER ( 1 ) NOT NULL,
>	USER_WRITE NUMBER ( 1 ) NOT NULL,
>	GROUP_READ NUMBER ( 1 ) NOT NULL,
>	GROUP_WRITE NUMBER ( 1 ) NOT NULL,
>	OTHER_READ NUMBER ( 1 ) NOT NULL,
>	OTHER_WRITE NUMBER ( 1 ) NOT NULL,
>	ROW_USER_ID NUMBER ( 12 ) NOT NULL,
>	ROW_GROUP_ID NUMBER ( 12 ) NOT NULL,
>	ROW_PROJECT_ID NUMBER ( 12 ) NOT NULL,
>	ROW_ALG_INVOCATION_ID NUMBER ( 12 ) NOT NULL,
>	CONSTRAINT PK_BIBLIOGRAPHICREFERNECE PRIMARY KEY
>(BIBLIOGRAPHIC_REFERENCE_ID)
>);
>
>
>
>