Module Description
This module allow you to connect to datasets from external databases and use it in your Drupal 8 website. While content lives external, Drupal sees those remote entities as internal. This makes it possible to alter the field displays, add references, comments, pathaliases, share buttons, webshop products and more.
External data You can use within your website museum collections, content of Wikipedia, external specialised thesauri for wildlife, streetnames, members, and other systems in use within an organisation. If the back-end supports updating as well, you can even create, edit and delete remote entities, making Drupal a central hub for content in an organisation.
Plugins
* External Entities Wikibase plugin
* External Entities Database plugin
* Database cross-schema query API
* External Entities Multiple Storage plugin
* External Entities Manager
* External Entities Files plugin
* External Entities Image File (exif) Storage plugin
* External Entities TSV Files Storage plugin
* External Entities JSON Files Storage plugin
* External Entities Yaml Files Storage plugin
* External Entities XML Files Storage plugin
Background Drupal 8 is built database agnostic. It should not matter for Drupal anymore if data for an entity is coming from the internal SQL-database, an external json file or anything else.
Technique The module provides an option to define an external entity type per endpoint and mapping for each field. Currently the module is using a REST back-end (more back-end types can be added since they are just plugins).
Known limitations
* Views: #2079019: Make Views use SqlEntityStorageInterface and http://cgit.drupalcode.org/efq_views/log/?h=8.x-1.x as a solution you can use search based views through the search api, as search can index external entities
* Comment: #2496699: Allow comments to be attached to entities using a string primary key, as a solution you can use comments fields attached as annotations
Drupal and this module assumes all fields of an entity are coming from the same dataset. All fields within that entity type reads the data from the defined source and writes data to that source. You can add fields, but they only become filled when they are mapped to a field in the datasource or autofilled. To deal with this, this module provides 'annotations' connected to an entity where you can define your own fields.
External data You can use within your website museum collections, content of Wikipedia, external specialised thesauri for wildlife, streetnames, members, and other systems in use within an organisation. If the back-end supports updating as well, you can even create, edit and delete remote entities, making Drupal a central hub for content in an organisation.
Plugins
* External Entities Wikibase plugin
* External Entities Database plugin
* Database cross-schema query API
* External Entities Multiple Storage plugin
* External Entities Manager
* External Entities Files plugin
* External Entities Image File (exif) Storage plugin
* External Entities TSV Files Storage plugin
* External Entities JSON Files Storage plugin
* External Entities Yaml Files Storage plugin
* External Entities XML Files Storage plugin
Background Drupal 8 is built database agnostic. It should not matter for Drupal anymore if data for an entity is coming from the internal SQL-database, an external json file or anything else.
Technique The module provides an option to define an external entity type per endpoint and mapping for each field. Currently the module is using a REST back-end (more back-end types can be added since they are just plugins).
Known limitations
* Views: #2079019: Make Views use SqlEntityStorageInterface and http://cgit.drupalcode.org/efq_views/log/?h=8.x-1.x as a solution you can use search based views through the search api, as search can index external entities
* Comment: #2496699: Allow comments to be attached to entities using a string primary key, as a solution you can use comments fields attached as annotations
Drupal and this module assumes all fields of an entity are coming from the same dataset. All fields within that entity type reads the data from the defined source and writes data to that source. You can add fields, but they only become filled when they are mapped to a field in the datasource or autofilled. To deal with this, this module provides 'annotations' connected to an entity where you can define your own fields.
Module Link
Project Usage
368
Security Covered
Covered By Security Advisory
Version Available
Production
Module Summary
This module aims to solve the issue of connecting to datasets from external databases and using them in a Drupal 8 website, treating remote entities as internal for customization and manipulation purposes.
Data Name
external_entities
OPENAI CHATBOT
OPENAI CHATBOT
