One of my tasks here is to synchronise genomic data between ACeDB and a
An issue with this is that ACeDB does not represent exons in transcripts
as individual objects, but merely as tags within a ?Sequence object.
However, I would like to be able to store the unique IDs that these
exons have in the relational database in ACeDB.
Thus, I am considering adding an extra field to the Source_exons tag in
?Sequence to store the exon's id.
I am concerned though, that this is a part of the model which is tightly
integrated with the FMAP display (and possibly much else) and
consequently this could well be a bad idea, in case AceDB's developers
opt to change the Source_Exon model themselves later.
Does anyone have any thoughts as to how this could be achieved in such a
way that it won't break with future releases of ACeDB?
"It is the job of Sales and Marketing to insulate those who know what
they're talking about from each other"
-- I know who said this, but I'm not telling.