PHPackages                             openeuropa/oe\_search - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Search & Filtering](/categories/search)
4. /
5. openeuropa/oe\_search

ActiveDrupal-module[Search & Filtering](/categories/search)

openeuropa/oe\_search
=====================

Search features for the OpenEuropa project.

2.16.1(2mo ago)1100.1k↓25.9%[3 PRs](https://github.com/openeuropa/oe_search/pulls)2EUPL-1.2PHPPHP >=8.1

Since Apr 25Pushed 2mo ago19 watchersCompare

[ Source](https://github.com/openeuropa/oe_search)[ Packagist](https://packagist.org/packages/openeuropa/oe_search)[ RSS](/packages/openeuropa-oe-search/feed)WikiDiscussions 2.x Synced 1mo ago

READMEChangelog (10)Dependencies (30)Versions (63)Used By (2)

OpenEuropa Search
=================

[](#openeuropa-search)

[![Build Status](https://camo.githubusercontent.com/8deb9623380b578e25558d2edb0356c7622f076be9f35b8a1c889927ed35ad62/68747470733a2f2f64726f6e652e66706669732e65752f6170692f6261646765732f6f70656e6575726f70612f6f655f7365617263682f7374617475732e7376673f6272616e63683d322e78)](https://drone.fpfis.eu/openeuropa/oe_search)

The OpenEuropa Search module integrates [Europa Search Client](https://github.com/openeuropa/europa-search-client) with [Search API](https://www.drupal.org/project/search_api).

Europa Search is the corporate search engine for the European Commission.

Features provided
-----------------

[](#features-provided)

- Search
- Ingestion (Content and Files)
- Multilingual support
- Facet support

Usage
-----

[](#usage)

Before using Corporate Search, API Key, Consumer Key and Consumer Secret are needed. All this information can be provided together with the correct endpoints by Corporate Search Team during the onboarding process.

Please note that for any Corporate Search application to work with the SearchAPI, the following fields must exist in the related index. These fields should be added when the application is created in Corporate Search. The Search API will not work without them.

```
    SEARCH_API_ID
    SEARCH_API_DATASOURCE
    SEARCH_API_LANGUAGE
    SEARCH_API_SITE_HASH
    SEARCH_API_INDEX_ID

```

It is recommended to explore the functionality by first installing and configuring the Demo module. Please refer to the demo documentation to understand how to configure the different endpoints and credentials. When configured correctly the number of documents in the Search API index should show the total number of documents in the Europa Search database.

Limitations
-----------

[](#limitations)

- Only content entities can be ingested.
- Ingested entities should expose a canonical URL. Alternatively, third-party code may alter the document being ingested and provide an arbitrary URL. See the **API** section below.

Requirements
------------

[](#requirements)

- PHP 8.1 or newer.
- Drupal >= 10.
- [Search API](https://www.drupal.org/project/search_api) Drupal module 1.19 or newer.
- [Europa Search Client](https://github.com/openeuropa/europa-search-client) library.

For a full list of dependencies, please check the [composer.json](composer.json) file.

Development setup
-----------------

[](#development-setup)

You can build the development site by running the following steps:

- Install the Composer dependencies:

```
composer install
```

A post command hook (`drupal:site-setup`) is triggered automatically after `composer install`. It will make sure that the necessary symlinks are properly setup in the development site. It will also perform token substitution in development configuration files such as `behat.yml.dist`.

- Install test site by running:

```
./vendor/bin/run drupal:site-install
```

Your test site will be available at .

**Please note:** project files and directories are symlinked within the test site by using the [OpenEuropa Task Runner's Drupal project symlink](https://github.com/openeuropa/task-runner-drupal-project-symlink) command.

If you add a new file or directory in the root of the project, you need to re-run `drupal:site-setup` in order to make sure they are be correctly symlinked.

If you don't want to re-run a full site setup for that, you can simply run:

```
$ ./vendor/bin/run drupal:symlink-project

```

### Using Docker Compose

[](#using-docker-compose)

Alternatively, you can build a development site using [Docker](https://www.docker.com/get-docker) and [Docker Compose](https://docs.docker.com/compose/) with the provided configuration.

Docker provides the necessary services and tools such as a web server and a database server to get the site running, regardless of your local host configuration.

#### Requirements:

[](#requirements-1)

- [Docker](https://www.docker.com/get-docker)
- [Docker Compose](https://docs.docker.com/compose/)

#### Configuration

[](#configuration)

By default, Docker Compose reads two files, a `docker-compose.yml` and an optional `docker-compose.override.yml` file. By convention, the `docker-compose.yml` contains your base configuration and it's provided by default. The override file, as its name implies, can contain configuration overrides for existing services or entirely new services. If a service is defined in both files, Docker Compose merges the configurations.

Find more information on Docker Compose extension mechanism on [the official Docker Compose documentation](https://docs.docker.com/compose/extends/).

#### Usage

[](#usage-1)

To start, run:

```
docker-compose up
```

It's advised to not daemonize `docker-compose` so you can turn it off (`CTRL+C`) quickly when you're done working. However, if you'd like to daemonize it, you have to add the flag `-d`:

```
docker-compose up -d
```

Then:

```
docker-compose exec web composer install
docker-compose exec web ./vendor/bin/run drupal:site-install
```

Using default configuration, the development site files should be available in the `build` directory and the development site should be available at: .

#### Running the tests

[](#running-the-tests)

To run the grumphp checks:

```
docker-compose exec web ./vendor/bin/grumphp run
```

To run the phpunit tests:

```
docker-compose exec web ./vendor/bin/phpunit
```

#### Step debugging

[](#step-debugging)

To enable step debugging from the command line, pass the `XDEBUG_SESSION` environment variable with any value to the container:

```
docker-compose exec -e XDEBUG_SESSION=1 web
```

Please note that, starting from XDebug 3, a connection error message will be outputted in the console if the variable is set but your client is not listening for debugging connections. The error message will cause false negatives for PHPUnit tests.

To initiate step debugging from the browser, set the correct cookie using a browser extension or a bookmarklet like the ones generated at .

Contributing
------------

[](#contributing)

Please read [the full documentation](https://github.com/openeuropa/openeuropa) for details on our code of conduct, and the process for submitting pull requests to us.

Versioning
----------

[](#versioning)

We use [SemVer](http://semver.org/) for versioning. For the available versions, see the [tags on this repository](https://github.com/openeuropa/oe_search/tags).

API
---

[](#api)

### Alter a document being ingested (indexed)

[](#alter-a-document-being-ingested-indexed)

Third party modules are able to intercept and alter the indexed document subscribing to `Drupal\oe_search\Event\DocumentCreationEvent` event:

**mymodule.service.yml**:

```
services:
  mymodule.alter_indexed_doc:
    class: Drupal\mymodule\EventSubscriber\AlterIndexedDocSubscriber
    tags:
      - { name: 'event_subscriber' }
```

**src/EventSubscriber/AlterIndexedDocSubscriber.php**:

```