BCMS Activity stream and production reports
In our call on Friday we discussed these use cases for viewing activity in the BCMS:
- As an Editor or org admin, I want to see all the activity for the books I am responsible for and drill down on the activity for a particular book or user in my team.
- As a Sys admin, I want to see all activity across the BCMS and drill down on the activity for a for a particular org, collection, book or user
- As a Sys admin, I want to see all activity for the orgs I am assigned to, and drill down on the activity for a particular collection, book or user.
Similar to a user viewing his notification, the above use cases can be handled on a 'all activity' page that only sys admins, Orgs admins and Editors see.
For the purpose of scoping the activity stream, here is a rough wireframe. The filters Organization, Collection, Book, Workflow, Type, By user cater for the above.
The more activity events we track, the more development time required, so we should be sure about exactly which activity is shown here. The list currently includes:
- Status changes (which includes when a preview has been generated or when errors are reported)
- Additional events related to reviewing content
- A user has requested a review of content
- A user has requested revisions to content
- A user has approved content
In addition to viewing activity, the Sys admin needs to draw production reports on the activity for a particular cases, and download these in Excel or CSV format:
- dates of all status changes to show the full production
- when content was approved
- when content was published
- the duration of time the content was in an "Error" state
- the duration of time the content was in an "In review" state
- the duration of time the content was in an "PDF conversion" state (which shows Apex's time on conversion)
This functionality is shown with the additional filters 'date of status' and 'duration of status'. The sys admin can then select the time range for the report.
Getting a report on the date of status is fairly straight forward, but calculating the duration of status is more complex so we need to confirm which statuses durations are required to provide a reasonable dev time estimate. For example the status "In review" starts when the Author or Editor requests a review from the assigned previewers; the status ends with all previewers approve the content or when the Editor decides to mark the content as 'Ready to publish' before all previewers have approved.
Stacy we also spoke about the functionality of drawing a report on the current status of all content in the Dashboard and Book manager page (for books that have chapter processing). These pages always show the current status of content, so I want to make sure this is really needed. Why would an Org Admin or Editor want this report when she can always see the current status in the UI? Is it only for sharing with external people who are not users in the BCMS?
Can we sense check this with your team in our call today?