CDR Tickets

BZDATETIME::2010-10-05 17:11:16
BZCOMMENTOR::William Osei-Poku
BZCOMMENT::1

Considering our discussion on this issue last week, I had further discussions with users and made some modifications to the original requests. I am also attaching a sample report to display the changes to request #3. (The change is in red font for easy identification)

> 1. Would it be possible to create a link from the CDR ID to the Doc history > > of
> the document?
>

To explain this further, for our monthly reports, we record all major changes that require a Date Last Modified Change. As more and more major changes are made to a particular summary document within a month, it becomes difficult to capture all the changes at the end of the month with the current report. In a particular month, for example, the Date Last Modified date could have changed multiple times. The report meanwhile displays only one Date Last Modified change. In order to get an accurate count of the number of changes that need to be reported, users will have to retrieve the document, run the Doc History report and sometimes may have to consult previous versions of the document to get an accurate count of the changes made. If this request is implemented, users will be advised to make a version comment to indicate whether a Date Last Modified change was made or not. This will reduce the amount of time needed to get an accurate count of the changes made for a given period.

> 2. We will also like to have another column that will display comments from the
> last publishable version of the document.
Users will be Okay with #1 in lieu of this request #2.
>
> 3. Could the report also be modified to run for specific users?
>

While the initial request for this modification was to be able to run the report to display changes for only one specific user I just found out that users may also want to be able to run the report for two or more users at a time. The original idea was to include a field in the user interface to enter a user id, for example. Considering the complexity of this request and perhaps its implementation, I would like to suggest the addition of another column to the spread sheet that will display the name of the user who created the version that matches the Date Last Modified reported.

Attachment sample DLM report.xls has been added with description: sample DLM report with user column

BZDATETIME::2010-10-06 09:16:15
BZCOMMENTOR::Volker Englisch
BZCOMMENT::2

(In reply to comment #0)
> 1. Would it be possible to create a link from the CDR ID to the Doc history of
> the document?

If I understand this correctly all that you need to have done is a link to the Document Version History report, right?
Based on the explanation though I'm getting the feeling that the final report might be different from this modified report and I am wondering if it's possible to create that final report that's being compiled to begin with or something close to it? I'm thinking it may be possible store the information when the DateLastModified has been changed in the database which could make it easy to identify the count of how often a summary has been modified during a given time period.

> 3. Could the report also be modified to run for specific users?

You only need to see the last user that updated the document and not all of the users that updated the document during that time frame.
Is that correct?

I will not start with this task until we had another chance to talk about it at our status meeting.

BZDATETIME::2010-10-06 19:31:25
BZCOMMENTOR::William Osei-Poku
BZCOMMENT::3

(In reply to comment #2)
> (In reply to comment #0)
> > 1. Would it be possible to create a link from the CDR ID to the Doc history of
> > the document?
>
> If I understand this correctly all that you need to have done is a link to the
> Document Version History report, right?

That is correct. Just a link to the document version history is what is needed in this case.

> Based on the explanation though I'm getting the feeling that the final report
> might be different from this modified report and I am wondering if it's
> possible to create that final report that's being compiled to begin with or
> something close to it? I'm thinking it may be possible store the information
> when the DateLastModified has been changed in the database which could make it
> easy to identify the count of how often a summary has been modified during a
> given time period.
>
It was not my intention in request #1 to have the report modified. Request #1 is only to create a link to the document version history.

>
> > 3. Could the report also be modified to run for specific users?
>
> You only need to see the last user that updated the document and not all of
> the users that updated the document during that time frame.
> Is that correct?
>

That is correct and I understand that there is a possibility that the DLM could be changed multiple times by multiple users before one of the users saves a version. In that case, just report only the user who saved the version and not all the users who made changes.

BZDATETIME::2010-10-12 15:39:18
BZCOMMENTOR::Volker Englisch
BZCOMMENT::4

I've added the save_user column to the doc_save_action view to allow me to display the user name of the user who created the last version.
Also, the link to the Document Version History has been added to the program
SummaryDateLastModified.py

This is ready for review on MAHLER.

BZDATETIME::2010-10-19 11:07:00
BZCOMMENTOR::William Osei-Poku
BZCOMMENT::5

(In reply to comment #4)
> I've added the save_user column to the doc_save_action view to allow me to
> display the user name of the user who created the last version.
> Also, the link to the Document Version History has been added to the program
> SummaryDateLastModified.py
>
> This is ready for review on MAHLER.

Verified on Mahler. Please promote to Bach.

BZDATETIME::2010-10-19 18:25:47
BZCOMMENTOR::Volker Englisch
BZCOMMENT::6

The following program has been copied to FRANCK and BACH:
SummaryDateLastModified.py - R9926

The view doc_save_action has been modified to add another column in
tables.sql

Please verify on BACH and close this bug.

BZDATETIME::2010-10-26 13:48:32
BZCOMMENTOR::William Osei-Poku
BZCOMMENT::7

(In reply to comment #6)
> The following program has been copied to FRANCK and BACH:
> SummaryDateLastModified.py - R9926
>
> The view doc_save_action has been modified to add another column in
> tables.sql
>
> Please verify on BACH and close this bug.

Verified on Bach. Issue Closed. Thank you!