Import and export

Every register can be downloaded as Excel, CSV or a print view, with the filters and columns you choose; registers with outlines also download as GeoJSON or KML. Most records can be added or updated in bulk from a spreadsheet, and boundaries from a map file.

Export

Needs data.export and the register’s view permission

  1. Open the register. Set the filters and sort you want, and tick rows if you only want some.
  2. Click Export (beside the count). The export dialog opens with the list’s filters already filled in.
  3. Rows: everything matching the filters, only the ticked rows, or only the rows on this page.
  4. Filters: change them here without leaving the dialog. The count beside the heading follows every change, so you see how many rows you will get before downloading.
  5. Columns: untick what you don’t need (All / None to start over). Your choice is remembered for that register.
  6. Format: Excel (.xlsx), CSV, GeoJSON or KML (registers with outlines: properties and projects), or Print view (A4).
  7. Click Download N rows, or Open print view.

What can be exported

WhereExport
RegistersProjects, properties, claimants, surveys, compensation cases, conflicts, spatial flags, background jobs, staff, messages and message deliveries: Export beside the count. Fill the gaps exports the incomplete records it lists.
Properties page headerExport items: every item on the properties matching the filters (ref no, project, dictionary, code, item, quantity, unit, rate, value). The same layout imports back.
Compensation cases page headerCase lines: what each listed case pays for, line by line. Payment schedule: the cash cases approved or with a cheque issued, with the claimants’ bank details.
Any record’s Minutes tabExport: its minute sheet (when, action, from → to, note, by).
Any record’s Evidence tabList: the documents attached (kind, description, file name, size, who uploaded it and when).
Map page headerExport projects: every project, with its boundary in GeoJSON or KML.
A project’s Map tabGeoJSON / KML: the project boundary with all its properties.
Dictionaries page headerExport rates: the current rate of every priced item in every dictionary, in one sheet. Each dictionary also exports its own items.
Administration › TagsExport: the tag list (name, group, colour, applies to, rules, records using it).
LocationsExport: every LGA, ward and area.

Source columns say how a record was captured: Office, Field, Import or Map scan draft. Missing lists what the record still lacks, in the words of its completeness checklist.

Import

Needs data.import and the permission to change those records

  1. Click the import button in the page header (see the table below).
  2. Download the template (Excel or CSV) and fill it in, one record per row. The Excel template has dropdowns for fixed lists. An export of the same register can be edited and imported back instead.
  3. If the import has a choice of how rows are applied (property items: add and update or replace), choose it.
  4. Choose the file and click Check file. Nothing is saved yet.
  5. If the file’s headings don’t say which column is which, the dialog asks: for each column of your file, choose what it holds (or “not imported”), then click Check file again. A file with unused columns offers Choose the columns too.
  6. Read the result: how many rows would be New, Update, Remove or No change, and every problem by row and column.
  7. If there are problems, fix them in the file and click Choose another file. Otherwise click Import.

What can be imported, and how rows match

Import (where)Matched byRequired columnsOther columns
Projects (Projects › Import)Project codeProject code, NameLGA (name), Status, Start date (YYYY-MM-DD), Description, Tags
Properties (Properties › Import)Ref noRef no, Project code, Property type, LGAWard, Area, Address, Land area (m²), Latitude, Longitude, Claimant ID (e.g. CL-0012), Notes, Boundary, Tags
Property items (Properties › Import items)Property + dictionary code (or custom item name)Property ref no, QuantityDictionary code, or Custom item with Custom details and Custom value per unit (NGN); Notes
Claimants (Claimants › Import)Claimant ID (CL-0012); blank = new claimantFull nameGender, Phone, NIN, Email, Address, ID type, ID number, Bank, Account name, Account number, BVN, Notes, Property ref no (links the claimant), Tags
Payments (Compensation cases › Import payments)Case numberCase numberCheque number, Cheque bank, Cheque date, Amount (NGN) (checked, not saved), Collected on, Note
Survey assignments (Field surveys › Import assignments)Property ref noProperty ref no, Surveyor—
Staff invitations (Staff › Import invitations)EmailName, Email, Staff ID, RolePhone
Tags (Administration › Tags › Import)Group + nameNameGroup, Colour, Applies to, Field app, One per record, Description, Active
Rates (Dictionaries › Import rates)Dictionary + codeDictionary, Code, Rate (NGN)Note
Dictionary items (inside a dictionary)CodeCode, LabelParent code, Unit, Rate (NGN), Active, Order
Locations (Locations › Import)LGA + ward (+ area) namesLGA, WardArea

The Tags column

Property, claimant and project exports end with a Tags column ("Priority: High; Revisit"). The same column can be imported: the tags named there are added to the record (tags already on it stay). Each name must be an existing, active tag that fits the record; an unknown name is reported on its row and nothing is imported.

The Boundary column (properties)

Optional. Give the outline in one cell, either as corners — lat lng; lat lng; …, for example 10.5231 7.4402; 10.5231 7.4410; 10.5238 7.4410; 10.5238 7.4402 — or as WKT: POLYGON((lng lat, lng lat, …)). Note that WKT puts longitude first. For many outlines, a boundary file is easier (below).

Claimants: NIN and duplicates

Property items

Payments from a bank file

Needs data.import and comp.cheque or comp.complete

  1. Download the Payment schedule (Compensation cases page header) and send it to the bank.
  2. When it comes back, fill in Cheque number, Cheque bank and Cheque date for each case paid (the schedule’s other columns can stay), and later Collected on when the claimant collects.
  3. On Compensation cases, click Import payments and choose the file.

Survey assignments

Needs data.import and surveys.assign

One row per property: Property ref no and the Surveyor (their email, staff ID or full name — an active field surveyor). A property that already has an open or approved survey is left as it is (No change).

Staff invitations

Needs data.import and users.manage

Tags

Needs data.import and tags.manage

A tag is matched by its group and name: a match is updated, anything else is created. Colour is one of the tag colours (Navy, Blue, Teal, Green, Olive, Amber, Orange, Red, Rose, Purple, Slate, Brown). Applies to is blank (any record) or a list such as Properties, Claimants. Field app, One per record and Active are Yes or No.

Rates across dictionaries

Needs data.import and dictionaries.manage

  1. On Dictionaries, click Export rates: every priced item of every dictionary, with its current rate.
  2. Change the Rate (NGN) of the items whose rate changed (add a Note saying why, if you like).
  3. Click Import rates and choose the file.

Dictionary items

Needs dictionaries.manage

Import boundaries

Needs data.import and properties.manage (properties) or projects.manage (projects)

To give many properties — or many projects — their outline at once, from a GIS or survey file:

  1. On Properties (or Projects), click Import boundaries.
  2. Choose a GeoJSON, KML or zipped shapefile (.shp, .shx, .dbf and .prj together). Each outline must carry the property’s reference number in an attribute called refNo, ref or ref_no (or name) — for projects, the project code in code or project_code (or name); in KML, the placemark’s name.
  3. Click Check file. Nothing is saved yet. The result shows how many outlines matched, how many will replace an existing boundary, and any problems (no match, an invalid outline).
  4. Click Import N boundaries to save the matched outlines, or Choose another file.

Keeping leading zeros

Account numbers, BVNs, NINs and phone numbers

Excel drops leading zeros from numbers: 0123456789 becomes 123456789 and fails the 10-digit check. Use the Excel template and keep those columns formatted as Text. Opening a CSV in Excel and saving it again loses the zeros.

Common import problems

See Troubleshooting › Import and export for every message and its fix.