g2e
commented
10 years ago This is a separate download and is no longer as much of a concern space-wise. Loading time was improved by limiting to appropriate networks. Unfortunately creating the database takes about a day and isn't something I do often because of the time involved. Web-based sacpz access and tying it in with the database (basically saving any downloaded sacpz info if desired for offline usage) is definitely the way to go. Still need to make it happen though. That will reduce the database (if one is needed at all). When I get to it, I will make the web-based access as the default for getsacpz with a fallback to the database when there is no internet. Another function to save the downloaded sacpz info to the db will finish this issue.
Can we shrink it? It will get worse when the metadata from rdseed 5.X is parsed (requires sacpz read/write updates). We should support web-based access too! We update the db to include any updates found on the web for a specific dataset's metadata. Something like websacpzdb then a unique merge with sacpzdb.