Difference between revisions of "Configuring the Items ID Generator"

From IMSMA Wiki
Jump to: navigation, search
Line 1: Line 1:
IMSMANG provides a local identifier (local ID) data element for each item category or subcategory, which when used on data entry forms allows information managers to track items and Data Entry Forms entered into IMSMANG. These local ID data elements enable data entry clerks to click a button and insert an automatically generated ID rather than enter one manually, helping to reduce duplicate local IDs in the system.  
+
IMSMA<sup>NG</sup> provides a local identifier (local ID) data element for each item category or subcategory, which when used on data entry forms allows information managers to track items and Data Entry Forms entered into IMSMA<sup>NG</sup>. These local ID data elements enable data entry clerks to click a button and insert an automatically generated ID rather than enter one manually, helping to reduce duplicate local IDs in the system.  
 
{{HowTo's
 
{{HowTo's
 
|[[Set Object ID Fields to Autogenerate Object ID Numbers|Set Object ID Fields to Autogenerate Object ID Numbers]]
 
|[[Set Object ID Fields to Autogenerate Object ID Numbers|Set Object ID Fields to Autogenerate Object ID Numbers]]
Line 8: Line 8:
 
|[[View or Change a Local ID Type|View or Change a Local ID Type]]
 
|[[View or Change a Local ID Type|View or Change a Local ID Type]]
 
}}
 
}}
IMSMANG comes with a default local ID type per item, but there is no limit to how many different types can be created. It is recommended to create at least one local ID type per item subcategory. For example, create a local ID type for completion reports, another for clearance reports and another for minefields. Also, establishing a convention for the local ID types makes it easy to understand and find data.
+
IMSMA<sup>NG</sup> comes with a default local ID type per item, but there is no limit to how many different types can be created. It is recommended to create at least one local ID type per item subcategory. For example, create a local ID type for completion reports, another for clearance reports and another for minefields. Also, establishing a convention for the local ID types makes it easy to understand and find data.
  
 
Local ID types are typically comprised of the following components:
 
Local ID types are typically comprised of the following components:
Line 19: Line 19:
 
| '''Local ID Name''' || A text string that represents the item category or subcategory. For example, a completion report could be represented by “CR.”
 
| '''Local ID Name''' || A text string that represents the item category or subcategory. For example, a completion report could be represented by “CR.”
 
|-
 
|-
| '''System Name''' || A value specified in the Client Configuration Tool of the IMSMANG TrayLauncher where system administrators can set a separate system name for each installation of IMSMANG. For example, the Headquarters installation could have “HQ” as a system name while a regional installation could have “R1.”
+
| '''System Name''' || A value specified in the Client Configuration Tool of the IMSMA<sup>NG</sup> TrayLauncher where system administrators can set a separate system name for each installation of IMSMA<sup>NG</sup>. For example, the Headquarters installation could have “HQ” as a system name while a regional installation could have “R1.”
 
|-
 
|-
 
| '''Incremented Number''' || A value that increases each time a new ID is generated. Information managers can specify the next number to be generated when the local ID generator button is clicked. For example, a new local ID starting with CR-HQ-1 and proceeding to CR-HQ-2 and so on will be generated each time the Completion Report local ID generator is clicked.
 
| '''Incremented Number''' || A value that increases each time a new ID is generated. Information managers can specify the next number to be generated when the local ID generator button is clicked. For example, a new local ID starting with CR-HQ-1 and proceeding to CR-HQ-2 and so on will be generated each time the Completion Report local ID generator is clicked.

Revision as of 19:48, 2 August 2013

IMSMANG provides a local identifier (local ID) data element for each item category or subcategory, which when used on data entry forms allows information managers to track items and Data Entry Forms entered into IMSMANG. These local ID data elements enable data entry clerks to click a button and insert an automatically generated ID rather than enter one manually, helping to reduce duplicate local IDs in the system.

IMSMANG comes with a default local ID type per item, but there is no limit to how many different types can be created. It is recommended to create at least one local ID type per item subcategory. For example, create a local ID type for completion reports, another for clearance reports and another for minefields. Also, establishing a convention for the local ID types makes it easy to understand and find data.

Local ID types are typically comprised of the following components:

[Local ID Name]-[System Name]-[Incremented Number] For example, CR-HQ-1.

Local ID Name A text string that represents the item category or subcategory. For example, a completion report could be represented by “CR.”
System Name A value specified in the Client Configuration Tool of the IMSMANG TrayLauncher where system administrators can set a separate system name for each installation of IMSMANG. For example, the Headquarters installation could have “HQ” as a system name while a regional installation could have “R1.”
Incremented Number A value that increases each time a new ID is generated. Information managers can specify the next number to be generated when the local ID generator button is clicked. For example, a new local ID starting with CR-HQ-1 and proceeding to CR-HQ-2 and so on will be generated each time the Completion Report local ID generator is clicked.
Note.jpg
  • Information managers can also create an individual local ID for each Data Entry Form template that indicates the kind of information in the form. For example, a completion report can have a local ID beginning with “FR-CR-” to give users an immediate understanding of the content of the form.
  • For templates intended to update existing items, such as status change templates, information managers can remove the local ID generator or the ID field entirely to prevent users from accidentally creating new local IDs for existing items.

Template:NavBox Getting started with IMSMA