This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
hashtagvalues [2025/06/15 19:37] – admin | hashtagvalues [2025/09/21 16:01] (current) – admin | ||
---|---|---|---|
Line 1: | Line 1: | ||
======Hashtag Value Analysis====== | ======Hashtag Value Analysis====== | ||
+ | **Introduction**\\ | ||
+ | This is a special feature of //Git Winch// that can be used in multiple-ways in any office. The core reason for using this feature is to do assessment of work. An owner or manager would often be keen to know and award marks for the work being done in the office. Usually, this is done in the Kanban groups. But you can also use the same approach for assessing the creation of various files in the office too. | ||
+ | |||
+ | The central concept that we work with and further expand is called "// | ||
+ | |||
+ | **Hashtags**\\ | ||
You must have heard of // | You must have heard of // | ||
Line 9: | Line 15: | ||
To avoid that, what many do is to tag the same content with // | To avoid that, what many do is to tag the same content with // | ||
- | **Hashtags**\\ | + | **Uniform, Common |
What we propose is to keep one common reference file for the hashtags that you want to use in the office. To avoid confusion, your office can agree on a common set of hashtags for different types of work.. | What we propose is to keep one common reference file for the hashtags that you want to use in the office. To avoid confusion, your office can agree on a common set of hashtags for different types of work.. | ||
Line 44: | Line 50: | ||
But if you do use this method (in whatever variations) our system can collect these hashtag-values and put give them as a CSV file to you. Then you can choose how to use that CSV file as per your office policies. | But if you do use this method (in whatever variations) our system can collect these hashtag-values and put give them as a CSV file to you. Then you can choose how to use that CSV file as per your office policies. | ||
- | **How to do Hashtag Value analysis**\\ | + | =====How to do Hashtag Value analysis===== |
- | When you click on the ' | + | When you click on the ' |
+ | |||
+ | For example; if you want to find out Hashtag values for the following hashtags: #admin, #accounts, #redlining enter this line into a text file and save that. | ||
| | ||
- | If you notice, there are no # character there, and each hashtag is separated from the next by a comma. Do not use carriage returns. It is a simple text file, which can be created/ | + | If you notice, there are no //#// character |
+ | |||
+ | Do not use carriage returns. It is a simple text file, which can be created/ | ||
+ | |||
+ | So this is the reference file that you need to load when clicked the " | ||
+ | |||
+ | **NOTE:**\\ | ||
+ | The above file only lists the // | ||
+ | |||
+ | For e.g. Though in the above file, the office had listed // | ||
+ | |||
+ | The // | ||
- | So this is the file that you need to load when clicked the " | ||
Then //Git Winch// will extract those hashtag-values and place them into a CSV file. You can then further work on that CSV file using a spreadsheet application such as Excel, and complete the analysis. | Then //Git Winch// will extract those hashtag-values and place them into a CSV file. You can then further work on that CSV file using a spreadsheet application such as Excel, and complete the analysis. | ||
+ | =====Who can do this analysis? | ||
+ | |||
+ | Anyone can invoke the Hashtag analysis. However; internally, //Git Winch// will assume that you are the owner of some //Kanban Group// in the web-app, and also owner of some repositories too. If you are not an owner of either, the generated CSV file will be empty. | ||
- | **Who can do this analysis**\\ | + | **//Git Winch// will only search in Kanban |
- | Anyone can invoke the Hashtag analysis. Internally, | + | |
- | Internally, //Git Winch// will check the backend coordination server' | + | Internally, //Git Winch// will check the backend coordination server' |
- | It will find out who else was the one who created the Kanban card. Or, in case of Repository file-notes; who else had written notes for that particular file. The first line of such comments and/or notes would be examined for comma-separated //hashtag values//. | + | It will find out the person |
- | For example; on one comment for a particular Kanban card you wrote the following comment | + | For example; on one comment for a particular Kanban card you may have written |
# | # | ||
- | In another file-note you had written the following | + | In another file-note you had written the following: |
# | # | ||
- | As you can see; you did not write just #admin or just #redlining. Instead you also gave a value for those hashtags. | + | As you can see; you did not write just #admin or just #redlining. Instead you also gave a value for those hashtags. |
- | Internally, //Git Winch// will place the values | + | This is quite similar to a teacher in a classroom giving marks for various subjects to students in the class. So the students (aka other members) themselves do not write their own hashtag |
- | After processing those hashtag | + | Internally, //Git Winch// will place the values |
+ | =====Whose hashtag values are to be used?===== | ||
+ | ONLY the hashtag values of // | ||
+ | |||
+ | After processing those hashtag values, the CSV file is generated. You will get a message stating that the CSV File data is now available, and it will then open a file save dialog. | ||
+ | |||
+ | =====Format===== | ||
Here is the [[csvfile? | Here is the [[csvfile? | ||
+ | =====Additional Info===== | ||
+ | |||
+ | **Graphs**\\ | ||
+ | You can easily visualize the CSV data graphically using this free tool: https:// | ||
**Hierarchical System**\\ | **Hierarchical System**\\ |