377
edits
Changes
Jump to navigation
Jump to search
Redesign Assignment and Patent Database (view source)
Revision as of 17:22, 3 November 2017
, 17:22, 3 November 2017→Unique Attributes Tables
===Unique Attributes Tables===
There are several attributes that have been identified and are unique, applying to only one kind of patent. Instead of adding all these fields to the main patent table, which will introduce a lot of NULL entries because three out of four patents will not have any particular attribute. Therefore, I have created three new tables to store these unique attributes - one for each type of patent with unique attributes.
For each table, the primary key is the patent_number, which connects a row to a row in the main patent table.
TODO: Figure out best way to generate these tables.
* Note that I did include some unique attributes for Utility patents as seen below in the "Finding New Paths Unique to Plant, Reissue, and/or Design Patents" section, but for now (11/3/2017) I'm not going to create a separate table for those fields. Most of them seem to be repeated in Reissue, and the other fields, while interesting, are perhaps not very useful.
====DESIGN====
* patent_number (varchar(255)) unique identifier for the patent from the UPSTO office, can contain letters hence varchar
* latin_name (varchar(255)) latin name for the plant
* us_botanical_variety(varchar(255)) denotes what variety of plant it is - for example, a rose has several different varieties
====REISSUE====
For Reissue
* parent_doc_status (Varchar(255)) status of the parent document. It is unclear whether this refers to a parent reissue application (if there happen to be multiple applications relating to the reissue of this patent) or the patent for whom the reissue is being reissued. This goes for all fields beginning "parent_doc"
* parent_doc_number -
*
====PLANT====
