Skip to end of metadata
Go to start of metadata

So many great things to work on next, help us understand where you'd like us to start by voting below. You can also edit the page and add a row to the table if we're missing your top need. Voting will only be available for a short period of time, so please vote now!

If there is something that you feel is important but not listed, you may edit the page and add that to the table.

EDSC Feature Description Votes Voters
Bulk Download Improve user experience related to downloading many granules 7 Alicia Scott, Amy Steiker, Dana Wilson, Jeanne Behnke, Jennifer Wei, Lindsey Harriman, Daine Wright
Additive Model Allow individual granules to be added to projects (a la Reverb) 6 Alicia Scott, Dana Wilson, Jeanne Behnke, Jennifer Wei, Lindsey Harriman, Mark Reese
WCS Related URL Surface collection-level WCS link which would allow user to plug URL into desktop GIS app 4 Alicia Scott, Dana Wilson, John Scialdone, Daine Wright
Responsive Layout Support a wider range of display sizes and formats 3 Amy Steiker, Jeanne Behnke, John Scialdone
E2E Services (OPeNDAP) Continue E2E services implementation (OPeNDAP) 3 Alicia Scott, Dana Wilson, Mark Reese
Timeline Improvements Update timeline in response to usability testing feedback 0
Subsetter Scale Out Interact with WCS to provide single API for EDSC to interact with and return OPeNDAP links to users 0


0


0


0


0

