Skip to content
Open Integration Hub master data models
Branch: master
Clone or download
Latest commit 690013d Mar 8, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github
Assets
Decisions Divided decisions into "Open" and "Closed" May 7, 2018
MasterDataModels Merge pull request #135 from openintegrationhub/DSCES-UpdatedCollabor… Dec 11, 2018
Protocols
src
CODE_OF_CONDUCT.md Corrected typos May 16, 2018
CONTRIBUTING.md Update CONTRIBUTING.md Aug 14, 2018
LICENSE Create LICENSE Aug 14, 2018
README.md Update README.md Dec 11, 2018

README.md

Sublime's custom image

The revolution in data synchronization — the Open Integration Hub enables simple data synchronization between any software applications and thus accelerates digitalisation.

Visit the official Open Integration Hub homepage

Table of Content

Introduction

The Open Integration Hub enables data synchronization across a variety of applications. This requires unified data structures — the master data models of the Open Integration Hub. Currently, there are models for the domains addresses and products. In addition, two more models for the domains collaboration and documents will follow soon. More models are to be developed in the very near future. To elaborate further models and to make the Open Integration Hub even better - we need you! So join us and help us grow as an open source community!

Contribution

Getting Started

Within the scope of the master data models of the Open Integration Hub you can contribute in two different ways. You can either request/propose a change to an already existing model or contribute a new model for an currently not existing domain.

Propose a Model Change

An existing model can be change in different ways. The possibility exists to add or remove something from the model or to change an existing part, such as an attribute.

If you want to propose a model change please use the request for model change survey (Currently only available for the domain addresses).

The unified process for changing a model is explained in the following:

  1. Fill out the request for model change survey
  2. Submit the proposal
  3. The relating workgroup will check the proposal according to fix rules
  4. If the proposal is approved the change will be incorporated into the model
  5. A new model version will be published within the next release

Change Request Flow:

Change Request

Realization of Request Sub-Task:

Realization of Request

Contribute a new Model

If you want to contribute a new model for a currently not yet existing domain, please consider the following steps:

Before you start please read the Introduction into Open Integration Hub master data models and How to contribute a new data model.

Contribution Guidelines

Before you contribute please read our contribution guidelines.

Code of Conduct

To see how members of the community are expected to behave, please read the code of conduct. We apply the code of conduct defined by the Contributor Covenant, which is used across many open source projects, such as NodeJS, Atom and Kubernetes.

Contact

When looking for further information or support, please contact: datamodels@openintegrationhub.com .

Content

Folders

  • Decisions: This folder contains all outstanding/made decisions by the workgroup categorized by open and closed decisions
  • MasterDataModels: This folder contains general information about the data models, an explanation of the OIHDataRecord and all currently existing master data models
  • Protocols: Contains meeting protocols of the workgroup meetings
  • src: All JSON schemes can be found here. This includes JSON schemes for all existing master data models, the overarching OIHDataRecord and a generic example as a starting point for writing JSON schemes for the relating data model

Documents

  • CONTRIBUTING: Gathers any rule considering the contribution for the Open Integration Hub project
  • Onboarding: Describes how to proceed when developing a master data model and a connector. It lists the most important documents from the connectors repository and the data and domain models repository, to simplify the onboarding process.
  • CODE_OF_CONDUCT: Contains an explanation of the expected behavior of the community members, following the code of conduct defined by the Contributor Covenant

Workgroup

Information

  • Each workgroup has atleast one status call every two weeks
  • Every committer must attend the status call
  • The governance model defines the workgroup members' roles into managers, committers or contributors

Member

Member Name GitHub Alias Company Role
Philipp Hoegner philecs Cloud Ecosystem Manager
Hansjörg Schmidt hschmidthh Wice Committer
Elke Altendorf ealtendorf StoneOne Committer
Andreas Giloj ag737 Fraunhofer IESE Committer
Franz Degenhardt FranzDegenhardt X-Integrate Committer

Wording

Within the project different terms and abbreviations are frequently used. All terms and abbrevations are explained within the glossary and our list of abbrevations.

You can’t perform that action at this time.