GDP now checks incoming parameters in both GET and POST to make sure that incoming parameters include a 'dataset' and 'algorithm' kvp. If not, GDP will redirect to the landing page using the same method (GET/POST) that was used to get to the GDP using the same parameters as incoming. Otherwise, we allow the GDP to function as previous. The next step is to update the landing page to accept GET or POST and when complete there, resend to the GDP using the same method with the same set of parameters.
Issue #GDP-671 - Verify that sciencebase workflow works with new landing page.
Using released version of csw-excat simple client
GDP Landing page now accepting GET and POST from GDP, memoizing the parameters. Next step is to include those parameters as a GET or POST back to GDP when user wishes to get sent back to GDP
Issue #GDP-671 - Verify that sciencebase workflow works with new landing page.
GDP Landing Page is now redirecting properly back to GDP with GET and POST types
Issue #GDP-671 - Verify that sciencebase workflow works with new landing page.
The only thing left to do at this point is to update how Sciencebase incoming works with this redirecting scheme
Issue #GDP-671 - Verify that sciencebase workflow works with new landing page.
Merge pull request #47 from isuftin/master

GDP UI Landing Page Progress
Merge branch 'master' of github.com:USGS-CIDA/geo-data-portal.git
need to figure out the token replacement, but this is the configuration needed for R to work within GDP process
* README files describe directories, and hold the place for them
* unzipRenameFile.R is used for shapefile support, I remember issues if it isn't there
* The remote Rserve might be a problem with this version that we should fix and supply back to n52