ongr-archive / oxidconnectorbundle

DEPRECATED, DO NOT USE WILL BE REMOVED

OXID Connector Bundle

Warning

This bundle is work in progress in preview stage. Codebase will change rapidly with BC breaking features.

Introduction

ONGR OXIDConnector Bundle is responsible for transforming data taken from OXID database into Elasticsearch format.

License

This bundle is under the MIT license. Please, see the complete license in the bundle LICENSE file.

oxidconnectorbundle's Issues

Wrong classes configured

https://github.com/ongr-io/OXIDConnectorBundle/blob/master/Resources/config/services.yml#L3

must use

https://github.com/ongr-io/ConnectionsBundle/blob/master/Sync/Extractor/Relation/SimpleSqlRelation.php

Same applies to other triggers.

Sql relations services not configured

Missing url mapping.

ORM mapping for urls is not defined in Category, Article and Content entities.

DataSync test

[doc] ES manager in installation guide

In installation guide "oxid" es manager is used, but not fully documented its configuration. Should be documented fully or changed to default manager, to make installation easier.

Disable generating code coverage html

SEO urls missing

Currently when importing from OXID, no urls are set for product/category/content documents.

Connector should import custom SEO urls or generate them using rules from http://wiki.oxidforge.org/Tutorials/Understanding_OXID_SEO

Review composer.json

Review composer.json and update to support newest bundle versions.

[doc] Documentation improvement

• User friendly overview,
• Details of implementation,
• Customizations? Expandability?

Documentation lacks introduction

Despite the name talks for itself, I think only installation guide is not enough. IMO at least one sentence about what this bundle does would be nice for introduction.

Add installation documentation

Add lang documentation

We need to analyze if we can set up multilanguage shops in oxid connector and write documentation for it.

Default pipelines should be configured.

There should be default pipelines configured in connector, for easer launch out of the box.

Migrations seems not to be sane

hi,

i am followed the bundle with the purpose to see other connections to oxid than my own, that we created the last weeks. So i wanted to have a look into the migration. At the first view the mapping on the database cols seems to be very cool and easy, but it isn't oxid has got a lot of logic in their objects, that manipulates them. So you can't see the database tables as the entities you can work with. I will give you two examples:

Price calculation

You won't ever see the value of OXPRICE in the frontend. The value is manipulated depending on several shop settings (net/brut view, payment rules)

Translated text - Title of a product

Your mapping will work for shops with one base language. Oxid generates the translations by adding an extra col to the database table like title_1, title_2, ... So you won't be able to map the right col in your entity for the migration.

I would see two different solutions. Both base on the situation, that you need Oxid the oxid logic (means the shop it self) in between.

1. Create a SDK
   That means the Connector would just define some interfaces and services to to update the Ongr values. So the oxid shop devs would create its own module with its own logic to connect to Ongr. They would just extend the oxArticle 's save()/delete() method and create their own mapping to the document you persist. Mostly the devs would same methods/mechanism that oxid is calling when creating the values for the frontend.
2. Implementing that Connector and bootstrapping parts of the shop ...
   ... to call its own logic while fetching the values from the objects.

Even when i would mean to create an other package/module, i would prefere the first solution.

Bundle has a lot of unused configurations.

Seems like most of things defined here are not used anywhere

ongr_oxid:
    database_mapping:
        oxid:
            tags:
                @shop_tag: '_1'
                @lang_tag: '_1_en'
            shop_id: 0
            lang_id: 0
    entity_namespace: ONGROXIDConnectorBundle

Upgrade codesniffer standard to ~2.1

Upgrade to connections bundle v0.6.0

Relation definitions needs updating:

• Change argument arrangement.
• Changed used class names.

Add overall test for data import process

Test whole process:

• add data to the database
• run pipeline to collect data in sync. storage
• run pipeline to import data into elastic search
• test results from elastic search

[doc] Wrong command given

https://github.com/ongr-io/OXIDConnectorBundle/blame/master/Resources/docs/index.rst#L8

At current time there is no stable version of bundle, those documentation should be changed or stable version should be released.