Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 0 additions & 17 deletions spp_base_spmis/README.rst
Original file line number Diff line number Diff line change
Expand Up @@ -45,10 +45,6 @@ modules, offering:
gender details, and a clear distinction of registrant type (e.g.,
individual, group). This enables more comprehensive data capture and
analysis for beneficiaries.
- **Top-up Card Management**: Supports the integration and validation
of Top-up Cards as a specific form of identification within the
system. This is crucial for programs utilizing physical cards for
beneficiary interactions.
- **Core UI and Role Configuration**: Provides fundamental user
interface elements and initial security configurations, including
global and local user roles. This ensures a consistent look and feel
Expand All @@ -74,10 +70,6 @@ integrating their features and extending them for OpenSPP:
like `OpenSPP Area <spp_area>`__ and `OpenSPP Service
Points <spp_service_points>`__ by providing the underlying registrant
framework and unique identifiers used across the system.
- It supports identity management features such as
`spp_idpass <spp_idpass>`__ and `spp_idqueue <spp_idqueue>`__ by
defining the 'Top-up Card' ID type and its validation rules, crucial
for card issuance and tracking.
- OpenSPP Base underpins UI customization and filtering through
`OpenSPP Custom Field <spp_custom_field>`__, `OpenSPP Custom Fields
UI <spp_custom_fields_ui>`__, `OpenSPP Hide
Expand Down Expand Up @@ -115,15 +107,6 @@ household). This module also integrates ``Gender`` information into
individual and group membership records, allowing for more detailed
demographic analysis of beneficiary populations.

Top-Up Card Identification
~~~~~~~~~~~~~~~~~~~~~~~~~~

OpenSPP Base manages the specific ``Top-up Card`` identification type,
including its unique identifier (``Card UID``). The system ensures data
accuracy by validating that all entered Top-up Card UIDs are exactly 10
characters long. This standardization is essential for reliable card
issuance, tracking, and usage in program distributions.

Foundational UI and Role Configuration
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Expand Down
3 changes: 1 addition & 2 deletions spp_base_spmis/__manifest__.py
Original file line number Diff line number Diff line change
Expand Up @@ -50,7 +50,6 @@
]
}, # not directly required, pinned by Snyk to avoid a vulnerability and for fastapi, compatibility issues.
"data": [
"data/top_up_card.xml",
"security/ir.model.access.csv",
"views/registrant_view.xml",
"views/users_view.xml",
Expand All @@ -61,5 +60,5 @@
"application": True,
"installable": True,
"auto_install": False,
"summary": "Establishes core system settings and generates unique identifiers for records, enhancing registrant profiles with attributes like tags, gender, and type. The module also integrates Top-up Cards for identification and provides fundamental user interface elements with initial security configurations for user roles.",
"summary": "Establishes core system settings and generates unique identifiers for records, enhancing registrant profiles with attributes like tags, gender, and type.",
}
5 changes: 0 additions & 5 deletions spp_base_spmis/data/top_up_card.xml

This file was deleted.

12 changes: 0 additions & 12 deletions spp_base_spmis/i18n/lo.po
Original file line number Diff line number Diff line change
Expand Up @@ -14,11 +14,6 @@ msgstr ""
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: \n"

#. module: spp_base_spmis
#: model:ir.model.fields,field_description:spp_base_spmis.field_g2p_reg_id__card_uid
msgid "Card UID"
msgstr ""

#. module: spp_base_spmis
#: model:ir.model,name:spp_base_spmis.model_res_partner
msgid "Contact"
Expand Down Expand Up @@ -59,13 +54,6 @@ msgstr ""
msgid "String Kind"
msgstr ""

#. module: spp_base_spmis
#. odoo-python
#: code:addons/spp_base_spmis/models/reg_id.py:0
#, python-format
msgid "Top-up Card UID should have 10 characters"
msgstr ""

#. module: spp_base_spmis
#: model:ir.model,name:spp_base_spmis.model_spp_unique_id
#: model:ir.model.fields,field_description:spp_base_spmis.field_spp_unique_id__spp_id
Expand Down
12 changes: 0 additions & 12 deletions spp_base_spmis/i18n/spp_base.pot
Original file line number Diff line number Diff line change
Expand Up @@ -13,11 +13,6 @@ msgstr ""
"Content-Transfer-Encoding: \n"
"Plural-Forms: \n"

#. module: spp_base_spmis
#: model:ir.model.fields,field_description:spp_base_spmis.field_g2p_reg_id__card_uid
msgid "Card UID"
msgstr ""

#. module: spp_base_spmis
#: model:ir.model,name:spp_base_spmis.model_res_partner
msgid "Contact"
Expand Down Expand Up @@ -58,13 +53,6 @@ msgstr ""
msgid "String Kind"
msgstr ""

#. module: spp_base_spmis
#. odoo-python
#: code:addons/spp_base/models/reg_id.py:0
#, python-format
msgid "Top-up Card UID should have 10 characters"
msgstr ""

#. module: spp_base_spmis
#: model:ir.model,name:spp_base_spmis.model_spp_unique_id
#: model:ir.model.fields,field_description:spp_base_spmis.field_spp_unique_id__spp_id
Expand Down
12 changes: 0 additions & 12 deletions spp_base_spmis/i18n/spp_base_spmis.pot
Original file line number Diff line number Diff line change
Expand Up @@ -13,11 +13,6 @@ msgstr ""
"Content-Transfer-Encoding: \n"
"Plural-Forms: \n"

#. module: spp_base_spmis
#: model:ir.model.fields,field_description:spp_base_spmis.field_g2p_reg_id__card_uid
msgid "Card UID"
msgstr ""

#. module: spp_base_spmis
#: model:ir.model,name:spp_base_spmis.model_res_partner
msgid "Contact"
Expand Down Expand Up @@ -58,13 +53,6 @@ msgstr ""
msgid "String Kind"
msgstr ""

#. module: spp_base_spmis
#. odoo-python
#: code:addons/spp_base_spmis/models/reg_id.py:0
#, python-format
msgid "Top-up Card UID should have 10 characters"
msgstr ""

#. module: spp_base_spmis
#: model:ir.model,name:spp_base_spmis.model_spp_unique_id
#: model:ir.model.fields,field_description:spp_base_spmis.field_spp_unique_id__spp_id
Expand Down
1 change: 0 additions & 1 deletion spp_base_spmis/models/__init__.py
Original file line number Diff line number Diff line change
@@ -1,6 +1,5 @@
# Part of OpenSPP. See LICENSE file for full copyright and licensing details.

from . import reg_id
from . import spp_unique_id
from . import registrant
from . import group_membership
Expand Down
19 changes: 0 additions & 19 deletions spp_base_spmis/models/reg_id.py

This file was deleted.

6 changes: 0 additions & 6 deletions spp_base_spmis/readme/DESCRIPTION.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,6 @@ The OpenSPP Base module establishes the core framework and essential capabilitie

* **System Foundation**: Establishes core system settings and a mechanism for generating unique identifiers for various records. This ensures consistent data tracking and integrity across all OpenSPP modules.
* **Enhanced Registrant Profiles**: Extends the base registrant model to include additional, critical information such as registrant tags, gender details, and a clear distinction of registrant type (e.g., individual, group). This enables more comprehensive data capture and analysis for beneficiaries.
* **Top-up Card Management**: Supports the integration and validation of Top-up Cards as a specific form of identification within the system. This is crucial for programs utilizing physical cards for beneficiary interactions.
* **Core UI and Role Configuration**: Provides fundamental user interface elements and initial security configurations, including global and local user roles. This ensures a consistent look and feel and lays the groundwork for robust access control.
* **Integration Enabler**: Serves as a central integration point, allowing other OpenSPP modules to seamlessly interact with core registrant data and system settings.

Expand All @@ -18,7 +17,6 @@ The OpenSPP Base module is deeply integrated into the OpenSPP ecosystem, extendi

* It extends the core G2P Registry models, including `res.partner` (registrants), `g2p.reg.id` (registrant IDs), and `g2p.group.membership` (group memberships) from [G2P Registry Base](g2p_registry_base), [G2P Registry Individual](g2p_registry_individual), and [G2P Registry Group](g2p_registry_group). This provides foundational data structures for all registrants.
* This module integrates with geographical and service delivery modules like [OpenSPP Area](spp_area) and [OpenSPP Service Points](spp_service_points) by providing the underlying registrant framework and unique identifiers used across the system.
* It supports identity management features such as [spp_idpass](spp_idpass) and [spp_idqueue](spp_idqueue) by defining the 'Top-up Card' ID type and its validation rules, crucial for card issuance and tracking.
* OpenSPP Base underpins UI customization and filtering through [OpenSPP Custom Field](spp_custom_field), [OpenSPP Custom Fields UI](spp_custom_fields_ui), [OpenSPP Hide Menus](spp_hide_menus), and [OpenSPP Custom Filter UI](spp_custom_filter_ui), establishing common interface elements and simplifying user workflows.
* It defines global and local roles, which are utilized by [OpenSPP User Roles](spp_user_roles) to manage permissions and access control for users based on their responsibilities and assigned areas.

Expand All @@ -34,10 +32,6 @@ The module provides a robust system for generating unique identifiers for variou

It extends the core registrant profile by adding critical fields for more comprehensive data capture. Users can assign multiple `Registrant Tags` for flexible categorization and reporting, and easily see the `String Kind` of a registrant (e.g., individual, household). This module also integrates `Gender` information into individual and group membership records, allowing for more detailed demographic analysis of beneficiary populations.

### Top-Up Card Identification

OpenSPP Base manages the specific `Top-up Card` identification type, including its unique identifier (`Card UID`). The system ensures data accuracy by validating that all entered Top-up Card UIDs are exactly 10 characters long. This standardization is essential for reliable card issuance, tracking, and usage in program distributions.

### Foundational UI and Role Configuration

This module establishes the fundamental user interface components and initial security settings for the OpenSPP platform. It pre-defines `Global Roles` and `Local Roles` to streamline user permission management and sets up the basic views for interacting with registrants and user accounts. This ensures a secure, consistent, and user-friendly operating environment from the outset.
Expand Down
2 changes: 0 additions & 2 deletions spp_base_spmis/static/description/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -311,8 +311,6 @@ <h2>Module Dependencies and Integration</h2>
<h2>Additional Functionality</h2>
<p>The <strong>OpenSPP SPMIS Base</strong> module introduces the following key functionalities:</p>
<ul class="simple">
<li><strong>Top-up Card ID Type</strong>: Adds a new ID type specifically for managing "Top-up Cards", including a dedicated field (<code>card_uid</code>) for storing the unique 10-character UID of each card.</li>
<li><strong>Registrant View Enhancements</strong>: Modifies the registrant views (both individual and group) to include the <code>card_uid</code> field, making it accessible for data entry and display.</li>
<li><strong>Menu Icon Customization</strong>: Replaces the default icon for the "Registry" menu item with a custom OpenSPP icon, enhancing visual branding.</li>
<li><strong>Menu Item Hiding</strong>: Hides specific menu items related to "Link Tracker" and "Discuss" to streamline the OpenSPP user interface and focus on relevant functionalities.</li>
</ul>
Expand Down
2 changes: 0 additions & 2 deletions spp_base_spmis/tests/__init__.py
Original file line number Diff line number Diff line change
@@ -1,3 +1 @@
# Part of OpenSPP Registry. See LICENSE file for full copyright and licensing details.

from . import test_top_up_id
20 changes: 0 additions & 20 deletions spp_base_spmis/tests/test_top_up_id.py

This file was deleted.

8 changes: 0 additions & 8 deletions spp_base_spmis/views/registrant_view.xml
Original file line number Diff line number Diff line change
@@ -1,15 +1,11 @@
<?xml version="1.0" encoding="UTF-8" ?>
<odoo>

<record id="view_group_spp_base_spmis_form" model="ir.ui.view">
<field name="name">view_group_spp_base_spmis_form</field>
<field name="model">res.partner</field>
<field name="priority">1000</field>
<field name="inherit_id" ref="g2p_registry_group.view_groups_form" />
<field name="arch" type="xml">
<xpath expr="//field[@name='reg_ids']/tree[1]/field[@name='value']" position="after">
<field name="card_uid" required="id_type == %(spp_base_spmis.id_top_up_card)d" />
</xpath>
<xpath expr="//field[@name='related_2_ids']/tree/field[@name='relation']" position="after">
<field name="relation_inverse" />
</xpath>
Expand Down Expand Up @@ -52,9 +48,6 @@
<field name="priority">1000</field>
<field name="inherit_id" ref="g2p_registry_individual.view_individuals_form" />
<field name="arch" type="xml">
<xpath expr="//field[@name='reg_ids']/tree[1]/field[@name='value']" position="after">
<field name="card_uid" required="id_type == %(spp_base_spmis.id_top_up_card)d" />
</xpath>
<xpath expr="//field[@name='related_2_ids']/tree/field[@name='relation']" position="after">
<field name="relation_inverse" />
</xpath>
Expand Down Expand Up @@ -90,7 +83,6 @@
</xpath>
</field>
</record>

<record id="view_individuals_list_spmis_tree" model="ir.ui.view">
<field name="name">view_individuals_list_spmis_tree</field>
<field name="model">res.partner</field>
Expand Down
Loading