-
Notifications
You must be signed in to change notification settings - Fork 496
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
OpenStack Integration - Compute Buttons #3747
Comments
This branch was created based on on 4.5-export-harvest-swift which recently had code from ferrys:4.5-export-harvest-swift-update merged into it. This new branch was not a straight merge, however, because there was some cruft in it that we don't want in the git history. The latest from develop was merged into this new 3747-swift-and-compute-button branch and a `git reset` was performed to make a single commit with all of the changes (and only the changes) that we think we want. This single commit is being made by @pdurbin but thank you to @ferrys @anuj-rt and @landreev who did all the actual work!
Please see UI/UX guidance for the compute button in this document: |
When this is picked up, work should be done on a different branch created from the Swift branch: https://github.com/IQSS/dataverse/tree/3747-swift-and-compute-button |
…group to dataset pg. Moved dataset version number into label next to title on dataset and file pgs. [ref #3747]
…pg in the Installation Guide. [ref #3747]
…l, and other related action buttons on the file, dataset and dataverse pgs. [ref #3747]
… from fragment with file Explore/Download buttons. [ref #3747]
…e button text to bundle. [ref #3747]
#3747 This is a new branch based on 3747-swift-with-derivative-file-support Conflicts (3747-swift-with-derivative-file-support wins): doc/sphinx-guides/source/installation/config.rst src/main/java/edu/harvard/iq/dataverse/dataaccess/DataAccess.java src/main/java/edu/harvard/iq/dataverse/dataaccess/SwiftAccessIO.java
@ferrys said we should merge I'm moved this issue to Code Review at https://waffle.io/IQSS/dataverse |
@ferrys is going to look into publishing not working and will commit a fix to the new |
UI clean up and various other loose enough have been tied up. Documentation placeholder on the Dataset + File Management pg in the User Guide is ready when the documentation is. |
As part of the UI clean up on the dataset and file pg associated with this issue, we also resolved this issue, Version number display #3706. |
A few issues, some found by Mike:
|
…with help text in Cloud Storage Access block. [ref #3747]
Fixed jumping issue with Copy button, and spacing and grammar issues with help text in Cloud Storage Access block. |
Yes, 2-4 are fixed, just whether compute button appears to guest and excessive logging on dataset load, happens with both local and swift files but more with swift. 13 cat images also a good test case ;) |
Wrote new sections on Cloud Dataverse for user guide and added a note about file restrictions in Swift to the Installation Config guide.
Just added new material about Cloud Dataverse to the Installation and User guides. @mheppler, I recommend checking the Guides link in the Cloud Storage Access help text on the dataset page to make sure it still correctly links to the Cloud Storage Access section of the Dataset Management section of the user guide. I tried to set it up so it'll still work, but I want to make sure. |
Added additional detail and emphasis on warnings related to restricted file problems in Cloud Dataverse in both installation and user guides.
…ile Management pg. Minor revisions to Configuration and Installation pgs in Installation Guide. [ref #3747]
Fixed typos on Dataset Management page, put Cloud Computing section before Cloud Storage Access, made assorted minor style edits.
…ed download link for Dataverse Project logo to Foundations pg. [ref #3747]
For the Openstack summit in early May, we should allow users to access an OpenStack instance through Dataverse via a "Compute" button or other means (design will fill in detail here).
The text was updated successfully, but these errors were encountered: