nyuuzyou/wikis huggingface dataset:
Import biblios oaipmh endpoint RFC

== Bugs ==
* REST API: create endpoint for importing OAI-PMH records from external OAI-PMH clients (NEW)
== Actions and routes ==
General proposed routes. 
Description 	Action	Proposed path
Import an OAI-PMH XML record as a biblio record	POST 	/import/oaipmh/biblios
=== Importing an OAI-PMH XML record as a biblio record ===
OAI-PMH is a protocol which only uses XML, so we have to submit OAI-PMH XML records to the API.
The API endpoint will do add/update/delete as required based on the information in the OAI-PMH XML record and how it corresponds to data saved in the Koha database.
== Comments ==
=== tcohen ===
* I'd prefer /import/biblios/oai_pmh, because we could want another import methods, and I'd prefer to group them by type (i.e. biblios in this case).
* OAI-PMH might support different data formats, do you have plans for that? The /biblios endpoint uses the Accept header to specify that, maybe Content-type is to play a role here. Even if we don't still support other format than MARCXML at this point.
=== dcook ===
Only noticing tcohen's comments a couple years later...
* I'd be fine with /import/biblios/oai_pmh
* At the plugin level, it accepts text/xml Content-type since the inbound data is OAI-PMH data which encapsulates MARCXML so can't really use the Content-type here to be more specific
* Data that isn't MARCXML is silently ignored at the moment. I don't have any plans to support anything other than MARCXML at this point. However, since OAI-PMH is XML, we could always provide a list of acceptable XML namespaces to Koha, and it could judge based on that
Category:RFCs
Importing MARC from LibraryThing to Koha

