SQLite Column Header Naming Convention

Setting	Description
Capitalization	Use Camel Caps or Title Caps with underscores ("_") as separators as necessary to make the column header more readable.
First Column	According to the rules of SQLite, the first column of every table must contain unique entries. Every first row will be called "RowNum" and will be numbered consecutively.
Columns that contain counts	For columns that contain counts, the header will start with "Num" followed by what is being counted. Example: a column showing the number of beams will be called NumBeams.
Columns that contain a RAMSS Unique ID	For columns that contain a RAMSS Unique IDs, the header will start with the member type name followed by a "_" followed by UID. Example: a column of beam unique ids will be called Beam_UID.
Columns that contain member numbers that the user will see on the screen or in a report	For columns that contain member numbers as seen on the screen or a report, the header will start with the member type name followed by a "_" followed by "Num". Example: a column of beam numbers will be called Beam_Num
Columns that contain Labels, generally a user entered label	For columns that contain a text labels as seen on the screen or a report, the header will start with the type of label it is, followed by "_", followed by "Label". Example: a column of story labels will be called Story_Label

Capitalization

Use Camel Caps or Title Caps with underscores ("_") as separators as necessary to make the column header more readable.

First Column

According to the rules of SQLite, the first column of every table must contain unique entries. Every first row will be called "RowNum" and will be numbered consecutively.

Columns that contain counts

For columns that contain counts, the header will start with "Num" followed by what is being counted.

Example: a column showing the number of beams will be called NumBeams.

Columns that contain a RAMSS Unique ID

For columns that contain a RAMSS Unique IDs, the header will start with the member type name followed by a "_" followed by UID.

Example: a column of beam unique ids will be called Beam_UID.

Columns that contain member numbers that the user will see on the screen or in a report

For columns that contain member numbers as seen on the screen or a report, the header will start with the member type name followed by a "_" followed by "Num".

Example: a column of beam numbers will be called Beam_Num

Columns that contain Labels, generally a user entered label

For columns that contain a text labels as seen on the screen or a report, the header will start with the type of label it is, followed by "_", followed by "Label".

Example: a column of story labels will be called Story_Label