Hi all, Im with the others - I would rather go for option 1 with the suggestions of Grainier using a small SP Icon (maybe top left part). Otherwise the name is very long as well.
Patrick > Am 30.11.2020 um 02:13 schrieb Grainier Perera <[email protected]>: > > Hi all, > > I think we shouldn't use `Internal` prefix (which might give a wrong idea > to the end-user). So, I'm also in favour of option 3, or option 1 with > icons to clearly show that those are internal/special components. > > Grainier Perera. > > > On Mon, 30 Nov 2020 at 03:25, Dominik Riemer <[email protected]> wrote: > >> Hi Philipp, >> >> I think it's a good idea to rename the sinks according to your optoin 3. >> I'd also suggest to modify the icons so that it is clear that these sinks >> affect internal components (e.g., by adding a small StreamPipes logo along >> with the name of the sink). >> >> On 2020/11/29 18:19:13, Philipp Zehnder <[email protected]> wrote: >>> Hi, >>> >>> Patrick has already created a page with improvements in Confluence for >> bigger changes. >>> I think a quick improvement would be to standardize some of the names. >>> >>> Currently we have three data sinks that we use internally called: >> “Notification”, “Data Lake”, and “Dashboard Sink”. >>> The data of those sinks can be viewed by selecting “Notifications”, >> “Data Explorer”, “Dashboard” on the left. >>> There we also use different Icons than for the sink icons. >>> >>> My suggestion would be to harmonize the naming and the icons. >>> >>> * Alternative 1: “Notification”, “Data Explorer”, and “Live Dashboard” >>> * Alternative 2: “Internal Notification”, “Internal Data Explorer”, and >> “Internal Live Dashboard” >>> * Alternative 3: “StreamPipes Notification”, “StreamPipes Data >> Explorer”, and “StreamPipes Live Dashboard” >>> * Alternative 4: “Notification”, “Historic Data Explorer”, and “Live >> Dashboard” >>> >>> What is your opinion? >>> >>> Philipp >>
