I have some questions about how closely AceDb graphical user
interfaces are tied to the data and model files. For example, we have
downloaded the sample Acedb at ncbi.nlm.nih.gov, which comes with a
lovely gui that lets you point and click on regions of chromosomes.
Suppose I am not really interested in the sample data this comes with,
and instead want to view my own data with that interface.
My questions are:
1. I presume that I can delete the existing data, and load in my own
data as long as it conforms to the existing model definitions
(schema). Correct?
2. How *closely* does the model definition of my new data have to
conform? That is, I presume that the existing schema could be
modified somewhat without having to alter the code for the gui's
(otherwise the gui's are very brittle). Is there some way of knowing
what part of the model definitions must remain stable?
3. Is there a "library" of such gui's and the requirements they place
on the model definition files?
I am interested in this because we are looking at translating data
"into" and "out of Ace" format. Getting data "out of" Ace format is
useful for integrating data from Acedb databases with data from other
sources, such as relational and ASN.1. Getting data "into" Ace format
will allow us to use the great user interfaces that have been
developed in connection with Ace and still maintain the data in our
own local databases.
If you are familiar with this part of Ace, or know of a document and
its source that would be helpful, please let me know.
Thanks,
Susan Davidson
