-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tag usage statistics #16
Comments
Each of these stats could be stored in its own file of persisted/replicated storage a.k.a.
See ARK-Builders/arklib-android#86 for concrete task about 2 and 4. |
ARK-Builders/ARK-Navigator#310 implements all 4 of the statistics. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For usage in tag selectors, it would be convenient to have tag stats: kind of metrics, which we can't count just by looking at resources in corresponding collections. Stats can be, e.g. amount of times tag was used or how recently tag was used.
These stats can be kept in Room, but this way stats from one device will not transport to another. Sometimes it might be preferred to treat devices differently though (e.g. a phone and a laptop could be used for different workflows). In terms of performance, we will not have penalty if we will write stats into tags storage (we write to it every time we tag a resource anyway). We can allow a user to set her preferences regarding to persist stats or not.
Statistics to consider:
Here, 1 and 3 are query stats and 2 and 4 are label stats, but I am not sure that this separation of stats is really useful. It is based on the fact that we have query tag selector and label tag selector, they are similar but not the same and we can sort tags in them basing on different stats. On other hand, we can simplify 4 stats into just 2.
About 3 and 4: "how recently" doesn't necessarily mean "time". We can implement these stats using timestamps, but we need to sort tags by them, so might be more practical to just keep stack and put a tag on top of it when it is used.
The text was updated successfully, but these errors were encountered: