A Community Server is a web-based application that receives Open Tenure claims either online or manually when tablet is linked to computer by USB cable. This module explains the uses of aCommunity Server and how to register as a user.
Community Tenure Recording Training Material Community Server – User Training
1. UN FAO, Land Tenure Team
COMMUNITY TENURE RECORDING
Training Material
Community Server – User Training
2. Community Server
• Web based application
• Receives Open Tenure claims either online or manually when
tablet is linked to computer by USB cable
• Provides community access to Open Tenure claims and
community moderated tenure rights including mapping
• Map layers includes claims, Google Earth and wms map layers
including those published by Community Server Geoserver
• Supports community review processes for Open Tenure claims
including editing claims and associated mapping
• Supports community moderation of Open Tenure claims
• Can generate certificates of community recognised tenure rights
• Supports updating of community moderated tenure rights
3.
4. Voluntary Guidelines on Responsible Governance
of Tenure of Land, Fisheries and Forests (VGGT)
For Communities, Open Tenure is an Enabling Technology for the
implementation of the VGGT in that it:
• Identifies and safeguards tenure rights not recorded by formal
land administration
• Engages with all tenure right holders in tenure governance
processes
• Exercises self-governance for communities with customary
tenure systems
• Protects against unauthorized use of land, fisheries and forest
resources
• Ensures citizen and community involvement
5. SOLA Open Source Software
Tenure recording and mapping using mobile devices
Provides community access to & community processing of tenure records &
mapping collected using Open Tenure
System Admin functionality for SOLA software
Supports registration & cadastre functions in Land Office environment
Supports State land administration including acquisition & disposal
Supports systematic (first time) registration
Land Administration
Community Tenure Recording
6. What is Community Server?
• Helps communities to record tenure relationships
existing in their community
• Uses tablet devices and Open Tenure open source
software to record in the field a range of tenure
relationships and map them using satellite imagery
and GPS measurements
• Uses a web based Community Server to store Open
Tenure claims from Community Recorders and to
update those claims when they are accepted and
recognized by the community
8. Tenure Recording & Mapping Roles
Community Recorders
A field based role to record and map tenure rights claims using
Open Tenure
Community Secretary
An office based role that utilises Community Server to tidy-up
Open Tenure claims including any editing to add any new details
received
Community Moderator
The person (or committee of senior representatives of the
community) who reviews Open Tenure claims and, if satisfied,
grants “community recognition”
Community Technologist
The person responsible for the Open Tenure & Community Server
setup, system administration and first level user support
9. Getting Started with Community Server
1 Register as a user of your Community Server
https://demo.opentenure.org
10. Getting Started with Community Server
2 Complete user registration
https://demo.opentenure.org/admin
11. After Field Recording
1 Upload Claim
https://demo.opentenure.org
Menu Claims-Upload
Connect tablet by USB
(set tablet for USB File
Transfers)
Click Browse
Select Export File & Click
on Upload
From Dashboard, Open Claim & Click on Submit
This is a “manual” alternative to the direct Upload
from Open Tenure using internet or wireless
12. Displayed for specified
period
After Field Recording
2 Claim displayed on Community Server
https://demo.opentenure.org
Initial status when
uploaded
Open Tenure is a mobile application developed for both Android and iOS devices that allows citizen recording of tenure rights (a.k.a. crowd sourcing).
For Open Tenue to be used for community based tenure relationship recording not only is there a need for a mobile device running the Open Tenure mobile software application, there also needs to be a “Community Server”.
The Community server can be a cloud based computer on the internet or it can be a regular desktop computer operated by the community either as a stand-alone computer or as part of a network.
The Community Server will run software that makes high resolution imagery available for downloading onto the Open Tenure mobile devices (software such as GeoServer)
The Community Server also needs software that allows tenure data to be uploaded and downloaded by the Open Tenure mobile devices. This software also needs to be able to correct and approve as “community recognised” data that has been uploaded to it from Open Tenure mobile devices. In this trial the software used for this purpose is open source software called “SOLA Community Server”
This suggested workflow will be considered by the community to see if it is appropriate for them. This means it can be changed to reflect the wishes of the community.
The suggested workflow consists of these steps:
Preparation of Mobile Devices for tenure relationship recording field work in a particular area within the community by Community Recorders
In-the-field recording of tenure relationships by Community Recorders and the uploading of complete claims to the Community Server
Display of completed Claims within the community
Review of completed claims for consistency and completeness by Open Tenure Secretary
Moderation of claims by committee of respected community members
Community Recognition of claims
A similar but possibly simplified process would be followed when there are changes in the tenure relationships (such as inheritance)
Open Tenure is a mobile application developed for both Android and iOS devices that allows citizen recording of tenure rights (a.k.a. crowd sourcing).
A Community Recorder must enrol as a user so that they can download and upload data to a Community Server.
They must connect to the internet on a computer or their mobile device and go to the web address for the Community Server – www.otmcf.org
Go to the Registration menu item, select “New Registration” and enter the details including user name, password and email address.
The Community Server will send you an email. Click on the link in the email OR note the verification code and go back onto the internet to www.otmcf.org and select the “Account activation” menu option.
If you do not have an email account inform the Open Tenure Technologist (Neil) or Community Secretary of your user name and they will activate your Open Tenure Community Server user account
A Community Recorder must enrol as a user so that they can download and upload data to a Community Server.
They must connect to the internet on a computer or their mobile device and go to the web address for the Community Server – www.otmcf.org
Go to the Registration menu item, select “New Registration” and enter the details including user name, password and email address.
The Community Server will send you an email. Click on the link in the email OR note the verification code and go back onto the internet to www.otmcf.org and select the “Account activation” menu option.
If you do not have an email account inform the Open Tenure Technologist (Neil) or Community Secretary of your user name and they will activate your Open Tenure Community Server user account
Once you have uploaded a claim to the Community Server, it can be seen by any other person who goes onto the internet and to the Community Server (www.otmcf.org)
You can search for a claim on the Community Server using the claim name, the name of the claimant and the date it was uploaded. You can also look at the Community Map and find a link to all the details that were captured using the Open Tenure tablet. On the Community Server some details such as phone number and email address are hidden to general users to protect the privacy of the claimant and owners. Only the Community Secretary and Moderation Committee can see those details.
There are three new fields that are important to note:
Firstly, a Claim Number has been allocated (15010620 in the example shown on the screen example above)
Secondly, the Challenge expiration is when the time for challenging a claim finishes. So any disputes about details shown in a claim must be recorded and uploaded to the Community Server (in the same way as an ordinary claim) before this date (29 January 2015 in the example shown on the screen example above).
Thirdly, the status of the claim (for a recently uploaded claim this is always ‘unmoderated’)
More claim details can be found, including the map and the supporting documents if you access the claim through the Claim Tabs (found underneath the Claim Number)
Once you have uploaded a claim to the Community Server, it can be seen by any other person who goes onto the internet and to the Community Server (www.otmcf.org)
You can search for a claim on the Community Server using the claim name, the name of the claimant and the date it was uploaded. You can also look at the Community Map and find a link to all the details that were captured using the Open Tenure tablet. On the Community Server some details such as phone number and email address are hidden to general users to protect the privacy of the claimant and owners. Only the Community Secretary and Moderation Committee can see those details.
There are three new fields that are important to note:
Firstly, a Claim Number has been allocated (15010620 in the example shown on the screen example above)
Secondly, the Challenge expiration is when the time for challenging a claim finishes. So any disputes about details shown in a claim must be recorded and uploaded to the Community Server (in the same way as an ordinary claim) before this date (29 January 2015 in the example shown on the screen example above).
Thirdly, the status of the claim (for a recently uploaded claim this is always ‘unmoderated’)
More claim details can be found, including the map and the supporting documents if you access the claim through the Claim Tabs (found underneath the Claim Number)
The following processes occur on the Community Server and are performed by the Community Secretary / Administrator (NOT the Community Recorder):
The Community Secretary can only work on claims that have been displayed on the Community Server for the specified number of days.
The Community Secretary must Assign a claim to themselves so that they are able to make changes to the claim (to improve and correct the claim or to follow the instructions of the Moderation Committee)
The Community Secretary then makes the changes to any of the details describing the claim
The Community Secretary may attach an additional supporting document with their recommendations for the Moderation Committee
The Community Secretary then ‘Approves the Claim’ and then ‘Unassigns’ the Claim using the buttons below the Claim Number and above the Claim tab labels
The following processes occur on the Community Server and are performed by the Community Secretary / Administrator (NOT the Community Recorder):
The Community Secretary can only work on claims that have been displayed on the Community Server for the specified number of days.
The Community Secretary must Assign a claim to themselves so that they are able to make changes to the claim (to improve and correct the claim or to follow the instructions of the Moderation Committee)
The Community Secretary then makes the changes to any of the details describing the claim
The Community Secretary may attach an additional supporting document with their recommendations for the Moderation Committee
The Community Secretary then ‘Approves the Claim’ and then ‘Unassigns’ the Claim using the buttons below the Claim Number and above the Claim tab labels
The following processes occur on the Community Server and are performed by the Community Secretary / Administrator (NOT the Community Recorder):
The Community Secretary can only work on claims that have been displayed on the Community Server for the specified number of days.
The Community Secretary must Assign a claim to themselves so that they are able to make changes to the claim (to improve and correct the claim or to follow the instructions of the Moderation Committee)
The Community Secretary then makes the changes to any of the details describing the claim
The Community Secretary may attach an additional supporting document with their recommendations for the Moderation Committee
The Community Secretary then ‘Approves the Claim’ and then ‘Unassigns’ the Claim using the buttons below the Claim Number and above the Claim tab labels
The following processes occur on the Community Server and are performed by the chair person of the Moderation Committee (NOT the Community Recorder):
Assign the claim to themselves
Approve the claim (button below the Claim number)
Now the Claim is noted as “community recognised”.
Note the status is now “Moderated”
And the colour of the claim in the Community Server map is now blue.
Now the Claim is noted as “community recognised”.
Note the status is now “Moderated”
And the colour of the claim in the Community Server map is now blue.