clarity-h2020 / marketplace Goto Github PK

To harmonise the Taxonomies which are used in the CSIS

1. Create the Vocabularies on the Marketplace and the profile instance. The have to have the same machine names than on the CSIS
2. Create a REST View on the CSIS which exposes the taxonomy Terms. This can be one View which exposes the Terms of all vocabularies if the Vocabulary is exposed as well. Pleaseuse Display Fields instead Display Entity in teh views settings and chose the fields.
3. Create a migration which fetches the data from the CSIS and import it to the instances

profile.miclimateservices.eu:

• Sectors Taxonomy #6
• Solution Offers Taxonomy #5

myclimateservices.eu (marketplace):

• Sectors Taxonomy #6
• Solution Offers Taxonomy #5
• Hazards Taxonomy
• EU-GL Step ?
  ...

Transfer EU-GL Taxonomy from CSIS.

• Update Sectors Taxonomy in CSIS Instance.

The Taxonomy is used in Service Provider Organization Profiles and in Solution Offers.

@fgeyer16 The Taxonomy is implemented in the CSIS Drupal Instance and has to be reused in the Profiles Drupal Instance.

As proposed by Denis some kind of marketplace should be introduced to Clarity, which would give solution providers an opportunity to promote their solutions, which would include different hazards, elements at risk and reference showcases.

For a first draft the following steps need to be done:

• create 3 vocabularies (Hazards, Elements at risk, Solution offer types)

• create 2 content types (Supported scenario, Showcase) with necessary view modes

• install module Paragraphs

• create a View for the Entity Browser ("Entity Browser for Content")

• create Entity Browser for "Supported scenario" and "Showcase"

• create Paragraph "Solution offer reference" which links to showcases

• create Group type "Solution offer"

• create View for Solution offers overview page

• add styling to subtheme

• i18n support, see #7

The layout of this screen could be improved:

• Update Solution Offers Taxonomy in CSIS Instance.

In Service Provider Organization Profiles, this is called "Classify your CS product/service".

TODO: Extract product / service types from individual exploitation plans (T5.2 Exploitation Strategy and Business) and create taxonomy.

@fgeyer16 The Taxonomy is implemented in the CSIS Drupal Instance and has to be reused in the Profiles Drupal Instance.

Simplify and and implement Expert Profiles in profiles.myclimateservice.eu Drupal 8 instance and link with www.myclimateservice.eu and csis.myclimateservice.eu instances (Single-Sign-On).

Todo list for the marketplace

Preparation

• Create Profiles #2

• Harmonise marketplace entities #3

• Create solution offers #1

• solution offers Taxonomy #5

• sectors taxonomy #6

• Projects on marketplace #11
  ...
  Integration

• Taxonomy harmonisation #9

• Content exposure to other drupal instances #13 (how to clear implementation on need)

• Show content of other drupal instances #12 (how to clear implementation on need)

• Projects on market place #15

• Solutions and show cases on marketplace #14

• Single Sign on #10
  ...

You can reference here existing projects which use your offer as a use case. You can write a short description about the project and the use of the offer in the text field. If there is no project on the marketplace to reference yet you can add a project here here.

Following the link https://marketplace-dev.myclimateservices.eu/project/add behind the second here results in 404 Page not found.

TypeError: this._handles.disableSelection is not a functionresizable-min.js:4:4486

The SingleSignOn on Infrastructure is now implemented.
For now SSO only works if the user visits the SSO login page from every Instance. If he is already logged in he will be redirected to the page without seeing the login form.

The system supports so called gateway functionallity, which allows automatic sign in on visiting certain pages, so the user does only need to visit the login page once.
Theoretically we could set this on every page on csis and market place. Practically this disables page caching of drupal. Since drupal without caching is very slow it is not advisable to do make a global gateway.

So we have to define pages on which the single sign on is performed only. These page will be not cached so the should not be pages which are heavily to render.
We then should guide the users to this pages by presenting links.

There can also be pages on which the SingleSignOn can be forced.

Showcases should be shown on the Twins Map.

"edit project phases" without function. It shouldn't be visible for users that don't have the right to edit the project.

Illustration is not shown:

although available in edit view:

Hi! I've received reports from people trying to register for our event this Friday that they are having trouble with the Register button. They have reported that upon clicking on it nothing would happen or it would just load indefinitely.

