Cedar Creek makes available all data supported wholely or in part from LTER funds in accordance with LTER Data Access policy. The large majority of data is Type I, and is released within 2 years of collection. Data is freely available, though users must create an account to access full datasets. Users agree to Cedar Creek’s data use policies
All Cedar Creek data, metadata, personnel information, and publication information are stored and organized in an Oracle database. EML and text files are dynamically generated through php and PERL scripts via the Cedar Creek website. Archival text files are also generated and stored in a hierarchical directory system on a central server as a primary data archive.
Cedar Creek web and database servers are maintained by the Minnesota Supercomputing Institute. The web server runs SUSE SLES 10.2, and has 1 CPU with 2 gb of memory. The database server has 16 CPUs, 128 gb of memory and is running Oracle Database 10g release 10.2.0.4.0.
QA/QC is designed into all data and sample collection protocols. Multiple levels of independent checks at the sample collection and processing level are designed to minimize error. Additional series of checks at the data processing stage are intended to eliminate incorrect data. QA/QC protocols for plant productivity sampling can be seen here.
All Cedar Creek computers undergo daily incremental backups to a central backup server. This backup server is mirrored on an offsite server. The offsite server is baked up to portable media and stored for 3 weeks.
The Cedar Creek Oracle database and web server has full weekly backups as well as daily incremental backups. Copies of backups are made to portable media and stored for 30 days. All database tables are also stored as text files to provide for the possible need to migrate data to new database or other data management systems. Additionally, all datasets, with associated metadata, are stored as text files on the web server and information management computers for long term data accessibility and flexibility for future data needs. All database tables, archive files, and information management working files are backed up annually to portable media and stored in on-site and off-site safes. Each annual backup includes all prior year backups, thus keeping all information on media compatible with current technology.
