Search 1.9 billion lines of Odoo code on GitHub
business_requirement_deliverable_project_task_mandatory
| Author: | Elico Corp |
|---|---|
| License: | AGPL-3 |
| Branch: | 11.0 |
| Repository: | gastonfeng/odoo-addons |
| Dependencies: | business_requirement_deliverable_project, and project_project_category |
| Languages: | Python (42, 37.5%), XML (30, 26.8%), and reStructuredText (40, 35.7%) |
Show more...
purchase_consignment_inventory_line_domain
| Author: | Numigi |
|---|---|
| License: | LGPL-3 |
| Branch: | 11.0 |
| Repository: | Numigi/odoo-purchase-addons |
| Dependencies: | product_supplier_info_helpers, purchase_consignment_inventory, stock, and stock_inventory_line_domain |
| Languages: | PO File (27, 10.7%), Python (205, 81.3%), and XML (20, 7.9%) |
Restrain the selection of products on inventory lines.
Show more...
account_advanced_reconcile_ref_deep_search
| Author: | Camptocamp,Odoo Community Association (OCA) |
|---|---|
| License: | no license |
| Branch: | reconcile-deep-search |
| Repository: | mdietrichc2c/bank-statement-reconcile |
| Dependencies: | account_advanced_reconcile, and account_easy_reconcile |
| Languages: | Python (61, 76.2%), and XML (19, 23.8%) |
Show more...
product_supplierinfo_for_customer_discount
| Author: | Serv. Tecnol. Avanzados - Pedro M. Baeza, Antiun Ingeniería S.L., Odoo Community Association (OCA) |
|---|---|
| License: | AGPL-3 |
| Branch: | 8.0 |
| Repository: | alanljj/antiun-odoo-addons |
| Dependencies: | product_supplierinfo_discount, and product_supplierinfo_for_customer |
| Languages: | Python (60, 60.6%), and reStructuredText (39, 39.4%) |
Show more...
stock_aggregated_shipment_documents_webkit
| Author: | Savoir-faire Linux |
|---|---|
| License: | no license |
| Branch: | 7.0_stock_aggregated_shipment_document |
| Repository: | savoirfairelinux/stock-logistics-reporting |
| Dependencies: | base, base_headers_webkit, delivery, report_webkit, stock, stock_bill_of_lading_webkit, and stock_picking_pickup_date |
| Languages: | Mako (271, 59.0%), Python (99, 21.6%), and XML (89, 19.4%) |
Show more...
account_invoice_from_picking_without_salesperson_group
| Author: | Trey (www.trey.es) |
|---|---|
| License: | AGPL-3 |
| Branch: | 8.0 |
| Repository: | acysos/trey-addons |
| Dependencies: | sale, sale_stock, and stock_account |
| Languages: | Python (159, 48.9%), and SVG (166, 51.1%) |
Account invoice from picking without salesperson group
Show more...
mrp_bom_widget_section_and_note_one2many_obsolete_voir_pr_oca
| Author: | GRAP |
|---|---|
| License: | AGPL-3 |
| Branch: | 12.0_ADD_MRP_Bom_widget_sectionnote |
| Repository: | quentinDupont/grap-odoo-incubator |
| Dependencies: | mrp, and sale_mrp |
| Languages: | HTML (348, 65.9%), PO File (48, 9.1%), Python (41, 7.8%), XML (42, 8.0%), and reStructuredText (49, 9.3%) |
Add section and note in Bills of Materials
Show more...
account_advanced_reconcile_transaction_by_purchase_line
| Author: | Eficent Business and IT Consulting Services S.L., Odoo Community Association (OCA) |
|---|---|
| License: | AGPL-3 |
| Branch: | 9.0 |
| Repository: | Bonainifo/ao-odoo |
| Dependencies: | account_advanced_reconcile, account_easy_reconcile, and account_move_line_purchase_info |
| Languages: | Python (100, 61.0%), XML (25, 15.2%), and reStructuredText (39, 23.8%) |
Allows to reconcile based on the PO line
Show more...
cenit_geneea_natural_language_processing_1_0
| Author: | Cenit IO |
|---|---|
| License: | no license |
| Branch: | 8.0 |
| Repository: | andhit-r/odoo-integrations |
| Dependencies: | base, and cenit_base |
| Languages: | HTML (38, 5.2%), Python (67, 9.2%), and XML (625, 85.6%) |
<div class="api-description"> <h2>Authentication</h2> <p>For all calls, supply your API key. <a href="https://geneea.3scale.net/">Sign up to <em>obtain the key</em></a>.</p> <p> Our API supports both <em>unencrypted (HTTP)</em> and <em>encrypted (HTTPS)</em> protocols. However, for security reasons, we strongly encourage using only the encrypted version. </p> <p>The API key should be supplied as either a request parameter <code>user_key</code> or in <code>Authorization</code> header.</p> <pre><code>Authorization: user_key <YOUR_API_KEY></code></pre> <h2>API operations</h2> <p> All API operations can perform analysis on supplied raw text or on text extracted from a given URL. Optionally, one can supply additional information which can make the result more precise. An example of such information would be the language of text or a particular text extractor for URL resources. </p> <p>The supported types of analyses are:</p> <ul> <li><strong>lemmatization</strong> ⟶ Finds out lemmata (basic forms) of all the words in the document. </li> <li><strong>correction</strong> ⟶ Performs correction (diacritization) on all the words in the document. </li> <li><strong>topic detection</strong> ⟶ Determines a topic of the document, e.g. finance or sports. </li> <li><strong>sentiment analysis</strong> ⟶ Determines a sentiment of the document, i.e. how positive or negative the document is. </li> <li><strong>named entity recognition</strong> ⟶ Finds named entities (like person, location, date etc.) mentioned the the document. </li> </ul> <h2>Encoding</h2> <p>The supplied text is expected to be in UTF-8 encoding, this is especially important for non-english texts.</p> <h2>Returned values</h2> <p>The API calls always return objects in serialized JSON format in UTF-8 encoding.</p> <p> If any error occurs, the HTTP response code will be in the range <code>4xx</code> (client-side error) or <code>5xx</code> (server-side error). In this situation, the body of the response will contain information about the error in JSON format, with <code>exception</code> and <code>message</code> values. </p> <h2>URL limitations</h2> <p> All the requests are semantically <code>GET</code>. However, for longer texts, you may run into issues with URL length limit. Therefore, it's possible to always issue a <code>POST</code> request with all the parameters encoded as a JSON in the request body. </p> <p>Example:</p> <pre><code> POST /s1/sentiment Content-Type: application/json {"text":"There is no harm in being sometimes wrong - especially if one is promptly found out."} </code></pre> <p>This is equivalent to <code>GET /s1/sentiment?text=There%20is%20no%20harm...</code></p> <h2>Request limitations</h2> <p> The API has other limitations concerning the size of the HTTP requests. The maximal allowed size of any POST request body is <em>512 KiB</em>. For request with a URL resource, the maximal allowed number of extracted characters from each such resource is <em>100,000</em>. </p> <h2>More information</h2> <p> <a href="https://geneea.atlassian.net/wiki/display/IPD/The+Interpretor+API+Public+Documentation" target="_blank"> The Interpretor Public Documentation </a> </p> </div>
Show more...
cenit_high_performance_building_database_1_0
| Author: | Cenit IO |
|---|---|
| License: | no license |
| Branch: | 8.0 |
| Repository: | andhit-r/odoo-integrations |
| Dependencies: | base, and cenit_base |
| Languages: | HTML (38, 20.4%), Python (67, 36.0%), and XML (81, 43.5%) |
The Buildings Database is a shared resource for the building industry. The Database, developed by the U.S. Department of Energy and the National Renewable Energy Laboratory (NREL), is a unique central repository of in-depth information and data on high-performance, green building projects across the United States and abroad.
Show more...