The notifications emails should look better, provide more meta data (e.g. first x lines of docs). Additionally it needs to be possible for customers to configure these notifications mails (e.g. add header, footer etc.).
Additionally there should be an option for users to un-subscribe these email notifications. ...
In 851 the user profiles need to be defined in the discussion database directly. However most users don't want to enter this data redundantly. This feature will allow pulling data from other discussion databases where users have already defined profiles or from any other custom Notes database.
It should be able to mark certain topics as sticky so that they also show up at the top of a view (e.g. all topics view, most recent topics).
See here for more - idea 013.02
In 8.5 the web user interface was refreshed via XPages for the core end user functionality. On the rich client the UI however is still the older UI. In 8.5.1 the XPages UI could be used on the rich client but the template still launches the classic rich client UI ...
There are various features missing in the 851 web user interface that exist on the rich client. Except of some configuration features they should be added to the 851 user interface. Some of these features had existed in the web, but got lost when the 85 web interface was redone ...
Topics should be able to expire so that they don't show up in the standard views for end users anymore. This is important to manage the 'flood' of topics and make it easier for users to find the important topics. Often topics have only a short life cycle (e.g. 'car ...
Moderators should be able to mark topics as to be archived so that they don't show up in the standard end user views anymore (e.g. all topics).
When marked as such formulas can be written so that the documents are removed/archived via the standard Notes archive feature.
Similar to Connections but with less data than in Connection profiles (just the data as in 851 discussion profiles).
See here for more - idea 003
* be able to create To Do's with a link to the Topic, when people need to take action as a result of the discussion.
In addition to the existing preferences there need to be new and more important ones: 1. New responses to topics I created 2. Changes in topics I've commented on And (1) and (2) should be turned on by default. These preferences are stored per discussion database even if user profiles ...
Sometimes topics contain information that shouldn't be in the topic/discussion (e.g. confidential data). In this case end users should be able to report a topic to a discussion moderator.
See here for more - idea 009
It should be possible to see in an opened topic where in the tree the user currently is. In 851 only the responses to a document are shown, but not the parents.
Additionally to better use real estate it needs to be possible to only show the subjects of responses ...
The subject line used in discussions is often not detailed enough. Presenting the response thread using the 'Conversations' feature in the 8 inbox would allow at least part of the response body to be displayed as well. This would give a better overview of the thread content.
Ideally I would like to see ...
Similarly to Lotus Connections Activities it should be able to easily add Notes documents (e.g. mails) as topics to the discussion (e.g. via context menu).
See here for more - idea 016.03
End users should be able to mark topics as read only so that nobody except of them (and moderator) can change them and nobody can create responses.
See here for more - idea 013.01
In addition to the email notifications there need to be feeds that users can subscribe to in order to get notified about changes. Users can then see these notifications in their feed reader of choice (e.g. Notes 8).
Users need to be able to subscribe to different feeds:
CSSs allow the modifications of the look & feel of the HTML based user interface. While in theory every XPages app can be changed via stylesheet changes it is something not easy (e.g. not documented, not all stylesheet information within nsf, etc.). So the goal is to provide at least ...
Users should be able to create drafts of topics (not responses) so that they can continue later to write the topics before publishing them. There should be a view for the drafts of the current user and a list of all drafts for a moderator (or a general view where ...
End users should be able to send email notifications to certain users pointing to one specific topic or response.
Users should be able to define who to send this notification to:
- All people with access to discussion database
- All people who have contributed to topic
- Subset ...
Users should be able to mark a new topic as 'ready to be approved' so that moderators can review topics before they are published.
Some customers might want to restrict the creation of new topics to always go through this approval workflow first. In this case there should be ...
It should be possible to see for all person names in the discussion to see whether they are online in Sametime (rich client and web). Plus it should be possible to start a chat by clicking on a person name.
This is related to profiles. There probably should be a ...
While on the web there are typically file upload controls where users browse to files, on the rich client it should additionally be possible just to drag and drop files to add them to a topic.
See here for more - idea 016.02
While in HTML basically all actions are rendered in the big rectangle on the rich client actions are typically integrated in the overall rich client user experience. It needs to be defined how consistent we want to be to web user interfaces vs. how much we want to use a ...
This extension is similar to this one ('user profiles from other NSFs') with the difference that profiles data is used from non NSFs. A good example is Connections profiles.
See here for more - idea 002
Customization (as opposed to extensibility) is done via declarative changes. More options than in 851 (e.g. company logo page footer) should provided.
See here for more - idea 020.04
The full text search in 851 has some limitations. For example search results cannot be re-sorted.
Also there is no way to do parametric searches (e.g. search for topics with certain state).
See here for more - idea 017.03
Categories in discussions allow the categorization and filtering of topics to easier find interesting topics. There used to be user visible categories in the template and they still exist in the 851 rich client version but in the 85 web version they got lost. More precisely they got merged together ...
From Peter D Presnell:
<<I think it would be a cool feature to have the ability to save Sametime Chat transcripts directly to a Discussion database. Discussion often start in a discussion database and then move to Sametime or even start in Stametime and need to be ...
There need to be more options for admins to control what features can be used on how. For example they might want to turn off the rather expensive tags
Tags (turn on/off, which ones, who can create)
Categories (turn on/off, which ones, who can create)
All new ...
A new view should be provided with all topics that users have an interest in. This view however shouldn't be a static view that needs to be maintained manually (like My Favorites) but it should be more intelligent by using the users' interest profiles (see 004).
In 851 users can ...
Embed-able what's new controls should be made available for web applications and the rich client. This might or might not be the same impl. Similar to ideajam rectangle on OpenNTF homepage.
See here for more - idea 022
Would it be nice is you could add topics where it would display on selected dates ? user selectable by Profile that can see the Time and date FIELDS
With the 851 web user interface it is very hard to find interesting topics via view navigation. Part of this is a rather poor real estate management. There are also some inconsistencies to the normal Notes/Domino view navigation around expand/collapse.
See here for more - idea 017.02
The navigator needs to support hierarchical views and a collapse/expand function since several additional views (for topic states and custom views) should show up there as well.
See here for more - idea 019.01
Maybe the most typical extension to the discussion template is to add new fields to topics, e.g. a role field 'developer' or 'end user'.
This needs to be possible without touching the original design elements.
See here for more - idea 020.02
Moderators should be able to censor a topic so that it doesn't show up in any standard end user view anymore (e.g. all topics).
See here for more - idea 012.05