[Websyntax-users] Syntax db structure query

[Adrian C. <ad...@da...>]

Hi Syntax users,

We've recently installed Syntax on our server and have been planning the
database according to our website's content needs. We've been struggling to
understand the best way to customise the software and would really
appreciate some help. Attached is a word document containing a table that
outlines our plan so far for the database tables, indicating the fields of
each datatype, and our basic database fields as well.

The first column - Database fields is the fields of the database. The second
column - Fieldtype is the type of content that field will contain. The third
column - Event DataType Field and other columns with '+' or 'x' in indicate
whether that database field is relevant for each of the datatypes. The Event
Datatype Field Description column and Music DB field description,
etc indicate what that database field is used for in each datatype.

I understand that Syntax works best is for there to be a minimum number of
fields in the database by repurposing fields that are used for a specific
purpose in one datatype (Eg, the Events datatype), for use in another
datatype (Eg, the Music datatype). That occurs for DB field Date3 in the
attached document - the fields are called different names in the different
datatypes.

So basically I have tried to have the least number of DB fields by
repurposing the fields used by the different datatypes in other datatypes to
some extent but am finding it a real mental exercise.

Would anyone mind taking a look at the document and checking out the DB
fields in the left hand side column labelled "MUSIC and EVENTS", and the
items labelled "PEOPLE, PLACES, and ORGANISATIONS", and see if you can see
which if any of the fields can be re-purposed between these two groups of
datatypes? Or if anyone can offer a better strategy for this normaization
process that would be fantastic. I also understand that Syntax needs
datatypes to have identical field types for this to work.

All of this seems very difficult to do quickly, and our project's deadline
is very soon. I'm guessing we could just set up the db with as many fields
as needed by the different datatypes (even if some fields will be used in
only one or two datatypes) and then cut out irrelevant fields one-by-one as
we find
matches along the way. Is that correct (or do we absolutely need to
repurpose all fields among the different datatypes wherever possible from
the very start)?

Are we on the right track?

Regards,

Adrian