Menu

#12 Date/release info for imported data

closed
nobody
5
2015-11-18
2005-03-29
No

Since the update of ChEBI (e.g. update of KEGG
COMPOUND-derived entries) is very time-consuming, it
could be useful to place either date or release no. for
every item originated from KEGG COMPOUND (or for any
other database which we intend to update
systematically). The data could look like:

Synonym ; Type ; Source; Release ; Status
term A ; NAME ; KEGG COMPOUND ; 27.0 ; CHECKED
term B ; SYNONYM ; KEGG COMPOUND ; 28.0 ; OBSOLETE
term C ; SYNONYM ; KEGG COMPOUND ; 28.0 ; CHECKED
term B ; SYNONYM ; KEGG COMPOUND ; 29.0 ; CHECKED

Let's say terms A and B were introduced in KEGG release
27.0; term A is still there (nothing happens); when
ChEBI was updated after release 28.0, new term C was
added and term B was deleted so it became OBSOLETE in
ChEBI; in release 29.0, the same term B was reinstated.

Discussion

  • pmatos

    pmatos - 2005-04-07

    Logged In: YES
    user_id=1169048

    I think this is a good idea. At the moment the only database
    we update is KEGG but once we fully merged with IntEnz this
    will make alot more sense to use version numbers. Another
    way is to store the history of the compound which we have
    also discussed previously. I think this is done in IntEnz.

     
  • Venkatesh Muthukrishnan

    • status: open --> closed
    • Group: --> Next Release (example)
     
MongoDB Logo MongoDB