...

• 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 (parameter https://search.sit.earthdata.nasa.gov/search?portal/=your-portal-name)
     this is backwards compatible with the previously established  with bookmark-able links within the portale.g. (https://search.earthdata.nasa.gov/portal/your-portal-name)
• 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
• Inclusion of custom provider-developed CSS and/or Javascript resources into every page to make arbitrary updates to page style and add or remove featuresconfiguration allowing for the manipulation of basic Earthdata Search user interface elements such as showing the only-granules and non-eosdis additional filter checkboxes

The remainder of this document will walk through the process of creating and configuring a portal.

...

We're here to help, and we want to understand community needs so we can refine our features. Email Valerie Dixon (valerie.dixon@nasadixon@nasa.gov) to get started with your portal and get in touch with developers.

...

A significant amount of configuration can be done through this config.json file. You can view an example configurations at configuration at https://github.com/nasa/earthdata-search/treeblob/mastermain/portals/simpledefault/config.json and or browse https://github.com/nasa/earthdata-search/tree/mastermain/portals/complex/config.json to see all portal configurations. Here is an explanation of the configuration:

features

    advancedSearch

    authentication

    featureFacets

        showAvailableFromAwsCloud

        showCustomizable

        showMapImagery

footer

   attributionText

    displayVersion

    primaryLinks

{

 href: "The 

URL 

the 

link 

will 

follow",

title: "The viewable text 

of the link

" 

}

    secondaryLinks

hasStyles

hasScripts

logo

    id

moreInfoUrl

    image

    link

    title

org

pageTitle

parentConfig

portalBrowser

query

  "query": {
    "dataCenter": "ORNL_DAAC",
    "hasGranulesOrCwic": null
  },

  "query": {
    "project": "AirMOSS",
    "hasGranulesOrCwic": null
  },

  "query": {
    "tagKey": ["gov.nasa.impact.*"],
    "hasGranulesOrCwic": null
  },

title

    primary

    secondary

ui

 showNonEosdisCheckbox

 showOnlyGranulesCheckbox

    showTophat

`

Inheriting Configuration Values

Portals now will inherit configuration values from a parent configuration. See the "parentConfig" value above. This allows you to use all of a parent's config values and keep your portal configuration portal configuration minimal if your portal needs most of the same features as the parent configuration.

Advanced Configuration

Portals allow authors to provide SASS styles and JavaScript to run on each page within the portal. These can be useful for altering the page style, hiding unnecessary features, or adding new features that do not make sense for inclusion in Earthdata Search. You can do essentially anything that can be done with Javascript or SASS.

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 (christopher.s.lynnes@nasa.gov) can put you in touch with.

styles.scss

Setting up a Custom Portal Logo:

Adding Portal Logo

To This is the preferred way to add a new logo image, which are displayed next in the left toolbar to the NASA meatball, centered vertically. You can reference the existing portals in the ./portals/... directory for examples of how this works in practice.

...

establish the search context or on the  the portal browser modal (optionally. see portalBrowser boolean config field).

Save your image into the

...

./portals/myportal/images/ directory

...

and name this file logo.png

Custom Logo Best Practices:

• Images will be displayed at a maximum of

...

• 75px tall by

...

• 75px wide. Logos should be trimmed to

...

• fit

...

• within those

...

• dimensions.

...

• It is highly encouraged that images be provided at twice their displayed size (50px x 114px maximum) for better display on high resolution screens.
• Images

...

• must be named

...

• logo.

...

• png

...

Adding Portal to the index.js list

In the /portals directories you will need to add the name of your portal to the portals list in the index.js file. The string you enter should be the same as the name of the directory for your portal. Portals should be added in alphabetical order.
    

portals [
  'above',
    ...
  'your-portal-example'
]

scripts.js

This file will load and execute any JavaScript you need in EDSC. Because EDSC is a single page React application, the uses of this file are limited. But, you can use it to pre-load and second version of your logo to be used when the user hovers over the image. To do this refer to https://github.com/nasa/earthdata-search/tree/master/portals/ornldaac/scripts.js and https://github.com/nasa/earthdata-search/tree/master/portals/ornldaac/styles.scss.

...

Step 5:  Incorporating Changes into Earthdata Search
...
When a pull request is merged, it starts a build. Within a few minutes of the build becoming green, that those changes gets get 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.
...