Hi Eugene,
If Internet Explorer is not supported, specific versions of the browsers this does support need to be listed. Slippery slope excluding certain browsers.
[IN REVIEW] Added clarification regarding support for IE older than 11: “Directory listing editor is not supported on Microsoft Internet Explorer browser older than version 11.”
Updated to: “Directory listing is accessible by current vendor supported browsers delivered with the OS (operating system).”
2.1.1:
– What are the kinds of things departmental support can expect to be able to troubleshoot outside of the listed FAQ?
I assume that you are referring to the “question mark” FAQ on the menu bar. Outside of the how-to guide in the FAQ, departmental support can assist with standard user-support issues such as page not loading because of certain privacy settings (e.g., no javascript enabled) in the users’ browsers for example.
– Is it possible to list each department’s primary and secondary contacts on the department’s A-Z page so that requests to update the info can go directly to the responsible party? Should the department’s local IT support info be listed as a tertiary contact?
[IN REVIEW] Awesome idea. Noted as an enhancement request to application.
3.1:
– Item on poor implementation and planning does not apply?
Agreed. This is part of the SLA template’s language which is being reviewed and revised holistically outside of this SLA’s scope.
– Is there a specific format required for bulk updates that would make this more efficient for UNM IT and the department?
There will be. One of the enhancement requests in the queue is to add an “import” feature. Once this feature is implemented, the standardized format will be publicized to departments.
2.2.2 and 9.1:
– If system performance and availability reporting are not available for this service then is it appropriate to list a specific uptime of 99.9%?
[IN REVIEW] Good point. Revised language for reporting to: “System availability reports for this service are available on request.”
Service-related questions:
If an employee separates or changes roles, is A-Z a directory that gets updated from Banner or is it a standalone system? If it is a standalone system, end-users need to be responsible for keeping this up to date. UNM HR separation checklist (http://hr.unm.edu/docs/employment/separation-checklist-for-staff-employees.docx) should be updated to reflect the supervisor having to submit directory listing changes that are not automated.
This is a standalone system. I agree with your line of thinking that end-users (designated contacts) need to keep the info updated. HR and IT have not had a conversation regarding the direction in which this application should take place yet. The next version of this application (no ETA) – in my mind – will more than likely pulls information directly from Banner as to avoid duplication of data across the various sources.
Is this directory using a different data source than what is available on directory.unm.edu and what a user can change via Directory Self Service (DSS)? How does DSS and what appears in A-Z differ? Not required of the SLA, but I think helps to better define the service and where users can expect updates to appear (or not).
This is a standalone system at this time. It uses a different data set in a different database than what directory.unm.edu (people) uses.
This service could be powerful if exposed in some fashion for folks to incorporate on other web sites. A single version of the directory that is accessible via web services that every department doesn’t have to duplicate in some fashion would make it an Enterprise service.
[IN REVIEW] Could not agree more. API is on the roadmap.
Eugene
Thanks for your feedback.
- This reply was modified 8 years, 4 months ago by tbui.