8000 Ability to update existing project export · Issue #363 · Riverscapes/QRiS · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Ability to update existing project export 8000 #363

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.

Sign up for GitHub

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

Jump to bottom
Closed
KellyMWhitehead opened this issue Apr 19, 2024 · 5 comments
Closed

Ability to update existing project export #363

KellyMWhitehead opened this issue Apr 19, 2024 · 5 comments
Assignees
@Jdgilby
Labels
enhancement New feature or request
Milestone
1.0 - Public Release

Comments

@KellyMWhitehead
Copy link
Collaborator
  1. Grab the project warehouse id tag
  2. Export new project.xml with the tag
  3. Overwrite or new project export?
  4. Other considerations??
@KellyMWhitehead KellyMWhitehead added the enhancement New feature or request label Apr 19, 2024
@KellyMWhitehead KellyMWhitehead self-assigned this Apr 19, 2024
@joewheaton joewheaton added this to the 1.0 - Public Release milestone Sep 13, 2024
@joewheaton
Copy link
Contributor

@KellyMWhitehead it seems like you are doing this correctly now? @Jdgilby feedback. If you both agree. Close.

@KellyMWhitehead
Copy link
Collaborator Author
KellyMWhitehead commented Sep 17, 2024 •
edited
Loading

ready for 0.9.4.

@Jdgilby Please test this out:

  1. export and upload a project to the Data Exchange (or use one you have already uploaded).
  2. Open in Qris and make a change.
  3. Export the project: Select 'Update Existing' and browse to the project.rs.xml of the uploaded project. Ideally this should be exported to a new folder.
  4. Upload this new project to the data exchange. It should upload as an existing project.

Let me know right away if there are any issues, or the workflow is too complicated. I think we can make it easier, but should suffice for now.

KellyMWhitehead added a commit that referenced this issue Sep 17, 2024
@KellyMWhitehead
Ability to update existing project export #363
d81db20
@KellyMWhitehead KellyMWhitehead mentioned this issue Sep 17, 2024
Merged
philipbaileynar pushed a commit that referenced this issue Sep 17, 2024
@KellyMWhitehead @philipbaileynar
Ability to update existing project export #363
9eead1d
@Jdgilby
Copy link
Collaborator
Jdgilby commented Sep 18, 2024 •
edited
Loading

@KellyMWhitehead This appears to be functional. I successfully updated an existing project in the exchange.

2 things:

  1. The dialog box when exporting a project should be the first thing to pop up not a browse to directory. This is redundant and confusing.
  2. Just to clarify, when exporting from QRIS to a new project.rs.xml you should be exporting to a new folder separate from the original export folder, but you still select update existing project and browse to the old project.rs.xml in the original folder? This is a little confusing, maybe in 1.1 we can make it a little more streamlined.
8000

@KellyMWhitehead
Copy link
Collaborator Author

For Version 0.9.5:

  1. Done - the form opens before you specify the output folder.
  2. I adjusted the form a little bit - hopefully it is a little more helpful. We should still revisit this in the future.

Image

KellyMWhitehead added a commit that referenced this issue Sep 18, 2024
@KellyMWhitehead
Form modifications to export existing project #363
b2c9c6a
@KellyMWhitehead KellyMWhitehead mentioned this issue Sep 18, 2024
Merged
philipbaileynar pushed a commit that referenced this issue Sep 18, 2024
@KellyMWhitehead @philipbaileynar
Form modifications to export existing project #363
c1a68c7
@Jdgilby
Copy link
Collaborator
Jdgilby commented Sep 19, 2024

This is working and much more straightforward. I successfully exported to a new folder updating the old xml as well as exported to the existing folder updating outputs as well as xml. Closing for now, we can start a new issue if we want changes in the future.

@Jdgilby Jdgilby closed this as completed Sep 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Jdgilby Jdgilby

Labels
enhancement New feature or request
Projects
None yet
Milestone
1.0 - Public Release
Development

No branches or pull requests
3 participants
@joewheaton @KellyMWhitehead @Jdgilby
0