nyuuzyou/wikis huggingface dataset:
Kohacon23/Social

In good tradition, a page where you can note your arrivals/departures and other random information about things.
== Arrivals ==
* 2023-08-11 - Caroline (17:25 from Frankfurt)
* 2023-08-12 - Owen (mid-morning)
* 2023-08-12 - Gladys Cathelain (early evening from Lyon-Munich)
* 2023-08-12 - Laurence Rault (early evening from Toulouse - Munich)
* 2023-08-12 - Mengu (16:15 From Antalya)
* 2023-08-13 - Katrin (late evening from Zürich)
* 2023-08-13 - Robin (early evening from Schiphol)
* 2023-08-13 - Chris (late evening from Zurich)
* 2023-08-13 - Alex Buckley (mid-day from Copenhagen)
* 2023-08-13 - Paul Poulain (unknown time: we'll arrive from 1 week in the lake area)
* 2023-08-13 - Brendan (mid-morning)
* 2023-08-13 - Paul Derscheid (afternoon)
* 2023-08-13 - Magnus Enger (afternoon)
* 2023-08-13 - Sophie Meynieux (mid-day from Tallinn)
* 2023-08-13 - Nick Clemens (afternoon)
== Departures ==
* 2023-08-17 - Alex Buckley (early morning)
* 2023-08-18 - Paul Derscheid (afternoon)
* 2023-08-18 - Magnus Enger (afternoon)
* 2023-08-19 - Brendan (noontime)
* 2023-08-19 - Sophie Meynieux (mid-afternoon to Paris)
* 2023-08-20 - Katrin (early morning to Zürich)
* 2023-08-20 - Laurence Rault (early morning)
* 2023-08-20 - Gladys Cathelain (mid-day to Munich - Lyon)
* 2023-08-20 - Robin (early afternoon)
* 2023-08-20 - Chris (early morning)
* 2023-08-20 - Owen (morning)
* 2023-08-20 - Mengu (15:45 from Helsinki to Istanbul)
* 2023-08-21 - Paul Poulain (early morning)
* 2023-08-21 - Nick Clemens (early morning)
* 2023-08-25 - Caroline (evening)
Kohacon24

== Social ==
You can write your arrival and departure dates and other social things.
Arrival and departure
Name 	Arriving 	Departing 	Staying
Aleisha Amohia and partner Ben Paviour-Smith	Sat Sept 21, 20:59 (AC308) 	Sun Sept 29, 08:10 (AC581) 	Flat (1470 Rue Mackay)
Ed Veal 	Sun Sept. 22 	Fri Sept 27, 15:45 (AA) 	Doubletree by Hilton Downtown
George Williams 	Sun Sept 22, 12:00 (Delta) 	Sat Sept 28, 12:45 (Delta) 	Doubletree
Jason Robb 	Sun Sept 22, 16:31 (AA) 	Sat Sept 28, 7:29 (AA) 	Hotel10
Katrin Fischer 	Thu Sept 19, 15:00 (LX) 	Tue Oct 1, 16:40 (LX) 	Hôtel Saint-Laurent
Lisette Scheer 	Sun Sept 22, 15:48 (AC514) 	Sat Sept 28, 18:30 (AC515) 	Doubletree by Hilton Downtown
Matthias Meusburger 	Fri Sept 20th, 15:00 (AF346)	Sun Sept 29th, 17:00 (AF345)	Flat (210 rue Saint Jacques)
Paul Poulain 	Fri Sept 20th, 12:05 (AF344)	Sun Sept 29th, 23:00 (AF349)	Flat (210 rue Saint Jacques)
Sophie Meynieux 	Sat 21, 15:50 (TS 435) 	Sat 28, 22:40 (TS 434) 	Flat (210 rue Saint Jacques)
Spencer Smith 	Sun Sept 22, 14:50 (AA) 	Fri Sept 27, 15:45 (AA) 	Le Square Phillips Hotel (1193 R. du Square-Phillips)
Tomás Cohen Arazi 	Sun Sept 21, 16:12 (DL5128) 	Sat Sept 28, 8:35 (AC1650) 	Doubletree by Hilton Downtown
Owen Leonard 	Sun Sept 22, 20:20 	Sat Sept 28, 14:56 	Econo Lodge
Thibaud Guillot 	Sun Sept 22, 15:50 (TS435) 	Sat 28, 22:40 (TS 434) 	Hôtel Ambrose
Laurence Rault 	Fri Sept 20th, 13:35 (AC879)	Sun Sept 29th, 19:45 (AC878)	Flat (210 rue Saint Jacques)
Brendan Gallagher 	Saturday (driving) 	Saturday 28th (Driving) 	Doubletree by Hilton Downtown
Kohacon 2016: Who is arriving when

== Berlin Hackfest ==
* Katrin
* Mirko
* Chris C
* Alex S
* Robin (Arr: 22 May, Dep: 28 May)
==Arriving==
* May 28 09:25 Chris C Staying at Hotel Olympia
* May 28 morning Jonathan D. somewhere close to the uni
* May 28 16:30 Laurence Rault (BibLibre)
* May 28 ~20:00 Mirko Staying at Hotel Olympia
* May 28 ~20:20 Katrin, Robin, staying at Hotel Olympia
* May 28 ~23:30 Paul P. staying in an appt, with 7 other BibLibre staff (arriving on 28th or 29th)
* May 29 8:45 AM land Brendan Gallagher staying at Hotel Olympia 
* May 28 09:25 Chris C Staying at Hotel Olympia
* May 28 landing at 09:45 S. Bargioni Staying at Hotel Olympia
* May 29 13:30 Sonia B (Lyon3/KohaLa) Staying at Olympia Hotel
* May 29 ~15:20 Claire Staying at Hotel Olympia
* May 29th, landing at 20:05 Frédéric Demians
* May 29th 20:05 Julian Maurice, Alex Arnaud, Gaetan Boisson and Matthias Meusburger staying in an appt, with 7 other BibLibre staff
* May 31, ~09:00 Alex S
==Departing==
* June 02 take off 10:30 S. Bargioni
* June 05 take off 6:30 Paul P.
* June 05 8:00 am Gaetan Boisson
* June 05 940AM depart Brendan Gallagher
* June 05 ~10:00 Mirko
* June 05 ~10:25 Katrin
* June 05 ~10:25 Claire
* June 05 ~10:25 Laurence Rault
* June 05 14:05 Sonia B (Lyon3/KohaLa)
* June 05 15:30 Chris C
* June 5th, take-off at 20:45 Frédéric Demians
* June 5th 20:45 Julian Maurice, Alex Arnaud and Matthias Meusburger
* June 04, ~11:00 Alex S
* June 05 @ 14:10 Robin
Category:KohaCon16
Kohacon History

==History==
KohaCon has been held in the following places:
*2025: Wellington, New Zealand
*2024: Montreal, QC, Canada
*2023: Helsinki, Finland
*2022: Lawrence, KS, USA
*2021: Islamabad, Pakistan
* 2020: Wellington, New Zealand
* 2019: Dublin, Ireland
* 2018: Portland, OR, USA
* 2017: Makati City, Philippines
* 2016: Thessaloniki, Greece
* 2015: Ibadan, Nigeria
* 2014: Cordoba, Argentina
* 2013: Reno, Nevada, USA
* 2012: Edinburgh, Scotland, UK
* 2011: Thane, India
* 2010: Wellington, New Zealand
* 2009: Plano, Texas, USA
* 2006: Paris, France
Category:Koha_Conferences
Category:Participation
L2C2 Technologies

L2C2 Technologies was founded on April 12, 2004 by Indranil Das Gupta. 
"No bribes. No scams. Honest with a great sense of integrity. The only Koha service provider I'd currently trust in India." -- Mark Tompsett
Phone: +919830020971 / +919874580971
Email: indradg@l2c2.co.in 
Blog: http://blog.l2c2.co.in/
Website: http://www.l2c2.co.in/
Category:Support_Companies
Ldap testing

You can test LDAP functionality using:
https://www.forumsys.com/tutorials/integration-how-to/ldap/online-ldap-test-server/
Enter into your koha-conf.xml:
 <useldapserver>1</useldapserver>
 <ldapserver id="ldapserver">
 <hostname>ldap://ldap.forumsys.com</hostname>
 <base>dc=example,dc=com</base>
 <replicate>1</replicate>
 <update>1</update>
 <user>cn=read-only-admin,dc=example,dc=com</user>
 <pass>password</pass>
 <auth_by_bind>0</auth_by_bind>
 <anonymous_bind>0</anonymous_bind>
 <principal_name>uid=%s</principal_name>
 <mapping>
 <cardnumber is="potato"></cardnumber>
 <branchcode is="">CPL</branchcode>
 <categorycode is="">PT</categorycode>
 <surname is="uid"></surname>
 <userid is="uid"></userid>
 </mapping>
 </ldapserver>
Additional remarks concerning this example.
Instead of using ldap you better use ldaps.
We are using replicate = 0 cause we do not want to add users automatically to Koha, when they could successfully connect via LDAP auth. Then I suppose you also don't need the mapping.
And of course we use update = 0 cause we do not want to change anything within Koha, when LDAP properties are changing.
Category:Tips & Tricks
You can adjust the mappings - cardnumber was mapped to potato to ensure no value was received
On the Bywater page you can find this hint concerning the usage of LDAP auth in combination with allowing local Koha user accounts:
"If an LDAP user is found we then search for a corresponding Koha user and log them in if found. If the ldap lookup fails, or the credentials don't match, the username and password are then checked against the Koha database directly and the user is signed in if the credentials are valid"
The point is, that it makes a difference, if a user can be found in LDAP or if the LDAP auth fails. So take care on this and check if there are no users in your LDAP active directory having the same Koha username as a local Koha user has.
LetsEncrypt

Koha should have an option to use Let's Encrypt certificates out of the box. Bug 15303 is about that.
I don't want to flood the bug tracker with changing test plans and other information, so I will add some things here.
=Implemented=
* SSL-only Apache template
* mechanism to get a certificate automatically when doing koha-create
* HTTP to HTTPS forwarding
* --letsencrypt option for koha-list
=Not implemented=
* automatic renewal by Koha cron job
** May not be necessary until the code is in Koha
=Information for testers=
* if you can, do it on a "real" server in the web
* if that is not an option, you need to make port 80 in your VM accessible from the web for the test. Port forwarding and a network bridge in Virtualbox works for me, a host-only adapter+a NAT adapter won't
* you need "real"/global subdomains pointing to an IP that is that of your test server or is forwarded to it on port 80. That is where the webroot check of letsencrypt happens before they issue the certificate
* dyndns pointing to your IP should work
* for the staff client, /etc/hosts file with ip.of.your.vm <instancename>-intra.your.domain.tld on the machine you are browsing the test instance from should work for testing Not sure if this is valid anymore. use real subdomains.
* put the real (sub)domain that you want to use in koha-sites.conf before you create the instance. The default of mydns-something won't work
=Limitations=
There are rate limits. At the moment (09 April 2016, public beta), these are
* Rate limit on registrations per IP is currently 500 per 3 hours
* Rate limit on certificates per Domain is currently 20 per 7 days
Source
That could lead to problems when testing, but also when renewing certificates on servers with multiple instances! I planned to use a cron job to renew all instances found with koha-list --letsencrypt every 60 days (certs are valid for 90 days). With the current rate limits, that won't work with more than 20 instances using separate certs.
It got increased from 5 to 20 certs per 7 days, which should be fine for most use cases.
==Possible workarounds==
* Letsencrypt is working on a rate limit override request form, it's supposed to be available January 2016. Source
** More info needed
* Multi-domain certs are possible, with bug 15303 we already make use of that (one cert for OPAC + intranet)
** Using one cert for all instances in one installation would work, only one cert to renew every 90 days
*** SAN multi-domain certs have a limit of 100 domains atm (01/16) Source
** It may be possible to keep the current workflow and add an option to use koha-list --letsencrypt to get all relevant instances, issue a single cert for all of them and change the apache configs
*** Not going to be in bug 15303
=Windows XP=
Not that I care, but XP is supposed to be supported by the intermediate certificate now. https://community.letsencrypt.org/t/upcoming-intermediate-changes/13106
Category:Development
Category:Bugs
Libraries endpoint RFC

This RFC should be the basis for discussing the libraries endpoint. Work is being done in bug 16497
== Actions and routes ==
The following table presents the current implementation, and the proposed changes.
Description 	Action	Proposed path
List libraries 	GET 	/libraries
Add a library 	POST 	/libraries
Get a library 	GET 	/libraries/{library_id}
Overwrite a library 	PUT 	/libraries/{library_id}
Delete a library 	DELETE	/libraries/{library_id}
Partially update a library	PATCH 	/libraries/{library_id}
== Library object definition ==
DB schema 	tcohen 	Katrin
branchcode 	library_id 	library_id
branchname 	name 	name
branchaddress1 	address1 	address1
branchaddress2 	address2 	address2
branchaddress3 	address3 	address3
branchzip 	zip 	zip_code (match with patron api)
branchcity 	city 	city
branchstate 	state 	state
branchcountry 	country 	country
branchphone 	phone 	phone
branchfax 	fax 	fax
branchemail 	email 	email
branchreplyto 	reply_to 	reply_to_email
branchreturnpath	return_path	return_path_email
branchurl 	url 	url
issuing 	REMOVED 	Agree!
branchip 	ip 	ip
branchprinter 	REMOVED 	Agree!
branchnotes 	notes 	notes
opac_info 	 	
geolocation 	geolocation	geolocation
marcorgcode 	marcorgcode	marc_org_code
== Permissions ==
It is important to check what data is to be publicly available (for OPAC usage, for example) and which won't ('ip', for example). The attributes that are not intended for 'all users', should be marked required: false on the spec. The controllers should take care of getting rid of those attributes.
We could consider adding new metadata to the schema files, as is_boolean (for example is_public).
Category:RFCs
Libsysguy's Proposal for QAA 3.12

==Improving The Quality of Koha's Code==
Koha has grown quite a bit in the the last few years. As it continues to grow we face new issues and are able to create new solutions. Currently Koha's code base is quite large and reflects the history of a system in a period when many of the technologies it uses have changed rapidly. We need to improve the quality of our codebase to enable growth and encourage and enable contributions from new developers.
===Standards===
As it currently stands, we as a community have developed certain standards and paradigms that we try to adhere to when submitting code. As QAA I would do my best to make sure that these standards are followed through each patch that is passed. I would also do my best to make sure that these standards are well known to current and new developers through feedback about patches and answers to questions through the IRC.
==Testing==
The primary role of this position should be testing. The question I should ask myself every time I test a patch is "Does this break something the original sign-offer missed?". 
===The Personal Touch===
Each patch that is QA-ed should be installed and tested against the current working main branch. This includes adding additional workflows for QA-ers to be able to say "Yup, I checked this".
===Testing Plans===
Each patch should include a testing plan so that those who are not familiar with the area of Koha the patch deals with should still be able to test it. Yes, this does deal more with community members signing off, but it can also be helpful to QA team members as well. 
===Unit Tests===
Unit tests are now required for all new additions to C4 and Koha. I would like to make sure that all new submissions adhere to this standard set fourth.
===Automated testing===
After reading JCamins proposal for automated testing I think it is a great idea. This could be a great asset to Koha. I would like to start developing automated suite using WWW::Mechanize so that Koha users could run these test on development systems against their data. Inevitably, we will miss something in testing no matter how many layers of testing we have. This could alert them to any potential problems and allow us to expand our testing ability beyond just our QA team and RM.
==Documentation==
As a developer I often find writing documentation akin to having my fingernails pulled out. That being said it is a very important part of development, especially in a large project like Koha. I would like to work to develop POD templates for submitters to use. This would make documentation more uniform and give submitters a good place to start with documentation.
Linux Kiosk

== Building a Linux Web Kiosk (updated Feb 2014) ==
Using the Ubuntu Linux operating system, Opera browser, Ajenti browser-based system administration panel, and open source Sanickiosk plugins. 
To download a ready-to-install disk image visit sanickiosk.org.
== Steps ==
*Read the documentation online at sanickiosk.org.
*Install Ubuntu Server. 
*When installation is complete login and type:
 sudo su
 wget http://links.sanicki.com/kioskscript -O kioskscript.sh
 chmod +x kioskscript.sh
 ./kioskscript.sh
 
*Reboot and perform standard configuration steps from the documentation. 
*Customize and create an installable disk image according to the directions in the documentation.
----
View the script.
Live DVD Blueprint

==Koha Live DVD: a blue print==
 
===Operating system===
Xubuntu 12.04
Xubuntu give traditional desktop and lightweight suitable for new and old computers. We can limit the Live DVD size below 1 GB. 
Live DVD customisation tool	
===Remastersys===
http://www.remastersys.com/ubuntu.html
Very flexible tool, suitable to create clone of the system and can retain the Koha user settings and environment. Suitable for running in live mode and for installation.
===Koha version===
3.12.00 ??? Yet to be released
===Koha installation method===
Koha from Ubuntu packages
===Backup mechanism===
Either we can trust existing backup mechanism of Koha or make use other tools like automysqlbackup . Otherwise we can create a shell script to automate backup in every one hour. The location of backup place can be /home/koha/backup.
===Audience of the Live DVD===
For Koha newbies. Librarians, research scholars, LIS students and teachers.
===Extent of Koha customisation===
Customisation of Koha in certain extent is needed in Live DVD. It can give a friendly interface for Koha users. Post installation steps should complete in Live DVD. Following are the details of customisations:
# Some sample reports from Koha SQL Report Library
# On and off certain system preferences
# Addition of ACQ cataloguing framework
# Customisation of BKS Framework in cataloguing. Removal of unwanted fields and retaining commonly used MARC tags. See the screenshot. http://picpaste.com/customised-cataloguing-fields-pc9fiUbu.png
===Materials to be included in the DVD===
* Read me file
===Additional tools in Koha Live DVD===
#Koha Offline Circulation tool http://kylehall.info/index.php/projects/koha/koha-offline-circulation/
===Artwork===
* Koha wallpaper
==See also==
* Koha LiveCD (lite) alternative
* Koha-GSDL integration live CD
Category:Obsolete
Logger

== Logger ==
Koha will have a logging module (Koha::Utils::Logger).
Please have a look at Bug 8190 for more information.
=== How to choose your log level? ===
8 levels are available: debug, info, normal, warning, error, critical, alert, unusable.
==== debug ====
Debugging information used by developpers.
Example: Display a variable's value.
==== info ====
An information message.
Example: The user's operations, indexation of data, etc.
==== normal ====
A normal operation is reported.
It is something quite important.
==== warning ====
The application could have strange behaviours.
Example: A regexp fails, a syspref does not exist, data is corrupted, etc.
==== error ====
An user error occurred. Koha catch the error and does not crash but something is wrong.
Example: Bad field format, SQL error, bad right on a file, etc.
==== critical ====
Koha is broken. The interface still responds but the service is degradated.
Example: a field is missing in the DB but the application is usable.
==== alert ====
Koha is going to be unusable, an action must be taken immediately.
==== unusable ====
The application is unusable.
Example: an important module is not installed, an important field is missing in the DB, the connection to the DB fails, etc.
Category:Documentation
MARC frameworks

Here we can put links to user created MARC frameworks
=== MARC Frameworks ===
==== Article Framework ====
* Developer: Shelley Gurney & Milton Lee (NZICA)
* Purpose: Cataloguing individual articles within the collection (Special Libraries) 
* Status: Completed 
* File:Article_Framework.sql‎
==== RDA Framework ====
* Developer: Chris Cormack 
* Purpose: MARC21 framework containing the RDA fields (not proposed ones though) 
* Status: Completed
* Updated: June 2015, fixing bug 10550
* File:Export RDA 2015.csv.
* File:Export RDA - Alternative.csv A slightly modified RDA framework.
==== RDA Framework: Realia====
* Developer: Liz Dukelow & Michael Adamyk
* Purpose: Minimal Marc fields including those for RDA and controlled vocabularies
* Status: Completed
* File:Realia.MARC.RDA.2021.csv‎
====Acquisitions Framework====
* Developer: ByWater Solutions
* Purpose: Works in conjunction with the System Preference :UseAcqFrameworkforBiblioRecords
* Status: Completed 
* File:AcqFramework.csv
==== Fast Add Framework====
* Developer: ByWater Solutions
* Purpose: Minimal Marc fields necessary for a Fast Add
* Status: Completed 
* File:FastAddFramework.csv
Category:Documentation
Category:Library
MRenvoize/Accounts Schema

= Koha Accounts Rewrite - DB Schema =
My attempt at a normalised database design for an alternative accounts re-write
== ac_Journals ==
Records itemized journals of money owed/credited against actions in koha [Fines, Credits, Invoices]
* id
* created [datetime]
* updated [datetime]
* amount (+Credit/-Debit)
* offset (starts as inverse of amount, tends toward 0)
* type [fine, purchase, refund, credit, debit] - ( ? should this be in it’s own table ? )
* detail [?]
* note [?]
== ac_JournalTransactions ==
Records transactions, money changing hands, against journals. One journal may have multiple transactions recorded against it (partial payments); likewise, one transaction may bit split between multiple journals (bulk payments)
* journal [ac_journals.id]
* transaction [ac_transactions.id]
* amount [+/-]
== ac_Transactions ==
Records transactions, money changing hands.
* id
* amount [+/-]
* type [credit card, cheque, cash, online]
== ac_TillTransactions ==
Records the till and staff member operating it and associates it with a transaction.
* till [ac_tills.id]
* transaction [ac_transactions.id]
* staff [borrowers.id]
== ac_Tills ==
Records virtual till details
* id
* name
* description
== ac_BorrowerJournals ==
* borrower [borrowers.id]
* journal [journals.id]
== ac_ItemJournals ==
Records
* item [items.id]
* journal [journals.id]
== ac_Tax ==
Records tax band configuration
* id
* name
* rate
== ac_JournalsTax ==
Records the tax association of a journal
* journal [journals.id]
* tax [tax.id]
MRenvoize/Editing record.abs

Koha's record.abs is a complicated file to update.
It takes the form:
melm 245$a Title-cover:w,Title-cover:p,Title-cover:s,Title:w,Title:p,Title:s
melm 245$c Author,Author-in-order:w,Author-in-order:p,Author-in-order:s
melm 245$d Author,Author-in-order:w,Author-in-order:p,Author-in-order:s
melm 245$e Author,Author-in-order:w,Author-in-order:p,Author-in-order:s
melm 245$9 Cross-Reference:w,Koha-Auth-Number
melm 245 Title:w,Title:p
Lets identify the parts!
*melm 245$a -> This is the Marc Tag we are working with... more specific (i.e melm 245$a) should come above less specific (i.e melm 245) in the file.
*Title-cover -> This is the zebra index name the field should be indexed under. It should appear as a comma delimited list of Indexes for which you wish the element to appear within.
*:w -> This is the zebra index type associated with the index name you want your marc field to be indexed in. (:w = Word, :p = Phrase, :s = String, :n = Number, default = Phrase)
==Specifics==
Default rules: You can assign a 'default' rule for an entire Marc Tag (i.e. melm 245). However, the default is overridden by more specific rules!
===Example===
Lets go through the above example line by line (starting at the bottom first).
melm 245 Title:w,Title:p
Default Rule: All Subfields of Marc Tag 245 are added to the Title:w and Title:p Zebra Search Indexes.
melm 245$9 Cross-Reference:w,Koha-Auth-Number
Specific Rule: This overrides the default rule! It removes subfield $9 from Title:w and Title:p Zebra Search Indexes, and adds subfield $9 to Cross-Reference:w and Koha-Auth-Number Zebra Search Indexes instead!
melm 245$c Author,Author-in-order:w,Author-in-order:p,Author-in-order:s
melm 245$d Author,Author-in-order:w,Author-in-order:p,Author-in-order:s
melm 245$e Author,Author-in-order:w,Author-in-order:p,Author-in-order:s
Specific Rules: These rules override the default rule! They remove subfields $e, $d and $c from the Title:w and Title:p Zebra Search Indexes, and add them instead to Author, Author-in-order:w, Autohr-in-order:p and Author-in-order:s Zebra Search Indexes instead!
melm 245$a Title-cover:w,Title-cover:p,Title-cover:s,Title:w,Title:p,Title:s
Specific Rules: This rule overrides the default rule! It remove subfield $a from the Title:w and Title:p Zebra Search Indexes, and adds it instead to Title-cover:w,Title-cover:p,Title-cover:s,Title:w,Title:p and Title:s Zebra Search Indexes instead!
So what's the overall result of the above declarations:
Category:Zebra