halestudio / hale

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

Enable loading edited csv schemas #782

Open JohannaOtt opened 4 years ago

JohannaOtt commented 4 years ago

When using a csv file as schema and data source and adding columns to it, hale studio could automatically recognize that there are additional columns in the csv file and provide a dialogue to the customer in order to define the new columns' datatypes. This would facilitate the use of csv files, espeacially if those are edited from time to time and these changes need to be addresses in the alignment.

thorsten-reitz commented 3 years ago

Is it possible to use the "reload and update schemas" process for CSVs? Because that would normally be the way to deal with changes to the schemas. hale studio doesn't generally recognize such changes.

thorsten-reitz commented 4 months ago

@JohannaOtt Do you think we should maintain this ticket?

JohannaOtt commented 4 months ago

Yes I assume so. At least I am not missing it regularly. Maybe @florianesser and @annat2022 can comment. AFAIK you are using csv schemas more often?

thorsten-reitz commented 4 months ago

I did use more CSV schemas, but am normally just reloading the schema through the respective process if I need to make a change.

annat2022 commented 4 months ago

I did use more CSV schemas, but am normally just reloading the schema through the respective process if I need to make a change.

I'm not using csv schemas often. But I just tested it: If I import a csv-file as schema with two attribute fields, save the hale studio project, adjust the used csv-file and add a third field, reload the schema or reload the hale studio project then the third attribute is not added and I'm getting an error for the csv-file import.

grafik

Might be that I'm missing something. But I assume in this case it would be definitely good when hale studio could handle these changes.

github-actions[bot] commented 2 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.