377
edits
Changes
Jump to navigation
Jump to search
Redesign Assignment and Patent Database (view source)
Revision as of 16:29, 8 December 2017
, 16:29, 8 December 2017no edit summary
}}
'''Final Notes''' This is more or less the finalized design for the patent database. Oliver Chang's code (see Reproducible Patent Data, which is his project page) more or less fits the design, though there are some differences and expect differences in variable names. In the future the code should be altered so that the name of variables match up and each table that is listed here exists in the database. The tables for the extra variables that exist for reissue, design, and plant patents have been added, and the instructions for adding tables can be found on Reproducible Patent Data.
'''For Oliver:''' Unfortunately I did not get to finish making the schema in your code fit the schema that is outlined here. For whoever works on this next, whether that be you or another intern, please note that the variable in the schema in the code do not match up exactly with the schema outlined here, except for perhaps the Reissues, Plants, and Designs tables in the Patent database (called patentsj in the code, I believe, but you can create a database with any name of course).
This is an extension of the work I did last semester under "Redesigning Patent Database". Instead of simply reconfiguring the existing database, this project encompasses and full redesign and creation of a new Patent database and a new Assignment database that will be joined together.
====PLANT====
=====Fields=====
* patent_number patent_no (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
=====Fields=====
* patent_number patent_no (varchar(255)) unique identifier for the patent from the UPSTO office, can contain letters hence varchar
* parent_doc_status (varchar(255)) status of the parent application. Probably related to whether the patent application is pending or not
* parent_doc_number (int) probably application number for the parent document
====DESIGN====
=====Fields=====
* patent_number patent_no (varchar(255)) unique identifier for the patent from the UPSTO office, can contain letters hence varchar
* length_of_grant (int) length of grant, most likely in years
* hague_registration_date (date) filing date of international patent application
