updates to readme
							parent
							
								
									6947e8946e
								
							
						
					
					
						commit
						d96f0b3429
					
				
							
								
								
									
										17
									
								
								README.md
								
								
								
								
							
							
						
						
									
										17
									
								
								README.md
								
								
								
								
							|  | @ -14,6 +14,23 @@ Also, most use cases of this data will likely be read only, so the sqlite | ||||||
| limitations on concurrent writes won't be an issue either. Finally, it's | limitations on concurrent writes won't be an issue either. Finally, it's | ||||||
| permissively licensed. | permissively licensed. | ||||||
| 
 | 
 | ||||||
|  | # Where we need the most help right now | ||||||
|  | 
 | ||||||
|  | ## Spells | ||||||
|  | It's time for everyone to put physical eyes on the `data/yaml/spells.yaml` file | ||||||
|  | and compare to **the actual print book or PDF** (taking into account any Errata | ||||||
|  | of course). The scrape could only do so much and there are many small errors | ||||||
|  | here and there. Please see issue #61. | ||||||
|  | 
 | ||||||
|  | Once we have the data proofread, I'll write a glue script to get the spell data | ||||||
|  | into normalized sql form. | ||||||
|  | 
 | ||||||
|  | ## Monsters | ||||||
|  | Come over to issue #40. We need help getting monsters into our (tentative) yaml | ||||||
|  | schema that you can see in the Ancient Red Dragon in `data/yaml/monsters.yaml`. | ||||||
|  | Once we have the data put together I'll write a glue script to get the monster | ||||||
|  | data into normalized sql form. | ||||||
|  | 
 | ||||||
| ## Roadmap | ## Roadmap | ||||||
| 
 | 
 | ||||||
| 1. Get data in YAML format (~~spells are in JSON for the time being; but will | 1. Get data in YAML format (~~spells are in JSON for the time being; but will | ||||||
|  |  | ||||||
		Loading…
	
		Reference in New Issue