occurrence download: properties for human readable presentation

18469
Reporter: bko
Assignee: fmendez
Type: NewFeature
Summary: occurrence download: properties for human readable presentation
Priority: Major
Resolution: Fixed
Status: Closed
Created: 2016-05-13 11:12:28.123
Updated: 2017-10-10 15:31:21.799
Resolved: 2017-10-10 15:31:21.775
        
Description: The goal is for the new web layer to show the query criteria like:
http://www.gbif.org/dataset/a4555281-5046-424f-9cd1-e7c103234416/activity?&offset=20

To give the web layer a ready-to-use query, it'll be useful and clean to have the following information added to the "download" object: http://api.gbif.org/v1/occurrence/download/dataset/a4555281-5046-424f-9cd1-e7c103234416

1. queryUrl: a constructed URL as shown on the struts page: http://www.gbif.org/occurrence/search?TAXON_KEY=9432&TAXON_KEY=5498&TAXON_KEY=9369&TAXON_KEY=6160&TAXON_KEY=2439923&TAXON_KEY=3240591&TAXON_KEY=2439920&TAXON_KEY=795&TAXON_KEY=2439881&TAXON_KEY=785&TAXON_KEY=731&TAXON_KEY=732&TAXON_KEY=798&TAXON_KEY=9418&TAXON_KEY=5489&TAXON_KEY=5219955&TAXON_KEY=5506&TAXON_KEY=5219946&TAXON_KEY=9619&COUNTRY=PA&COUNTRY=CO&COUNTRY=EC&COUNTRY=CR&COUNTRY=VE&HAS_COORDINATE=true&YEAR=2000%2C*

2. humanReadableQuery: { “Taxon”: [9432, 5498, 9369, 6160, 2439923, 3240591, 2439920, 795, 2439881, 785, 731, 732, 798, 9418, 5489, 5219955, 5506, 5219946, 9619], “Country:” [“PA”, “CO”, “EC”, “CR”, “VE]”, “Has coordinate”: “true”, “Year”: 2000}
]]>
    

Author: bko@gbif.org
Created: 2016-05-17 10:08:51.375
Updated: 2016-05-17 10:08:51.375
        
queryTable: [
{filterType: "Taxon",filterValues: [{comparison: "equals",value: "2443624"}],processedValue: "Rhinoclemmys"},
{filterType: "Has coordinate",filterValues: [{comparison: "equals",value: "true"}],processedValue: ""},
{filterType: "Has geospatial issue",filterValues: [{comparison: "equals",value: "false"}],processedValue: ""}
]

Hi [~fmendez@gbif.org], can you provide this in the API output, together with the composed URL?

Given the potential changes on the taxon key, it's a more fundamental issue to solve in the API and how we store people's queries. We should decide when we will address that. Apart from the quested 'queryURL' and 'humanReadableQuery'. Thanks.