They only pointer I have is that it may be related with Internet Explorer.

This could also be related with some issue with gotowebinar and that particular browser but I thought it would be better to check with you just in case.

I'm sorry if this issue does not go here but I haven't found a project related with the events.

Setup cypress.io UI Integration Tests for Marketplace and CSIS

• Fix Jenkins issues
• create new GitHub Jenkins users
• create 1st simple UI tests (Jenkins Job)

"Showcase" and "Solution Offers" shall be maintained in Marketplace (& synchronized with CSIS).

1st step is to move the respective data from CSIS to Marketplace. Since I don't expect that the data models are identical (there are also many references to CSIS-only taxonomies), this is a manual task.

2nd step is to synchronise CSIS with Marketplace. However, how can this work if the data models are different? Furthermore, in CSIS, "Showcases" and "Solution Offers" will only be used for the "Twins Tab" (Scenario Transferability). AFAIK we have to assign some taxonomy terms to these entities to make the twins functionality work. That means, if you create a new "Solution Offers" in Marketplace, you would have to assign a CSIS taxonomy term, e.g. "Hazard".

We need a possibility for Customers to describe his project, so he can find experts or solutions providers who fit to his needs or they can find him.Creating a Study on the csis for this purpose seems to be an overkill.
Andrea and I propose a "project" content type on the Marketplace. AT least it should have fields which contain the same data as the Context Tab for a csis-study and the projects location. If this is the case the project can have a "create study" button which will then create a Study with this data in the csis.
I think this being a content and no group is sufficient enough since souch a short description is nothing what needs cocreation between multiple users.

In Solution Offer / Manage Display One Column Layout is selected

The display shows actually 2 columns:

Why? Where is this layout configured?

Solution providers and Experts needs to have a page where they can see which Projects search solutions or expertise they offer

Harmonise Solution Offers + Twins Data Models and link with Adaptation Options and Expert Profiles Entity Types.

Data model before harmonisation:

Two issues in Categorization Screen:

• rendering of keywords should be improved (tags instead of plain text with internal drupal id)
• when you hit ENTER (e.g. in textfield "Keywords"), the action behind the button "BACK TO DESCRIPTION" is executed -> all information this form are lost

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
• Showcases - URL: .../rest/myclimateservices/showcases not necessary any more since these moved to marketplace
• adaption options
• Twins - URL: .../rest/myclimateservices/twins
• Solution offer types (taxonomy) - URL: .../rest/myclimateservices/taxonomy/solution_offer_types
  ...

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

For customer we need apage on the marketplace on which they can see Solution offers and show cases which are relevant for them

Whether and how do we address Solution Offers and / or Showcases in different languages? Are there inbuilt Drupal functions for i18n content?

ATM, I'm creating a showcase for a municipality in Germany. The web application I'm embedding is German (https://csis.myclimateservice.eu/node/487), so the Showcase description is.

Should I add a field 'language' to the Showcase Entity Type and then create 'Languages' Taxonomy, or is there a better way to do this?

Profile informations, Solutions offer, show cases, and so on have to available on all Drupal instances (CSIS, Marketplace,Profile,..). There are two posibilites to archieve this goal:

1. Synchronise all content over all instances or
2. Get content by REST and ajax where we need it.

To solution 1:
I found some modules which would do the job for 1 for us but they need an external pay service (https://www.drupal.org/project/entity_pilot)or relay on JSON API v1 while we already use v2 (https://www.drupal.org/project/entity_share). We can also archive the goal by using Drupal core functionality. The drawback of multiplicating content over the instances is, that we have an bigger maintenance workload since we have to do changes in structure on every instance: Changes in the content has also to be synchronized. This will not be a problem at the beginning, but if the site grows keeping all the content synchronized can get a performance problem.

To solution 2:
If we fetch the content to show from the drupal instance it originates, we have only one point to maintain structure and there is no need to synchronize content. Since drupal views provides a REST Display, we can filter the content in the same way if it is on the same drupal instance. Only complicated qureies which require heavy use of relationships are not possible over drupal instances then. I think this can be overcome by using more links to other views.

I prefer Solution 2 and already started to create a custom module, which allows embedding external content by a block or field.in an entity.