Can you give an estimate of implementing a quicker way to re-export (with last settings) from HALE?

[simboss]

Freshdesk Ticket ID: 17287
Freshdesk Ticket Agent: Support
Freshdesk Ticket Agent Email: support@geo-solutions.it
Ticket Priority: High
Freshdesk Ticket Description:

Can you give an estimate of implementing a quicker way to re-export (with last settings) from HALE? As suggested in https://groups.google.com/forum/#!topic/npra-gs/2FKz8Jwu-UY
This about avoiding have to perform many mouse clicks, and enter the same 3 text fields of values (Hostname, database, schema), for every attempt to export and test a modified HALE mapping.
I often do small changes trial and error, at a time in HALE, and want to test. And the lengthy process to export allignment adds up over time.
This applies to both the options exporting "App-Schema Configuration" and "App-Schema Configuration [Direct Upload]".

[simboss]

Comment added by agent Marketing Agent in Freshdesk ticket id 17287:

Dear Gabriel,
I have put this on Nuno's table.

We should get back to you with an idea next week; it might need a little reasearch time but that is on us this time.

Regards,

==
Our support, Your Success! Visit http://www.geo-solutions.it/enterprise-support-services for more information.
==

GeoSolutions S.A.S.

Via di Montramito 3/A

55054  Massarosa (LU)

Italy

phone: +39 0584 962313

fax:     +39 0584 1660272

http://www.geo-solutions.it

http://twitter.com/geosolutions_it

-------------------------------------------------------

[nmco]

Implementation note:

I see two options:

1. we manage to store App-Schema export configuration along with the HALE project, unfortunately this depends on HALE architecture so not sure it is possible, although they made some update regarding this on more recent HALE versions

2. when exporting App-Schema stuff we ask the user if he wants to store this configuration and where, we can even say this is better since it will allow us to have configurations for different geoservers \ environments

[simboss]

Comment added by agent Support in Freshdesk ticket id 17287:

Dear Gabriel,

We have think about this, and the best solution here would be that when exporting App-Shema configuration (both direct or ZIP) the user would have the option to store the forms values (GeoServer URL, GeoServer credentials, host name, database name, etc ...) in a file and then reload \ reuse them the next time.

In practice this means that when exporting App-Schema configuration the user would have an option to enter a file path from where the form values can be stored, loaded or updated. This will also allow the possibility of having several exports configuration, e.g. GeoServer test instance vs production GeoServer instance.

Our estimation to implement this is 5 days, we will need to battle with HALE framework to implement this.

Please let me know if you any doubt \ question.

Kind regards,

Nuno Oliveira

Ticket: http://geosolutions.freshdesk.com/helpdesk/tickets/17287

 

==

Our support, Your Success! Visit http://www.geo-solutions.it/enterprise-support-services for more information.

==

Support Engineer

GeoSolutions S.A.S.

Via di Montramito 3/A

55054  Massarosa (LU)

Italy

phone: +39 0584 962313

fax:     +39 0584 1660272

http://www.geo-solutions.it

http://twitter.com/geosolutions_it

[simboss]

Comment added by customer Gabriel Jonsson in Freshdesk ticket id 17287:

Hi!

That sounds too expensive for the benefit.

I was hoping for some simple fix. Maybe that particular dialog box could be storing the entered values in memory and auto-insert them as default values in the next export in the same session?

If HALE also saved and remembered these between startups would be convenient but I don't see a need for it, at leas not at that cost. At this point it is more about reducing time spent in the development cycle. If it's not a small fix we can live with those extra clicks and presses.

Best regards

Gabriel