=Work in progress!!=
LibraryThing MARC Export
==Chat on the toppic==
[09:25] 	nengard	yesterday i exported my librarything collection and imported it to koha!! :)
[09:26] 	nengard	now my test system has my real library
[09:26] 	oleonard	Does it export items too?
[09:26] 	nengard	no
[09:26] 	nengard	I had a few steps:
[09:26] 	nengard	1. export from LT http://www.librarything.com/more/export-marc
[09:26] 	nengard	2. import to koha
[09:26] 	nengard	3. export from koha
[09:26] 	nengard	4. open in marcedit
[09:26] 	nengard	5. add items
[09:26] 	nengard	6. clean original koha import
[09:27] 	nengard	7. rebuild zebra
[09:27] 	nengard	8. import marc file with items to koha
[09:27] 	nengard	The reason I did it that way was cause the LT file wouldn't open in marcedit cause of errors in the file that koha just ignored :)
[09:27] 	kf	cool!
[09:27] 	magnuse	nengard: what format did you export from LT? 
[09:27] 	nengard	I used the 001 as my barcode (since it's a fake system) and the 050ab as my call number
[09:27] 	kf	can you put that on the wiki somewhere?
[09:28] 	kf	I would love to try that sometim
[09:28] 	nengard	magnus the first one ... fuzzy i think
[09:28] 	nengard	kf sure can
[09:28] 	kf	is there a trick to add a lot of items at once?
[09:28] 	kf	wit marcedit?
[09:28] 	nengard	it's easy peasy
[09:28] 	nengard	you do add field and add a 952 with you $a, $b, $2, $y
[09:28] 	magnuse	having that on the wiki would be super cool! 
[09:28] 	nengard	and then you can do swap field data to pull the call number and barcode
[09:29] 	nengard	I'll gladly share
[09:29] 	nengard	it was a bit frustrating, so I'd love to help you all :) hehe
[09:29] 	magnuse	nengard++
[09:29] 	nengard	of course this only works for a not real library - otherwise you have to go in and add real barcodes to all of the items
Category:Obsolete
Improved batch capabilities RFC

== Improved batch capabilities ==
For 3.2, Howard County Library proposes adding the following batch capabilities to Koha.
=== Batch withdraw/discard ===
This functionality would provide staff with the ability to enter a "withdraw" or "discard" mode and scan in several barcodes at a time and have them withdrawn in a single step.
=> this one is included in 3.2. With item batch modification you can do that easily :
* enter item batch modification
* choose the changes you want to make (including setting "withdraw" status)
* scan barcodes or upload them (or upload itemnumbers)
* click OK, it's done
=== Batch update ===
This functionality would provide staff with the ability to search for a group of items with similar codes (library, item type, collection, shelving location, status), sort them by any item field and change the data automatically for each item.
Category:Abandoned_RFC
Improved granular permissions RFC

== Improved granular permissions ==
For 3.2, Howard County Library propose adding the ability to create roles, as well as, expand upon the existing koha permissions.
=== Roles ===
The creation of roles would allow a System Administrator to more easily manage individual staff permissions.
* Roles would consist of any number of certain specific permissions
* A system administrator would have the ability to view a list of Employees and assign roles to multiple staff members at a time
* Several example roles would be
** Cataloging-Advanced
*** View, add, edit, delete authorities
*** View, add, edit, delete bibs
*** View, add, edit, delete items
*** Import bibs and authorities
*** Merge bibs
*** Do global authority updates
** Cataloging-Basic
*** View authorities
*** View bibs
*** View, add, edit, delete items
=== Additional permissions ===
In addition to the permissions that currently exist in Koha, and the ones proposed by LibLime, it would be helpful to see the following permissions available.
* Under LibLime's "for hold requests" add the ability to change the priority of existing holds
* Acquisitions
* Distinguish between running of existing reports vs. creation of new reports
* Have separate permissions for view, add, edit, and delete bibs vs. a single permission for all four functions
* Have separate permissions for view, add, edit, and delete items vs. a single permission for all four functions
* Under ability to edit items, make it possible for the library to specify which item fields can be edited for different levels of staff -- all fields for Cataloging staff, Lost and Shelving Location for Public Service staff, etc. 
* Ability for Circulation to create only fast add bibs and items without access to any other cataloging functions
=== Granular permissions work planned by LibLime ===
LibLime plans to add the following granular permissions
* view, add, edit, and delete for the following record types
** bibs
** items
** summary/holdings records
** authority records
** patron records
* for circulation transactions, the following distinctions
** check out
** check in
** change due date
** use dropbox mode
** circulation reports
* for patron fines:
** add fines/create manual invoice
** pay fines
** forgive fines
* for hold requests:
** view requests
** add requests
** edit requests
** delete requests
* for patron records:
** update PIN
** proxy patron maintenance
* for serials
** serials view
** serials add subscription
** serials edit subscription
** delete subscription
** serials check-in
** serials claiming
* a permission for each administration page
* a permission for access to 'Lists' in the staff interface.
Category:Abandoned_RFC
Improving searches on orders RFC

== RFC : Better searches on orders ==
This RFC would enhance acqui/histsearch.pl
One could reuse the filters for statistics as defined in RFC Improving statistics on acquisitions RFC. 
Id est:
* order date: beginning; end
* reception date: beginning; end
* library branch
* vendor
* librarian
* budget
* budget's authorized value #1
* budget's authorized value #2
These would be added to the existing search options (Title, Author, Vendor).
Category:Searching RFCs
Category:Acquisitions_RFCs
Category:Koha_3.2_RFCs
Category:3.2
Improving statistics on acquisitions RFC

== RFC : Better statistics about acquisitions ==
This RFC re-makes /report/acquisitions_stats.pl
The goal would be to be able to use this tool to follow acquisitions practices by librarians.
This RFC speculates that 2 authorized values fields will be added to a budget (see Refining the budgets hierarchy and informations RFC)
Two things are separated out: filters to select the information; definition of a visualization by the librarian.
Filters.
The following filters can be used (at once):
* order date : from date; to date
* reception date : from date; to date
* library branch
* localisation
* vendor
* librarian login
* budget
* budget authorized value #1
* budget authorized value #2
Visualization. Once the set of data is filtered, one can select informations to be shown in the report:
* all of the above (from order date to budget authorized value #2)
* short bibliographic informations
* call number
* location
* item type
* price
Koha still, as it does, lets the user choose between screen and csv output.
Category:Acquisitions_RFCs
Category:Reports_RFCs
Category:Koha_3.2_RFCs
Category:3.2
IndependentBranches v.s. multiple instances

So you have one server and multiple libraries. What is the best way to install and run Koha? 
The short answer is: "If you want different libraries with entirely different collections, policies, preferences, etc, then you need different instances".
Please note that whichever way you choose, the recommended mode of installation on Debian and Ubuntu is to use the packages for installation. 
There are three options:
== One instance ==
You run koha-create once, and then toggle the IndependentBranches syspref to suit your needs. 
=== Pros ===
* All libraries share the same bibliographic records, so a document only has to be catalogued once. 
=== Cons ===
* Librarians can see patrons from all libraries, unless IndependentBranches=ON
== Multiple instances ==
You run koha-create once for each library. This results in completely independant instances, where each instance has its own database, with bibliographic records, patrons, setting etc completely independent from all the other instances. 
=== Pros ===
* Each library can have its own circulation rules, systempreference settings, OPAC customizations etc
=== Cons ===
* There is no easy sharing of bibliographic records (well, they can be shared via Z39.50, of course)
Category:Installation_alternatives
Indian Pop Culture

If you don't edit me to properly reflect the facts, you'll have a Yank cultural imperialist's view of Indian pop culture.
==Music==
* Ainvayi Ainvayi (from Band Baaja Baaraat)
* Kehna Hi Kya (from Bombay) A.R. Rahman
* Rakkamma Kaiya Thattu (from Thalapathi) Ilaiyaraaja 
* San Sanana (from Asoka) Get your Bollywood Dance groove on
==Movies==
* Amal (IMDb) Can't get this through Netflix, but Oak liked it, so hey.
* Asoka (2001) (IMDb) "Total trash" according to kmkale. I included this because this is what I'd term a classic epic Bollywood film. It has Shah Rukh Khan, which of course makes it worth watching just there. :P
* Dhobi Ghat (Mumbai Diaries) (2010) (IMDb ) Definitely a chick flick. Sod off.
* Raajneeti (2010) (IMDb ) It's Washington, only it's not! Very violent, but watchable in a trainwreck sort of way.
* Slumdog Millionaire (2008) (IMDb ) Lots of hype round this one, and it's got 8 Oscars to show for it.
* Swades (2004) (IMDb ) Follows SRK once again as a "non returning Indian."
==Books==
The Mahabharata (from Brown)
==Web Links==
==Television Series==
* The Story of India (at PBS) If it's written by the British, it is surely neutral. ;)
* Gordon's Great Escape, Series 1 ( at BBC America) Watch it if only to see him brought to tears for having zero heat tolerance.
Category:KohaCon11
Instalando Koha 3.6 en Debian squeeze usando un servidor MySQL separado

La mayor parte de las instrucciones de Koha 3.6 en Debian Squeeze asume que instalara un servidor de base de datos MySQL local. Si va a utilizar un servidor de base de datos externo o independiente, es importante que usted no ejecute koha-create - create-db mylibrary. En su lugar, utilice los siguientes pasos:
* koha-create --request-db mylibrary
Salida de Ejemplo:
 root@web:~# koha-create --request-db mylibrary
 See mylibrary-db-request.txt for database creation request.
 Please forward it to the right person, and then run
 /usr/sbin/koha-create --populate-db mylibrary
 Thanks.
 Restarting web server: apache2 ... waiting .
 
* Show database request:
 root@web:~# cat mylibrary-db-request.txt
 Please create a MySQL database and user on mysql as follows:
 
 database name: koha_mylibrary
 database user: koha_mylibrary
 password: somerandomstring
 
 Thank you.
 
* Create MySQL database and set privileges. Use the database name, user name, and password specified in mylibrary-db-request.txt:
 ssh root@db
 # (Enter login credentials, if necessary.)
 root@db:~# mysql -u root -p
 Enter password: 
 Welcome to the MySQL monitor. Commands end with ; or \g.
 Your MySQL connection id is 20353
 Server version: 5.1.49-3 (Debian)
 
 Copyright (c) 2000, 2010, Oracle and/or its affiliates. All rights reserved.
 This software comes with ABSOLUTELY NO WARRANTY. This is free software,
 and you are welcome to modify and redistribute it under the GPL v2 license
 
 Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
 
 mysql> create database koha_mylibrary;
 Query OK, 1 row affected (0.00 sec)
 
 mysql> grant all privileges on koha_mylibrary.* to 'koha_mylibrary'@'web.my.domain' identified by 'somerandomstring';
 Query OK, 0 rows affected (0.17 sec)
 
 mysql> flush privileges;
 Query OK, 0 rows affected (0.12 sec)
 
 mysql> exit
 Bye
 root@db:~# 
* Poblando la base de datos:
 root@web:~# koha-create --populate-db mylibrary
 Koha instance is empty, no staff user created.
 Enabling site mylibrary.
 Run '/etc/init.d/apache2 reload' to activate new configuration!
 Restarting web server: apache2 ... waiting .
 Starting Zebra server for mylibrary
 root@web:~#
==Background==
Installing_Multiple_Instances_of_Koha#Koha_on_a_remote_DB has some relevant info, but if your database server is set up as per MySQL best practices (i.e. non-local root logins disabled), the instructions there will not work.
Category:Installation
Install-instructions on the wiki RFC

Problem: A lot of people are finding and using other install instructions than the ones that come with Koha in the INSTALL.* files (and are QA'ed etc) - either on the wiki or on websites external to the Koha project. 
Aim: Make it easier for people to find the official install instructions. 
==Proposal 1==
* Copy the official install instructions to the wiki and link to the originals on git
** Someone should be responsible for keeping them uptodate - User:Magnus might volunteer for that (and it might be automated with a small script)
** Make them read-only (for non-admins, or similar)
** Mark them clearly as "official"
* Mark all other install instructions on the wiki as "un-official" and link to the official ones
* Think about how we can make these pages more visible in search engines
Explain clearly how to get updates into the INSTALL.* files. We might want to have a separate page for each instruction that is open to editing, as a kind of draft version (and clearly marked as such), and a process for getting changes from those pages into the INSTALL.* files - with quality control.
==Proposal 2==
* Replace all install instructions on the wiki with links/embeds/redirects to the ones on http://git.koha-community.org HEAD
Reasoning: the INSTALL.* files must remain the official source because they are downloaded with every copy of Koha. Moving the official installation instructions to the wiki is not viable because it would cause severe inconvenience to any installers without live internet access at installation time and leave them vulnerable to any network service problems.
Comment: The original proposal says nothing about moving the INSTALL.* instructions to the wiki, just copying, to make them more visible. ;-) --Magnus 02:31, 11 January 2012 (EST)
Rebuttal: Then the proposal seems a bit null because most of the INSTALL.* instructions have been copied to or from the wiki at some point. Copying the rest would introduce more duplicate content which may get stale. Copying in order to manipulate search engine visibility (as proposed above) is allegedly penalised (see Google Webmaster Tools: Duplicate Content), so it could actually reduce its visibility. We should reuse work and not copy-paste it. If we want to improve its visibility, we should link to it more. The wiki should link to it and not copy-paste it. -- Mjr.towers.org.uk 13:15, 14 January 2012 (EST)
Category:Koha_Wiki_RFCs
Install Koha 3.6 on Debian squeeze using a separate MySQL server

Most of the instructions in Koha 3.6 on Debian Squeeze assume a local MySQL database server. If you intend to use an external or separate database server, it is important that you don't run koha-create --create-db mylibrary. Instead, use the following steps:
* koha-create --request-db mylibrary
Example output:
 root@web:~# koha-create --request-db mylibrary
 See mylibrary-db-request.txt for database creation request.
 Please forward it to the right person, and then run
 /usr/sbin/koha-create --populate-db mylibrary
 Thanks.
 Restarting web server: apache2 ... waiting .
 
* Show database request:
 root@web:~# cat mylibrary-db-request.txt
 Please create a MySQL database and user on mysql as follows:
 
 database name: koha_mylibrary
 database user: koha_mylibrary
 password: somerandomstring
 
 Thank you.
 
* Create MySQL database and set privileges. Use the database name, user name, and password specified in mylibrary-db-request.txt:
 ssh root@db
 # (Enter login credentials, if necessary.)
 root@db:~# mysql -u root -p
 Enter password: 
 Welcome to the MySQL monitor. Commands end with ; or \g.
 Your MySQL connection id is 20353
 Server version: 5.1.49-3 (Debian)
 
 Copyright (c) 2000, 2010, Oracle and/or its affiliates. All rights reserved.
 This software comes with ABSOLUTELY NO WARRANTY. This is free software,
 and you are welcome to modify and redistribute it under the GPL v2 license
 
 Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
 
 mysql> create database koha_mylibrary;
 Query OK, 1 row affected (0.00 sec)
 
 mysql> grant all privileges on koha_mylibrary.* to 'koha_mylibrary'@'web.my.domain' identified by 'somerandomstring';
 Query OK, 0 rows affected (0.17 sec)
 
 mysql> flush privileges;
 Query OK, 0 rows affected (0.12 sec)
 
 mysql> exit
 Bye
 root@db:~# 
* Populate the database:
 root@web:~# koha-create --populate-db mylibrary
 Koha instance is empty, no staff user created.
 Enabling site mylibrary.
 Run '/etc/init.d/apache2 reload' to activate new configuration!
 Restarting web server: apache2 ... waiting .
 Starting Zebra server for mylibrary
 root@web:~#
==Background==
Installing_Multiple_Instances_of_Koha#Koha_on_a_remote_DB has some relevant info, but if your database server is set up as per MySQL best practices (i.e. non-local root logins disabled), the instructions there will not work.
Category:Documentation
Category:Installation
Category:Debian_Packages
Category:Installation_alternatives
Category:Koha_Versions
Category:3.6
Install Koha via Chef and Vagrant

== Deploying Koha from git with Chef and Vagrant ==
* See http://halcyoncorsair.tumblr.com/post/31841813338/deploying-koha-from-git-with-chef for the original post.
I use Vagrant (http://vagrantup.com/) a lot to manage my VirtualBox virtual machines, so my first step was to get Koha up and running via Vagrant on an Ubuntu Precise LTS VM.  Koha has eleventy-billion perl dependencies, and having to install them every time I tore down and rebuilt the VM was really killing my buzz, so I took the vanilla precise64 base box from http://www.vagrantbox.es, installed all the perl dependencies along with a couple other useful tools, repackaged it, and put it in my Dropbox public folder: https://dl.dropbox.com/u/5595111/precise64-kohadeps.box.
Koha cookbook (https://github.com/halcyonCorsair/chef-koha) dependencies:
* apache2
* perl
* mysql
These cookbooks can all be found on the Opscode community site (http://community.opscode.com/) and on github (https://github.com/opscode-cookbooks).  I created a Berksfile (https://gist.github.com/3725346) the Berkshelf (http://berkshelf.com/) tool to fetch the cookbook dependencies for me. Then a Vagrantfile (https://gist.github.com/3725466) for my soon to be chef-controlled instance of koha. Then simply:
vagrant up
Once vagrant has booted up the VM and chef has finished provisioning the system, with any luck, a koha development copy will have been installed on the vm at /home/vagrant/koha, you will be able to access the opac via http://localhost:8000, and the web installer will be ready to go on http://localhost:8080.
 
Category:Git
Category:Documentation
Installation Documentation

== Koha Production Environments ==
These instructions can be used to set up a production installation of Koha:
=== Debian ===
*Koha on Debian 
=== Ubuntu ===
*Koha on Ubuntu 
== Koha Development Environment ==
If you plan on doing development for Koha, we provide a development environment that is set up with all the important tools using Docker. This is NOT to be used for production environments.
* koha-testing-docker
Category:Documentation
Category:Installation
Category:3.0
Category:3.10
Category:3.12
Category:3.14
Category:3.2
Category:3.4
Category:3.6
Category:3.8
Integrate Subscriptions with Acquisitions

== New Subscriptions ==
Currently subscriptions and acquisitions are distinct. We propose to integrate the two, the new process will be:
1. Create a partially or fully filled subscription record that is not active, this is for purposes of initiating an order
2. An optional purchase order approval process, see more details here: Purchase Approvals Process
3. Create an order using an inactive subscription record. If purchase approvals are turned on, only approved subscriptions records can be entered into the order basket
4. Upon receipt of the vendor invoice, make the subscription record active. This replaces the "accessioning" step used for books
5. An optional payment process, see more details here: Payments Process
== Renewals ==
Proposed process for renewals is:
1. If purchase approvals (see more details here: Purchase Approvals Process) are turned on, request for approval of subscription renewal
2. Create an order using for the current subscription. If approvals are turned on, only approved renewals can be entered into the order basket
3. Upon receipt of the vendor invoice, renew the subscription. 
4. An optional payment process, see more details here: Payments Process
Category:Acquisitions_RFCs
Category:Serials_RFCs
Category:Koha_3.4_RFCs