Difference between revisions of "Shelby Bice (Research Plan)"
Jump to navigation
Jump to search
ShelbyBice (talk | contribs) |
ShelbyBice (talk | contribs) (→Log) |
||
| Line 30: | Line 30: | ||
'''2/16/2017''' - Talked over project with Ed, began reading existing wiki pages related to patent data and databases | '''2/16/2017''' - Talked over project with Ed, began reading existing wiki pages related to patent data and databases | ||
| − | '''2/21/2017''' - Brushed up on | + | '''2/21/2017''' - Brushed up on SQL, Entity - Relationship model of designing databases |
* In the documentation, I want to briefly explain what the entity-relationship model is before including | * In the documentation, I want to briefly explain what the entity-relationship model is before including | ||
the diagram so that readers have a little bit of background | the diagram so that readers have a little bit of background | ||
| Line 40: | Line 40: | ||
* Definitely need to include more detail about what these do in the documentation | * Definitely need to include more detail about what these do in the documentation | ||
* insert into command inserts a new entry into the table | * insert into command inserts a new entry into the table | ||
| + | |||
| + | '''2/23/2017''' - Read great database design article, dug through some more wiki articles, started reviewing Perl | ||
| + | * What client do we use to interact with the current patent database? | ||
| + | * Will need to determine all the fields that need to be included in the database before finishing the design and ER diagram, will need Ed's input | ||
Revision as of 12:19, 23 February 2017
Overview
Overall goals:
- Create better database that includes all the patent data to which the McNair Center has access.
- More importantly, create documentation of process so it can improved upon/replicated in the future.
General Outline - updated 2/21/2017
- Familiarize myself with SQL, Perl, and database design
- Familiarize myself with existing scripts and schema for existing database
- Design a better representation for database
- Fix scripts if necessary
- Start moving data into new database by querying existing databases (using SQL)
- Use scripts to query new data
- Test database
- Remove extraneous information from database (copies, patents that we're not interested in, etc.)
Documentation I need to include:
- Schema of new database (with justification of design), would like to include a visual representation
- SQL commands that were used to fill database with explanation of what they do
- Clear instructions on where to find scripts in bulk drive and an explanation of what each script does
Project Pages: Shelby Bice (Redesigning Patent Database)
Log
2/16/2017 - Talked over project with Ed, began reading existing wiki pages related to patent data and databases
2/21/2017 - Brushed up on SQL, Entity - Relationship model of designing databases
- In the documentation, I want to briefly explain what the entity-relationship model is before including
the diagram so that readers have a little bit of background
- Found a tool for creating a visual representation called ERDPlus.com - create a standalone instead of an account, can download
Learning commands from Patent Data - SQL Steps
- copy command is PostgreSQL that copies a SQL table to a text file
- DELIMITER set what will separate columns in text file
- HEADER specifies that there will be a header in the text file with the names of the columns
- Definitely need to include more detail about what these do in the documentation
- insert into command inserts a new entry into the table
2/23/2017 - Read great database design article, dug through some more wiki articles, started reviewing Perl
- What client do we use to interact with the current patent database?
- Will need to determine all the fields that need to be included in the database before finishing the design and ER diagram, will need Ed's input
