Skip to content
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

Can no longer export #1032

Closed
JDziurlaj opened this issue Jul 7, 2020 · 2 comments
Closed

Can no longer export #1032

JDziurlaj opened this issue Jul 7, 2020 · 2 comments
Labels
est:Moderate Moderate effort to implement est:Score=3 Score for estimate of effort required (scale of 1 upwards) problem:Bug A bug

Comments

@JDziurlaj
Copy link

Current Behaviour (for problems)

When testing 1.2.1-beta, I can no longer export successfully. I tried a very simple example, and filled in all the usual required information. However, I end up with the Export package error of There is a problem with at least 1 package property. Please check and try again.

Steps to Reproduce

  • Open -> Comma Seperated
  • Fill in Table, Provenance, Package info
  • Click Export

Your Environment

  • Data Curator version: 1.2.1-beta
  • Operating System and version: Microsoft Windows [Version 10.0.18363.900]
@ghost
Copy link

ghost commented Jul 14, 2020

Thanks for logging this @JDziurlaj
I'll have a look at this today.

@ghost ghost added est:Moderate Moderate effort to implement est:Score=3 Score for estimate of effort required (scale of 1 upwards) problem:Bug A bug labels Jul 14, 2020
@ghost ghost closed this as completed in abe01e9 Jul 14, 2020
@ghost ghost added this to the Bug fixes in support release 1.2.5 milestone Oct 8, 2020
@carlhiggs
Copy link

I have installed version 1.2.5.0_x64 from the Microsoft Store, and while some initial trials appeared to work, I just experienced this issue after completing full metadata for my CSV data table with no export being produced. It generates the "Export package error" of 'There is a problem with at least 1 package property. Please check and try again.', but there is no indication what this error is. This sounds like it could be the same issue as reported in this closed issue, albeit using the updated release.
image

Prior to attempting export, I experienced some instability when attempting to add sources (it wouldn't add multiple, with the option to add a source ceasing to work in the Package view; and in the table view, when adding a path for a source it complained of an invalid URL when the URL was valid, and when adding an additional source, the entries for both sources appeared corrupted (all blank except title, which for both replaced with a single character of last key pressed). I removed all attempts to provide a source, and there were not specific errors marked for this upon attempt to export -- but it didn't work. So I am not sure if the instability related to sources has resulted in the mysterious error preventing export.

Perhaps this is the same issue, still being an issue? A possible work around would be if I could export the JSON on its own regardless of errors --- then I wouldn't lose my work, and could perhaps modify this manually. Currently, I am concerned that if I close the program I will lose the metadata entries already added.

Here are my windows version details:
image

Cheers, Carl

ghost pushed a commit that referenced this issue Apr 21, 2021
…correctly emptied and removed, before validating on export.
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
est:Moderate Moderate effort to implement est:Score=3 Score for estimate of effort required (scale of 1 upwards) problem:Bug A bug
Projects
None yet
Development

No branches or pull requests

2 participants