You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To show content across all drupal instances the content host instance has to expose its content to the other instances via a REST Interface. SO we have to create REST views for following Contents:
CSIS
Solution Offers not necessary since these moved to marketplace
@fgeyer16
I looked into this a bit and as discussed today during our telco I will not display the whole entities in those views, but rather the individual fields (this gives us more flexibility).
How to neatly organize all those views?
We already have a couple of different REST views (used by Emikat, Map component etc.), where we could include those additional views, but I'd rather create separate dedicated views on all Drupal instances (CSIS, Profile, Marketplace) with a common naming convention, so it's clear that those views are meant to be used by the other Drupal instances (maybe: Drupal-shared ENTITY-TYPE, so for example "Drupal-shared Content" and "Drupal-shared Groups"?) and each of those views would get a display for each bundle that we want to share among all the Drupal instances.
Similar to that I would use for the path of each View display a commonly shared prefix, followed by the bundle name, the format type (hal_json) and optional filters (e.g.: /rest/myclimateservices/showcases?_format=hal_json&eu_gl_methodology=201).
To show content across all drupal instances the content host instance has to expose its content to the other instances via a REST Interface. SO we have to create REST views for following Contents:
CSIS
...
Profile
...
Marketplace
...
The text was updated successfully, but these errors were encountered: