Re: [Hypercontent-users] More functionality - will be help for all

[Alex V. <al...@bi...>]

On Aug 20, 2007, at 2:51 AM, tom tom wrote:

> Hi Alex,
>
> We got hypercontent running on production with no
> issues, after business users (authors,approvers)
> spending lot of time with the tool, they came up with
> some valid requirements, I hope these are very valid
> and important functionalities that may be some other
> institute also might look into,
>
> Here am listing some of those and hoping to send some
> more in the other email.
>
> If you can comment on each item that would be great,
> also keep in mind that we got a staging area and also
> we got seperate authors, approvers and publishers.
>
> 1) Content authors do editing on many future releases,
>
>     e.g first text change should appear in the next
> monday release and both first and second text change
> should appear on next Friday release,
>
>   Can we assign the change to a release or some kind
> of form like that,
>
> Can we get this functionality as shown in the Schedule
> section of the workflow, if so can you illustrate an
> example by means of the entries shown in the workflow
> screen schedule section. what is meant by an edition
> here.
>
> e.g
> Please enter a beginning date as YYYY-MM-DD
> [00-23]:[00-59]
>
> Please enter an ending date??
>
> Please enter the edition to appear on the start
> date???

The file edition is a number that represents a certain revision to  
the file.  If you go to the file revisions screen and mouse over the  
links, you will see "edition" as a parameter on the URL for each  
entry.  If you would like to show the edition number more clearly on  
the revisions screen, you could add

$sub.getAttribute('edition')

around line 36 of /screens/revisions.vm

>
> 2) If we can assign each change to a release or
> whatever, and if we press build or publish which
> release or tag get process, can we instruct to build a
> specific release or tag.

There is currently no mechanism for assigning a tag to multiple  
files, or for building based on that tag.

>
> How can we do this with the use of scheduling(in the
> workflow screen) or without the use of scheduling.
>
> Does the scheduling works as shown in the workflow
> screen.
>

The scheduling does work.  The script that is there simply changes  
the "current edition" flag of the targeted file, so that the  
designated edition becomes active.

>
> 3) When the request goes to a approver as an email,
> approvers are presented with the complete text, is
> there any way to identify the exact change did.
> Can we have some comparison based on the original
> file.

Diff functions are not available currently.  It may be possible to  
integrate an open-source diff library.

>
>
> 4) In an institute all though we have listed all the
> approvers in one big group, there are for .e.g
> Admission approvers, Scholarship Approvers,
>
> Due to this, instead of sending the mail to the entire
> group, how can the author request only for a subset of
> users, e.g if scholarship change then only to
> scholarship approvers e.g

You do not have to have a single "approvers" group; you can create as  
many approver groups as you need as long as each has a unique name.   
You will need to create additional copies of the approval workflow  
configuration scripts for each content "area" and make a couple  
changes, e.g.

...
<workflow binding="/scholarship/**/*.*">
...
<email who="group:scholarship-approvers" subject="[HyperContent]:   
Approval requested" content-type="text/html">
...


Alex