# Manage Palette 'dashboard'
**URL:** https://discourse.nodered.org/t/manage-palette-dashboard/95297
**Category:** Core Development
**Tags:** dashboard-2
**Created:** [10 February 2025 20:14 UTC](https://discourse.nodered.org/t/manage-palette-dashboard/95297 "2025-02-10T20:14:18Z")
**Posts on this page:** 20
**Page:** 1
### Author:  [@jbudd](https://discourse.nodered.org/u/jbudd)
#### Post date: [10 February 2025 20:14 UTC](https://discourse.nodered.org/t/manage-palette-dashboard/95297/1 "2025-02-10T20:14:18Z")
If I search in Manage Palette | Install for "dashboard" it shows me 10 results of which #1 is `node-red-dashboard`.
`@flowfuse/mode-red-dashboard` however, is not in the first 10 results.
In fact it's not in the `+110 more` results either, it's nowhere!
That's with default sort order - relevance.
Shouldn't node-red-dashboard get banished lower down the list and dashboard-2 somehow promoted?
---
### Author:  [@E1cid](https://discourse.nodered.org/u/E1cid)
#### Post date: [10 February 2025 21:27 UTC](https://discourse.nodered.org/t/manage-palette-dashboard/95297/2 "2025-02-10T21:27:26Z")
> [@jbudd](#):
>
> n fact it's not in the `+110 more` results either, it's nowhere!
It is number 23 for me.
> [@jbudd](#):
>
> Shouldn't node-red-dashboard get banished lower down the list and dashboard-2 somehow promoted?
No that could lead to some form of discrimination.
---
### Author:  [@jbudd](https://discourse.nodered.org/u/jbudd)
#### Post date: [10 February 2025 21:36 UTC](https://discourse.nodered.org/t/manage-palette-dashboard/95297/3 "2025-02-10T21:36:41Z")
Yes you are right, No 23.
Still, that's 22 places below where I feel it ought to show.
My search failed to find @flowfuse until I copied everything into vi!
> [@E1cid](#):
>
> some form of discrimination.
I don't understand what you are getting at here.
---
### Author:  [@E1cid](https://discourse.nodered.org/u/E1cid)
#### Post date: [10 February 2025 21:58 UTC](https://discourse.nodered.org/t/manage-palette-dashboard/95297/4 "2025-02-10T21:58:12Z")
> [@jbudd](#):
>
> I don't understand what you are getting at here.
Where would/should we stop with this idea. should we start shadow banning/deranking software that is old, not to our liking.
The search term matched well so it came up first. if I search @flowfuse, dashboard2 is number one.
---
### Author:  [@jbudd](https://discourse.nodered.org/u/jbudd)
#### Post date: [10 February 2025 22:33 UTC](https://discourse.nodered.org/t/manage-palette-dashboard/95297/5 "2025-02-10T22:33:03Z")
> [@E1cid](#):
>
> should we start deranking software that is old, not to our liking.
Node-red-dashboard is _deprecated_, and it does come up in _first place_.
> [@E1cid](#):
>
> if I search @flowfuse
I guess that a newcomer to Node-red, wanting a _dashboard_ solution, is more likely to search for "dashboard" than for "@flowfuse".
---
### Author:  [@E1cid](https://discourse.nodered.org/u/E1cid)
#### Post date: [10 February 2025 22:58 UTC](https://discourse.nodered.org/t/manage-palette-dashboard/95297/6 "2025-02-10T22:58:56Z")
> [@jbudd](#):
>
> dashboard is _deprecated_, and it does come up in _first place_.
As it would because it is the best match for the search term dashboard.
> [@jbudd](#):
>
> I guess that a newcomer to Node-red, wanting a _dashboard_ solution, is more likely to search for "dashboard" than for "@flowfuse".
As a newcomer I would hope you research the available dashboards, maybe look at the flow library and github, check when last updated, read some reviews etc.
I would not just install the first one in list without some form of due diligence.
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [11 February 2025 07:27 UTC](https://discourse.nodered.org/t/manage-palette-dashboard/95297/7 "2025-02-11T07:27:07Z")
Does anyone know what search algorithm is used?
It does seem reasonable that low rated or deprecated nodes should be lower in the results.
---
### Author:  [@GogoVega](https://discourse.nodered.org/u/GogoVega)
#### Post date: [11 February 2025 08:43 UTC](https://discourse.nodered.org/t/manage-palette-dashboard/95297/8 "2025-02-11T08:43:57Z")
A simple comparison with `indexOf` and `localeCompare` on package name and node types.
I've asked in the past to change this comparison to a more "real" algorithm based on many factors but I don't know if Nick has had time to look at it.
---
### Author:  [@joepavitt](https://discourse.nodered.org/u/joepavitt)
#### Post date: [11 February 2025 09:43 UTC](https://discourse.nodered.org/t/manage-palette-dashboard/95297/9 "2025-02-11T09:43:21Z")
> I've asked in the past to change this comparison to a more "real" algorithm based on many factors but I don't know if Nick has had time to look at it.
It's very much this. Internally within FlowFuse we've discussed the same. The ability to mark packages as deprecated is important addition I think, and is not discriminatory.
Search order is then quite tricky, some level of "popularity" should be considered based on all matches that get a string match. The popularity metric is the tricky part.
---
### Author:  [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)
#### Post date: [11 February 2025 09:49 UTC](https://discourse.nodered.org/t/manage-palette-dashboard/95297/10 "2025-02-11T09:49:08Z")
Same here.
And I agree, it is "relevance" sorted by default - not sure quite what the calculation for that is. It is #19 I think for alphabetically sorted. It is #9 if sorted by date.
---
### Author:  [@E1cid](https://discourse.nodered.org/u/E1cid)
#### Post date: [11 February 2025 09:49 UTC](https://discourse.nodered.org/t/manage-palette-dashboard/95297/11 "2025-02-11T09:49:31Z")
> [@joepavitt](#):
>
> It's very much this. Internally within FlowFuse we've discussed the same. The ability to mark packages as deprecated is important addition I think, and is not discriminatory.
There should be a flag in library to mark a package deprecated, and that flag should show in the palette as a to notify, but this should not deranked a node,. deranking/order should be about downloads and last updated, this way a deprecated node would move down naturally over time.
There should also be a flag about known security vulnerabilities to.
---
### Author:  [@joepavitt](https://discourse.nodered.org/u/joepavitt)
#### Post date: [11 February 2025 10:02 UTC](https://discourse.nodered.org/t/manage-palette-dashboard/95297/12 "2025-02-11T10:02:46Z")
> [@E1cid](#):
>
> There should be a flag in library to mark a package deprecated, and that flag should show in the palette as a to notify, but this should not deranked a node,.
Yes, I completely agree.
> [@E1cid](#):
>
> deranking/order should be about downloads and last updated,
Last updated can be misleading though. I published a satellites node about 6 years ago, haven't need to update it since because it's still functional.
---
### Author:  [@E1cid](https://discourse.nodered.org/u/E1cid)
#### Post date: [11 February 2025 10:10 UTC](https://discourse.nodered.org/t/manage-palette-dashboard/95297/13 "2025-02-11T10:10:40Z")
> [@joepavitt](#):
>
> Last updated can be misleading though. I published a satellites node about 6 years ago, haven't need to update it since because it's still functional.
I would not worry by recently updated you are still number 1 (2 years 9 months ago). Or number 2, note there are only 2.
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [11 February 2025 10:47 UTC](https://discourse.nodered.org/t/manage-palette-dashboard/95297/14 "2025-02-11T10:47:43Z")
> [@joepavitt](#):
>
> Last updated can be misleading
Absolutely, one of mine has not been updated in 8 years but continues to work and is used.
---
### Author:  [@E1cid](https://discourse.nodered.org/u/E1cid)
#### Post date: [11 February 2025 11:18 UTC](https://discourse.nodered.org/t/manage-palette-dashboard/95297/15 "2025-02-11T11:18:04Z")
If you show the node some love it would rank higher in the search results. Node developers who want a better ranking would be incentified to update/add features.
I don't see any other way of ranking except name, download and last updated.
What other wasy of ranking do others see?
---
### Author:  [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)
#### Post date: [11 February 2025 11:29 UTC](https://discourse.nodered.org/t/manage-palette-dashboard/95297/16 "2025-02-11T11:29:35Z")
One thing I have just raised is that there are entries in the catalogue that no longer have a corresponding entry in npm. So there appears to be some tidying needed.
---
### Author:  [@GogoVega](https://discourse.nodered.org/u/GogoVega)
#### Post date: [11 February 2025 11:41 UTC](https://discourse.nodered.org/t/manage-palette-dashboard/95297/17 "2025-02-11T11:41:23Z")
I had these points:
> [@FR: Catalog: Limit developer frustration about sorting packages](https://discourse.nodered.org/t/fr-catalog-limit-developer-frustration-about-sorting-packages/83431/9):
>
> Maintenance Releases frequency Commits frequency Has few issues open Quality Version \> 1.0.0 Engine (Node) Is deprecated version? Outdated dependencies? Few dependencies? Has Readme Has License Popularity Downloads Count Downloads Constant? Stars Count Forks Count Contributors Count What about those in Scorecard?
Other related discussion:
> [@Node catalog purge](https://discourse.nodered.org/t/node-catalog-purge/92831):
>
> In your one post Nick you state you are looking to group nodes for easy searching. Yeah! Has any thought been given to purging the catalog? There are nodes that haven't been touched for years and while some may work there are many that don't. This may be, no, I'm sure will be a contentious subject but maybe a purge of old nodes should be adopted? It's frustrating enough to search for one but after finding one and it doesn't work and hasn't been touched in years.... Yes, you can look at the date…
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [11 February 2025 11:49 UTC](https://discourse.nodered.org/t/manage-palette-dashboard/95297/18 "2025-02-11T11:49:01Z")
> [@E1cid](#):
>
> If you show the node some love it would rank higher in the search results. Node developers who want a better ranking would be incentified to update/add features.
It does not need any additional features. It does what it is supposed to do.
> [@E1cid](#):
>
> I don't see any other way of ranking except name, download and last updated.
The presence of a github repository that allows issues to be submitted, and how many open issues there are might be helpful.
Also the number of stars in its rating.
---
### Author:  [@GogoVega](https://discourse.nodered.org/u/GogoVega)
#### Post date: [11 February 2025 11:52 UTC](https://discourse.nodered.org/t/manage-palette-dashboard/95297/19 "2025-02-11T11:52:32Z")
> [@Colin](#):
>
> It does not need any additional features. It does what it is supposed to do.
I think he was referring to the fact that some developers are just doing the bare minimum (what makes UI poor). There are also nodes that still haven't migrated to the config node.
---
### Author:  [@E1cid](https://discourse.nodered.org/u/E1cid)
#### Post date: [11 February 2025 12:02 UTC](https://discourse.nodered.org/t/manage-palette-dashboard/95297/20 "2025-02-11T12:02:30Z")
> [@Colin](#):
>
> Also the number of stars in its rating.
Not sure star rating is reliable also, as low usage nodes can have a five star, due to only one ranking and high downloads nodes can get more low star ratings due to not knowing how to use the node.
> [@Colin](#):
>
> The presence of a github repository that allows issues to be submitted
Do we count open issues? As dashboard 2 is at 350ish and dashboard 80ish
One last input
I think we should keep this as simple as possible and allow users to do their due diligence. Possibly an option to sort by download, update, rating and flags.
[Next page](https://discourse.nodered.org/t/manage-palette-dashboard/95297.md?page=2)