Changes

Jump to navigation Jump to search
no edit summary
{{Project|Has project output=Data|Has sponsor=McNair ProjectsCenter
|Has title=Redesign Assignment and Patent Database
|Has owner=Shelby Bice,
|Is dependent on=Reproducible Patent Data,
}}
'''FOR ED:Final Notes''' I finished adding going through This is more or less the finalized design for the unique paths patent database. Oliver Chang's code (you can 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 unique fields I identified at future the bottom code should be altered so that the name of this page, under "Finding New Paths Unique to Plant, Reissue, variables match up and/or Design Patents"each table that is listed here exists in the database. Then, under my design The tables for the Patent Databaseextra variables that exist for reissue, there's a new section called "Unique Attributes Tables" where I've begun detailing a design , and plant patents have been added, and the instructions for adding tables can be found on Reproducible Patent Data. These three new tables that would include information that is unique to Design, Reissueshould fit the schema seen here, but as stated previously the schema in the code DOES NOT fit the schema here exactly and Plant tablesshould be altered in the future to fit this schema. Here are some questions I have:
'''1.For Oliver:''' Do you like design for the new tables? How do you think we should populate these tables? Unfortunately I can think of one way (putting all did not get to finish making the information schema in your code fit the main patent tables and then moving it out to Plantschema that is outlined here. For whoever works on this next, Reissuewhether that be you or another intern, or Design as needed) but I was wondering if there might be an easier way.  '''2.''' There were some unique attributes to utility patents please note that I also included the variable in "Finding New Paths Unique to Plant, Reissue, and/or Design Patents". They only appear to be the schema in two of the oldest XML versions (4.1 and 4.0) and I'm code do not sure match up exactly with the information is particularly useful - but please take a look at schema outlined here, except for perhaps the field names Reissues, Plants, and let me know if you disagree and think they are useful and should be included Designs tables in a table the Patent database (called patentsj in the patent database. '''3.''' Do you know what some of these fields represent? For example, I've been trying to research online what a "Parent Document" and/or "Parent Grant Document" might represent for a reissue patentcode, and I've found a couple possible options. I will keep researchingbelieve, but if you know what they represent or one can create a database with any name of my descriptions for a field is wrong, please let me knowcourse).
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.
==ER Diagram for Assignment and Patent Databases==
Note: this is currently out of sync with matches the current description design below for but may not match the patent exact database(nor the code that creates the schema of the database currently. It will In the future these should be updated once I have finalized how we will organize unique attributes for plant, design, and reissue patentsmade to sync up.
[[File:PatentAndAssignmentER2Erdplus-diagram (3).png]]
Attributes for each table are listed below with descriptions - because of how many attributes there are, I decided the ER diagram would be better suited as an overview of the tables rather than trying to show all the attributes on the diagram.
 
If you would like to edit the diagram, you can find the ER diagram you can go to https://erdplus.com/ and click "Open Diagram File" under the "Diagram" dropdown, then navigate to E:/McNair/Project/Redesigning Patent Database/New Patent Database Project/ERDiagramforPatentandAssignmentDatabases.erdplus. You should be able to edit the file then.
==Assignment Database Structure==
====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_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
Also in the paper, they mentioned the Assignments on the Web for Patents (AOTW-P), a searchable database of individual USPTO assignment records keyed on reel-frame identification, patent number, and assignor or assignee name (https://assignment.uspto.gov/patent/index.html#/patent/search). Obviously it would not be possible to individually use this tool to query all the patent numbers, but if it would be possible to write a script to somehow query each patent number using the rf_id and parse the response, this could potentially be useful to check the patent numbers, but might not be any more accurate than what will already be in DOCUMENT_INFO.
==Finding New Paths Fields Unique to Plant, Reissue, and/or Design Patents==
Based on Oliver's script which searched all xpaths and compared which were unique to particular types, we see that the following attributes are unique to each type of patents other than utility patents. These attributes vary by the XML version, which changed over time. Therefore, the lists below are a superset of the attributes that are unique to each of the patents types listed below across all XML versions.
** Address
* US Provisional Application Status (XML41)
 
==Paths for the New Fields Related to Plant Reissue, and/or Design Patents==
 
===Plant Patents===
XML 4.4, 4.3, 4.1, and 4.0
parent node: us-patent-grant/us-bibliographic-data-grant/us-botanic
fields: latin-name, variety
 
XML 4.5
parent node: us-patent-grant/us-claim-statement/
field: i
 
XML 4.2
parent node: us-patent-grant/us-bibliographic-data-grant/us-botanic
fields: latin-name, variety
 
parent node: us-patent-grant/us-claim-statement/
field: i
 
===Reissue Patents===
 
XML 4.5
parent node: us-patent-grant/us-bibliographic-data-grant/us-related-documents/reissue/relation/parent-doc/
fields: parent-status
 
XML 4.4
parent node: us-patent-grant/us-bibliographic-data-grant/us-related-documents/continuing-reissue/relation/
fields: parent-doc/parent-grant-document/document-id/date
parent-doc/document-id/country
parent-doc/parent-grant-document/document-id/country
child-doc/document-id/country
child-doc/document-id/doc-number
parent-doc/document-id/doc-number
parent-doc/parent-grant-document/document-id/doc-number
parent-doc/document-id/date
(everything in XML 4.3 except parent-status)
 
XML 4.3
parent node: us-patent-grant/us-bibliographic-data-grant/us-related-documents/reissue/relation/
fields: child-doc/document-id/doc-number
parent-doc/parent-grant-document/document-id/date
parent-doc/parent-status
parent-doc/document-id/date
parent-doc/document-id/country
parent-doc/document-id/doc-number
parent-doc/parent-grant-document/document-id/country
child-doc/document-id/country
parent-doc/parent-grant-document/document-id/doc-number
XML 4.1
parent node: us-patent-grant/us-bibliographic-data-grant/us-related-documents/reissue/relation/
fields:
child-doc/document-id/doc-number
child-doc/document-id/country
parent-doc/parent-status
parent-doc/document-id/kind
parent-doc/document-id/country
parent-doc/document-id/doc-number
parent-doc/document-id/date
parent-doc/parent-grant-document/document-id/kind
parent-doc/parent-grant-document/document-id/country
parent-doc/parent-grant-document/document-id/date
parent-doc/parent-grant-document/document-id/doc-number
 
other parent node: us-patent-grant/us-bibliographic-data-grant/us-related-documents/us-reexamination-reissue-merger/relation/
fields:
child-doc/document-id/doc-number
child-doc/document-id/country
parent-doc/document-id/date
parent-doc/document-id/doc-number
parent-doc/document-id/country
parent-doc/parent-grant-document/document-id/kind
parent-doc/parent-grant-document/document-id/country
parent-doc/parent-grant-document/document-id/date
parent-doc/parent-grant-document/document-id/doc-number
 
XML 4.0 and XML 4.2
parent node: us-patent-grant/us-bibliographic-data-grant/us-related-documents/reissue/relation/
fields: parent-doc/document-id/kind
parent-doc/document-id/doc-number
parent-doc/parent-grant-document/document-id/kind
parent-doc/parent-grant-document/document-id/country
child-doc/document-id/country
parent-doc/parent-grant-document/document-id/doc-number
child-doc/document-id/doc-number
parent-doc/parent-grant-document/document-id/date
parent-doc/parent-status
parent-doc/document-id/country
parent-doc/document-id/date
 
===Design Patents===
XML 4.5
parent node: us-patent-grant/us-bibliographic-data-grant/
fields: hague-agreement-data/international-registration-date/date
hague-agreement-data/international-registration-publication-date/date
us-term-of-grant/length-of-grant
hague-agreement-data/international-registration-number
hague-agreement-data/international-filing-date/date
 
XML 4.1, 4.3, and 4.4
parent node: us-patent-grant/us-bibliographic-data-grant/us-term-of-grant/
fields: length-of-grant
 
XML 4.0
parent node: us-patent-grant/us-bibliographic-data-grant/
fields: us-term-of-grant/length-of-grant
classification-locarno/edition
classification-locarno/main-classification

Navigation menu