-
Notifications
You must be signed in to change notification settings - Fork 0
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
Sectors Taxonomy #6
Comments
We have some other Taxonomies which has to be/should be used on the Marketplace or the Profilöe as well. So we will implement a REST view on the CSIS from which the other site will fetch the taxonomies periodically or manualy triggerd if there are changes. |
Here is a comparison between the two sectors taxonomies
|
Revised approach - explore purpose: What for is the sector taxonomy used in CSIS? What for is the sector taxonomy used in marketplace?
Question: This is the link to the Worldbank taxonomy as .xls In marketplace the taxonomy needs to be replaced. |
It is used in Studies and Solution Offers . Since Studies are closely related to Projects and Solution Offers are closely related to Profiles, the Taxonomies must be identical.
Yes, there are not so many entities in the CSIS that use the Sectors Taxonomy at the moment, so we can change it. This has to be done before internal and external providers enter their their Solution Offers and Profiles in CSIS and marketplace, respectively Shall I replace the current CSIS and Marketplace Sectors Taxonomies with the World bank Taxonomy? |
That will be great! Another question: |
OK, I updated the Sectors Taxonomy in CSIS. I'll transfer it to the marketplace, once I've found out how.
yes |
I will take over due to a strange problem in the configuration of marketplace which does not allow to import configuration.
a basic content type already exists now on the marketplace. |
done |
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.
The text was updated successfully, but these errors were encountered: