7,612
edits
Changes
Jump to navigation
Jump to search
It is possible that ====DESIGN=========Fields=====* patent_no (varchar(255)) unique identifier for the parent document is patent from the parent application - that isUPSTO office, the first patent application filed in regards to an invention. That would explain why Reissue also has several fields related to a child document - a child document could be a child applicationcan contain letters hence varchar* length_of_grant (int) length of grant, which is filed while a parent application is still pending. So most likely in this case, a child document years* hague_registration_date (date) filing date of a reissue international patent would be an application regarding * hague_filing_date (date) not necessarily the same as the filing date of the international patent application, this is the date that was filed while the reissue International Bureau receives all necessary elements for the international patent application was still pending. A child document is either a continuation, disclosure, or continuation-in-part * hague_registration_pub_date (date) datethat the International Bureau publishes the international patent application * hague_international_registration_number ([http://www.patenttrademarkblog.com/parent-and-child-patent-applications/ source]varchar(255)).international registration number* edition (varchar(255)) possibly the edition of the Classification Locarno which determined main_classification====PLANT====* main_classification (varchar(255)) classification for what type of design the patent is for
* Continuing Reissue (XML44)
** Document ID
** Relation
** Document Number
Redesign Assignment and Patent Database (view source)
Revision as of 13:41, 21 September 2020
, 13:41, 21 September 2020no 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==
* 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.
====DESIGNPLANT=========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
====REISSUE====
In the following table, you'll notice lots of fields related to three different kinds of "documents" - a "parent document", a "child document", and a "parent grant document". It is not immediately clear what these three documents represent for a reissue patent. After some research, I think I have determined that these "documents" are, but please know that I do not have definitive proof as there is little available information about these "documents" in regards to a reissue patent. It is possible that the "parent document" is the parent patent application - that is, the first patent application filed in regards to an invention. That would explain why reissue patents also has several fields related to a "child document" - a "child document" could be a child application, which is filed while a parent application is still pending. So in this case, a "child document" of a reissue patent would be an application regarding the same patent that was filed while the reissue application was still pending. A "child document" is either a continuation, disclosure, or continuation-in-part application ([http://www.patenttrademarkblog.com/parent-and-child-patent-applications/ source]). Based on this logic, I think that the difference between a "parent document" and a "parent grant document" depends on whether the parent patent application has been granted. If the parent patent application is still pending (meaning the patent has not yet been granted yet) then I believe the reissue patent will store information about the parent patent under "parent document". However, if the parent patent application has been granted, then the information will be stored under "parent grant document". This seems like the most logical explanation, especially considered the path to any field related to "parent grant document" contains "parent document" as with the example below: us-patent-grant/us-bibliographic-data-grant/us-related-documents/reissue/relation/parent-doc/parent-grant-document/document-id/date Therefore, a particular reissue patent will probably only have the fields filled for either the "parent document" or "parent grant document" if I am right about what they represent. =====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 documentapplication. It is unclear Probably related to 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 application is being reissued. This goes for all fields beginning "parent_doc"pending or not* parent_doc_number (int) probably application number for the parent document
* parent_doc_id (varchar(255)) it is unclear how this is different from parent document number. In the xpaths, the path will be something like ./parent_doc/document-id/doc-number, so it's possible it's not actually different from the document number and rather just a broader category.
* parent_doc_kind (varchar(255)) this may actually denote what the "parent document" is - I will need or may refer to look it's purpose (i.e. reissue, continuation, continuation-in an actually XML file to see what these field looks like-part, etc.)* parent_doc_country (varchar(255)) the country of origin of the parent document* parent_doc_date (date) probably the date the parent document was published In addition to parent document, there is a subcategory that has the same fields (minus status) called parent_grant_document. This is probably a patent that has been granted, given that the field names includes grant, but I am not sure. Again, I am not sure of what all of these fields representfiled* parent_grant_doc_number (int) probably application number for the parent grant document
* parent_grant_doc_id (varchar(255)) it is unclear how this is different from parent grant document number. In the xpaths, the path will be something like ./parent_doc/parent-grant-doc/document-id/doc-number, so it's possible it's not actually different from the document number and rather just a broader category.
* parent_grant_doc_kind (varchar(255)) this may actually denote what the "parent grant document" is , or may refer to it's purpose (i.e. reissue, continuation, continuation- I will need to look in an actually XML file to see what these field looks like-part, etc.)* parent_grant_doc_country (varchar(255)) the country of origin of the parent grant document* parent_grant_doc_date (date) probably the date the parent grant document was publishedfiled* child_doc_number (varchar(255)) probably the application number of the child application* child_doc_id (varchar(255)) it is unclear how this is different from child document number. In the xpaths, the path will be something like ./child_doc/document-id/doc-number, so it's possible it's not actually different from the document number and rather just a broader category.* child_doc_country (varchar(255)) country of origin of the child application
==Connecting Patent database and Assignment database==
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.
** Document Number
** Country (XML43)
Note about fields related to the parent document and/or parent grant document:
* Hague Agreement Data (XML45) - allows people to file design patents in 66 countries with one application
** International Registration Date
** International Filing DataDate
** International Registration Publication Date
** International Registration Number
** 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
