SchemaSpy Analysis of sola_cs.administrativeThe SOLA implementation of the LADM Administrative package. Models land use rights and restrictions how those rights and restrictions relate to property and people. Generated by
SchemaSpy
Generated by SchemaSpy on ?? ??? 16 22:00 ALMT 2015
Database Type: PostgreSQL - 9.1.4 SourceForge.net


XML Representation
Insertion Order Deletion Order (for database loading/purging scripts)

Table / View Children Parents Columns Comments
ba_unit 10 3 16 A Basic Administrative Unit a.k.a. BA Unit or Property. Used to link the rights and restrictions over one or more parcels to the parties that hold those rights and restrictions. A right must be homogeneous over the entire BA Unit. Implementation of the LADM LA_BAUnit class.
Tags: LADM Reference Object, Change History
ba_unit_area 2 9 Identifies the overall area of the BA Unit. This should be the sum of all parcel areas that are part of the BA Unit.
Tags: FLOSS SOLA Extension, Change History
ba_unit_as_party 2 3 Associates BA Unit directly to Party. Implementation of the LADM LA_BAUnit to LA_Party relationship. Not used by SOLA.
Tags: LADM Reference Object, Not Used
ba_unit_contains_spatial_unit 3 7 Associates BA Unit with Spatial Unit. Indicates the parcels that comprise the BA Unit. Implementation of the LA_BAUnit to LA_SpatialUnit relationship.
Tags: LADM Reference Object, Change History
ba_unit_rel_type 1 4 Code list of BA Unit relationship types. Identifies the type of relationship between two BA Units. E.g. priorTitle, rootTitle, etc.
Tags: FLOSS SOLA Extension, Reference Table
ba_unit_target 2 7 Identifies existing BA Units that are included in a transaction. Used by SOLA to mark existing BA Units for cancellation when the transaction is approved.
Tags: FLOSS SOLA Extension, Change History
ba_unit_type 1 4 Code list of BA Unit types. E.g. priorTitle, rootTitle, etc. Implementation of the LADM LA_BAUnitType class.
Tags: LADM Reference Object, Reference Table
condition_for_rrr 2 11 Captures any statutory or agreed conditions in relation to an RRR. E.g. conditions of lease, etc. An RRR can have multiple conditions associated to it.
Tags: FLOSS SOLA Extension, Change History
condition_type 1 4 Code list of condition types.
Tags: FLOSS SOLA Extension, Reference Table
Function: ba_unit_name_is_valid 0 Checks if the first and last name for a BA Unit match the naming convention used by this SOLA implementation.
Function: get_ba_unit_pending_action 0 Determines the action (New, Vary or Cancel) that applies to the BA Unit based on the service it is associated with.
Function: get_calculated_area_size_action 0 Returns the sum of any official parcel areas (i.e. cadastre.spatial_value_area) associated to the BA Unit.
Function: get_concatenated_name 0 Returns a concatenated list of all cadastre objects associated to the BA Unit
Function: get_objections 0 Returns a list of dates indicating when objections were lodged against the BA Unit. Used by Systematic Registration.
Function: get_parcel_ownernames 0 Returns a list of names of people associated to the BA Unit as an owner.
Function: getsysregmanagement 0 Used for systematic registration
Function: getsysregprogress 0 Indicates the number of applications at various stages of the systematic registration process.
Function: getsysregstatus 0 Indicates the number of applications at various states of the systematic registration process
mortgage_isbased_in_rrr 2 7 Identifies RRR that is subject to mortgage. Implementation of the LA_Mortgage to LA_Right relationship. Not used by SOLA as the primary right will always be the subject of the mortgage.
Tags: LADM Reference Object, Change History, Not Used
mortgage_type 1 4 Code list of Mortgage types. E.g. levelPayment, linear, etc. Implementation of the LADM LA_MortgageType class.
Tags: LADM Reference Object, Reference Table
notation 4 15 Notations (a.k.a memorials) are text that summarise the affect a transaction has to a property/title. SOLA automatically creates template notations for every RRR change.
Tags: FLOSS SOLA Extension, Change History
notifiable_party_for_baunit 12 Parties to be informed about transaction on baunit.
party_for_rrr 4 8 Identifies the parties involved in each RRR. Also identifies the share each party has in the RRR if the RRR is subject to shared allocation.
Tags: FLOSS SOLA Extension, Change History
required_relationship_baunit 3 8 Identifies relationships between BA Units. Implementation of the LADM LA_RequiredRelationshipBAUnit class. Used by SOLA to represent a range of relationships such as linking a new BA Unit to the BA Unit it supersedes (a.k.a Prior Title) as well as geographic relationships such as all property within a village, or all villages within a region or island, etc.
Tags: LADM Reference Object, Change History
rrr 7 5 22 RRR are the specific rights, restrictions and responsibilities that can be registered on a property e.g. freehold ownership, lease, mortgage, caveat, etc. Implementation of the LADM LA_RRR class.
Tags: LADM Reference Object, Change History
rrr_group_type 1 4 Code list of RRR group types. Used to identify if an RRR is a responsibility, right or restriction. SOLA's representation of the LADM LA_Responsibility, LA_Right and LA_Restriction classes.
Tags: LADM Reference Object, Reference Table
rrr_share 2 1 9 Identifies the share a party has in an RRR. Implementation of the LADM LA_RRR.share field.
Tags: FLOSS SOLA Extension, Change History
rrr_type 4 2 9 Code list of RRR types. E.g. freehold owernship, lease, mortgage, caveat, etc. Implementation of the LADM LA_ResponsibilityType, LA_RightType and LA_RestrictionType classes.
Tags: LADM Reference Object, Reference Table
Sequence: ba_unit_first_name_part_seq 0 Sequence number used as the basis for the BA Unit first name part. This sequence is used by the generate-baunit-nr business rule.
Sequence: ba_unit_last_name_part_seq 0 Sequence number used as the basis for the BA Unit last name part. This sequence is used by the generate-baunit-nr business rule.
Sequence: notation_reference_nr_seq 0 Sequence number used as the basis for the Notation Nr field. This sequence is used by the generate-notation-reference-nr business rule.
Sequence: rrr_nr_seq 0 Sequence number used as the basis for the RRR Nr field. This sequence is used by the generate-rrr-nr business rule.
source_describes_ba_unit 2 7 Associates a BA Unit with one or more source (a.k.a. document) records. Implementation of the LADM LA_BAUnit to LA_AdministrativeSource relationship.
Tags: LADM Reference Object, Change History
source_describes_rrr 2 7 Associates a RRR with one or more source (a.k.a. document) records. Implementation of the LADM LA_RRR to LA_AdministrativeSource relationship.
Tags: LADM Reference Object, Change History
sys_reg_owner_name 13 Used by systematic registration to identify the owners for each property subject to SR.
sys_reg_state_land 11 Used by systematic registration to identify state land under SR.
systematic_registration_listing 7 Used by systematic registration to list parcels subject to SR.
Trigger Function: f_for_tbl_rrr_trg_change_from_pending 0 Function triggered on an update to the RRR table that sets the status of any Current RRR matching the Nr of the RRR record being updated to Previous. Used to implement versioning of RRR records.
         
35 Tables     177  
3 Views     31