The letters between Justice and the FSC back in June of '05 clarified some of these issues, and those clarifications have been addressed in the newest regulations (the ones that go into effect in March.)

For a database-driven site, the regulations now only require some way of identifying the depiction (image or video) and linking it to the required 2257 identification and cross-referencing information, which is a much more reasonable way of approaching the situation.

The way we accomplish this is to use a file naming structure that identifies the set ID and individual image or video ID (as well as various other attributes of the scene, such as whether it's explicit, nonexplicit, single model, or multiple model.) That set ID is cross-linked in our 2257 database to all of the model's required 2257 information, ID images, other scenes and/or DVDs the model is in, other stage names he's used, etc.

When the page is displayed, the HTML generated by PHP has the filenames of all the images or videos, and those filenames directly reference back to the sets and ID information.

There are probably other ways of doing that, but this method was the best we came up with.