nyuuzyou/wikis huggingface dataset:
Roles for 3.8

With the release of 3.6.0 scheduled for October 22 2011, its time to start thinking about roles for 3.8
Anyone who wants take on any of these roles is more than welcome to put their name next to one and perhaps link to their proposal. 
*Release Manager
** Paul Poulain Here is my proposal
*Translation Manager
** Frédéric Demians: I'd like to pursue in this role, but associated with an active Koha international contributor, like Katrin or Magnus. It would facilitate a smooth transition for a new translation manager for version 4. From my perspective, the priority for 3.8, will be to extract translation files (.po files) from Koha main git repository and push them into a 'koha-i18n' Git submodule. See the stats of my thinking on the subject in Git Splitting and Shrinking
*Documentation Manager
**Nicole C. Engard (I'll continue doing what I'm doing)
*Documentation of DB
**Nicole C. Engard (I'll continue doing what I'm doing)
*Bug Wranglers (the more the merrier, probably?)
** Katrin Fischer
** Magnus Enger: Sign off patches, close bugs, keep an eye out for duplicates, help organize Global bug squashing days, etc...
*QA Manager
** Ian Walls (continuing role from 3.6)
*Assistant QA Manager
** Marcel de Rooy: Sorry for adding this subcategory. QAM would be too much, but I'm willing to assist the QAM in checking signed patches in most of the Bugzilla categories.
** Jonathan Druart: I think I can help for this task. I am new in Koha but code quality is important for me. I already make QA at BibLibre
*Specific Module maintainers
*Release Maintainer
*Packaging Manager
** Mason James, i would be keen to help with packaging tasks
** Robin Sheat: officially doing the role I've been informally doing already :)
*Bus Driver 
**Brooke (I feel like an usurper, so I want some official backing for what I've informally been doing, like Robin.)
Category:Release_Management
Category:3.8
RoomBookingRFC

= Features wishlist =
* Ability to set times when a bookable can be booked
* Ability to set maximum amount of time for a booking per person (e.g. a room can only be booked for 3 hours maximum per person)
* Ability to set maximum number of days ahead of booking date a booking can be submitted (e.g. can only book a room up to 7 days ahead of time)
= Tables =
== Bookable Types - Room, Projector, Computer, Etc ==
*id 
*name
== Bookables - Concrete Examples of Reservable Types ==
*id 
*name 
*type
== Bookable By - Specify patron categories ( or supercategories ) that can reserve this type/bookable ==
*id 
*categorycode 
*category type 
*reservable_id
== Bookings ==
*id 
*booked_from - date/time 
*booked_to - date/time 
*booking_id 
*borrowernumber
Feature will be implemented as a pure REST interface endpoint, with the front end being Javascript based ( most likely React or Polymer )
Category:RFCs
SMS for recalls

Implement SMS notifications for recalls, sponsored by Toi Ohomai Institute of Technology.
=== Getting started ===
We need two borrowers - Borrower A and Borrower B.
Ensure the SMSSendDriver and EnhancedMessagingPreferences system preferences are set.
=== Test plan ===
#Edit the messaging preferences of both borrowers. Tick the SMS box for both recalls notices (Recall awaiting pickup and 'Return recalled item').
#Make sure that both borrowers have an SMS number (does not have to be an accurate mobile number, but make sure this field is filled!)
#Get the barcode of an Item (Item A) and check this out to Borrower A.
#Login to the OPAC as Borrower B.
#Go to the detail page for Item A.
#Place and confirm a recall for Item A.
#Check the Notices tab for Borrower A in the Staff Intranet. You should see the 'Return recalled item' notice in this table, with the type sms.
#Check in Item A and confirm recall waiting.
#Check the Notices tab for Borrower B. You should see the 'Recall awaiting pickup' notice in this table, with the type sms.
=== Other links ===
Go back to main recalls page
Sample novel record/

Category:Resources
Category:Tips_&_Tricks
Category:Documentation
Category:Shared_resources
Training_resources#Cataloging
== Sample book record, MARC21, novel in a series ==
This record in SF Maritime NHP's Koha catalog.
This record on WorldCat.org.
=== Plain MARC21 version of record: ===
000 01250cam a2200337 a 4500
001 ocm37770195 
003 OCoLC
005 20190703084733.0
008 971002s1998 nyub 000 1 eng 
010 _ _ ‡a 97032216 
040 _ _ ‡aDLC‡cDLC‡dFIT‡dUDU
020 _ _ ‡a0553103245
050 0 0 ‡aPS3558.O33636‡bS55 1998
082 0 0 ‡a813/.54‡221
090 _ _ ‡aPS3558.O33636‡bL58 v.1
049 _ _ ‡aUDUA
100 1 _ ‡aHobb, Robin.‡93668
245 1 0 ‡aShip of magic /‡cRobin Hobb.
264 _ 1 ‡aNew York :‡bBantam Books,‡c[1998].
264 _ 4 ‡c©1998.
300 _ _ ‡axiv, 685 p. :‡bmaps ;‡c24 cm.
490 1 _ ‡aThe liveship traders ;‡vbk. I
520 _ _ ‡aThe heroine is a living ship which has feelings 
and can talk. On the death of her master she is inherited 
by a conniving man who wants to use her for transporting 
slaves. The ship is against this and forms an alliance with 
the man's sister-in-law who had hoped to inherit it and 
now plots to get it.
650 _ 0 ‡aWomen sailors‡vFiction.
650 _ 0 ‡aCargo ships‡vFiction.
650 _ 0 ‡aSeafaring life‡vFiction.
650 _ 0 ‡aPirates‡vFiction.
650 _ 0 ‡aSlavery‡vFiction.
655 _ 7 ‡aFantasy fiction.‡2lcsh
800 1 _ ‡aHobb, Robin.‡tLiveship traders ;‡vbk. 1.‡93669
994 _ _ ‡aX0‡bUDU
999 _ _ ‡c13081‡d13081
945 _ _ ‡c1‡dHeather Hernandez
Sample serial record/

Category:Resources
Category:Tips_&_Tricks
Category:Documentation
Category:Shared_resources
Training_resources#Cataloging
== Sample serial record, MARC21 ==
This record in SF Maritime NHP's Koha catalog.
This record on WorldCat.org.
=== Plain MARC21 version of record: ===
000 01883cas a2200493 i 4500
001 ocm56019231 
003 OCoLC
005 20190611142933.0
008 040726c20049999ncuqr p 0 a0eng c
010 _ _ ‡a 2004213210
040 _ _ ‡aNSD‡beng‡erda‡cNSD‡dDLC‡dTXA‡dPAU‡dOCLCQ‡dINU‡dUBY‡dOCLCF‡dHLS‡dCOD‡dHLS‡dOCLCO‡dNDD‡dZCU‡dOCLCQ‡dUDU
012 _ _ ‡k1‡l1‡m0
022 0 _ ‡a1551-5001‡l1551-5001‡21
035 _ _ ‡a(OCoLC)56019231
037 _ _ ‡bOP Media, LLC, 1315 8th St., Eureka, CA 95501
042 _ _ ‡apcc‡ansdp
050 0 0 ‡aZ284‡b.O7
082 1 0 ‡a002.075‡213
090 _ _ ‡aZ284‡b.O7
049 _ _ ‡aUDUA
222 _ 0 ‡aFine books & collections
245 0 0 ‡aFine books & collections.
246 3 _ ‡aFine books and collections
264 _ 1 ‡32004-2009 :‡aEureka, Calif. :‡bOP Media
264 3 1 ‡32010- :‡aDurham, NC :‡bJournalistic, Inc.
300 _ _ ‡avolumes :‡billustrations (some color) ;‡c28 cm.
310 _ _ ‡aQuarterly,‡b<2010->
321 _ _ ‡aBimonthly,‡b2004-
336 _ _ ‡atext‡btxt‡2rdacontent
337 _ _ ‡aunmediated‡bn‡2rdamedia
338 _ _ ‡avolume‡bnc‡2rdacarrier
362 1 _ ‡aBegan with v. 2, no. 5 (Sept./Oct. 2004).
515 _ _ ‡aIssues for Vol. 2, no. 5 (Sept./Oct. 2004)-v. 6, no. 6 (Nov./Dec. 2008) also carry whole numbering, no. 11-36.
515 _ _ ‡aIssues for 2009 only published electronically.
515 _ _ ‡aSpecial issue 47 (winter 2010) also published.
515 _ _ ‡aIssues for <autumn 2010-> are called <issue 8.3->
588 _ _ ‡aDescription based on: Vol. 2, no. 5 (Sept./Oct. 2004)
588 _ _ ‡aLatest issue consulted: Issue 16.2 (spring 2018).
590 _ _ ‡aResearch Center has only selected issues.
650 _ 0 ‡aBook industries and trade‡vPeriodicals.
650 _ 0 ‡aBook collecting‡vPeriodicals.
780 0 0 ‡tOP (Eureka, Calif.)‡x1542-9962‡w(DLC) 2002214989‡w(OCoLC)51273042
994 _ _ ‡aC0‡bUDU
999 _ _ ‡c41598‡d41598
Sass lint rules

Koha now has a default Sass lint configuration file, .sass-lint.yml, which can be used when working with staff client SCSS. The file contains a set of rules which can be used by various tools to lint SCSS with sass-lint. Some default rules have been defined, including the following notable rules:
* attribute-quotes - Attribute values should be quoted
* empty-line-between-blocks - There should be a blank line between nested blocks
* force-attribute-nesting - Require that attributes be nested
* force-element-nesting - Require that elements be nested
* force-pseudo-nesting - Require that pseudo elements/classes be nested
* leading-zero - Disallow a leading zero on decimal numbers
* no-color-keywords - Require that colors be delcared using hexadecimal
* no-duplicate-properties - No duplicate properties within the same block
* no-important - Forbid the use of !important
* no-mergeable-selectors - Forbid duplicate selectors
* no-url-domains - Forbid urls containing domain names
* no-vendor-prefixes - Forbid the use of vendor prefixes
* one-declaration-per-line - Each declaration should appear on its own line
* single-line-per-selector Each selector should appear on its own line
* space-after-colon - There should be a single space after a colon
* space-after-comma - There should be a single space after a comma
* space-before-brace - There should be a space before an opening curly brace
* space-before-colon - There must not be a space before a colon
* trailing-semicolon - All declarations should end in a semicolon
* url-quotes - URLs should be quoted
* zero-unit - Values of 0 for length should be unitless
Category:Coding_guides
Scratch:Playground

my $foo = $#{ $bar };
páginas en españo
אני יכול לאכול זכוכית וזה לא מזיק ל
Կրնամ ապակի ուտել և ինծի անհանգիստ չըներ։ 
Կրնամ ապակի ուտել և ինծի անհանգիստ չըներ։ მინას ვჭამ და არა მტკივა. 
.من می توانم بدونِ احساس درد شيشه بخور
SearchEngine Layer RFC

== Developpment documentation ==
=== References ===
* Just a kanban to show the work and features in progress https://trello.com/board/koha-searchengine-solr/4f66f7f3dda1266d4f5e408e
* Schema items organisation https://docs.google.com/a/biblibre.com/drawings/d/1ZdsQsoThYgIVSgH3LqgRZy17xm9X7XkLT6RG3fDYCzs/edit 
=== Installation ===
New clean page in progress
=== Features ===
* https://trello.com/board/koha-searchengine-solr/4f66f7f3dda1266d4f5e408e
* Works:
** record your configuration in a yaml file via interface (indexes.pl)
** index records (easiest way)
** opac simple search
** display facets
=== Code files ===
Koha
├──...
├── SearchEngine
│   ├── Config.pm
│   ├── ConfigRole.pm
│   ├── FacetsBuilder.pm
│   ├── FacetsBuilderRole.pm
│   ├── Index.pm
│   ├── IndexRole.pm
│   ├── QueryBuilder.pm
│   ├── QueryBuilderRole.pm
│   ├── Search.pm
│   ├── SearchRole.pm
│   ├── Solr
│   │   ├── Config.pm
│   │   ├── FacetsBuilder.pm
│   │   ├── Index.pm
│   │   ├── QueryBuilder.pm
│   │   └── Search.pm
│   ├── Solr.pm
│   ├── Zebra
│   │   ├── QueryBuilder.pm
│   │   └── Search.pm
│   └── Zebra.pm
├── SearchEngine.pm
* Work on Zebra https://github.com/xercode/Data-SearchEngine-Zebra
Category:RFCs
Search Koha with a Google Android phone

# Install Barcode Reader app from the Android store ($0)
# Open the app and go Menu > Settings.
# In 'Custom product search URL' and enter http://<your server>/cgi-bin/koha/opac-search.pl?idx=nb&q=%s
# OK and exit.
# Scan an item with an ISBN barcode.
# Enjoy.
by Mark Osborne mosborne@ashs.school.nz
The same with screenshots on : http://www.biblibre.com/fr/blog/billet/koha-sur-android
and http://www.biblibre.com/en/blog/entry/koha-on-android
Category:Tips_&_Tricks
Category:Documentation
Category:Tips_&_Tricks
Category:Documentation
Search authorities using keywords from same menu as keyword search RFC

Can consideration please be given to-
# adding a system preference to enable authorities to be searched by patrons using the same drop down list as for keyword searches as opposed to the separate authorities search box. An option to make the separate authorities search box available for patrons to search should be retained.
=> (paul_p) this will be a part of our Solr development (that we should submit in a few months)
# adding a system preference to allow authority records to come up in results to help patrons find what they are looking for. A “more information” link or picture could appear next to the record instead of the usual “item type” picture so patrons can click on it to get further information using the authority record.
=> (paul_p) this will be a part of our Solr development (that we should submit in a few months)
Thomas Mizanowski (t_mizanowski AT yahoo.com.au)
Category:RFCs
Category:MARC_Authority_data_support_RFCs
Category:Searching_RFCs
Category:RFCs_not_targeted_at_a_particular_Koha_version
Searching Group Meeting 2005-06-02

====== Searching Group Agenda for 2005, June 21 ======
Meeting notes for this meeting
Chris's concerns (from his blog):
Currently the search works well, in that its functionally correct and returns correct and complete results.
the main points ill be making are
* We have 2 audiences, the librarians and the public
* Most important, we return correct results, speed comes a close second
* The public do not care (for the most part) why/how the results are derived, just as long as they are right
* Innovative tools will win us a little fame
I cant stress the correct results enough, its very frustrating to search for an item, see that its on the shelf then find it isnt.
I agree that our goal is 1. accuracy and 2. speed. As I mentioned recently to a French audience, Koha's search results are currently 'correct and complete' for small collections. But when you have 150K records and a search returns an un-sorted list of (say) 5,000 items that match your search that's just not a feasable system. So in this case, NPL actually has a sorting routine for just such a condition (using current MARC setup) however, the overhead for performing it makes searches that large return results in 1-3 minutes. So for larger collections speed and accuracy are closely related. -- Joshua
===== 1. Zebra =====
* Zebra is an indexing and search retrieval back end
* It indexes many formats including native MARC21 and UNIMARC
* The retrieval engine is a fully standards-complaint Z39.50 Server
* Z39.50 is not the _latest_ technology for searching ... but :
* Zebra when combined with yaz-proxy (http://www.indexdata.dk/yazproxy) can convert CQL to RPN queries (Z39.50 default query type)
So our questions are:
* is CQL (Common Query Language) the way to go?
 http://www.loc.gov/z3950/agency/zing/cql/
* should it replace marc tables in Koha?
===== 2. opensearch =====
* http://opensearch.a9.com
* http://dilettantes.blogspot.com/2005/06/gussying-up-opensearch.html
* http://liblime.com/opensearchportal.html
So with some additional elements added opensearch could be the ultimate federated searching engine. Mike and I have also found a way to pass CQL queries through opensearch (though that's not in the original spec).
===== Other References: =====
If you're new to Koha you may find these references useful in evaluating these topics.
 
* Demos with 150K Records:
 Current OPAC: http://search.athenscounty.lib.oh.us
 Plucene demo: http://search.athenscounty.lib.oh.us/cgi-bin/koha/plucene/search.cgi?query=stephenson
 marc_words demo:
 mysqlfulltext demo:
 Zebra: http://liblime.com/zap/advanced.html
Category:IRC_Meetings
Security Mailing List Proposal

- Background
* An individual has started combing the Koha code for SQL injections and reporting them to us
* Had asked how to report, was told (for lack of better alternative) to email current and past RMs, RMaints, and QAMs
- Proposal: We publish a way to report security bugs
* preference to simply use Bugzilla
* issues judged by the reporter to be more sensitve to be sent to a mailing list
- Mailing list
* form a new mailing list to be called koha-security
* initial membership to be RMs, RMaints, QAMs, past, present, and future
* other interested devs can join on request
* focus is on timely response to security issues, not abrogating the scope of koha-devel
* publicly archived, but with a delay of six months to allow fixes to be made before exploits are published
* preference is to have discussion on koha-devel; security list meant for fast response and discussion of sensitive issues that would threaten library catalogs if an exploit got published prematurely
* concurrent with starting koha-security, closing the old koha-manage list
- Security advisories
* Get registered for CVEs?
- Start a position of Security Manager?
Selective dissemination of information

= Selective dissemination of information =
This is how it will work:
1. Staff setup SDI topics or profiles
2. Patrons subscribe to one or more SDI profiles
3. Emails with brief information on new material sent to subscribed patrons
== SDI profile ==
Library staff will be able to setup SDI profiles. Each profile will include a search expression and limits similar to what is available on the advanced search page
== Subscribing to Topics ==
Patrons will to subscribe to one or more SDI profiles. Library staff will also be able to subscribe to SDI profiles on patrons' behalf.
== Generating/Sending Emails == 
A batch process will generate content for each profile - essentially a list of new items matching the search expression for that profile - and dispatch the content to subscribed patrons via email. A system preference will control the frequency (daily, weekly, monthly) of generation and dispatch of emails.
Category:RFCs
Category:Notices_RFCs
Category:RFCs_not_targeted_at_a_particular_Koha_version
Sending a "request to pull"

Sometimes your patches are a bit too unwieldy to be sent to the koha-patches mailing list in the usual way. What you can do then is push the changes to a publicly available git repository (for example GitHub, another similar service or a repository that you host yourself), and send a "request to pull" to koha-patches. 
To do this, make sure you have pushed your changes to the public repo, and that you are on the branch that contains your changes. Then do this: 
 $git request-pull origin/main git://git.workbuffer.org/git/koha.git | mailx koha-patches@....org -s “Bug 1234 - Request to pull”
Where:
* origin/main is the name for the main branch of the official repo, so if you called that something other than origin you must change accordingly
* git://git.workbuffer.org/git/koha.git is the address for your publicly available repository
* koha-patches@....org is the address of the koha-patches mailing list
This will only work if you have mailx and sending of emails set up correctly on your machine. If you do not, you can run this part of the command: 
 $git request-pull origin/main git://git.workbuffer.org/git/koha.git
and copy/paste the output into an ordinary email in the email program of your choice, give it a proper subject and send it to koha-patches.
==See also==
* git-request-pull(1) Manual Page
Category:Git
Serials routines need major refactor

Routines for handling serials are showing their age. In 3.4 the serials management package needs a thorough update. There probably need to be some db changes too. This should also allow us to address some functional improvements that users are raising: Better integration of acquisitions, better reporting possibilities, improvements to claims handling. A good test suite to test such fun things as serials predictions.
Something has already been done by Colin Campbell see his serials-mods branch
Category:RFCs
Category:Serials_RFCs
Category:RFCs_not_targeted_at_a_particular_Koha_version
Set an email alias for Koha patches

With the recent move of the Koha mailing lists to http://lists.koha-community.org/, the full email address for submitting a patch is now koha-patches@lists.koha-community.org. Since that’s a bit long to type every time you submit a patch, here’s one way to save a few keystrokes.
First, create a text file file to define a short alias for the email address. I chose to call the file ~/.git_aliases. The file should contain a line like this:
 alias kpatches koha-patches@lists.koha-community.org
Next, tell Git that you want to use this address book file:
 $ git config --global sendemail.aliasesfile ~/.git_aliases
 $ git config --global sendemail.aliasfiletype mutt
Now, all you have to do is use kpatches in place of the full address. For example:
 $ git send-email 0001-bug-4801-fix-paging-in-display-of-staged-bibs-and-im.patch
 
 Who should the emails appear to be from? [Galen Charlton ]
 
 Who should the emails be sent to? kpatches
or
 $ git send-email -to kpatches 0001-bug-4801-fix-paging-in-display-of-staged-bibs-and-im.patch
* Written by Galen Charlton
Category:Git
Category:Documentation
Setting up Koha SIP and 3M machines

First, follow Koha SIP2 server setup
== Changes made to the 3M Self Check Machines to work with Koha. ==
From an email from Susan Mustafa and based on http://lclpioneer.wordpress.com/2011/05/02/getting-a-3m-self-check-to-work-with-koha/ (dead link)
 
 1. Login to 3M Self Check System Administration web page. 
 2. Select the network menu 
 3. Scroll down to Host Communications and change 
 1. Communication Type Telnet 
 2. TCP Port 8041 
 3. Host Name or IP 75.101.142.135 (This is the test SIP server IP) 
 4. Scroll down to the 3M Command Center (CIMS) and click Save Changes 
 5. Scroll down to Send/Expect Scripts and click Edit Login Send/Expect 
 
 
(in 2 and 3 below replace sipuserid with your SIP USER ID and sipuserpassword 
with your SIP USER PASSWORD , see below) 
 
No double quotes -- 
 
 1. Click Menu+ 
 1. Send String (leave blank) 
 2. Expect String login: 
 3. Timeout 30 
 4. Retries 3 
 5. Click Add 
 2. Click Menu+ 
 1. Send String sipuserid\r 
 2. Expect String password: 
 3. Timeout 30 
 4. Retries 3 
 5. Click Add 
 3. Click Menu+ 
 1. Send String sipuserpassword\r 
 2. Expect String Login OK. Initiating SIP (note 2 spaces after OK. ) 
 3. Timeout 30
 4. Retries (or 3 works as well) 
 5. Click Add
Category:Circulation
Setting up Z39.50 Servers for Urdu MARC records in Koha 3.x

Setting up Z39.50 Servers for Urdu MARC records in Koha 3.x for two main MARC repositories, [National Library of Pakistan] (NLP) and [Lahore University of Management Science] (LUMS) with a step-by-step guide using screen-shots can be found at LISolutions's Official Website at the following link:
[http://lisolutions.org/2011/01/11/z3950-nlp-lums/]
Category:Tips_&_Tricks
Shelf Map RFC

This is not a concrete project yet, more an attempt to gather some ideas. 
==OPAC==
===opac-detail.pl===
* Show a link to the shelf map for each item, in the form of a link/button/icon next to the call number
===opac-shelfmap.pl - new script===
* Textual description of where the item is located
* img-tag to show the actual map
===opac-image.pl===
* Extend this script to take a new parameter shelfmap, with the ID of a shelf map as its value
* This will fetch the image from where it is cached and return it as an image to the browser
==Intranet==
Don't use the shelf maps in the staff interface for the first iteration.
===Sysprefs===
* New syspref for activating shelfmaps
===Permissions===
* New permission for editing shelfmaps
* Users with the permissions should only see and edit shelfmaps for their own library
* Superlibrarian should be able to see and edit all shelfmaps
===Tools > Shelfmaps===
* Maps
** Add
** Edit
** Delete
* Markers
** Add
** Edit
** Delete
==Call number schemes==
Anyone who hangs out in the IRC channel will be familiar with "@quote 123"...
* Start simple, add more schemes over time. 
* Dewey-number + letters seems like a good place to start? 
** E.g.: 575.01 Dar
==How should the maps be generated?==
Choose one to begin with, maybe add more later if needed.
===Compound image on the fly===
* Take the map of the library and add the marker to it, to generate a new image. 
* Caching
===JavaScript for placing markers, a la Google Maps===
* Are there Free software packages that can do this? 
===HTML5 Canvas===
* A bit too early, perhaps? 
===Flash===
* Don't think so. 
==API==
What information can we use to determine the location on a map? 
See Holdings data fields (9xx) for available item fields. 
===MARC21 and NORMARC===
* 952$b - branchcode (holdingbranch) 
* 952$j - Shelving control number
* 952$o -	Koha full call number
* 952$y - Koha item type?
* 952$8 - Collection code
===UNIMARC===
* ?
== Examples in the wild ==
* From the Catalog to the Book on the Shelf: Building a Mapping Application for Vufind journal.code4lib.org/articles/6924 
*BIBMAP (Germany) 
*BIBSYS (Norway): Record - Map (Implemented in PHP by User:Magnus some years ago - source code available here. The BIBSYS shelfmap "protocol" is described in Norwegian here.)
Category:OPAC_RFCs Category:RFCs_not_targeted_at_a_particular_Koha_version Category:Submitted_RFC