nextcloud / nextcloud/user_usage_report

Information retrieved seems to be confusing

Open
#59 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

1. to develop enhancement
Dominant language
PHP
Stars
45
Forks
12
Avg merge
13h 25m
Merged PRs (30d)
19

Description

This is not a bug but more of a lack of documentation issue I suppose. Can anyone shed some light on how the data for the last 4 columns in each row is calculated. Have a test setup deployed with some test users and files. Am getting output that is not at all intuitive. The output in the report is not consistent with the information available from the Web UI for each user

For eg.
A user with no file in the web panel is shown in the report as having 3 files. On adding a single file in the web ui, the file count is increased to 9 in the report.
The count of shares is also different than what is visible in the web ui.
Similarly the case of new reads/views.
It would be great if anyone could document this. as we are looking to generate a monthly report for one of our customer.

Thanks

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing how the report calculates its last four columns, then compare those values with the Web UI's file, share, and read/view information for the test users described. Done means documenting each calculation clearly and explaining the reported differences from the Web UI.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
analytics, documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.