Hi Charles, first of all: welcome! I am slightly worried about reading 3.2 in your email, as this is a very old and outdated version of Koha by now. Can you explain a bit more on how you installed Koha and which version exactly? For testing right now I'd recommend using the latest 18.11 version. One easy way to get a test system running (not for use in production) is using a kohadevbox: https://gitlab.com/koha-community/kohadevbox Also usually it's good to start with the installation instructions provided on the wiki and linked from our home page as those are the most up to date. I've just checked: 242 is not indexed by default in newer versions either. But it would not be a hard thing to do. If you feel up for it, filing a bug on Bugzilla would be great. Someone might be able to pick it up and help you along with it. Note: you will be able to search it as keyword now already as you can always search the whole record. Hope this helps, Katrin On 09.06.19 04:46, Charles Kelley wrote:
Greetings, everyone!
First and foremost, I wish to thank everyone for help in installing Koha.
Second, I forgot a few times to copy the title line ("subject") from various posts to this discussion email group. I'm sorry for doing so. I'll make the effort to be more diligent in the future.
I have recently moved to another library and I find myself tasked with implementing Koha here. This is the first time I have had to do something like this. While I was the system administrator for my old library's InnoPAC/Millennium, it amounted to changing preferences, options, settings, etc., installing system updates, and occasionally teaching the staff on new and updated features. I did change the hard drives a few times, but by and large InnoPAC/Millennium ran itself. Network issues were handled by IT staff both internal to the library and external to it.
To experiment with Koha, I found Josh Hertel's testlibrary Koha 3.2 Debian Jessie. Because my new library doesn't yet have permission to implement Koha on the system, we set it up on a demonstration machine. It's a Mac laptop running Mojave, and Koha runs in emulation in VirtualBox Debian 9.9.
I recently discovered that my new library uses MARC tag 242 (title translation) extensively. Koha doesn't index 242 automatically from what I can tell. I found instructions on how to add a tag to the indexing, but I cannot add 242 in Hertel's test library because he apparently locked out access to the underlying Debian OS. I could convert tag 242 to 740 through MarcEdit and solve the problem that way. But I feel compelled to preserve 242 given the environment. And it would address another underlying problem, to wit: local library decisions on what (additional) tags to index and what tags not to index in cases like mine. I don't want to get into a full discussion of the underlying philosophical problem; just the immediate problem of indexing 242 will do for the present.
So I have to connect to my implementation of Koha and begin using it henceforth.
But, while I can connect to Hertel's test library, I cannot connect to my implementation of Koha. I have followed his installation instructions and the installation of several videos presented on YouTube (with adjustment for updates and upgrades in Debian, adjustments for Ubuntu vs. Debian, differences between Parallels and VirtualBox, etc.). The settings look the same to me. But clearly I missed something. Can anyone suggest what I missed?
Thanks for your help, all.