Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revisionLast revisionBoth sides next revision | ||
import_and_export:importing_regions [2021/08/10 15:57] – [Doing the import] Gary Willetts | import_and_export:importing_regions [2021/08/11 15:16] – [Doing the import] Gary Willetts | ||
---|---|---|---|
Line 2: | Line 2: | ||
====== 16.10. Importing regions ====== | ====== 16.10. Importing regions ====== | ||
- | Information coming soon. | + | Regions are geographic boundaries, currently used in mSupply to help in displaying data on maps. At the moment they are only used in certain customisations but more use of them will follow as development progresses. |
===== Import spreadsheet format ===== | ===== Import spreadsheet format ===== | ||
The first row of the spreadsheet is for the column headers and is **not** imported. | The first row of the spreadsheet is for the column headers and is **not** imported. | ||
- | The first 34 columns (up to, and including column AH, " | + | There must be 3 columns |
- | + | ||
- | < | + | |
- | + | ||
- | where **Property name** is the description the property will be given and **Property type** is one of " | + | |
- | + | ||
- | For example, a column header of **Project name (Drop down list)** will represent a drop down list property with the description **Project name**. | + | |
- | + | ||
- | During the import process, if any properties or entities (like asset locations) do not exist, they will be created. If any options for drop down list properties or standard asset drop down lists (categories) are found not to exist, they will also be created. | + | |
- | + | ||
- | The import | + | |
^ Column number | ^ Column number | ||
- | | 1 | A | Code | 255 alphanumeric characters. A code that the asset can be recognised by | | + | | 1 | A | Region name | **Mandatory**. 255 alphanumeric characters. The name of the region |
- | | 2 | B | Description | + | | 2 |
- | | 3 | + | | 3 |
- | | 4 | D | Model | 255 alphanumeric characters | + | |
- | | 5 | E | Serial number | + | |
- | | 6 | F | Supplier name | 255 alphanumeric characters. Name of the company/ | + | |
- | | 7 | G | Purchase order number | + | |
- | | 8 | H | Purchase order date | Valid date in current operating system format. The date the purchase order to buy the asset was confirmed | + | |
- | | 9 | I | Acquisition date | Valid date in current operating system format | | + | |
- | | 10 | J | Next maintenance due date | Valid date in current operating system format. The date the next maintenance is due to be carried out on the asset | | + | |
- | | 11 | K | Disposal date | Valid date in current operating system format. The date the asset will be or was disposed | + | |
- | | 12 | L | Last verification date | Valid date in current operating system format | | + | |
- | | 13 | M | Location code | 20 alphanumeric characters. The code the location name will have. Will be matched against the names currently in the database. If a name with this code does not exist, one will be created with the name provided in the Location name field. If the Location name field is empty the name will be created with the code as its name. This field is mandatory if you want mSupply to create the name. | | + | |
- | | 14 | N | Location name | 255 alphanumeric characters. | + | |
- | | 15 | O | Asset user name | 255 alphanumeric characters. The name of the asset user in the format "// | + | |
- | | 16 | P | Asset user phone number | + | |
- | | 17 | Q | Asset user email | 255 alphanumeric characters | | + | |
- | | 18 | R | Custodian location | + | |
- | | 19 | S | Custodian name | 255 alphanumeric characters. The name of the custodian | | + | |
- | | 20 | T | Custodian phone number | + | |
- | | 21 | U | Custodian email | 255 alphanumeric characters | | + | |
- | | 22 | V | Current status | + | |
- | | 23 | W | Proposed status | + | |
- | | 24 | X | + | |
- | | 25 | Y | Condition | + | |
- | | 26 | Z | Purchase price | Number, currency. The cost of the asset when it was purchased | | + | |
- | | 27 | AA | Purchase costs | Number, currency. Any costs that are ot be added ot the purchase proce to arrive at the total value of the asset to be depreciated | | + | |
- | | 28 | AB | In service date | Valid date in current operating system format. The date the asset starts to depreciate from | | + | |
- | | 29 | AC | Useful lifespan (months) | + | |
- | | 30 | AD | Disposal value | Number, currency. The value of the asset at the end of its useful life | | + | |
- | | 31 | AE | Insurer | + | |
- | | 32 | AF | Insurance policy number | + | |
- | | 33 | AG | Insurance renewal date | Valid date in current operating system format. The date the insurance should be renewed by | | + | |
- | | 34 | AH | Notes | Lots of alphanumeric characters! Any other information that needs to be stored against the asset | | + | |
- | | 35 onwards | + | |
- | Here is an example spreadsheet you can use (contains no property columns, only the standard mSupply columns): {{ : | + | Here is an example spreadsheet you can use: {{ : |
- | <WRAP important center round 90%> | ||
- | When entering dates in the spreadsheet, | ||
- | </ | ||
===== Doing the import ===== | ===== Doing the import ===== | ||
- | Go to the //File > Import > Import | + | Choose |
- | {{ : | + | {{ : |
- | mSupply uses the **code** field to determine whether the asset being imported is a duplicate; | + | mSupply uses the **Region** field to determine whether the region |
- | * **Import as new asset:** this option will import the duplicate as a new asset | + | * **Import as a new region:** this option will import the duplicate as a new region |
* **Skip the duplicate without asking:** the duplicate will not be imported and that row of the spreadsheet will be ignored | * **Skip the duplicate without asking:** the duplicate will not be imported and that row of the spreadsheet will be ignored | ||
- | * **Stop the import:** as soon as a duplicate is encountered, | + | * **Stop the import:** as soon as a duplicate is encountered, |
- | * **Update | + | * **Update existing |
- | The //Field// column of the table shows you all the columns that mSupply has detected in your import file, the //Value// column shows the values | + | The //Value// column shows the values |
You can carry out the import by clicking on the **Import now** button or cancel it by clicking on the **Cancel** button. | You can carry out the import by clicking on the **Import now** button or cancel it by clicking on the **Cancel** button. | ||
- | When the import has finished you will be shown a message telling you how many assets were imported | + | During |
+ | * if the row has no region name it will be skipped | ||
+ | * if the row has an empty Geometry field, it will be imported | ||
+ | * if the row has content in the Geometry field that does not match the geoJSON FeatureCollection schema it will be skipped | ||
+ | * if the parent region does not exist or is empty the region will be imported with no parent | ||
- | <WRAP info center round 90%> | + | When the import |
- | All the assets created by the import will have the text " | + | |
- | </ | + | |
\\ | \\ |