Page History

• ITInfo
  • XML Query
    • Not able to query XML to generate index pages (no XQuery), either at author time or runtime
    • Detail: We initially planned to have all of the current ITInfo content migrated to XML.  We would then use something like Xquery to query the XML, gather the appropriate data, and display said content to a page.  We have recently discovered that there is no way to effectively query XML content in this fashion, so we are investigating work-arounds.
  • More AVM in XSL
    • Almost all MIT author-time work-arounds require author time extensions via XSL which cannot trigger all of the events that we need; need more AVM functions in XSL
    • Detail: "Our approach to adding functionality to the authoring process has been to use the XSL to make AVM function calls. However, we cannot get the XSL to execute in all cases where it is needed in order to have a consistent behavior.  The repository has numerous events which can trigger some code to run (for example, to regenerate a new index page when a file in a folder is changed), but the WCM does not make them all available to us. Also, only a few AVM functions are ""built-in"" to the XSL and they are not enough for us; we have to create our own Java classes in order to access these functions.

...

• • •   The whole AVM API should be available to XSL."
  • Runtime DB cannot preview in Virtualization Server
    • Any runtime db/app solution is un-previewable thru virtual server; might need different solutions at author time & runtime
    • Detail: Solutions that use external tools cannot necessarily be run in Preview mode. If the data is stored differently at author time (in the Alfresco repository) or runtime (in file system, or XML database), then preview has to do something different in order to look the way it will look at runtime, and it may not be possible to get an exact correlation.

• Static Content Migration
  • Embedding HTML / Unescaped Markup
    •  Difficulty with embedding HTML in the "generic" webform using TinyMCE
    • Detail: We have a concern that our users are used to editing in Dreamweaver, and will not find the form-based GUI very easy to use.  The usability (or lack thereof) of the editor should not drive users away from the application.  Could be solved as of 2.0.1.
  • Content Regeneration
    • Regeneration of content when needed (see dependency mgmt)
    • The import process involves a great deal of re-formatting the incoming content, going from HTML to templatized XML. Even with scripts and Java classes, we keep discovering many small issues around this.

• Workflow
  • Workflow for non-Alfresco users
    • Non-WCM users need to be included in workflow (email w/URL, click to approve/reject), see Authentication for access issues
    • Detail: The workflow must account for non-Alfresco users. A non-Alfresco user must be able to view content in question and possibly comment on the content as well.
  • Commenting
    • Need commenting on tasks during workflow
    • Detail: Commenting on content must be part of the workflow, rather than simply offering a reviewer the option of approving or rejecting.
  • Task List
    • Need list of files in a workflow task
    • The same users will probably be part of many workflow processes going on simultaneously (there are only 2 final reviewers before content is published). These users need to know what files a particular task refers to
  • Workflow Override
    • Need originator/admin to be able to expire, cancel, and move workflow along without waiting for completion
    • Detail: Sometimes a reviewer may not respond in time, or a piece of content has to be elevated in urgency. Being "in flight" means a content item cannot be edited until the workflow is complete, and it will be necessary to have the ability to override the process.
  • Pooled Workflow
    • Pooling workflow has especially poor UI
    • Detail: We've tried workarounds to make parallel workflow act like pooled workflow, to no avail.