File name as Unique Identifier?

In many ways I think I got the easiest element of the schema. I simply have to create rules for assigning a unique identifier for each image. I think Dr. MacCall had a good idea from class about simply using the file names of the images as a unique ID. He also suggested adding some identifier of Alabama so that if our schema is used in other databases both the home and opponent names could be known from the unique ID. I think using the file name has a lot of merit as the file names have a lot of good information already embedded into it. The three digit numbers at the end of the file name are likely simply the number of pictures taken and that number might give valuable information as to the image’s relation to other pictures in the game. For instance two of my photos are one number after the other and may be in the same play. This information could be useful when trying to identify relationships between photos.


2 thoughts on “File name as Unique Identifier?

  1. I agree that using some variation of the file name as unique identifier is a smart and straightforward approach to this. As for your comment about using the numbers to designate relationships though, I think this could get a little misleading. For example while I have 2 related images with file names “75_Clemson_131” and “75_Clemson_132,” I also have 2 related images that are not quite consecutive: “MFB_Texas09_CJ02873” and “MFB_Texas09_CJ02878.” I supposes this is good news for me as the person responsible for the Relation element since it reinforces the need for an explicit Relation rule and entry.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s