search

halestudio / hale

(Spatial) data harmonisation with hale»studio (formerly HUMBOLDT Alignment Editor)
143 stars 44 forks source link

changing paths to lookup tables while opening a project does not affect stored paths #641

Open JohannaOtt opened 6 years ago

JohannaOtt commented 6 years ago

Version 3.5.0.SNAPSHOT Build 409 Revision c75b54928ec8c93b98f491069377135e74512bdd

-open a project with paths for lookup tables that cannot be found -set new paths to lookup tables -paths in Project-view and halex-file are not changed

florianesser commented 5 years ago

@JohannaOtt 's comment from #705:

When opening a project using CSV-files with hale studio 3.4.1 and a resource's path has been changed, you can select a new path for the resource using the wizard that is showing up. When saving the project afterwards the new path is saved to the halex-file. This is the behaviour I would expect for all kinds of source schemas/data, because a change in a resource's path is probably persistent.

I tested the behaviour using fgdb and xml files, but for these cases, saving the project does not lead to updated paths in the halex file.

JohannaOtt commented 5 years ago

The behavior could also be reproduced for transformation projects using Shape files as schema and data soruce

github-actions[bot] commented 4 months ago

This issue has been automatically marked as stale because it has not had activity in the last 60 days. It will be closed in two weeks if no further activity occurs. Thank you for your contributions.

florianesser commented 4 months ago

@JohannaOtt For confirmed bugs, there is the confirmed label that IMO should be used instead of pinned. For features or enhancements that we still plan to implement, there is the planned label.

JohannaOtt commented 4 months ago

For confirmed bugs, there is the confirmed label that IMO should be used instead of pinned

Agreed, adapted it accordingly.

For features or enhancements that we still plan to implement, there is the planned label.

I always understood that to only be used for things where an implementation is planned concretely in the next x months (which is not the case here AFAIK)