Notification workflow for public review of extensions

Imported from previous forum

Agree with Hanno. There are far too many email notifications about files that are ambiguous or meaningless. I definitely do not think emails need to go out when an already posted file has a permission or other attribute changed.

I had hoped the tab would initially show the most recent updates but the date issue raised by Lisa currently "prevents" that. I agree to combine the resolution of the date issue with this.

The Notification is currently triggered by any modication to the file- in this case the Access was changed from "Access: Committee: Global Technical Committee" to "Public".

"Save" vs "Save and Notify" capability will allow your suggested approach to be satisfied, subject to the relevant admin procedure being routinely followed.

The "Files" tab can only display a limited number of files as it is actually part of the same page, not a separate page. With a large number of categorised files (as for the GTC) the page-load would be excessive due to the aggregation of all the meta-data to drive all the tabs in single URL call (the Members list is also potentially very large, and is part of the same page data. It currently shows the most recent updates (the number is configurable, but kept fairly low in the interests of performance. Having discussed this we think it would be better to explictly label the current view "Recently Uploaded Files" within the Tab and also explicitly label the title/footer link to the full listing more prominently and appropriately so its clearer how to access the full categorised list of file artefacts.

Our suggestion would be to combine this improvement with the revision to the Date listing to reflect Lisa's recent request re modified/versioned files, as they will both impact the same system components so can be implemented in one sweep.

I would argue that a GTC member has no value in getting an upload notification without context. The main point however is that GTC members are notified by coincidence because the doc is uploaded to the GTC area. There is no need to notify a GTC member if a doc goes into public review. A GTC member has been part of a meeting where it was decided to release a doc for public review. A follower of General Q/A is to be notified and everybody interested in any subscription is at least subscribed to General Q/A.

Saving content w/o notification is definitely a useful feature. By the way, the docs uploaded to GTC are not even visible upon selecting the "Files" tab. One has to choose "all media" and search for it. What is the criteria for the files shown on the initial list of the tab?

Hi Hanno,

We think there may be some confusion here related to the fact that there are 2 unconnected notification processes involved, and you happen to be in the intersection of both sets.

1. A file was uploaded to the GTC and you received a notification about this since you are a member. Only members of the GTC received this and it did not contain any narrative since the file was uploaded without narrative included in the 'Description' field.

2. Independently a discussion was posted within the General Q&A Discussion Category which also generated a notification, on this occassion to all the followers of the General Q&A Discussion Category.

Since you are a member of one and a follower of the other, you received 2 notifications, however, most users would only be notified once since they are not GTC Members.

We are currently in the process of implementing a feature request which will allow content to be saved without notifications being sent. This would enable an Admin to prevent duplication in these circumstances by simply saving the file without triggering a notification. However, this needs to be used carefully since the implication is that any GTC Member who was not a follower of the General Q&A Discussion Category would not be notified at all.

Public review of extension proposals trigger two notifications whereby the one without context comes first (http://www.fixtradingcommunity.org/pg/file/fplpo/read/476067/fix-protocol-ga-cme-european-trade-reporting), followed by the only one that is actually needed which provides the context. The latter has the link to the doc (see above) as well as the link to the discussion entry (http://www.fixtradingcommunity.org/pg/view/842363). However, there are two issues with this:

  1. There is no text explaining what is behind that second link at the bottom of the email
  2. It requires another click to get to the actual entry (http://www.fixtradingcommunity.org/pg/discussions/topicpost/842363/public-comment-period-cme-european-trade-repository-reporting-enhancements).

The link to the doc does not need to be in the notification if we replace it with http://www.fixtradingcommunity.org/pg/discussions/topicpost/842363/public-comment-period-cme-european-trade-repository-reporting-enhancements. The second link (http://www.fixtradingcommunity.org/pg/view/842363) is then obsolete and does not require any preceding text to explain it in the notification.

Also, can the initial notification of the doc upload be suppressed by the person uploading the doc? I guess it has to be uploaded first before the discussion entry with the link to it can be created, but it is confusing. Information about doc uploads without context is of very limited value. Is it a user level configuration or what is it tied to?