Skip to content
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

MUDROD testing results #122

Closed
edshred2000 opened this issue Mar 29, 2017 · 7 comments
Closed

MUDROD testing results #122

edshred2000 opened this issue Mar 29, 2017 · 7 comments

Comments

@edshred2000
Copy link

edshred2000 commented Mar 29, 2017

Results to report testing the JPL MUDROD web site

  1. 'And' is perhaps the best default for free text keyword searches. 'Phrase' is too restrictive for longer keyword queries (e.g, 'coastal ocean wind')
  2. Keyword 'Altimetry' returns nothing. 'Altimeter' does. Ontology can help here ?
  3. No link to dataset landing page in search results. Nowhere to navigate to a data access page.
@Yongyao
Copy link
Collaborator

Yongyao commented Mar 29, 2017

@edshred2000 OK, we will fix this. If you or David find anything else, please also post it here.

@Yongyao
Copy link
Collaborator

Yongyao commented Mar 29, 2017

@lewismc @fgreg Any comments on "Keyword 'Altimetry' returns nothing. 'Altimeter' does. Ontology can help here ?" I think it has to do with the stemming function. Maybe we need a domain-specific one here.

@Yongyao
Copy link
Collaborator

Yongyao commented Apr 11, 2017

Comments 1 & 3 have been addressed in #123

@Yongyao
Copy link
Collaborator

Yongyao commented Apr 11, 2017

David's comments are below.

  1. Dataset indexing needs to be updated to include more up-to-date datasets; perhaps, this could be an automated cron job that runs once per week.
  2. For similar datasets with multiple versions, highest version number should be placed at higher ranking than older versions, regardless of differences in the existing user popularity.
  3. Ensure search terms that are a direct match to a mission/platform/sensor of a given dataset will result in highest rank compared to a related dataset of a different mission/platform/sensor.
  4. Abstract should include at least the first 150 characters (with option to expand to full description) of the Dataset Description.
  5. The following additional geospatial metadata should be displayed in search results; alternatively, these could be incorporated into a “faceted” search mechanism in the side-bar.
    Dataset start/stop date
    Dataset spatial resolution
    Dataset temporal resolution
    Data Format
  6. For the Topic, the term should be a hyperlink that points to existing Measurement information pages, such as:
    Surface Winds, Wind Stress, Vorticity, Surface Winds, Convergence/Divergence, Sigma Naught > https://podaac.jpl.nasa.gov/OceanWind
    Ice Extent, Sea Ice Age > https://podaac.jpl.nasa.gov/SeaIce
    Ocean Currents > https://podaac.jpl.nasa.gov/OceanCurrentsCirculation

@fgreg
Copy link
Collaborator

fgreg commented Apr 26, 2017

@Yongyao can you break this into individual issues? I think some of these have been address while others have not.

@fgreg
Copy link
Collaborator

fgreg commented Apr 26, 2017

@Yongyao @lewismc Actually I think this might have been done already?

#140
#141
#142

If so, I'd say close this issue.

@Yongyao
Copy link
Collaborator

Yongyao commented Apr 26, 2017

This is only one issue that remains to be solved. #152

@Yongyao Yongyao closed this as completed Apr 26, 2017
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants