-
Notifications
You must be signed in to change notification settings - Fork 13
CUAHSI Archive
1. Portal configuration
- Set the domain name to the fully qualified domain name or IP address of your portal.
- Both the units ontology and the measured property ontologies need to be set to "CUAHSI".
2. Archive configuration
- Click on the Archive button from your portal
- Select CUAHSI as the archive name and choose a push frequency which determines how often the data are archived. Enter the following information:
Base URL of Archive: http://hydroportal.cuahsi.org/CHORDS/index.php
Archive Username: chords
Archive Password: chords
- Click Save
3. Verify sites, instruments and variables
- Site names and CUAHSI site codes need to be unique. Be sure you have:
- Specified a site type for each site:
- Specified a topic category for each instrument:
- Specified a measured property and general category for each variable:
4. Configure resources
- Return to archive configuration page.
- Configure resources in the following order: sources, sites, instruments, variables:
5. The archive is now ready to receive data!
- Click on the Check Configuration and click on Enable Archiving to start sending data.
Note: If new sites, instruments, or variables are added, be sure to also configure them in the archive.
The archive jobs link on the archive configuration page leads to a list of existing archive jobs. Each archive job corresponds to a specific time frame as determined by the push frequency. Each archive job will have one of the following statuses:
- scheduled: data values are scheduled to be pushed into the archive
- success: data values were successfully pushed into the archive
- failure: one or more data values failed to be pushed into the archive.
If an archive job has failed, the message will contain the timestamps of the measurements that could not be pushed and the error that occurred.
The archive system is linked to CUAHSI's HydroServer Lite. There are currently some limitation to this system:
- Multiple pushes of the same resource or data value will go through. We have implemented duplicate checking for resources within CHORDS to prevent this from occurring, but be aware that duplicate pushes are possible.
- All resources (sources, sites, instruments, and variables) must be configured before activating the enable archiving button.
- Common configuration errors include not having unique site codes or site names, using a units or measured property ontology other than CUAHSI, and not specifying a site type, topic category, general category, or measured property.
Project Management
- Stakeholders
- Communication
- Use Cases
- Requirements
- Deliverables
- Milestones Associated with a Release
- "Sandbox" Milestones
- Github Workflow
AWS
- AWS Portal Migrations
- Amazon Appliance Workflow
- Overview
- Bringing up a new CHORDS Portal
- Cloud Formation
- EC2 Costing and Memory Constraints
Docker
- Running CHORDS
- Docker on AWS
- Duplicating Docker/Influxdb portals
- Docker on Raspberry Pi
- Docker Details and Tips
- Running CHORDS on Windows 10
Influxdb
Data Formats
Google Maps
Ingest Utilities
Miscellaneous
- Recovery from a full disk
- Github/Dockerhub release scheme
- CHORDS gh-pages and jeykll
- Bootstrap
- CHORDS Portal Web Site
- Dashboard Helper Refactor
- Development Notes
- Heroku
- Meteobridge
- Migrating from mysql to mysql/influxdb portals
- NCAR Wx Stations into CHORDS
- PAWS to CHORDS
- Post Get Query Syntax
- Postgres Testing
- Rails Tips
- Ruby and Rails Resources
- CUAHSI Archive
Historical Archive