Did you read the article on Database design? Was it useful? Yes, very, thank you
The report.pdf is a relationship diagram, and that is what we mean. There are a few general things I'd like to highlight - to make things easier for you.
*Don't use multivalued fields (Sequence etc.).sequence is an attachment field, SpeciesReactivity I "copied" from Suppliers in the Northwind database, because I also need to be able to select multiple values from 3 choices
*Use a naming convention that does NOT allow embedded spaces nor special characters. Limit names to alphanumerics and underscore"_" -- you'll save a lot of extra work.ok, will do
*Make sure your fields represent atomic values --single field, single meaning, single value.check, except Nanobodies table (see later)
*Each table should have a Primary key.check
*tables are related by Primary key and Foreign key check
*Do NOT use the same name for an Entity/Table and a field within that table (Expression Vector, Epitope General, Antigen) will do
*Tables/Entities should each deal with a single subject (Nanobodies seems to represent multiple ideas/thoughts/things. One nanobody is a combination of different properties, that's why earlier post suggested to work with a table linked with lookup tables, as I understood?
I strongly suggest you get your data model/relationships well understood/designed before you get too deeply into coding and comboboxes, checkboxes etc. You need to get the WHAT clear before you get into the various options for HOW.
It would seem that Nanobodies exist independent of Experiments. It seems analogous to Students and Courses to me. To bring Student and Course together, as in StudentIsEnrolledInCourse, you have a new table -- a junction table -- that relates a specific student to a specific course. Other information related to the combination of student and course would be fields in that junction table.
That's why I generated the NanobodiesExperiments table = junction table
You seem to be dealing with a subject matter that is somewhat foreign/unfamiliar to most of us. Going back to my McDonalds metaphor, could you tell us in plain English what you are doing to help us understand your environment and database?
I'm working in biomedical research, a nanobody is basically a small antibody.
I hope you have heared about this? foreign proteins that enter the body ( like on viruses, bacteria) are recognized / bound by antibodies, as part of the immune respons. THis property, the fact that antibodies can recognize a specific protein among thousands of proteins makes it a very usefull tool.
Imagine that you could engineer an antibody to recognize cancer cells, or you label an antibody with fluorescence marker, you could find out where your protein is? In muscle? in nerves? ... . The possibilities are endless
We use this nanobodies in experiments, an experiment is defined by the Nanobodies used, Date, and a comment box (short description). Many to many relationship between Nanobodies & Experiments
To describe a nanobody you have certain properties (see Nanobodies table),
but change one property and you get a different nanobody,
this is acually what is happening now, I have several very similar nanobodies, but different. To have a nice overview, I thought let's make an Access Database ( I worked with access before, but just to make a db of members of a club)
Questions for the db:
1) give an overview of the nanobodies
2) filter out nanobodies by a property
3) Which techniques can you use this nanobody? -} link Experiment
4) Which Nanobodies can be used for a Technique?
thanks for the support,
Sam
