Couple of things to consider:

--- can an image have more than 1 tag?

--- will additional tags, likely, be added in the future

I would tend to recommend a separate tag file.  It may be overkill, but
in the long run it will be more flexible (especially if either of the
above are true).

Because of the you worded the question "inserting their IDs into the
tag field", it sounds as if there can be multiple tags for an image --
and that you plan on inserting multiple tag IDs into a field of the
image record.  This is a bad practice as the field would not be
normalized (not atomic).

If, you do, in fact have 0-n tags possible for an image, then you have
a many-to-many relationship.  This should be implemented as follows:

      ImageRecord                      QualityTag
     --------------------                   ------------------
                 \                                         /
                   \                                     /
                        ImageToQuality
                       -----------------------

HTH

Dick

On Mar 10, 2004, at 3:10 PM, brobborb wrote:

> Hey guys, the app I am working on allows the user to view images in a
> directory and assign names or other kinds of data to them.��THey are
> basically QCing the images to make sure they are readable.��Sometimes
> they come across images that are too skewed, too dark or too light,
> and they would write this down on paper.��We now want to eliminate
> this by having the user choose tag a note to the image.��All possible
> tags are too light, too dark, poor quality, and cut.
>
>  Each folder consists of about 900 images, and they are QCing by the
> folder.��My question is this....
>   (tbl_images) table.��OR, should I just insert the actual TEXT
> instead, and not the IDs.
>
>  Please help!
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]

Reply via email to