*Note - Please use textile markup to input code examples in the comments box (e.g. start and end the code sections with @ signs). Click the pencil icon in the word processor to remove the WYSIWYG.
Cascade Server Ideas
Please submit your ideas on how to improve Cascade Server.
-
3
Improvement of starting publish delay
With Cascade 5.7.3, we observe that we have about a 30 seconds delay before the first asset in the publish queue starts its publication.
We need a parameter to optimize this delay. -
3
"Tags" Dynamic Metadata Field
It would be really cool to have a “tagging” metadata field type or a dropdown that also had a text box to add items. That way, users could add categories as needed, but would still receive a list of all existing categories. The interface could be like the search autocomplete or more like a traditional drop-down menu.
-
2
A method to send administrative messages to active users
It would be nice if you could somehow send a message (a noticable
message, not to the users’ inboxes) to the active users so that they
can be notified that, for example, the system is going down for
maintenance at a specified time. This would smooth out the process of
doing all of these upgrades by helping to eliminate the need for admins
to contact each user individually, or just kick them out of the system
and risk lost work. -
3
Ability to link to folders
We should be able to tell Cascade the default directory index page for each site, so that published links to those pages go to “/” or “/site/” instead of “/index.html” or “/site/index.php”.
-
0
Ability to modify look, feel, and text of workflow-generated emails
It would be nice if Cascade could allow administrators to modify the emails that are generated by workflows. -
0
Ability to require comments in workflows
It would be helpful if the Cascade had the ability to require comments
within a workflow. Similarly, if comments are not required, it would be
nice to bypass the page completely. -
1
Add a parameter to clean up the publish queue when cascade is restarted
The publish queue is now persistant when we restart Cascade 5.7.3
But in some cases, it might be interresting to ‘reset’ the system upon a restart. -
1
Additional auth methods for SFTP
We have a site that needs to publish to a server which, for security reasons, does not enable the “password” SSH auth method. For situations like these, it would be great if Cascade could support other common auth methods such as publickey and keyboard-interactive.
-
10
Ajaxify Publisher Status
Instead of refreshing the entire page, use ajax to update publisher status. In addition, possibly include a publisher status for each user at the top right to allow them to keep working while still knowing the status of their last publish.
-
-1
Allow connection to multiple LDAPs
Allow connection to multiple LDAP servers to facilitate pulling in users from different systems.
-
0
Allow data definition fields to be "grayed" out
Allow for data definition field to be grayed out as additional option for restricting field-level edit access in data definitions.
-
3
Allow disabling of TinyMCE
Somehow provide an option to disable TinyMCE on individual pages or sections.
This to be able to handle on an as-needed basis the inclusion of content that TinyMCE mangles in some way or another. -
2
Allow more asset factories to display on the dashboard in folder order
Allow more than six asset factories to display on the dashboard in the New Content Wizard area, as well as inherit the current folder order of the assets. The current folder order does not seem to translate to the dashboard.
-
3
Allow publishing of non-xml pages
Cascade users would like the ability to publish non-xml pages. -
1
Application should more intelligently determine if a tab is currently selected
This is in reference to an already existing feature request, although I think it’s more of a bug. In the 4.x we didn’t have a problem using the URL webedit.brandeis.edu for Cascade, but in 5.x (at least 5.5.2) the page highlights the Edit tab when viewing the page.
People can still view and can still edit so it’s not the most critical bug, but it is fairly confusing for the UI and should be fixed. -
1
Apply data definitions to blocks
It would be useful to be able to apply data definitions to blocks in
addition to pages. This would help in scenarios where there is
structured content which isn’t tied to any one page. -
16
Asset Recycling Bin
It would be great to have a more robust asset recycling bin to prevent users from accidentally deleting items that can’t be recovered by administrators.
-
1
Audit trail for access-change events
We’ve run into a few situations where, as best we can tell, someone stumbled into the access tab for one of the folders in their site (or the site folder itself) and inadvertently set it to be world-writable. Unfortunately, we can’t really go back and verify that this is in fact what happened, let alone figure out who did it and when.
It would be neat if any access changes made to assets were audited, that way we can verify that this is user error and follow up with that user to make sure they understand how to use the access screen.
-
0
Create Additional Roles
I love the fact that I can edit roles but I would like to be able to create my own roles to get more granular with permissions
-
5
Create editing plugin framework
Like the current Asset Factory plugins, it would be great to attach plugins to edit events. This would allow developers to do things like verify certain file extensions for edited file or naming conventions, etc. Currently, this can only be done on the initial asset creation.
Top / Up / Table of Contents
© 2001-2009 Hannon Hill Corporation. All rights reserved.
Accessibility | Legal | Technical Support | Knowledge Base | Site Map | Index
Accessibility | Legal | Technical Support | Knowledge Base | Site Map | Index
