Difference between revisions of "Reproducible Patent Data"
Jump to navigation
Jump to search
| Line 4: | Line 4: | ||
|Has start date=May 17 | |Has start date=May 17 | ||
|Has project status=Active | |Has project status=Active | ||
| − | |Does subsume=Redesigning Patent Database, Patent Data Restructure, | + | |Does subsume=Redesigning Patent Database, Patent Assignment Data Restructure, |
}} | }} | ||
A continuation of [[Redesigning Patent Database]] that aims to write faster, more centralized code to deal with the USPTO data. By having an end-to-end pipeline we can easily reproduce or update data without worrying about unintentional side effects or missing data. | A continuation of [[Redesigning Patent Database]] that aims to write faster, more centralized code to deal with the USPTO data. By having an end-to-end pipeline we can easily reproduce or update data without worrying about unintentional side effects or missing data. | ||
Revision as of 14:08, 25 May 2017
| Reproducible Patent Data | |
|---|---|
| Project Information | |
| Project Title | Reproducible Patent Data |
| Owner | Oliver Chang |
| Start Date | May 17 |
| Deadline | |
| Primary Billing | |
| Notes | |
| Has project status | Active |
| Subsumes: | Redesigning Patent Database, Patent Assignment Data Restructure |
| Copyright © 2016 edegan.com. All Rights Reserved. | |
A continuation of Redesigning Patent Database that aims to write faster, more centralized code to deal with the USPTO data. By having an end-to-end pipeline we can easily reproduce or update data without worrying about unintentional side effects or missing data.
