Pugio Database Structure

[Martin Moser]

Hi Cesar,

thanks for your proposition!

Its complicated.

One exemple: My recreated pugio:

1A2B1, 2A1B1, 3A3B2C2

Yes, indeed :-) )

But the problem with respect to the database is, I think (judging from the helmet database), that we need a system where a pugio can be allocated to one single place. For example, if we had only sheaths we might do it like this (simplified, just to show):

|
---Frame Sheaths
------early
------late
---Decorated Sheaths
---------fully enclosed
---------------Group 1
---------------Group2
---------------Others
---------front plate only
---------------Group 1
---------------Group2
---------------Others

This would make sure that every sheath was just in one category.

We could of course split this in three, so that you have thre parallel entry points to look/search through the database, like

|
|
---Hilts
------(subgroups)
|
---Blades
------(subgroups)
|
---Sheaths
------Frame Sheaths
---------early
---------late
------Decorated Sheaths
------------fully enclosed
------------------Group 1
------------------Group2
------------------Others
------------front plate only
------------------Group 1
------------------Group2
------------------Others


if the database frontend structure allows this without having to maintain the data seperately for all the major categories under which a pugio might fall (Jasper?)...


And, probably the most difficult of all, we'll have to decide on a classification after all - high hopes on you, Crispvs :-) )