Similarly as #3207759, as a local association, I would like to be able to promote case studies from within our region.
Currently, case studies can be filtered by Drupal version and sector:
https://www.drupal.org/case-studies/community
When adding a case study, you can't specify the region the case study related to
https://www.drupal.org/node/add/casestudy
I see the following steps we could do this
1) Provide a filter without the need to update/modify the data of existing case studies
The filter would likely be based on the "Offices in" field of the organizations linked to the case study. So when I filter by "Switzerland", I would get all case studies that have at least one organization involved that has offices in Switzerland
2) Allow to specify the country/ies that the case study relates to
Often, I see the end user not reflected in a case study. I would suggest to add a field "Country" that allows to specify one or multiple countries that the case study is relevant for. Usually, this would be the country that the end user / client operates in.
Issue fork drupalorg-3207977
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
- 3207977-allow-to-access
changes, plain diff MR !97
- 3207977-allow-git-renaming
changes, plain diff MR !98
Comments
Comment #2
dasjoComment #3
drummI think we would have to add the field to case studies. Many Drupal shops operate outside of their borders.
Comment #4
dasjoThanks drumm,
Maybe one clarification from my side. If you have a case study i.e. for a project by Axelerant for NASA, you could achieve the filtering without an additional field i think. The client organisation NASA would be tagged with US, so the filtering could display the case study under US.
Would that make sense for you?
Comment #6
crawleyhost commentedComment #8
drummYes, that’s a great simplification of the requirements here.
Comment #12
drummThis filter has been added.