34 Comments

  1. Re: bulk download - not only to improve user experience, but DAAC experience as well with regards to the removal of the 2k granule limit.

  2. Can the feedback on the timeline be shared before we vote on that particular feature (please)?

    1. From usability testing at both LP DAAC and NSIDC, the general consensus was that the timeline had useful features, but users did not immediately understand how to use the timeline or what was available to them. Once timeline functionality was demonstrated, every user said that they found it useful and would use it in the future.

      So our initial thought is to improve the affordance (intuitiveness) in some way. Another easy option is to add a timeline "help" function. We don't have any hard examples of what we would actually do, but we do have data showing users don't know how to use it, but find it useful once shown.

      1. I'd be interested (any others?) in breaking out just the ability to hide the timeline. Unless people are still actively asking for the timeline to be improved (I don't have any use cases), maybe any additional work should be tabled for a later date?

        1. Lindsey Harriman I'd be interested in adding a feature to hide the timeline, as well as improve intuitiveness, but these are lower priority to us compared to the other features. I could also see hiding the timeline as something related to the display size issue (less congestion on the page).

          1. Agree on lower priority!

  3. I'd like to combine both bulk download and granules capability.  In fact, most users would like to bulk download with subsetted data within their region of interest and time frame.

    1. I think we should keep the features separated in terms of voting. Any sort of "this is more valuable if combined with feature ___" should be noted during the call.

  4. Is an improved download manager (for native and/or "transformed" data) included in the Bulk Download feature? If not, I recommend adding this as a new row. 

    1. Yes. The idea for an improved bulk download experience is some new feature that isn't just a script. We've had some preliminary discussions about what could/should happen, but obviously no designs or work in earnest yet. But that's the general idea.

      1. It could still conceivably be a script, but it would be more effective and useful than the current, simple script that is generated.

        1. There is a distinction as far as script-user persona and GUI-user persona. Not all of our users know how to use a script and scripts tend to be platform-specific. The GUI user needs to be considered in this feature. 

          1. Poor choice of words on my part:  I meant that it could still conceivably include scripts. (Scripts are particularly useful when you want the data to go to a machine that is not the one you are running your browser on.)  Scripts might also be plural:  one for Windows and one for Mac / Linux.  We don't have to decide that in this voting process though.

      2. Okay, then I may suggest adding a data processing feature for bulk downloads, including user improvements to processing time expectations and order management. 

        1. That is on the radar, but more in the End-to-End Services Architecture and SDPS Services, which is where most of the work would have to be.  (EDSC would just query CMR or SDPS–not sure which right now–for an expected time.)

          However, our initial discussions suggest that this is pretty hard, probably at least a good year to get right.  Also, a lot of it might become unnecessary for services that can be converted from asynchronous bulk processing to synchronous one-by-one processing. Users would be able to see how long the first ones take, and would be able to start getting serviced data immediately, so a lot of the angst about "where's my order???" is alleviated.

          So, this leads to the question of whether we should even try this in the current EOSDIS architecture, or start folding this into Cumulus Services architecture?

          1. Before we create a new feature, should we see what solutions already exist? And identify all the issues/qualms with the current situation? Will DAACs be involved with that process?

            1. I would  characterize synchronous processing as an existing solution used at other DAACs, just not applied to SDPS services yet. It is essentiallly how OPeNDAP and some of the non-SDPS DAACs RESTful services work there.   But yes, we can look at additional solutions as well, like using S3 as an order distribution mechanism.  We will also likely do some performance testing and instrumentation of the services so we know what their performance characteristics are.

              Also, yes, other DAACs will be involved in that process, likely including some of the non-SDPS DAACs as well going forward.  It might actually be an appropriate follow-on activity to the UFG on data transformations, but focused more on the architectural aspect.

              1. I guess I was referring more to the "download manager" element/Mark's comment on "new feature." DAAC2Disk already exists for bulk download and then whatever is going on with Earthdata Drive.

                LP has found the current script to be effective, it just lacked documentation to indicate how it should be used - and then also the pause issue. We documented that this summer and then Jeanne mentioned that on the phone.

                One of the Reverb features we had requested to be rolled into Earthdata Search was the text file of download links - so you didn't have to use a browser feature (DownthemAll in Firefox doesn't work with the new version btw?) or a script to get your data - or make your own text file.

                Additionally, bulk download of data that has gone through processing (e.g. HEG) has caused issues at some DAACs, so the user-facing messaging could be looked at as well in addition to Amy Steiker's comment on order management.


                1. (DownthemAll in Firefox doesn't work with the new version btw?)

                  I just tested DownloadThemAll! against Earthdata Search and ORNL DAAC's order deliveries. It worked for me. What problems is it giving you? Which 'new version' of which thing? 

                  We've added that as a download mechanism for our orders, so I don't want to get surprised if it breaks.

                    1. Thanks! I've updated Firefox on one of my machines to experience the issue for myself. Looks like it's time to update some pages.

                      1. Great! We are looking into to doing the same (smile) 

                        1. Yep, we're doing the same as well. DownThemAll is still listed on EDSC after clicking on the "Direct Download" option. If you end up pointing to alternatives that are supported in Quantum, I'd be interested to know what those are! For now we'll add a disclaimer.

              2. From an operations standpoint, depending on the transformation taking place, client-side HTTPS timeout could be a concern. A queuing mechanism would also need to be in place on the EDSC side to alleviate bottlenecks on the DAAC end. Even if this were implemented, further improvements can (and should) be made to processing transparency and order status communication. Yes, a user watching their granules process in real-time could help, but that won't help set user expectations prior to order submission, or even during order submission if large orders are queued behind others. 

                1. Yes, all valid concerns.  Note that doing this in the cloud expands our solution space significantly.

  5. Can we add an item for natural language/ranking search? I know we provided a lot of comments this summer and would like to see where those are on the game plan.

  6. Relevancy Ranking is in the CMR task.  Some progress has been made, but we think we need lots more automatable tests to move further forward.

    However, we could add an EDSC item to allow the user to sort data collections on something other than Relevance, like Amazon does.  Could sort on Popularity, Collection End Date, ...

    Is that of potential interest?  (It's non-trivial because of the way that EDSC pages through its results with CMR, but nothing is impossible.)

    1. This summer we sent preferred rankings for how results would get returned for particular keywords/search terms/products - did those ever go into work?

      1. All the rankings of the form "Should see X above Y for query Z" are implemented in an automated test framework for relevancy ranking, which has been used to guide the improvement in relevancy ranking.

        We have not yet added "X should be in the top N for query Z" or "X should not be in the top N for query Z".  (I forget which category most of yours went into.) The test framework is up on github.

        What do people think, should we add the "Top N" set of tests?

    2. Yes, NSIDC would be interested in this (maybe not considered high priority, but definitely on the "nice to have" side). 

      1. LP as well - at least be able to get the newer versions ranked above the older versions.

        1. ORNL DAAC would appreciate this, but our main concern for sorting is the default sort order. That is being address with the CMR task.

    3. Does CMR currently have a way to rank popularity?

      1. Yes, it uses the number of users that downloaded a given data collection over the most recent N months. (I think N might be 6.) That information is exported from EMS on a regular basis.