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

Task/DES-2389: CSV/JSON Export #111

Merged
merged 8 commits into from
Apr 3, 2023
Merged

Conversation

duckonomy
Copy link
Contributor

Overview:

Fix the CSV/JSON export to work with new structure.

Related Jira tickets:

Testing Steps:

  1. Create a group with images
  2. Add Tag Templates
  3. Save tags with tag structures
  4. Ensure that all the saved tags show up properly in CSV/JSON
  5. Ensure that saved tags are correctly aligned with the corresponding headers in CSV

Copy link
Contributor

@nathanfranklin nathanfranklin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. 👍 I left some comments to consider.

I wonder if some of the issues with "Export to DesignSafe" should be ignored and put in a different follow jira issue that has a low priority. (we could just disable this for now if Fred is okay with that?)

I also wonder if we could just put both the csv and json in the zip. Then we just have one save button that saves a download or saves to DesignSafe. Probably not a priority though.

I found some other bugs unrelated to this PR, that'll I'll document on slack.


zip.generateAsync({ type: 'blob' }).then((content) => {
if (forExport) {
this.filesService.export(systemID, path, fileName, '.zip', content);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Export to DesignSafe:

  • file exported is not csv but maybe the zip. should the UI be updated
    to reflect that?
  • "If no filename is specified, it will default to the Gallery ID number." I don't think this is no longer true
  • when saving a file to DesignSafe if you don't change the name and leave it as "Custom File Name", then it fails as the formname has filename=""

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Adjusted so that it follows the scheme of CSV/JSON export as a fallback.

Copy link
Contributor

@nathanfranklin nathanfranklin Mar 8, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Regarding the below comments on "Export to DesignSafe:" menu, I don't think any of these are addressed. The last bullet still fails for me and then I'm still curious about the first two bullets.

  • file exported is not csv but maybe the zip. should the UI be updated
    to reflect that?
  • "If no filename is specified, it will default to the Gallery ID number." I don't think this is no longer true
  • when saving a file to DesignSafe if you don't change the name and leave it as "Custom File Name", then it fails as the formname has filename=""

I think we can spin them off into another JIRA issue but think they should be noted and followed on.

@nathanfranklin
Copy link
Contributor

related to #111 (comment), i wonder still abou this

I wonder if some of the issues with "Export to DesignSafe" should be ignored and put in a different follow jira issue that has a low priority. (we could just disable this for now if Fred is okay with that?)

as well as :

I also wonder if we could just put both the csv and json in the zip. Then we just have one save button that saves a download or saves to DesignSafe. Probably not a priority though.

thoughts?

@duckonomy duckonomy merged commit 8efa89c into master Apr 3, 2023
@duckonomy duckonomy deleted the task/DES-2389-csv-json-export branch April 3, 2023 23:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants