Manage cooperators of a cooperative.
A basic flow can be the following:
- Create subscription request for a person (moral or physical)
- Validate subscription request, a capital release request (an invoice: account.move). This invoice is sent to the future cooperator.
- Payment of the cooperator is registered and the capital Release request is marked as paid.
- A new cooperator (a special partner) is created, and the right type and amount of share is linked to this new cooperator.
- The new cooperator appears in the Cooperator Registry.
Features:
- Manage several share types
- Manage share subscription request
- Cooperators can be individuals or companies
- Get an up to date Cooperator Registry
- See shares of a cooperator on the partner view
- Manage departure of cooperators
- Manage conversion between different share type
- Send automatic mail to the future cooperator during the procedure
- Can be used with multi-company configuration
- Generate Cooperator Certificate and several reports about cooperators
Configurations:
- on the company, set a default payment term for the capital release requests.
- on the company, set the cooperator account.
Table of contents
## Migrating from easy_my_coop* to cooperator modules
Run this command before updating your modules
cat rename_deprecated_modules.py | ./odoo/odoo-bin shell -c odoo.conf --no-http --stop-after-init -d <db-name>## Deploying with pip
We used [odoo setup tools](https://pypi.org/project/setuptools-odoo/#packaging-a-single-addon) to generate the pypi files from the odoo manifests. To deploy any packaged module, so that odoo can later install them,
you can create a venv with this name (it's git-ignored)
`shell
python -m venv venv
`
And then pip-install them [from pypi](https://pypi.org/user/coopdevs/).
### Example
For instance, for the addon cooperator_portal
pip install odoo14-addon-cooperator-portal==14.0.1.0.0.99.dev9Beware that for word separation, pypi uses dashes - and odoo underscores _.
See the [documentation](https://doc.it4socialeconomy.org/books/application-cooperators) (not available in english ATM).
A localization module is needed with this module.
Gather and consolidate all cooperator settings in the application parameters.
Consider a refactoring for: 1. removing a potential redundancy between the boolean field "representative" and the address type "representative". 2. prevent new contacts to have the representative address type, if they are not representative. See [this issue](coopiteasy/vertical-cooperative#350)
known_caveats: the cooperator localization modules will have to be splitted in order to install the cooperator module without the cooperator_website module.
Registering a payment for a subscription request for a company other than the current one does not create the cooperative membership information for the partner.
A “Cooperative Memberships” page should be added to the res.partner form,
displaying all the cooperative memberships of the partner
(cooperative_membership_ids). The page should only be visible for users
that are both in the cooperator_group_user group and in the
base.group_multi_company group (how to do this?). Should it display the
memberships of all companies or only the ones in which the user is “logged in”
(checked in the menu)? If all companies, there would be a conflict with the
cooperative_membership_rule_company ir.rule.
Features
- Rework
res.partnerform view as has been done in version 16. (#105)
Bugfixes
- Remove duplicated member field in
res.partnerform view. (#47) - Fix error when creating a new contact (
res.partner) as has been done in version 16. (#105)
Features
- Each company now has their own mail templates for cooperator-related e-mails. If no template is set, the default (global) template is used. (#73)
- ir.sequences used by this module are no longer global; each company has its own sequence for cooperator memberships. (#74)
- Create subscription journal per company. (#75)
- Improve multi-company consistency by setting
company_idon records where needed and adding thecheck_companyflag onMany2onefields. (#77) - ir.rules for multi-company usage added. Users cannot access records of this module if they are not members of the relevant company. (#78)
- Move cooperative membership properties from
res.partnerto newcooperative.membershipmodel and add company-dependent computed fields onres.partnerfor backward compatibility. (#82)
Features
- Removed all selection widgets. (#55)
Improved Documentation
- Adding USAGE.rst to inform that localization modules are necessary. (#346)
Deprecations and Removals
- When no cooperator account is defined on the company, this module previously
defaulted to the account with code '416000'. This behaviour has been removed
because the code is Belgian-only. The functionality has been moved to
l10n_be_cooperator. (#314)
Bugfixes
- Fix name computation crash (#330)
Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback.
Do not contact contributors directly about support or help with technical issues.
- Coop IT Easy SC
- Coop IT Easy SC:
- Houssine Bakkali
- Robin Keunen
- Rémy Taymans
- Victor Champonnois
- Vincent Van Rossem
- Manuel Claeys Bouuaert
- Carmen Bianca Bakker
- hugues de keyzer
This module is maintained by the OCA.
OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.
This module is part of the OCA/cooperative project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.