-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
query re iterative data #1039
Comments
Hi @KyleHaynes
If there isn't a problem with the application itself, there might be some other ways to try to use the data (But again please let me know if I haven't quite understood the use case here):
Let me know if any of these cases help or if there is more detail for me to consider here. The use case(s) you've raised here though are a new one for me. If the schema that you have is a valid frictionless schema (ie: regardless of what the data may be), it would be useful for Data Curator to still import it, no matter what state the data is in. Once I've tested your example Kyle I'll add more to this |
Hi @KyleHaynes |
@mattRedBox - thanks a lot for the detailed reply - this has worked perfectly. |
No problem @KyleHaynes. Glad it worked. |
Thanks for such useful software.
Sorry if this question is extremely daft but from my brief usage of the software and scanning through associated documentation, I can't easily seem to see a simple solution.
Say if i receive data x from a data custodian on a monthly basis (with just new records appended), each time I want to import and store (mainly for the benefits of validation) in Data Curator, however, I can't seem to easily apply the original created metadata json schema.
I would have thought the process would be to 1. import csv data (easy enough to do) and then 2 file > import column properties > json from file ...
![image](https://user-images.githubusercontent.com/5267027/96807278-7f944380-1459-11eb-9146-f08879412050.png)
And select the schema from the original zip file (unzipped obviously)... but doing so just indicates it's not a valid schema.
Otherwise, I would have thought it might be possible from importing package properties, but the only option is from a URL, and the data that I'm interested in adding will never be uploaded to any internal/external URL.
Here is some dummy data if interested in poking about ...
ss_c1_export.zip
The text was updated successfully, but these errors were encountered: