The authors table holds one entry per author per project.  There is no overlap between projects, as in may cases there was no way to determine if and outer of the same name was the same author.  There is required to be at least one author per project.

Definition:

    Column     |       Type        | Collation | Nullable |                  Default

---------------+-------------------+-----------+----------+--------------------------------------------

 author_id     | integer           |           | not null | nextval('authors_author_id_seq'::regclass)

 project_code  | character varying |           | not null |

 username      | character varying |           | not null |

 firstname     | character varying |           | not null |

 lastname      | character varying |           | not null |

 pst_person_id | character varying |           |          |

 is_pi         | boolean           |           | not null |

Indexes:

    "author_id" PRIMARY KEY, btree (author_id)

Foreign-key constraints:

    "projects_authors_fk" FOREIGN KEY (project_code) REFERENCES projects(project_code) ON UPDATE CASCADE ON DELETE CASCADE

Columns:

author_id: an auto-generated id to uniquely identify each author.

project_code: the code of the project the author is linked to.

username: the selected username of the author, from the Proposal Submission Tool.

firstname: the first (given) name of the author.

lastname: the last name (surname) of the author.

pst_person_id: the id of the author in the Proposal Submission Tool.  In some cases this may be usable to determine if two authors are the same person.

is_pi: a true/false field indicating whether the author is the Primary Investigator for the project.  only one author should be marked as PI for any given project.