DigitalWell transition
index:
review of DigitalWell admin site
The page we're talking about is
here.
First of all, the security certificate needs renewal.
General site comments:
- Breadcrumbs at the top of the page work somewhat for the Sample collection, but not in my collection.
- The behavior of the index is erratic. It displays different amounts of
information at different times.
- note: I was unable to do thorough testing of the permissions part of the
system, since I only have one account and the largest part of the permissions
system is for allowing others various access to your own collections.
admin.digitalwell.washington.edu:
I think that the functionality of this site is fine. It does what it needs to
do in allowing people to log in and directing them to the main DigitalWell
page, the help pages, and the policy page.
I have a couple of questions about this page.
- What will the average user see in the "Collection:" dropdown? Will they see their own collection and any other collections they have permissions on?
- Was the site really only tested in IE 5 and up? It seems to work fine for me in mozilla-based browsers. If this is the case, maybe it should not have this recommendation, or make it more general to up-to-date browsers or browsers supported by C&C.
- How does the intended functionality of this site relate to the 'GFE' site? Is the admin site only for adding content, and the 'GFE' only for searching?
admin.digitalwell.washington.edu/admin/apppermissions.aspx:
The help bar on the right is very necessary. That info would have to be
displayed somewhere on page. This seems like a reasonable location for it.
- link on the right to catalyst group info is broken. (there is also a link
to this here:
admin.digitalwell.washington.edu/admin/permissions.html)
- Delete Permissions table doesn't have a grid in mozilla.
- Group ID field and NetId field are exclusive, but give no visual idea of
that. If Group ID field is filled in, NetID field is ignored.
- order of permission types in dropdown and help menu is different
- no help topic on the right about 'Admin' permission type
admin.digitalwell.washington.edu/admin/index.aspx:
- folders show a [+] next to them even when they contain nothing.
- I have a media group that I cannot get to appear in this view. I can see
it in IntroPage, but not in index. The name of the media group is 'test
group'. Wow, after fiddling with it a bit more, it won't show lots of things
I have. This needs work.
admin.digitalwell.washington.edu/admin/IntoPage.aspx:
- the lowest level table on this page never seems to contain anything. It
just makes an extra brown bar appear.
- My main folder, 'agraf', has its created and modified dates stuck at
1/1/1900 12:00:00 AM. I don't know if this is an artifact of how it was
created or a general error.
admin.digitalwell.washington.edu/admin/defaults.html:
- typo in "Follow the steps below to set a default values for your
collection:"
admin.digitalwell.washington.edu/admin/submitcomment.asp &
admin.digitalwell.washington.edu/admin/submiterror.asp:
- the titlepic.gif image is broken
admin.digitalwell.washington.edu/admin/everything.aspx &
admin.digitalwell.washington.edu/admin/folders.aspx &
admin.digitalwell.washington.edu/admin/mediaobjects.aspx:
- the img tag bullets for these lists have dimensions smaller than the
images themselves, causing the images to look wierdly cropped.
admin.digitalwell.washington.edu/admin/newmedia.aspx:
- cancel button doesn't do anything in mozilla-browsers
admin.digitalwell.washington.edu/admin/addmedia.aspx &
admin.digitalwell.washington.edu/admin/newfolder.aspx &
admin.digitalwell.washington.edu/admin/editfolder.aspx &
admin.digitalwell.washington.edu/admin/editevent.aspx:
- not all fields with a red star next to them are really 'required fields'
admin.digitalwell.washington.edu/admin/newfolder2.aspx &
admin.digitalwell.washington.edu/admin/newmedia2.aspx:
- In mozilla browsers the upper right corner has an empty box that doesn't exist in other
screens.
admin.digitalwell.washington.edu/admin/removeprofile.aspx &
admin.digitalwell.washington.edu/admin/deletemedia.aspx:
- has a check box, but doesn't require it to be checked to remove defaults.
This will eventually hold the GFE (search interface), and would likely have
links to the admin interface, digitalwell.org, and any digitalwell info on the
www/computing/web/streaming pages.
requirements:
- act as a center for the DigitalWell brand.
- a quick overview of what DigitalWell is.
- well-labeled links to resources on other pages.
- link to info on how to sign up for service.
requirements:
- make Admin Tool more apparent as the place to actually add content to DW.
- re-purpose the site from a general development information and links page
to a production tool information page, with technical information and
affiliated groups in a subordinate position to information about using and
accessing the current system interfaces.
ideas:
- Make appearance of homepage and sub-pages match admin page, or create
another consistent format for them.
- Make some or all of the content of digitalwell.org/DigitalWell
Introduction.pdf available in an html format. May also require revision.
phase 1: presuming replacement
requirements:
- remove material referring users to streaming media service activation.
- add material referring users to DW service activation.
- add material encouraging users to move media from streaming media servers
to DW.
- add page to URL references that tells users how to get URLs for media in
DW.
- create new versions of How-to guides that refer to DW use process.
ideas:
- divide page into material that refers to the recommended system (DW) and
the 'old' system (Streaming Media).
- we can start with the current page, including a link to DigitalWell
information and later switch to the new DigitalWell information with a link to
the old pages.
phase 1: presuming coexistence
work
thus far
requirements:
- add material referring users to DW (probably a link to
digitalwell.washington.edu)
- many of the current instructions will apply to streaming media stored
on digitalwell.
- add a page that explains the differences between setting up streaming
from digitalwell and the current system.
- should this page contain any information about metadata?
DigitalWell support heirarchy
I don't know how accurate this is. This is just a guess based on what I know
and have heard so far.
front lines
phone: Client Services - CCI & Tech Support
email: help@cac Routers
This level should be able to answer basic questions about the service and
provide access to reference materials (FAQs or webpages) or route to higher levels as they see fit based on client questions/problems and support necessity.
CCI will need to be informed about how the account creation process works,
and who to send requests to if the process isn't automated at first.
Tech Support should get access to DigitalWell prior to release for final
testing and so that they can familiarize themselves with the system for
support purposes.
Routers should have rref destinations in place for DigitalWell questions.
Web & Media associated Client Services consultants such as myself
These should be able to handle questions about documentation or
processes that clients have trouble with.
DigitalWell support
Should be able to answer architecture-specific questions/problems and fix any
problems that crop up. Should they be involved in the routing process through
projects like the bounce file project, or should they just be a destination
known to middle-level support personnel?
buck stops here
account creation plan & cases
It is unclear at this point who will create accounts for DigitalWell. The
easiest option would be to do this like all other services, with a checkbox on
the uwnetid.washington.edu/manage page.
In addition to account creation, quotas or 'guaranteed disk space' will have
to be managed for DigitalWell accounts. This should be planned and made
trivial so that users can have their quotas increased in a timely manner.
cases
- students
- staff/faculty
- myuw.net accts
- supplemental accts
- departmental
- course
- clinical
- SAO
- ???
Which of these accounts will be able to get the service, and when? What
source will be used to verify account types and how will any exceptions to the
normal procedure be handled?