https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26977 --- Comment #2 from Rex Barkdoll <rex@nicic.gov> --- I understand, but I think what I'm asking for is to add more detailed recommendations to the documentation. Throughout my (short) experience with Koha, there's been what feels like disconnect between people who have been using Koha for a long time and people who are new to it, by that I mean people who just know where stuff is based on experience versus people looking for these things the first time. Admittedly, this is an anecdotal assertion based on my experience and what I've identified with in other users' posts on forums, but I feel like I have seen enough people with growing pains to leverage the point. I believe good documentation is written toward first-timers, and preferably is written in crayon with neon signs pointing the way. Working at a library which services technophobic users, most of our tutorials and guides are written so an elementary school kid could follow along. Even so, our advanced users appreciate that it's hard for them to miss anything and we've tried to over-document to clear up any vague parts before they become and issue. With Koha, I've had to go to multiple sources and 3rd-party documentation (like Koha geek) to get answers and tutorials to things that really should have been in the official documentation/manual (initial setup, importing a previous koha database, setting up cron tasks, tutorials on XSLR modifications, detailed guides on building reports, etc). What if Koha geek or other third-party resources go away one day? By no means should the documentation say "this is always where this file will be found," but you could say: "Depending on your installation method and OS, this files will most likely be found in /usr/share/koha/... OR in /etc/koha/... You can also perform a simple find search if they are not located in either of these directories." I'm also not asking for the monumental task of changing every URL, just adding a recommended location at the top of each section to point someone in the right direction. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26977 Katrin Fischer <katrin.fischer@bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |Needs documenting -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26977 David Cook <dcook@prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dcook@prosentient.com.au --- Comment #4 from David Cook <dcook@prosentient.com.au> --- Looking at https://koha-community.org/manual/latest/en/html/cron_jobs.html I see the following: "The locations below assume a development install which puts the crons in misc/, if you have a standard install you may want to look in bin/ for these files if you cannot find them in misc/" That could probably be tweaked to something like: "The locations in the documentation assume a development install where files are found in misc/ relative to the git root checkout. If you have installed using Debian packages or the standard install from source, you will want to look for files in /usr/share/koha/bin/. Other locations are possible with other installation methods." -- FYI for anyone with shell access using Debian packages, the following command is an easy way to find files installed by a Debian package: dpkg -L koha-common This provides a comprehensive listing of the files installed by the koha-common package. You can then easily find the file from there. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26977 Caroline Cyr La Rose <caroline.cyr-la-rose@inlibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs documenting |RESOLVED Documentation| |Caroline Cyr La Rose contact| | Resolution|--- |FIXED Documentation| |https://gitlab.com/koha-com submission| |munity/koha-manual/-/merge_ | |requests/700 --- Comment #6 from Caroline Cyr La Rose <caroline.cyr-la-rose@inlibro.com> --- Thanks David! I used your sentence practically as is. I only added Rex's note about using find. Feel free to reopen if it's still not clear, providing what needs to be changed. Caroline -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.