| SchemaSpy Analysis of sola.transactionExtension to the LADM used by SOLA to track all changes made to data as a result of an application service. | Generated by SchemaSpy |
| Generated by SchemaSpy on Tue May 31 09:59 NZST 2016 | |
| Database Type: PostgreSQL - 9.4.6 |
|
XML Representation Insertion Order Deletion Order (for database loading/purging scripts) |
| Table | Children | Parents | Columns | Comments |
|---|---|---|---|---|
| reg_status_type | 6 | 4 | Code list of registration status types. E.g. current, historic, pending, previous. Tags: FLOSS SOLA Extension, Reference Table |
|
| transaction | 12 | 2 | 11 | Transactions are used to group changes to registered data (i.e. Property, RRR and Parcels). Each service initiates a transaction that is then recorded against any data edits made by the user. When the service is complete and the application approved, the data associated with the transction can be approved/registered as well. If the user chooses to reject their changes prior to approval, the transaction can be used to determine which data edits need to be removed from the system without affecting the currently registered data. Tags: FLOSS SOLA Extension, Change History |
| transaction_source | 2 | 7 | Associates transactions to source (a.k.a. documents) that justify the transaction. Used by the Cadastre Change and Cadastre Redefintion services. Tags: FLOSS SOLA Extension, Change History |
|
| transaction_status_type | 1 | 4 | Code list of transaction status types. E.g. pending, approved, cancelled, completed. Tags: FLOSS SOLA Extension, Reference Table |
|
| 4 Tables | 26 | |||
| 0 Views | 0 |