May I suggest combining the Globus material into one document? Instead of a Globus overview on one page, and Globus how-to instructions on another page, let’s combine everything Globus onto one page, “Globus at XSEDE”. We currently have a small software section consisting of Globus, P3DFFT, GRAM, and other documentation according to a “Software at XSEDE” template I made a few years ago. I’d like to keep consistent and document XSEDE software according to this template. Splitting up the content seems counter-intuitive.
What do you think?
I think it makes the most sense to organize documentation by what users are able to do rather than by vendor. For example, to organize around how how users can login, how users can move data, etc. I think the vendor is secondary to what users are able to do.
Most XSEDE users won't be wondering "how do I use Globus on XSEDE?" They'll instead be wondering, "How do I manage/move/share by data on XSEDE?" The latter question is answered comprehensively (Globus is a part, but only a part of the answer) at XUP -> Documentation -> Manage Data. That's the second page I revised as part of this activity, and it's where the details are.
If someone actually needs to know about Globus, specifically, we provide the page XUP -> Documentation -> User Guides -> Globus. We are not going to maintain a separate copy of all of the details from the Data Management page here. That's too much work. Instead, we provide a brief overview and link to the details on the Data Management page.
Note that it won't be too long (another month or two) before we are ready to roll out the second major Globus service on XSEDE: Web SSO. This is completely different from data management, and so it will have its own page(s). That service is aimed at science gateway developers, XSEDE staff, and campus administrators, so it will probably end up in the Resources -> Science Gateways section and/or a section for campus IT administrators. (Is there such a page? There ought to be, as it's a major element of our project.)
Does this make sense?
Thanks for your email.
I originally authored both docs and I organize and edit all the portal documentation. Way back when I did the Manage Data page I originally listed all the methods including an abbreviated globus section. About a year later I authored the Globus at XSEDE (same as Globus User Guide) doc focusing specifically on users in the XSEDE environment and XSEDE use cases. That’s the fascinating history.
As I re-examine the content and organization, I agree with your take.
How about this:
(Note that "Globus User Guide" and "Globus at XSEDE" are the same document.)
This way we avoid seeming vendor-specific and we streamline things.
Science Gateway pages are here: https://www.xsede.org/ecosystem/science-gateways and I doubt there is. I’ll be happy to work with you on that.
Cool, I didn't know who wrote these pages, and it's nice to know. :)
I would be happy if there was no longer a "Globus at XSEDE" page. I doubt it's visited very often--it's pretty hard to find except by searching--and I truly don't think many people come to our site asking, "I wonder how Globus works on XSEDE?"
I actually don't think we need to keep any of the text from the "new" version of that page that I drafted. The parts about data management will already be on the Manage Data page. The parts about Web SSO foreshadow something that isn't available yet, and it's not related to managing data so it certainly doesn't belong on the Manage Data page.
So I'd be happy with the first and last of the three bullets in your proposal, and not doing the second bullet at all. Is that ok with you?
Given that, is the revised version of the Manage Data page that I drafted in Google Docs suitable for replacing the Manage Data page? I followed your comments, updated the GridFTP endpoint table, and replied to the comment about the pros & cons table (basically agreeing with your suggestion to merge the pros/cons and just calling them "features" or something like that).
I had never thought of it that way, and now I can’t unthink it.
It looks fine to me. I can start working on it and post whenever you like. We can continue to edit as long as needed.
Also if you see any other portal documentation that needs updating please feel free to let me know.