This is really looking great. Thanks so much, Jen and Eric. I updated that page
with the link to the current screen shots. I have just a couple more
suggestions.
1. The register form could indicate under JVM properties the names of the properties that will be
included (e.g., "This includes Java vendor and version information."). Or perhaps you
could add to the System Information statement this note, "You will have a chance to review the
system information before it is submitted."
2. On the register form, the "Submit" button should be replaced with a label/link that
says something like "Review Registration Data."
3. If they elect not to share their information, does the review page not say, "Your
deployment will be added..."?
4. What if they want their deployment listed, but they don't want their contact information listed? Or are we implying that we will not list their email address regardless? I would think that a good number of folks want their university listed but not their email address.
5. I like the idea of having the information automatically appear on the deployments page, but I don't think we are set up for that at this point. Should we adjust the text accordingly? If this is going to be a manual process for the time being, should we have the text on the review and confirmation pages say something like, "We will use this information to update the list of uPortal deployments at http://www.jasig.org/uportal/deeployments.";
I should also note that I have asked the Board of Directors and the uPortal
Steering Committee to draft a statement about how this information is going to
be used. I guess this is like a privacy statement. Anyone interested in
following or contributing to this effort can reference the wiki page at
http://www.ja-sig.org/wiki/x/CASDAQ.
JimH
on 3/17/2009 5:30 PM Eric Dalquist said the following:
The last uPortal steering committee meeting had some very good feedback
from several sources about Jasig needing to do a better job keeping
track of portal deployments. To that end there have been some
discussions on the IRC channel that I thought I'd post about here. There
is a wiki page describing the plan and design:
http://www.ja-sig.org/wiki/display/UPC/Automated+Portal+Registration
The first step is something that we're going to try and get into the
3.1.0 release. It will be a portlet designated for the admin view that
provides a simple form for the administrator to fill out some
information about their install and some checkboxes about automatically
discovered data. The admin can then submit this information to a small
webapp that will reside on www.ja-sig.org. Handling the data would then
be up to the steering committee to deal with. Including this at the last
minute is a tough call but as the new code will be in no way critical
for uPortal to run the risk versus the reward is worth it.
We would very much like feedback on this though. Please review the wiki
page first and any comments, questions or suggestions are more than
welcome.
-Eric
--
You are currently subscribed to [email protected] as:
[email protected]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/uportal-dev
