eBAGIS Database Schema

BAGIS Schema Diagram

New schema diagram:

http://webservices.geog.pdx.edu/media/django_models.png

Old schema diagram:

https://drive.google.com/file/d/0BxVoOyGIutlLZzhTUk04SEd4UUk/view?usp=sharing

Entities

Relations

• AOI has AOI layers (1-M)

  • AOI layer could be a raster layer (1-1/1-M for archived layers)

  • AOI layer could be a vector layer (1-1/1-M for archived layers)

  • AOI has documents (1-M - no archiving option)

  • Document could be a map document (1-M - no archiving)

  • Document could be a document file (1-M - no archiving)

  • Document could be an image file (1-M - no archiving)

  • AOI has HRUs (1-M)

  • HRU has HRU layers (1-M)

  • HRU layer could be a raster layer (1-1/1-M for archived layers)

  • HRU layer could be a vector layer (1-1/1-M for archived layers)

  • HRU has HRU profiles (1-M)

  • HRU profile has profile parameters

  • HRU has parameter layers (1-M)

  • Parameter layer could be a raster layer (1-1/1-M)

  • Parameter layer could be a vector layer (1-1/1-M, current BAGIS-P databin doesn't have any vector layer)

Considerations

• • Support geoprocessing

  • Support web mapping

  • Support versioning / archiving

  • AOI boundaries geometry stores in the DB as well as in shapefile

  • A separate AOI layers catalog file is stored as .xml and updated when desktop BAGIS updates the AOI. The file is used for version control when the AOI is uploaded to the server.

Versioning, Archiving, and Purging

• • eBAGIS DB will not support concurrent editing. Later (newer) uploads change older data on eBAGIS to "archived" status.

  • Users have the option to not archive an existing AOI during upload.

  • General users only see the "current" version of the AOI data. Advanced users have the ability to select "archived" data for export and analysis.

  • AOI internal DEM and its derivative layers cannot be updated (per AOI creating workflow). PRISM, SNOTEL, and Snow Course could be updated. See the table below for the AOI layers and their archiving rules. The archiving rules are:

    • Modifiable = X, Versioned = N: Not managed in eBAGIS - these data will not be uploaded to eBAGIS

    • Modifiable = N, Versioned = N; Cannot be altered; These layers can only be uploaded as part of a new AOI; An existing AOI of the same name will prevent these layers from being uploaded

    • Modifiable = E, Versioned = N; No archiving - duplicate data will be overwritten

    • Modifiable = E, Versioned = I; Individual archiving - duplicate data will be archived individually

    • Modifiable = E, Versioned = G; The whole group of data will be archived if any of its components is updated

  • A PURGE tool to permanently remove all archived layers in an AOI will be available for System Admin users.

  • Dependencies to consider:

    • If parameter source data changes, it may no longer support the calculated parameters in the parameter tables

    • If settings change for profiles, methods, settings.xml, the configuration may no longer support the calculated parameters in the parameter tables

    • If an hru definition is uploaded the hru log should be included

    • If supplemental layers are changed and they were used in the rules to create an hru, may no longer support hru results