From what I read of you information, each scriptor should have zero of more scriptures right? and you are working on a app that runs by only ONE scriptor.
Despite this, if you have full control on table, you should go ahead and create a scriptor table and have it's information there, and then link it's ID to each scripture rows. It should help you model and relate data better.
If you don't like that, then you can always just create a simple POJO Scriptor class that capture all that information, and have it loaded at startup of your application (use ApplicationContext for webapp). If you need this information change and persist during the live of application run, then you need provide form and a way to store it anyway. So you might as well use the db.
[ August 08, 2008: Message edited by: Zemian Deng ]