Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create REST views to expose content to other drupal instances #13

Open
9 of 12 tasks
fgeyer16 opened this issue Apr 28, 2019 · 1 comment
Open
9 of 12 tasks

Create REST views to expose content to other drupal instances #13

fgeyer16 opened this issue Apr 28, 2019 · 1 comment
Assignees
Labels
BB: Marketplace myclimateservice.eu Marketplace
Milestone

Comments

@fgeyer16
Copy link
Contributor

fgeyer16 commented Apr 28, 2019

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

  • expert profile (co-implemented with user sync)
  • solution provider profile (co-implemented with user sync)
  • Project owner profile (co-implemented with user sync)
  • Organisation
  • user data
    ...
    Marketplace
  • offers
  • Projects showcases
    ...
@p-a-s-c-a-l p-a-s-c-a-l added the BB: Marketplace myclimateservice.eu Marketplace label Apr 29, 2019
@p-a-s-c-a-l p-a-s-c-a-l added this to To Do in T5.4 Climate Service Marketplace via automation Apr 29, 2019
@p-a-s-c-a-l p-a-s-c-a-l added this to the ECCA 2019 milestone Apr 29, 2019
@patrickkaleta
Copy link

patrickkaleta commented Apr 29, 2019

@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).

@fgeyer16 WDYT?

Note: Im using the terms Entity, Bundle,... as you described it here in this comment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
BB: Marketplace myclimateservice.eu Marketplace
Projects
No open projects
Development

No branches or pull requests

4 participants