| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| hashtagvalues [2025/06/15 19:11] – admin | hashtagvalues [2025/06/15 19:43] (current) – admin |
|---|
| |
| **Hashtags**\\ | **Hashtags**\\ |
| What we propose is to keep one common reference file for the hashtags that you want to use in the office. One useful method is to invent and get the office to agree upon the hashtags for the various kinds of work that is being done in the office. | 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.. |
| |
| For example: In an architect's office, people are doing #admin work, #clientmeetings, #accounts, #gfcdocs, #redlining, #designing, #rendering ... so that office agrees upon the hashtags that should be used. Ideally, use only one word (i.e. without spaces) to define such hashtags. | For example: In an architect's office, people are doing #admin work, #clientmeetings, #accounts, #gfcdocs, #redlining, #designing, #rendering ... so that office agrees upon the hashtags that should be used. Ideally, use only one word (i.e. without spaces) to define such hashtags. |
| |
| That means the person has done 5.5 hours worth of admin work and 0.5 hour worth of accounts work and 6.5 hours of redlining work. The owner or boss or manager of the office can then suitably reward that person for the work that was done (and can have different previously-agreed upon rates for each of those works) | That means the person has done 5.5 hours worth of admin work and 0.5 hour worth of accounts work and 6.5 hours of redlining work. The owner or boss or manager of the office can then suitably reward that person for the work that was done (and can have different previously-agreed upon rates for each of those works) |
| | |
| | |
| | ====Summary of how to use Hashtag values==== |
| | |
| | Here is a summary, in case you don't want to read the entire topic. |
| | |
| | * Use agreed office hashtags like #admin, #design etc. |
| | * Add numerical values for time, effort, or points: e.g., #admin:3.5 |
| | * These tags can be retrieved via the Hashtag Analysis tool as a CSV |
| | * You control what the value means: hours, % effort, money, etc. |
| | * CSV analysis is flexible — per project, per person, or office-wide. |
| | |
| |
| **Flexible and //loosely-coupled//**\\ | **Flexible and //loosely-coupled//**\\ |
| This is extremely useful in small/medium size offices where people may be asked to do //different kinds// of work. One source of anguish that employees often have is that they don't get recognized (aka paid) for the hard-work they put in different types of work they did for the office. Such hashtag values can be inserted in appraisals between an employee and his/her manger or owner as comments into the Kanban system. | The concept of //hashtag values// is extremely useful in small/medium size offices where people may be asked to do //different kinds// of work. One source of anguish that employees often have is that they don't get recognized (aka paid) for the hard-work they put in different types of work they did for the office. Such hashtag values can be inserted in appraisals between an employee and his/her manger or owner as comments into the Kanban system. |
| |
| This is a //loosely-coupled// system. Which means, we do not insist that you //must// use this. Maybe you may use this with other variations. For e.g. instead of giving the values as number of hours spent, it could be percentages, reward points or actual money or some kind of //gamification// points... that's all up to that office which uses //Git Winch//. | This is a //loosely-coupled// system. Which means, we do not insist that you //must// use this. Maybe you may use this with other variations. For e.g. instead of giving the values as number of hours spent, it could be percentages, reward points or actual money or some kind of //gamification// points... that's all up to that office which uses //Git Winch//. |
| **How to do Hashtag Value analysis**\\ | **How to do Hashtag Value analysis**\\ |
| When you click on the 'Hashtag Analysis' button in the //Manage// page, //Git Winch// fill first ask you to load a text file which contains the hashtags you want to retrieve. 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. | When you click on the 'Hashtag Analysis' button in the //Manage// page, //Git Winch// fill first ask you to load a text file which contains the hashtags you want to retrieve. 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. |
| | |
| accounts,admin,redlining | accounts,admin,redlining |
| | |
| 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/edited using Notepad,Notepad++ and other such //text-editors//. Do NOT use word-processors such as Microsoft Word, etc. | 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/edited using Notepad,Notepad++ and other such //text-editors//. Do NOT use word-processors such as Microsoft Word, etc. |
| |
| So this is the file that you need to load when clicked the "Hashtag Analysis" button in the //Manage// page. | So this is the file that you need to load when clicked the "Hashtag Analysis" button in the //Manage// page. |
| |
| Then it will extract those hashtag-values and places 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. //Git Winch// will only search in Kanban groups and repositories where you are the owner. |
| | |
| | Internally, //Git Winch// will check the backend coordination server's database and note down which all Kanban cards where you have commented, and all repository file-notes with your notes too. (Note: As stated above, I am repeating: only for the Kanban groups and Repositories that you had created). The first line of such comments and/or notes would be examined for comma-separated //hashtag values//. |
| | |
| | It will find out the person who created the Kanban card. Or, in case of Repository file-notes; it will note down all members who had written notes for that particular file. |
| | |
| | For example; on one comment for a particular Kanban card you may have written the following comment |
| | |
| | #admin:4.5 |
| | |
| | In another file-note you had written the following: |
| | |
| | #redlining:8;admin:9.5 |
| | |
| | As you can see; you did not write just #admin or just #redlining. Instead you also gave a value for those hashtags. |
| |
| | 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 values. But it is the teacher (i.e. the creator of the Kanban group or Repository) who wrote the hashtag value as a comment or file-note. |
| |
| **Who can do this analysis**\\ | Internally, //Git Winch// will place the values of 4.5 and 9.5 for //#admin//. And 8 would be the value for //#redlining//. Of course, the person to whom this value would be given would be based on whose Kanban card was being worked on. In case, of //file notes//, the values would be attributed to all those wh had put their own notes onthat file. |
| Anyone can invoke the Hashtag analysis. 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. | |
| |
| Internally, //Git Winch// will check the backend coordination server's database and note down which all Kanban cards have your comments, and which all repository file notes too. (Note: As stated above, only for the Kanban groups and Repositories that you had created). 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. Accordingly, the CSV file is generated. | After processing those hashtag values, the CSV file is generated. |
| |
| Here is the [[csvfile?do=export_xhtml|Hashtag CSV File Format]], which will give you more details on how to read the generated CSV. | Here is the [[csvfile?do=export_xhtml|Hashtag CSV File Format]], which will give you more details on how to read the generated CSV. |