mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-02-14 03:09:39 +03:00
[Feature Request]: Admin dashboard with summaries #2607
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @iTymz on GitHub (Jan 27, 2022).
Describe the feature you'd like
Hi!
I'm thinking about the dashboard that shows the count of pages, books, shelves is already in BookStack created.
It may also contain a graph that will show the variability of this data over time.
Describe the benefits this feature would bring to BookStack users
Transparency for administrators regarding the current amount of information in the BookStack.
Additional context
No response
@ssddanbrown commented on GitHub (Jan 27, 2022):
Thanks for the request @iTymz.
The trouble with getting into the analytics/data side is that it'd be very open ended since interpretations, use-cases and viewpoints can vary drastically. Before we delved down this path I think we'd need some thought into the bounds of scope.
The provided benefit of "Transparency" is very broad and could justify us having to dump all information possible. In addition, the case of "Transparency" is weaker for a self-hosted platform where this information could be fetched directly from the database.
I think we'd need to instead think about:
@iTymz commented on GitHub (Jan 27, 2022):
Thank you for your answer @ssddanbrown :)
I think about how many pages, chapters, shelves are created already in BookStack. The place I can check it per user right now is for example https://demo.bookstackapp.com/user/admin (Created Content), but there is no place that shows the summary. Created by all users. There is also a possibility to show the capacity of attachments and the types count.
For example when you want to migrate somewhere, how much content do you have to move, or what is the capacity of attachments. I guess there are more benefits, but t's depends on the situation.
@ssddanbrown commented on GitHub (Jan 27, 2022):
Thanks for the extra info @iTymz.
Okay, so you primarily want total counts. Is there a specific question being answered by seeing these totals? Or is that just for the purposes of potential migration as per your other answer?
Is this a specific statistic you currently have a need for? Or is this just an example?
We'd need to go to some specific lengths to handle showing this, either by adding functionality to track attachment sizes on upload or by handling the potentially slow process of checking attachment/upload sizes.
Sorry if I'm coming across quite pedantic, and I can understand if you're just raising this as something that could be interesting/useful to admins, but it's important to our long-term maintainability and sustainability that we focus on widespread needs and use-cases rather than things that could theoretically be useful.
@iTymz commented on GitHub (Jan 27, 2022):
Right now is for a potential answer in case of migration. I've checked directly in the DB, but I guess for the future it will be better to create some dashboard with summaries like this. It will save time to check it by creating queries, connecting to the DB, and other stuff related to that. This Feature Request can wait, it's not something critical ;)
If measuring the capacity of attachments is costs from the process point of view it can be skipped.