OmniUpdate
From Uweb
Contents |
Our Contact
John E. Schwartz
Regional Director
OmniUpdate
800-362-2605 ext 211
Email: jschwartz@websiteasp.com
From the Meeting
OmniUpdate- Minutes from the Meeting
Update: Followup to Meeting Questions
Full Page HTML Editor
As discussed this capability exist and during our presentation I was unable to demonstrate this feature due to a change that was part of our Version 7 release that was presented at our User Conference while I was in College Station â≠this change was to facilitate a more direct method with the access button in the page editor tab. If you have a few minutes, I could show you this with the â∠ÂSandboxââˆwe have established, or you can view this at you convenience â≠here is the path:
[http://testdrive.omniupdate.com/tamu/science.php]
>Departments
>Biology
>Positions in Science (scroll to direct edit link â≠date stamp at bottom of page)
>UN=kendra & PW=beasley
>Page Editor Tab
>Current Projects
> HTML Button â≠page must be checked for HTML Editing Access.
Also, when setting up toolbars for users, you are able to include a HTML Edit Button that will allow this access; however, this will only allow changes to the editable region that has been established for that user.
Designing/Customizing User Privileges (ACL)
yes, there is an ability to bring more customization to the Access Control Levels currently with OmniUpdate, and are releasing a more robust standard feature soon. As mentioned, many of our current clients are pleased with the preset levels and this is an option I was unaware of during our presentation. As for being able to customize privileges at individual schools for different sites we are still investigating this possibility. As for now, the changes we would make to your modified ACL would be global.
Changing Hyper-Links within the text body of a page
I was a little optimistic with the statement that XML would cure this, it can, but this will require some additional front end work. And for now with OmniUpdate you would have to manually change the same â∠Âdeadââˆlinks that are in other pages as well. We are however, releasing a link checker/versioning feature soon that will automate this task â≠I will notify you when this is available.
508 â≠â∠ÂTurn OffââˆAlt text/Uploading Pre 508 to Asset Library
for now this would need to be a manual operation that will be accomplished through the HTML editor. I had mentioned this to our tech staff, and they are intrigued by the request as this would assist in your keeping a consistency within the Asset Library.
Uploaded Multiple Images for Multiple Users
this is accomplished in OmniUpdate by uploading the file once and through privilege and folder access you will be able to grant asset privileges to individual users and groups. This was designed to eliminate the need to re-upload files, and create multiple Asset Libraries.
Webcast: XML and the College Website â≠Why the Time is Right
About the Webcast
When it comes to web content management, there are no greater challenges than content repurposing and template controlled publishing. Your institutionâ≢s website is complex, interconnected, and must be managed with the right balance of tools and techniques. XML combined with XSLT is the ideal way to tame the beast. But, is it worth the burden? And, what are real costs and risks associated with the migration to this new, powerful architecture?
To learn more about how to reduce the risks and speed your migration to XML, join Lance Merker, CEO of WebsiteASP, Inc. for this free, 30 minute Webcast. Youâ≢ll learn how to:
- Take best advantage of the XML/XSLT architecture - Selectively use XML and XSLT to repurpose content and manage design - Benefit immediately â≠without a complete website redesign - Best deploy template controlled publishing, while mitigating migration risks
To Register
http://www.omniupdate.com/webcast/index.jsp
Survey Results
1= BEST FIT / 5= WORST FIT
Averages
a. (2.60) Ease of use
b. (2.76) Centralized support and hosting
c. (3.00) Integration with external systems
d. (3.28) Cost for acquisition or purchase
e. (2.92) Version control and archiving of content
f. (2.64) Scalability
g. (2.84) Access to source code
h. (2.28) Web based client access
i. (2.60) Content management workflows
j. (2.91) Ability to host multiple independent sites
k. (2.58) Support for multiple delivery platforms
l. (3.06) User management
m. (2.71) Template driven interface
Questions / Comments ?
does not seem customizable enough
authentication? Ability to tie into LDAP or Active Directory, Independent sites? Same role definitions across multiple sites
