Data providers and other community stakeholders must currently invest operational and development resources producing search clients to serve a segment of the community. Earthdata Search portals reduce the overhead of providing a search interface similar to Earthdata Search to targeted users. It provides several useful features, including:
- Running a maintained, up-to-date instance of Earthdata Search without incurring the cost of hardware or administration
- The ability to present a limited set of collections to users, scoped to only those relevant to the target user community
- Presentation of additional logos, navigation, and page titles
- A simple URL for the portal ( with bookmark-able links within the portal
- Interoperability with the full Earthdata Search site, allowing users to optionally and easily search the full list of collections, and see their saved projects and past retrievals from the portal in Earthdata Search
The remainder of this document will walk through the process of creating and configuring a portal.
Step 1: Reach out!
We're here to help, and we want to understand community needs so we can refine our features. Email Chris Lynnes (email@example.com) to get started with your portal and get in touch with developers.
Important: The workflow for configuring portals is geared toward teams who have familiarity with basic development tools such as git. If this is not the case for you, please reach out to us and let us know; we may be able to assist you with basic configuration.
Because portal configurations are powerful enough to modify Earthdata Search's functionality in arbitrary ways, we must handle portal configuration through our Github project (https://github.com/nasa/earthdata-search/). This allows us to understand incoming changes, test existing portals against new features, and prevent insecure or malicious code from entering our operational environment.
To provide us configuration most efficiently, you will need to fork our GitHub repository. Clone the code from your fork and follow the README to get a local instance of Earthdata Search set up.
To create your portal you will need to create a new directory in "/portals" with a unique name you want as your portal identifier, for this example we will use "example". You then will create the config.json file ("/portals/example/config.json").
A significant amount of configuration can be done through this config.json file. You can view example configurations at https://github.com/nasa/earthdata-search/tree/master/portals/simple/config.json and https://github.com/nasa/earthdata-search/tree/master/portals/complex/config.json. Here is an explanation of the configuration:
This tells EDSC if it needs to load a "styles.scss" file, see Advanced Configuration.
|Boolean||This tells EDSC if it needs to load a "scripts.js" file, see Advanced Configuration.|
|Boolean||If true, EDSC will hide the checkboxes " and|
|Object (Optional)||Configuration for a logo to appear to the right of the NASA logo in the upper left of the page. If omitted, no logo will be added.|
|String (Optional)||This is the id attribute of the <a> tag that houses the logo image, see Advanced Configuration.|
|String (Optional)||Path to logo image. This is not recommended, please see Advanced Configuration for the preferred method of adding the logo image.|
|String (Optional)||This is the URL that users will be sent to when clicking on the logo image. If no value is provided clicking on the logo image will return the user to the EDSC portal home (/portal/example/search).|
|String (Optional)||This text is set as the title attribute in the <a> tag that houses the logo image, it will be displayed when you user hovers their mouse over the logo|
|String (Optional)||A short string representing the organization that replaces "Earthdata" in the top-left of the site toolbar. If omitted, it will just say "Earthdata."|
These parameters are used to filter the list of collections available in the portal.
Current supported values:
If you need support of another CMR query parameter, please contact us.
Refer to the CMR documentation for information on parameters:
|String (Optional)||A short string to be used when referring to the portal. This will appear verbatim where the word "Search" is in the top-left of the site toolbar and will appear in various other places as "Example Portal" when referring to the portal. If omitted, a capitalized version of the portal ID will be used, i.e. "Example."|
If you are authoring something complex or if you have needs that you feel would be better addressed at the basic configuration level, please reach out to our developers, who Chris Lynnes (firstname.lastname@example.org) can put you in touch with.
This is the prefered way to add a new logo image. Save your image(s) into "/portals/myportal/images/". In the logo section of your config.json file, if you set the "id" field to "example-logo", then you would use this SASS rule to load that image:
width: (set the correct width for your logo);
background-image: url('./images/<your logo image>');
You can reference the existing portals for real example of how this works.
In order for this file to be executed, hasStyles must be set to true in config.json
In order for this file to be executed, hasScripts must be set to true in config.json
Incorporating Changes into Earthdata Search
When you have made and tested your changes, push them to your forked copy of the Earthdata Search repository and issue a pull request into the main repository. Our developers will review and incorporate the changes as soon as possible.
Our normal progression to operations is as follows:
- When a pull request is merged, it starts a build. Within a few minutes of the build becoming green, that changes gets pushed to our SIT environment for testing: https://search.sit.earthdata.nasa.gov
- Every other Wednesday, our current UAT environment (https://search.uat.earthdata.nasa.gov) is deployed to our operational environment (https://search.earthdata.nasa.gov) and our SIT environment from the previous Monday is deployed to our UAT environment.
So the progression from a pull request being accepted to it becoming an operational change takes about a month, during which it is available in testing environments.
While we would prefer to stick to this schedule wherever possible, we understand you may have differing schedule needs. If you need it to reach operations sooner, please indicate the desired date on the pull request and we will do our best to accommodate.